Use ROI when…
The buyer is stuck on no-decision and hasn’t committed to changing anything yet. ROI justifies moving off the status quo by quantifying the cost of staying put.
Resources → Business Cases & ROI
Build the Case That Survives Finance & Procurement.
A business case only works if it holds up once it leaves your hands. These resources cover how to build ROI and TCO models, size the problem before pitching a fix, and package the result for an executive audience.
The same structure applies whether the buying committee includes a CFO evaluating SaaS spend or a CapEx committee weighing a capital equipment purchase. Only the inputs change.
Article
Why a Business Case Belongs Before the Demo
Modern B2B buyers expect cost justification as a matter of course, not as an afterthought reps produce once a deal is already stalled. Presenting a quantified, ROI-based business case before the product demo changes what the buyer is evaluating: instead of judging your product’s features against price, they’re judging a documented financial case against the cost of staying with the status quo.
This sequencing works because it front-loads the hardest question, the “is this worth it” question, before the buyer has invested time in a demo they might dismiss on price alone. A business case built early also gives your champion something concrete to circulate internally while the deal is still forming, rather than scrambling to build justification after stakeholders have already started asking questions.
The same logic applies whether you’re selling a SaaS platform or a piece of capital equipment: a plant manager deciding whether to greenlight a pilot wants the financial case as much as a CFO deciding whether to expand a software contract.
Article
ROI vs. TCO: Which One Wins Your Deal
ROI and TCO both provide financial justification, but they answer different questions and win different situations. An ROI analysis estimates the cost savings or revenue growth your solution creates relative to the buyer’s current situation, and it’s most effective when a buyer is stuck on “no decision,” unable to justify moving off the status quo at all.
A TCO analysis, by contrast, compares your total cost against a specific competing alternative, and works best once the buyer has already decided to change and is now comparing options. The diagnostic question is simple: are you losing deals to inaction, or are you losing deals to a competitor? The first calls for ROI. The second calls for TCO.
Industrial and capital equipment sellers see this pattern constantly. A plant that’s been running the same equipment for a decade needs an ROI case to justify change at all. A plant already shopping between two vendors needs a TCO comparison showing which option costs less over the equipment’s life, not just at purchase.
Article
What Makes a Business Case Defensible
A business case earns trust when its numbers are traceable, not when they’re impressive. Buyers want to see where an assumption came from, whether it’s benchmarked against real data, and whether it reflects their specific situation rather than a generic vendor average. A business case that can’t answer “where did this number come from” gets picked apart the moment it reaches finance.
Defensibility also means using the buyer’s own data wherever possible. A projection built from the buyer’s actual usage patterns, production volumes, or cost structure survives scrutiny in a way a generic industry benchmark never will, because the buyer recognizes their own numbers inside it.
This matters most for the stakeholder who never talks to you directly: the finance reviewer or procurement analyst who only sees the document, not your pitch. If the assumptions can’t defend themselves on the page, the case fails regardless of how compelling the sales conversation was.
Article
Assessment Tools: Sizing the Problem Before the Solution
Before a business case can quantify the benefit of your solution, the buyer often needs help quantifying the size of their current problem. Assessment tools exist for exactly this: helping buyers realize the scope and magnitude of an issue they may have underestimated, whether that’s inefficiency, downtime, or missed revenue, before any solution enters the conversation.
This step matters because a business case built on an underestimated problem produces an underestimated ROI. If a buyer believes downtime costs them a few thousand dollars a month when it actually costs tens of thousands, the resulting business case will understate your solution’s value even if every other assumption is accurate.
Assessment tools work as well on a plant floor as they do in a sales pipeline. A manufacturer assessing scrap rate and changeover time uncovers the same kind of hidden cost that a sales team assessing lead response time does. In both cases, sizing the problem accurately is what makes the eventual ROI number credible.
Article
Business Cases for Capital Projects and CapEx Committees
Capital equipment and industrial deals typically route through a CapEx committee, a group evaluating your project alongside every other capital request competing for the same limited budget. That committee usually sees a short summary of each project’s business case, which is why clarity and comparability matter as much as the underlying math.
The core inputs CapEx committees expect are payback period, IRR, and total cost of ownership, tied to operational outcomes like throughput, uptime, quality, or safety in the buyer’s specific plant. A business case that speaks only in generic percentage improvements, without connecting to these familiar capital-approval metrics, is harder for a committee to compare against competing projects.
Getting a capital project stalled after technical approval is a common failure point, not because the equipment doesn’t work, but because the internal financial justification was too weak to survive the committee. A defensible, benchmark-backed case gives your champion something they can carry into that room without you.
Framework
The ROI vs. TCO Decision Framework
Use this framework to decide which financial model fits your deal before you start building it.
Use TCO when…
The buyer has already decided to change and is now comparing your offering against a specific competing alternative on total cost over the asset’s life.
Diagnostic question: are you losing deals to inaction, or to a named competitor? Inaction calls for ROI. A named competitor calls for TCO. Many complex deals ultimately need both: ROI to get the deal moving, then TCO to win the final comparison.
Template
Executive-Ready Business Case Template
Structure your next business case document using this five-part outline, built for an audience that will spend less than five minutes reading it.
1. The problem, quantified
State the buyer’s current cost of the status quo in a single number, with the assumption behind it visible.
2. The proposed change
Describe your solution in one or two sentences, framed as the mechanism that removes the quantified cost.
3. The financial case
Show ROI or TCO (or both), payback period, and the benchmark data or buyer data behind each assumption.
4. Sensitivity and risk
Include a conservative, expected, and optimistic scenario, letting reviewers see the case doesn’t depend on best-case assumptions.
5. The ask
State exactly what approval or next step you need, and from whom, in one sentence.
FAQ
Common questions
What is the difference between ROI and TCO?
ROI estimates the cost savings or revenue growth your solution creates compared to the buyer’s current situation, and is most effective when a buyer is stuck on no-decision. TCO compares the total cost of your solution against a specific competing alternative, and is most effective when the buyer has already decided to change and is comparing options.
When should a business case be presented in the sales process?
A quantified business case works best when presented before a product demo, which lets the buyer evaluate the solution against a documented financial case rather than judging price against features alone.
Do capital equipment and industrial deals need a different kind of business case?
The structure is the same, but the inputs differ. Industrial business cases for CapEx committees typically emphasize payback period, IRR, and total cost of ownership, tied to operational drivers like uptime, throughput, and scrap, rather than software metrics like user adoption.
Build a business case that holds up in the room.
Try ValueNavigator free, no registration or credit card required, or talk with us about your specific deals.