Most transformation portfolios are not short of money.
They are short of financial discipline.
The problem is simple. Many organizations approve funding for projects, measure delivery against scope and schedule, then declare success when the system goes live.
That is not value creation.
That is activity completion.
If your funding model rewards teams for finishing on time rather than delivering measurable business results, you are financing motion, not outcomes.
CFOs, CIOs and portfolio leaders need to change the question.
Stop asking:
“Did the project stay within budget?”
Start asking:
“What business outcome did this investment create, and should we fund the next increment?”
This is the shift from project-based budgeting to outcome-based funding.
Projects end. Outcomes do not.
A project has a start date, an end date, a scope baseline and a budget.
That model works for a warehouse build, a network installation or a tightly bounded infrastructure migration.
It becomes unreliable when applied to modern enterprise transformation.
ERP modernization, customer platforms, workflow automation, data products and AI capabilities do not create value at go-live. They create value when people adopt them, processes change and measurable business performance improves.
Yet many organizations still fund them as temporary projects.
The result is predictable:
- Teams optimize for completing the approved scope.
- Business owners assume benefits will appear later.
- Adoption becomes someone else’s problem.
- Benefits are measured after the money is gone.
- Underperforming initiatives continue because stopping them feels like failure.
This is the Execution Gap: the distance between strategy, technology, execution, adoption and business outcome.
A programme can be green on cost and schedule while delivering little operational value.
That is not a paradox. It is a governance failure.
Research cited by Harvard Business Review has found that executives believe their organizations execute strategy effectively less than one-third of the time. The issue is rarely a lack of strategy. It is the failure to connect investment decisions to delivery and measurable results.
The funding unit must change
Project-based budgeting funds a temporary initiative.
Outcome-based funding funds an enduring business capability or value stream.
That distinction matters.
Under the traditional model, a business unit submits a project business case. Finance approves a budget. A delivery team is assembled. The team delivers the agreed scope. The project closes.
Under an outcome-based model, the organization funds a capability aligned to a defined result. The team remains accountable for improving that result over time. Funding continues only when evidence supports continuation.
For example:
| Traditional project measure | Outcome-based measure |
|---|---|
| Delivered within budget | Reduced cost per transaction |
| Completed on schedule | Increased customer adoption |
| Requirements delivered | Reduced case-processing time |
| System deployed | Improved straight-through processing |
| Training completed | Sustained active usage |
| Project closed | Benefits realized and owned |
The project may still exist as a delivery mechanism.
It is simply no longer the primary unit of value.
Lean budgeting approaches make a similar shift by allocating budgets to value streams rather than individual projects, while maintaining financial guardrails. Planview’s overview of lean budgeting describes this as a move toward continuous measurement, incremental funding and strategic alignment.
The principle is straightforward:
Fund the capability that creates value. Do not fund a temporary activity and hope value follows.
What CFOs should demand from every business case
An outcome-based funding model does not mean abandoning control.
It means improving control.
Every investment case should contain five elements.
1. A defined business outcome
“Modernize the platform” is not an outcome.
“Reduce invoice-processing cost by 25% within 12 months” is an outcome.
“Improve claims settlement time from 14 days to five days” is an outcome.
“Reach 70% active adoption among priority users within six months” is an outcome.
The outcome must be specific enough to measure and important enough to influence funding.
2. A baseline
Without a baseline, benefits claims are opinions.
Before approving funding, record the current state:
- Current processing time
- Current cost per transaction
- Current error rate
- Current adoption level
- Current revenue leakage
- Current compliance exposure
- Current customer or employee satisfaction
The baseline turns a promise into a testable hypothesis.
3. A named business owner
Technology teams can deliver a platform.
They cannot own every business benefit.
The accountable owner should sit in the business function that receives the value. That person must have authority to change processes, assign operational resources and enforce adoption.
If nobody owns the outcome, it is not an outcome. It is a forecast.
4. Leading and lagging indicators
Some benefits take time to appear.
Use leading indicators to determine whether the investment is moving in the right direction:
- User activation
- Completion rates
- Process-cycle reduction
- Defect trends
- Training completion
- Transaction migration
- Usage frequency
Then measure lagging outcomes:
- Cost reduction
- Revenue improvement
- Risk reduction
- Customer retention
- Productivity
- Compliance performance
This prevents executives from waiting 18 months to discover that users never adopted the solution.
5. A decision rule
Every funding request should state what evidence will trigger the next decision.
Continue.
Increase.
Pivot.
Pause.
Stop.
Without a decision rule, stage gates become theatre. The committee reviews status, congratulates the team for progress and releases the next tranche automatically.
That is not governance. It is scheduled approval.
Stage gates must release money against evidence
A stage gate should not ask whether the team completed its activity list.
It should ask whether the investment still has a credible path to value.
A practical outcome-based funding model can use four gates.
Gate 1: Strategic fit
Confirm that the investment supports a priority business outcome.
Reject work that is strategically interesting but operationally irrelevant.
Gate 2: Evidence of feasibility
Test the assumptions.
Can the technology work in the actual environment? Is the data usable? Are process owners engaged? Can the organization comply with security, regulatory and integration requirements?
Do not fund scale based on a slide deck.
Gate 3: Adoption and operational readiness
Before releasing major deployment funding, verify that the operating model is ready.
Check:
- Process ownership
- User readiness
- Training and support
- Data quality
- Controls and compliance
- Integration performance
- Support capacity
A technically complete solution that nobody uses is not ready for scale.
Gate 4: Benefits realization
After release, compare actual performance with the baseline and target.
The decision is not “did we go live?”
The decision is “did the investment produce enough value to justify continued funding?”
The UK Government’s Gate Review 5 guidance explicitly connects operational review with benefits realization. That is the discipline many enterprise portfolios still lack.
Adoption is a financial control
Most organizations treat adoption as a change-management workstream.
That is too weak.
Adoption is a financial control.
If the intended users do not change their behavior, the business case is broken. The organization is paying for capacity that is not producing value.
Consider an automation programme that reduces theoretical handling time by 40% but is used for only 20% of eligible transactions. The technical benefit may be real. The realized financial benefit is not.
This is why release criteria should include adoption.
Examples include:
- At least 60% of priority users active within 90 days
- At least 75% of eligible transactions routed through the new workflow
- Error rates below the agreed threshold
- Business owners signed off on the new operating process
- Support volumes stable after deployment
- Benefits data available for monthly review
The exact thresholds will vary.
The principle should not.
No adoption. No realized value. No automatic next tranche.
The model is not suitable for everything
Outcome-based funding is not a replacement for all project budgeting.
Use conventional project controls where the work is genuinely discrete:
- A regulated facility build
- A defined data-centre exit
- A one-time acquisition integration
- A fixed infrastructure replacement
- A bounded compliance remediation
Even then, tie the project to the business capability or risk reduction it enables.
For evolving digital products, enterprise platforms, AI initiatives and workflow modernization, a value-stream model is usually stronger.
Use a hybrid structure:
- Project-level cost control for delivery accountability
- Value-stream funding for the enduring capability
- Stage gates for investment decisions
- Benefits reviews for continued funding
- Business ownership for adoption and realization
This preserves financial discipline without pretending that a three-year transformation can be accurately specified in year one.
What to do in the next 90 days
Do not begin by redesigning the entire finance operating model.
Start with one portfolio.
Choose a transformation area where funding is significant and benefits are currently unclear. Then:
- List every active project and the outcome it is supposed to create.
- Remove projects with no credible business owner.
- Define baselines for cost, cycle time, adoption and risk.
- Group related projects into value streams or business capabilities.
- Set quarterly funding reviews.
- Define evidence required at each gate.
- Make adoption and benefits realization part of release approval.
- Reallocate funding from low-performing work to initiatives producing evidence.
- Report value delivered alongside cost and schedule.
- Stop using “green” status as a substitute for business performance.
This will expose uncomfortable truths.
Some projects will not survive.
That is not failure. It is capital discipline.
The real failure is continuing to finance work after the evidence says it is not creating value.
Conclusion: fund the result, not the activity
Transformation funding is not a technical issue.
It is a capital-allocation issue.
CFOs need better evidence for where money is going. CIOs need funding models that reflect how modern platforms and products create value. PMO leaders need governance that measures business performance rather than administrative compliance.
The answer is not to eliminate projects.
The answer is to stop treating project completion as the definition of success.
Fund the outcome.
Release money in stages.
Measure adoption.
Validate benefits.
Stop, pivot or scale based on evidence.
That is how organizations close the Execution Gap.
If your portfolio is full of projects but short on measurable results, a Delivery Diagnostic with Dark Consultancy can identify where funding, governance, ownership and execution are breaking down.
Frequently Asked Questions
What is outcome-based funding?
Outcome-based funding allocates investment to a measurable business result, capability or value stream rather than only to a temporary project. Continued funding depends on evidence of progress, adoption and benefits realization.
Is outcome-based funding the same as agile budgeting?
They are closely related but not identical. Agile or lean budgeting generally funds value streams and supports incremental planning. Outcome-based funding adds explicit business-result measures and links funding decisions to realized value.
How can CFOs measure whether an outcome has been achieved?
Start with a baseline, define a target and assign an accountable business owner. Track leading indicators such as adoption and process performance alongside lagging indicators such as cost reduction, revenue impact, productivity or risk reduction.
Should every project be funded this way?
No. Discrete projects with fixed deliverables may still use traditional project budgeting. Outcome-based funding is most useful for evolving products, platforms, transformation programmes, AI initiatives and capabilities where value emerges incrementally.
What happens when an initiative misses its benefits target?
The portfolio should decide whether to continue, pivot, pause or stop funding. Missing a target is not automatically a reason to terminate, but continuing without a credible recovery plan is poor capital allocation.
About the Author
Kunal Patel : CEO & Founder, Dark Consultancy
Kunal Patel founded Dark Consultancy after two decades leading technology and transformation programmes across the public sector, financial services, defence, and energy industries. He has directly managed programme recovery engagements for government agencies, development finance institutions, and regulated enterprises across the US, Middle East, South Asia, and Southeast Asia ; ranging from $5M platform migrations to $200M+ enterprise transformation portfolios. Kunal is a recognised practitioner in delivery governance for regulated environments and holds PMP and PRINCE2 Practitioner certifications. He leads every new client engagement personally and remains accountable throughout the programme lifecycle. Connect with Kunal on LinkedIn