Building Commercial Acumen: The Budget Skills That Separate Mid from Senior PMs
2 August 2026 2 min read
Most mid-level PMs can track a budget against a spreadsheet competently. What separates senior PMs isn’t tracking the numbers more accurately — it’s understanding what those numbers actually mean for the business, and being able to talk about trade-offs in those terms.
Know the difference between cost, value, and ROI
A mid-level PM reports “we’re £20k under budget this quarter.” A senior PM can explain whether that’s actually good news — maybe it means a workstream is under-resourced and at risk of slipping, not that the project is efficient. Understanding cost (what you’re spending), value (what the business gets from that spend), and return on investment (whether the value justifies the cost, over what timeframe) as three separate, related questions is a genuine skill gap between levels, not just terminology.
Learn to read — and challenge — a business case
If you’ve never built a business case yourself, start by critically reading ones that have already been approved at your organisation. What assumptions did they make about benefit realisation? What happened to the actual numbers versus the projected ones once the project delivered? Understanding where business cases tend to be optimistic (almost always on benefit timing, less often on raw cost) makes you a more credible voice when you’re building or defending your own. See building a PMO business case your board will approve for the structure senior stakeholders actually respond to.
Get comfortable with the language finance teams use
Terms like capex versus opex, amortisation, and payback period aren’t decoration — they’re the actual language a finance director or board uses to evaluate whether your project deserves continued funding. You don’t need a finance qualification, but knowing enough to hold a real conversation with your finance business partner, rather than nodding along, changes how seriously your projections get taken.
Practise translating technical or delivery risk into commercial terms
“There’s a risk the API integration slips by three weeks” is a delivery statement. “A three-week slip pushes our go-live past the Q3 renewal deadline, risking a £40k contract penalty” is the same risk in commercial terms — and it’s the version that gets a senior stakeholder’s attention and unlocks a decision, rather than a shrug.
This is a skill you build by doing it badly a few times first
Nobody starts fluent in this. Volunteer to help build or present the commercial case on your next project, even if it’s uncomfortable the first time — this is a skill built through repeated, slightly awkward practice, not through reading about it once.