The cost of inaction framework, explained with numbers

The calculation

Cost of inaction is monthly loss multiplied by the number of months the problem persists. A support backlog costing $4,000 a month over the twelve months before anyone fixes it carries a $48,000 cost of inaction.

That figure is your anchor: the amount of value in play. A fee of $4,800 to $9,600 against it is straightforward to justify, because the client is comparing your invoice to a loss they already accepted.

Where it overstates the case

Three failure modes make finance teams dismiss the number outright:

• Counting the same money twice — lost revenue and wasted staff time that already overlap.
• Assuming an unrealistic horizon. Twelve months only holds if nothing else would have fixed it.
• Using a monthly loss the client never confirmed. If you supplied the number, it is your number, not theirs.

Sanity-check against other frameworks

Run time-to-value compression (monthly upside multiplied by the months you save them) and the expected value matrix (impact multiplied by the change in success probability) alongside it. If cost of inaction is triple everything else, your horizon or your monthly figure is probably too aggressive.

When the frameworks disagree, showing a range is more credible than defending the highest number. PropelQuote lets you anchor on high, low, middle, or a range and shows the client only what you selected.

Say it out loud that it is an estimate

Every model rests on assumptions the client supplied. An explicit disclaimer that ROI figures are illustrative estimates, not guarantees or financial advice, costs you nothing in credibility and gains you a lot. PropelQuote includes one on proposals and live views by default; you can toggle it off, but there is rarely a reason to.