Every company says it allocates capital strategically. Almost none of them can show you how.
Ask a CFO how their last ten capex projects were compared against each other, and you’ll usually get a story about business cases, not a framework. Project A had a strong ROI. Project B was “strategically important.” Project C got funded because the plant manager who requested it doesn’t ask for much. None of those are wrong reasons on their own. Together, they’re not a capital allocation process. They’re a collection of individual decisions that happened to get made in the same year.
That distinction matters more than it sounds. Capital allocation isn’t a finance function. It’s a strategy function that happens to run through finance.
Why most capex evaluation isn’t really capital allocation
The standard approach looks something like this: a business unit submits a request, finance checks the numbers, someone senior signs off. Repeat for every project, every quarter.
The problem isn’t any single step. It’s that each project gets judged in isolation. A positive NPV tells you a project clears the bar. It doesn’t tell you whether that project deserves capital more than the fifteen others also clearing the bar this quarter. Most organisations can justify almost every request that lands on their desk. The scarce resource was never good ideas. It’s capital, and the discipline to say no to some of them.
Real capital allocation starts one step earlier than approval: building a single view of everything competing for the same budget, so trade-offs are visible before money moves.
A framework that actually holds up
1. One portfolio, not a stack of business cases. If capex requests live in separate spreadsheets, separate meetings, and separate approval chains, you can’t compare them. You can only approve or reject them individually. Bring every active and proposed project into one place, evaluated on the same assumptions, before any capital gets committed.
2. Rank against strategy, not just ROI. Financial return matters, but it’s not the only currency. A project with a modest return that protects a critical customer relationship or removes a safety risk can outrank a higher-IRR project that just happens to be optional. The framework needs room for both.
3. Decide what to fund, delay, resize, or stop, as a set. This is the step most companies skip. Capital allocation isn’t a yes/no filter applied project by project. It’s a portfolio decision: given everything on the table, what’s the combination that gets funded this year, and what gets pushed, trimmed, or cut?
4. Revisit the allocation, not just the individual project. Markets shift. A project approved in January can look different by September. Good capital allocation treats the portfolio as something to rebalance, not a decision made once and filed away.
What good capital allocation actually changes
Companies that do this well aren’t necessarily investing more. They’re investing in a different mix. They fund fewer projects, more deliberately, with clearer accountability for the outcome. That shows up less in any single project’s return and more in the average return across the whole portfolio over several years.
It also changes the conversation in the room. Instead of “should we approve this project,” the question becomes “is this the best use of the capital we have left”. That is a harder question, and the right one.
Where this connects to the rest of your capex process
A capital allocation framework only works if it’s connected to what happens before and after it. The capex strategy sets the priorities the framework ranks projects against. Without it, “strategic value” is just an opinion in a meeting. And once priorities are set, capital budgeting is where the portfolio view actually gets built and maintained, rather than reconstructed from scratch every planning cycle.
See how Weissr helps
Weissr Capex Strategy
See how Weissr sets the priorities a capital allocation framework ranks projects against.
