Get in touch →
October 16, 2026

The business case that wins approval can lose the project

A project can meet its deadline and stay within its agreed budget yet still fail to deliver the reason it was approved. That outcome is often treated as a delivery problem, however, sometimes the problem was already present in the business case.

In a September Technology & Innovation Forum poll, 34% of participants said unrealistic business cases or expectations were among the risks that most often materialised in their projects. It was the joint most common answer. In the same session, 43% identified a minimum viable product (MVP) being pared back to meet budget or deadline as the weakest point in project planning. Together, they point to a familiar sequence: a case is made persuasive enough to secure approval, then the project is managed against a promise that was never realistic.

When time or cost begins to bite, the team looks for room to move. The MVP is cut, a process change is deferred, or an integration is pushed into a later phase. Each decision may look reasonable on its own but if the original case depended on those elements, the project can deliver what remains while the business loses the value it was promised. A smaller launch is not automatically a bad outcome, yet it becomes one when the organisation has not agreed what value must survive the cuts, or what evidence would justify changing the plan.

This is why “scope creep” is too blunt a label for every change. Requirements become clearer as people see a solution take shape. Some changes improve the design; others add cost without improving the outcome. A useful plan makes that distinction visible. It sets out the first release, the later phases, the decisions that remain open and the conditions for changing direction. The roadmap should be firm enough to guide delivery and flexible enough to accommodate learning.

In July, the Technology & Innovation Forum raised a related issue: 67% of participants selected business acceptance of and readiness for change as the critical consideration most often overlooked in a technology selection. A business case can describe a technical solution and still understate the work needed to adopt it. If new processes, roles or controls are required, the case needs to account for the people who will define, test and use them. Otherwise, readiness appears later as delay, resistance or a reduced scope.

A stronger case starts with the business outcome and works backwards. What is the operation expected to do better? Which constraint is holding growth back? What needs to change for the improvement to happen, and what should remain as it is? These questions should be addressed before a supplier is selected, because the answer may be to keep a system and reconfigure it, change the process around it, or replace only the part that is holding progress back.

That changes the purpose of a technology selection. A long list of requirements can create the appearance of rigour while leaving the commercial case vague. A short, well-run selection can be more useful if it tests the essential outcomes, the fit with the existing technology stack, the delivery assumptions and the effort required from the business. The point is not to make every selection small but to make the process proportionate to the decision and be clear about what the organisation is buying. The business case should also survive contact with delivery. That means naming who can decide when a trade-off is needed, keeping a view of risks and unresolved issues, and recording why scope changes. If a deadline forces a feature out, the team should be able to say what value is lost, what is protected and whether the original return still holds. That gives executives a real choice rather than a quiet change in the definition of success.

Nor does delivery end at go-live. People need support as they move into the new process; data, controls and integrations need attention; and the next phase needs a funded place on the roadmap. Treating launch as the finish line encourages teams to spend the budget on implementation and leave adoption to business-as-usual capacity. A realistic case includes the work that makes the change stick.

For specialty finance businesses, the commercial question is not whether a project can be made to fit its initial approval. It is whether the change will help the business grow, and whether the plan protects that value when conditions shift. Finativ’s approach is to retain what works, reconfigure what holds growth back and replace only what must change, then deliver alongside the client team. The case for change should be as practical as the change itself.

If the expected return depends on an MVP that keeps losing pieces, the case needs to be revisited before the next cut is approved. What value must remain for the project to be worth completing?