Isolating Hard-Dollar vs. Soft-Dollar Savings

Your business case shows a large annual benefit. The CFO scans it for ten seconds, draws a line through two thirds of it, and says: “This part is real. The rest is productivity, and productivity never shows up in my budget.” The deal now rests on the third that survived, and you did not design the case around it. Separating hard and soft value before finance does it for you is one of the most practical habits an SE can build.

The problem this solves

Most business cases blend two different kinds of value. Hard-dollar savings are reductions in cash that leaves the company: a license that is cancelled, infrastructure that is switched off, a contractor who is not renewed. Soft-dollar value is time or efficiency gained: faster ticket resolution, fewer manual steps, less frustrated engineers. Both matter, but only one changes next year’s budget. When the two are mixed in one total, finance discounts the whole thing, and your strongest numbers lose credibility by association.

Sort every line into one of three buckets

Go through each benefit with your champion and classify it:

• Hard: a specific cost line that stops or shrinks, with a date. Example: a legacy tool whose renewal will not be signed next quarter.
• Soft: time or effort saved that will be redeployed, not removed. Example: hours engineers no longer spend on manual reports.
• Risk reduction: avoided losses that are real but probabilistic, such as fewer audit findings or outages.

Present them in that order and never add them into one headline figure. Lead with the hard total, then show the soft and risk value as upside.

Make hard-dollar savings verifiable

A hard number is only hard if someone can point to it. For each line, record the contract or invoice it comes from, the end date of the current commitment, and the owner who will actually cancel or downsize it. If a license cannot be cancelled until a multi-year term ends, the saving starts then, not now. Being precise here is what lets the CFO accept the number without rework.

Do not throw soft value away

Soft value is not worthless; it is just unbudgeted. Make it concrete by naming what the freed time will be used for: the backlog item that finally gets built, the audit preparation that moves from senior to junior staff. When a soft benefit enables a hard one later, say so, but keep it in the soft column until it does.

Adjust to the conversation

• During a budget freeze, the hard column alone has to carry the payback. If it cannot, be honest about the timeline.
• With a procurement lead focused on per-seat price, compare the hard total with the price difference between tiers.
• In a renewal, report realised value in the same three columns you used at signing. Consistency is your proof.
• Against a free open-source alternative, the hard cost is often hidden in infrastructure and support contracts. Find those invoices.

Decision and check

Before any value summary leaves your hands, verify:

1. Every line is labelled hard, soft or risk reduction, and the labels were reviewed with the champion.
2. Every hard line names a contract, invoice or budget line and the date the cost actually stops.
3. The headline figure is the hard total only, with the other columns shown separately.
4. Nothing labelled soft is counted toward payback.

If the hard column cannot justify the purchase on its own, decide now whether the deal needs a phased scope or a stronger risk case, instead of hoping finance will not notice.

Speaking the language of finance is part of the 80% of solution engineering that stays the same whatever you sell. SE Ignite shares these value engineering frameworks for free, with no paywall, so any SE can build business cases that survive the CFO’s pen.