Skip to content
Module 08 · The sales deck~150s dwell · weight 10

ROI / business case

Turn the cost of inaction and the product narrative into a specific payback number the buyer's champion can defend to their own boss. Without this, the buyer likes the product but has nothing to bring to the budget conversation.

Force Management's Command of the Message treats the business case as the artifact the champion carries into internal approval meetings; live, that math typically takes 2-3 minutes to build with the buyer.

Include
  • Restate the annual cost of inaction from earlier in the call
  • Show your price against that cost, side by side
  • Calculate payback period in months, not just a percentage
  • Include time saved as a secondary line, not the headline number
  • Ask the buyer if this is the number they'd need to bring to finance
Cut
  • ROI percentages with no visible cost or price behind them
  • Multi-year projections with compounding assumptions no one can verify live
  • Generic 'save time and money' framing with no specific figures
  • Hiding your price until after the ROI slide instead of showing it plainly
Red flags a reader notices
  • Buyer says 'I'd need to see this in a spreadsheet' and disengages from the live math
  • Buyer can't answer who would need to approve this internally
  • Payback period is longer than the buyer's stated planning horizon
Pitfalls behind them
  • The ROI number is presented as a percentage with no underlying dollar figures the buyer can verify.
  • The business case doesn't reference the specific cost of inaction number confirmed earlier in the same call.
  • Payback period isn't stated in months, so the champion can't easily compare it to their own approval threshold.
60-second self-test
  • · Does your ROI number trace directly back to the cost of inaction you built together earlier?
  • · Could the buyer's champion repeat your payback period from memory five minutes after the call?
Template
At $[annual cost of inaction] today and $[your price] a year with us, that's a payback period of [N] months.
Weak

"Our customers typically see over 300% ROI within the first year."

Strong

"You're losing about $9,600 a year to manual FX reconciliation. Nimbus runs $4,800 a year for your team size, which pays for itself in just under 6 months, before counting the 6 hours a month your ops lead gets back."

Reuses the exact cost-of-inaction figure from earlier, states price plainly, and computes payback in months the buyer can repeat verbatim.

Quick quiz

1. A defensible ROI number should be built from…
  • The same cost-of-inaction figure the buyer confirmed earlier in the call.
  • A generic customer-average ROI percentage.

Force Management frames the business case as an artifact the champion defends internally, so it must trace to numbers the buyer already owns.

2. Payback period is best expressed as…
  • A number of months.
  • A percentage ROI over an unspecified period.

Months map directly to a buyer's internal budget cycle and are easier for a champion to repeat and defend.

Sources