The hidden cost of building business cases by hand

A business case should only take a few hours of an analysts time to model. In most organizations it takes weeks. Why? The time goes into two things nobody schedules. Hunting for inputs that are not readily available, and then refining a model long past the point where it changes the decision.

A business case is not one document. It is research, a financial model, a risk section, scenario analysis, and a narrative that a busy executive will actually read. Done by hand, in spreadsheets and slides, each one quietly consumes weeks of senior time. Multiply that across a portfolio and a year, and business cases become one of the most expensive habits for finance and operations teams.

The cost you can see

The obvious cost is hours. If a handful of people each spend twenty hours a month on digging for data, analysis, and the reporting around them, that is hundreds of hours a year of your most expensive people, spent assembling documents rather than making decisions. We built a simple calculator if you want to put a number on your own team.

The costs you can't see

Nobody has ever been criticized for a business case that was too thorough, and that is part of the problem.

The search has no stopping rule. You go looking for specific costs, and there is no clean answer, so you keep looking. You ask three people and get three numbers. You pick one and then spend an afternoon building the justification for why you picked it. None of that is poor discipline. It is what happens when the work has no definition of good enough, so it expands.

Then the model keeps getting refined. Another scenario tab. Another year of projections. Sensitivity analysis on an assumption that would have to be wrong by a factor of three to change the answer. I've been guilty of this myself. Most of that refinement is not for the decision, it is for the review. Everyone has sat in the meeting where one unanswerable question sank a good case, so everyone builds armor. The irony is that the analysis that would genuinely help, Monte Carlo and real sensitivity work, is the first thing cut when the deadline moves, because the weeks already went into the search.

The bill for this arrives in two places, and neither of them is hours.

The first is delay. Weeks of refinement means the decision lands weeks later, and the inputs you worked so hard to pin down have moved by the time anyone acts on them. The precision decays before it gets used.

The second is the business cases that never got built at all. When each one costs weeks of senior time, you ration them. They get spent on the things you are already fairly confident about, and the marginal idea, the one that might have surprised you, never gets a hearing. That is the expensive one, and it will never show up on a timesheet, because the work was never done.

A better trade

None of this means business cases are a waste. They are how good capital decisions get made. The waste is in the search and the refinement, and neither is the part a person is uniquely good at.

That work is exactly what software should own in the age of AI. Let the research, the calculations and the formatting happen automatically, and let the range arrive with the case through predictive scoring, rather than as a separate project nobody has time for.

What that buys is not a faster document. It is the time to do the work the range was for. Where to allocate resources to take cost out, which risks need mitigating now, and how to line up GTM to capture the top of the range rather than the middle of it. That is the part only your people can do, and today it is the first thing that gets cut.