Most enterprise software purchases above a certain size need a business case: a document showing that the money spent will come back, with something to spare, within a reasonable time. Sellers often treat this as a formality and fill it with impressive totals. Finance teams have seen thousands of these and discount them heavily. The business cases that survive scrutiny are the ones that separate what is certain from what is hopeful and show the arithmetic plainly.
Start with a small example
A mid-sized company pays ₹12 lakh a year for three separate tools. A single platform would replace all three for ₹9 lakh a year. It would also save around two hours a day for each of ten employees, whose fully loaded cost is about ₹600 an hour.
The licence saving is straightforward: ₹12 lakh minus ₹9 lakh, or ₹3 lakh a year.
The time saving needs an assumption about working days. Two hours × ten people × ₹600 is ₹12,000 a day. Over 240 working days, that is ₹28.8 lakh a year. Different companies use anywhere from about 220 to 250 working days, so state the number you used. Total annual benefit on these assumptions: ₹31.8 lakh.
Now look at how a CFO would read it. The ₹3 lakh is a hard saving: an invoice that stops arriving. The ₹28.8 lakh is a soft benefit: those ten employees will still be paid the same salary. The company only gains if the freed time is used for something valuable, such as handling more volume without hiring, or moving people onto revenue-generating work. A business case that presents ₹31.8 lakh as if it were all cash will lose credibility the moment someone asks, “Are we reducing headcount?”
Hard, soft and strategic benefits
A credible business case sorts benefits into tiers, roughly in order of how much finance will trust them:
- Hard cost savings. Licences retired, contractor spend reduced, infrastructure decommissioned. These can be verified against invoices.
- Cost avoidance. Hiring that will not be needed as volume grows, an upgrade that will no longer be required. Real, but dependent on a forecast.
- Productivity gains. Time saved, converted into money at a loaded hourly rate. Only valuable if the time is redeployed.
- Revenue gains. Faster quoting, better conversion, fewer lost orders. Often large, but harder to attribute.
- Risk reduction. Lower chance of a compliance penalty, outage or breach. Usually expressed as probability multiplied by impact, which makes it easy to inflate.
A sensible approach is to make the case work on hard savings and cost avoidance alone if possible, then show productivity and revenue gains as upside. If the purchase only makes sense when every soft benefit is counted at full value, the case is fragile.
ROI and payback on a larger deal
Two measures appear in almost every business case. Return on investment compares net benefit with cost: (total benefits − total costs) ÷ total costs. Payback period is how long it takes for cumulative benefits to equal cumulative costs.
Consider an enterprise solution costing ₹2 crore over three years, which the customer expects to save ₹1.2 crore a year. The simple version: three years of savings is ₹3.6 crore, net benefit ₹1.6 crore, ROI 80%. If the full ₹2 crore is spent upfront, payback is ₹2 crore ÷ ₹1.2 crore per year, which is 20 months.
Reality is rarely that tidy. Suppose costs fall as ₹1 crore in year one (licences plus implementation) and ₹50 lakh in each of the next two years. Suppose too that savings reach only half their full level in year one because the system goes live part-way through and adoption takes time. Then:
| Year | Cost | Benefit | Cumulative net |
|---|---|---|---|
| 1 | ₹1 crore | ₹60 lakh | −₹40 lakh |
| 2 | ₹50 lakh | ₹1.2 crore | +₹30 lakh |
| 3 | ₹50 lakh | ₹1.2 crore | +₹1 crore |
Three-year ROI falls to 50% (₹1 crore net on ₹2 crore of cost) and payback arrives at roughly 19 months, assuming year-two benefits accrue evenly. The point is not that the second version is pessimistic. It is that the first version quietly assumed instant adoption, and a finance reviewer will spot that.
Costs people forget
Business cases written by sellers tend to understate the customer’s own costs. A fuller picture includes internal staff time for implementation, data migration, integration with existing systems, training, temporary productivity dips during changeover, and running the old system in parallel for a while. Including these makes the case smaller but much more believable, and it signals that the seller understands what implementation actually involves.
Whose numbers are they?
The strongest business cases use the customer’s own figures. Hours saved should come from the customer’s process owners, not from a vendor benchmark. Error rates, volumes and costs should come from their systems. The seller’s job is to structure the calculation and ask the right questions during discovery, then let the customer’s team own the inputs. A business case built that way becomes a document the champion can defend in a budget meeting the seller will never attend.
Finally, longer-horizon cases sometimes use net present value, discounting future benefits at the company’s cost of capital, because ₹1 crore received in year three is worth less than ₹1 crore today. For a three-year software purchase, simple ROI and payback are usually enough, but large capital decisions may require NPV, and it is worth asking the customer’s finance team which measures they use before building the model.
Written by the RP Strativa Team. Figures in the examples are illustrative.
Leave a Reply