We cannot prove ROI so deals stall
Here is how to work out why.

The short answer

Deals stall on ROI when the story is a vendor slide, not a buyer’s arithmetic. Name the value pillars in their P&L language, show the derivation, and set the instrumentation that would prove or kill the case after signature. Business Value Engineering is built for that. It is not a case-study deck and not an implementation of their analytics stack.

A stalled deal after a good demo usually means the economic buyer has no artefact they can defend. Champions like the product. Procurement asks for a payback. Finance asks where the number came from. Nobody in your company can show the working in the buyer’s chart of accounts, so the cycle stretches and then dies as “no decision”.

The common wrong response is more proof points: logos, ROI calculators with unexplained multipliers, a customer quote. Those help after the arithmetic is owned. Before that they are decoration. The buyer needs three things in their language: which line of their P&L moves, by how much under which assumption, and what they will measure in ninety days to see if it happened.

This is most acute in software, healthtech, and anything sold as a “platform”. It also shows up in professional services when a diagnostic cannot be distinguished from T&M, and in industrial when energy or yield claims cannot survive the plant controller. The engagement is Business Value Engineering (catalog id t11) — quantified value case, value pillars, QBR language, instrumentation. It is not building their data warehouse.

If the product cannot produce a falsifiable value case at all, that is a product or packaging problem, not a sales-enablement problem. BVE will surface that quickly. Pretending otherwise is how discounting starts as a substitute for proof.

How to tell this is actually your problem

These three together are the signature. One on its own usually points somewhere else.

✓ Champions stall after the demo waiting for a “business case”
✓ Your ROI calculator uses industry averages the buyer’s finance team will not accept
✓ Won deals cannot show a before/after the customer would put in a QBR

The move that usually makes it worse. Discounting to compensate for an unprovable value case, which trains the market that the number was never real.

Who this is not for

Percision is the wrong tool if you already know the answer and only need execution capacity, or if the business is pre-revenue — then the constraint is evidence about the market, not analysis of your own figures. Percision is not a lawyer, tax advisor, auditor, licensed appraiser, clinical or regulatory filer, or an AI implementation shop. It does not do HR casework, creative-only brand work, or impersonate a named consulting firm. It is a strategy analysis engine — not a template library. Also wrong if you need facilitation, politics, or someone to sit with a lender or buyer. Those are human jobs.

Percision is not a lawyer, tax advisor, auditor, licensed appraiser, clinical or regulatory filer, or an AI implementation shop. It does not do HR casework, creative-only brand work, or impersonate a named consulting firm. It is a strategy analysis engine — not a template library.

Industry cuts

Industry pages at {problem}-in-{industry} ship only with an unedited run excerpt. This canonical has none yet, so there is no eleven-cell grid and no -in-saas door. Home-services operators (HVAC, plumbing, electrical, landscaping, cleaning) hit the same binds as other owner-operated trades: crews fully booked, contribution unknown by job type, and growth that still depends on the owner answering the phone. Percision can analyse that shape of business. There is no /strategy-for-home-services hub yet — industry pages ship only with a named profile and an unedited run excerpt, so this language lives on the operator pages rather than as a twelfth grid.

Related live hubs: strategy by industry. Unedited excerpts, when they exist for this question, will be attached here — we do not reprint another problem’s sample run as if it were this one.

What the engine does with this question

It routes to Business Value Engineering (catalog id t11), one of 29 engagements. The output is a sequence with a stopping rule — which move first, what it funds next, and the observation that would say it is not working — rather than a list of things you could consider.

Read a complete report before deciding whether it is worth your time.

Questions people ask about this

Is this a sales-training problem?

Rarely first. Training people to tell a story that finance will reject just makes the stall more eloquent. The artefact has to survive a controller. Then training is useful.

What if we sell to mid-market buyers who do not have a formal ROI process?

They still have a payback in their head. Write it down in their units — hours saved, jobs per week, margin on a typical job — and you have the same case without the enterprise theatre.

Can Percision implement the instrumentation?

No. It designs which metrics would prove the case. Connecting those metrics to a warehouse, CRM, or model-ops stack is an implementation job Percision does not do.

When is Percision the wrong tool?

Percision is the wrong tool if you already know the answer and only need execution capacity, or if the business is pre-revenue — then the constraint is evidence about the market, not analysis of your own figures. Percision is not a lawyer, tax advisor, auditor, licensed appraiser, clinical or regulatory filer, or an AI implementation shop. It does not do HR casework, creative-only brand work, or impersonate a named consulting firm. It is a strategy analysis engine — not a template library. Also wrong if you need facilitation, politics, or someone to sit with a lender or buyer. Those are human jobs.

Does Percision replace a lawyer, tax advisor, auditor, or AI implementation team?

Percision is not a lawyer, tax advisor, auditor, licensed appraiser, clinical or regulatory filer, or an AI implementation shop. It does not do HR casework, creative-only brand work, or impersonate a named consulting firm. It is a strategy analysis engine — not a template library.