That all makes sense, and definitively feels like the right way to go about it. The issue I’ve seen in the past is having to operate in environments where that level of maturity is not present in terms of planning and prioritization - to the point of people actively ducking these conversations as you said! That means that even having that local level of understanding of future and current resourcing needs doesn’t sit well alongside the approach used by the wider business. For my situation at least, right now a simple heuristic like the hiring ratio - or something I tried to do at a previous role which was basically have the cloud/platform team be funded out of a share of the cloud spend - is easily digestible and understandable by peers and others who influence the budget-setting process. As the business evolves or if I end up somewhere with more rigorous practices, I would definitely look to adopt your more useful approach.