CAPEX (Capital Expenditure) Project Budget 

In my experience, the CAPEX/OPEX decision for project funding is not made by the project manager but by the CFO and his staff, who set the parameters and have to defend the arguments for activating assets and spending. I found one company seeing SW development as OPEX, another as CAPEX.

For PMs, I found no big difference for projects completed in the financial year. It gets interesting when you have multiyear budgets. And it has an impact on the ROI calculation, and also here, Finance has a say.

Excellent question, Maria Hrabikova
A critical topic for capital-intensive projects, especially when it comes to project selection and prioritization based on well-structured business cases.

A recurring lesson when developing CAPEX budgets is the importance of aligning financial planning with the asset’s lifecycle value, not just its initial acquisition cost.
This principle is at the heart of any robust and transparent business case.

Here are some practical insights with direct implications for business case formulation and evaluation:
- Involve operations early
When the business case integrates input from engineering, maintenance, finance, operations, and end-users, it gains realism and avoids downstream surprises.
Decisions made in silos often lead to misalignment between cost, functionality, and actual delivered value.
- Bridge organizational silos
In some organizations, CAPEX decisions are handled exclusively by Finance, with limited input from project, technical, or operational teams.
This siloed approach may optimize for accounting compliance but often neglects usability, integration challenges, and long-term performance.
A strong business case requires a shared understanding of value, with Finance acting not just as a gatekeeper, but as a strategic partner in delivering outcomes.
- Don’t underestimate commissioning and ramp-up
Phases such as installation, training, system integration, or temporary operational redundancy are often underestimated.
A complete business case should anticipate transition and maturity costs, not just pure CAPEX.
- Incorporate Total Cost of Ownership (TCO)
Comparing alternatives in a business case should go beyond initial investment. Evaluating the TCO (including maintenance, energy consumption, upgrades, obsolescence, and decommissioning) supports the selection of more sustainable, high-return options over the long term.
- Establish structured governance and stage validation
Strong business cases should go through structured reviews (stage-gates or investment committees), ensuring that each phase (preliminary study, estimate, detailed analysis, final approval) revalidates assumptions, risks, and updated decision criteria, especially in volatile contexts.
- Connect to strategy and the project portfolio
Beyond being a financial document, the CAPEX business case must clearly articulate how the investment supports the organization’s strategic objectives and how it fits within the overall project portfolio (expected benefits, urgency, interdependencies, cross-cutting risks).
- Include benefit realization mechanisms
A sound CAPEX business case should not end at approval. It must also outline how benefits will be tracked and realized post-implementation - whether through improved productivity, cost reduction, risk mitigation, or customer impact.
This reinforces accountability and ensures the investment delivers on its intended purpose.

In summary, the CAPEX budget is just one piece of the puzzle.
Real value emerges when the investment is selected based on a comprehensive, participatory, strategically aligned business case focused on real long-term value.