Revenue execution: from interested to closed
We have plenty of pipeline and nothing is converting: the complaint arrives in almost identical words, and the instinct that follows is always to pressure the close. It never works twice, because the deal died four steps upstream. What execution discipline looks like when stages are named after the buyer rather than the seller.
Summary
- A pipeline that will not convert is usually not a closing problem. The point where a deal dies is almost never the point where you notice it died.
- Most CRM stages are named after what the seller did, which is why pipelines look healthy while revenue does not arrive. Name them after what the buyer did, with exit criteria someone other than the rep could verify.
- Two numbers do the diagnosis: stage conversion tells you where deals die, cycle time by stage tells you where they stall. A conversion problem and a velocity problem have completely different fixes.
The complaint arrives in almost identical words. We have plenty of pipeline. Nothing is converting.
The instinct that follows is always the same too: pressure the close. More follow-ups, tighter Monday reviews, a discount to get it over the line. Sometimes it works for a quarter. It never works twice, because the problem was never at the close.
Execution is the third pillar of a revenue operating system, the discipline that moves an interested buyer to a signed contract. And the defining truth about it is that the point where a deal dies is almost never the point where you notice it died.
Your stages are named after the wrong person
Open your CRM and read your pipeline stages. In most companies they look something like: contacted, demo done, proposal sent, negotiation, closed.
Notice what those describe. They describe what your team did. Contacted. Demoed. Sent. Every one of them is an activity your seller can complete alone, on a Tuesday afternoon, without the buyer doing anything at all.
That is why pipelines look healthy and revenue does not arrive. A deal sitting in "proposal sent" tells you a document left your building. It tells you nothing about whether anyone read it, whether the person who can sign has seen it, or whether a budget line exists.
Stages should be named after what the buyer did.
Not "demo done" but "buyer has confirmed the problem is worth solving this year." Not "proposal sent" but "economic buyer has engaged with commercial terms." Not "negotiation" but "procurement process has started and a start date is under discussion."
Rewriting stages this way is the single highest-return change most companies can make to their execution, and it costs nothing but an uncomfortable afternoon. The discomfort is the point: the first time you re-stage the existing pipeline against buyer-verifiable criteria, a meaningful share of it moves backwards. That is not a loss. That was always the true position; you were simply reading a different report.
Exit criteria are the instrument
A stage without exit criteria is a folder. A stage with exit criteria is an instrument.
Exit criteria are the specific, observable things that must be true before a deal advances. Observable meaning someone other than the rep could verify them.
The qualification frameworks people argue about, MEDDIC, BANT and the rest, are all attempts at the same thing, and the argument over which to adopt is mostly a distraction. What matters is not which acronym you choose. It is whether your team can state, without looking, what has to be true for a deal to sit where it sits. If they cannot, the framework is decoration.
Two practical tests for whether your exit criteria are real:
- Could a deal fail to meet them? If every deal passes every gate, they are not criteria, they are descriptions.
- Would two different people place the same deal in the same stage? If not, your conversion rates are measuring judgement, not progress.
The two numbers that diagnose execution
Once stages mean something, execution has a very small diagnostic kit.
Stage conversion tells you where deals die. Look at the ratio of deals entering each stage to deals leaving it, by segment. There is nearly always one gate doing most of the damage, and it is rarely the last one. In our experience the biggest drop usually sits between initial interest and confirmed problem ownership, which is upstream qualification, not closing.
Cycle time by stage tells you where deals stall. A deal is not lost when it is marked lost; it is lost when it stops moving. Time in stage is the earliest available signal, and almost nobody watches it.
Together they tell you whether you have a conversion problem or a velocity problem, and those have completely different fixes. A conversion problem is usually qualification or value articulation. A velocity problem is usually process friction: legal, procurement, security review, or an internal handoff nobody owns.
Slippage is the quiet killer
Look at deals that have moved their expected close date three or more times.
They are rarely marked lost. They simply migrate, quarter to quarter, carrying forecast weight they have not earned and consuming attention that better opportunities deserve. A pipeline heavy with slipped deals looks healthy and forecasts terribly.
Two disciplines help. First, track slippage explicitly: number of date changes per deal, visible in the review. Second, establish a norm that permits someone to say the deal is not real. That norm is a governance question as much as an execution one: if naming a dead deal is professionally costly, nobody will do it, and your pipeline will fill with ghosts.
When the discount becomes the strategy
There is a pattern worth naming, because it sits exactly where execution and pricing meet.
A deal stalls. The buyer will not commit. And the only lever anyone reaches for is price.
Nine times out of ten, a deal that can only be won on price is an execution failure upstream: value was never established, the economic buyer was never engaged, the alternative was never displaced.
The discount is not solving the problem; it is paying to avoid diagnosing it.
This matters more than it sounds, because the discount is permanent and the deal is not. You have set an anchor for that account's renewal, and often for the segment, in exchange for closing one quarter slightly earlier.
Execution discipline is what gives a sales team something other than price to reach for.
The handoff nobody owns
One more place execution leaks, and it is after the signature.
The gap between "closed" and "delivering" is where a surprising amount of revenue quietly degrades. Scope agreed verbally but not documented. An implementation timeline that slips and pushes recognition into the next quarter. A customer whose expectations were set by the sales conversation and are not met by the delivery reality.
Execution does not end at signature. It ends when the customer is live and the revenue is real. Where that handoff has no owner, the cost shows up later as , as unbilled scope, and as a reference you cannot use.
Not every business closes deals
A note on archetype, because execution is the pillar that varies most.
In a sales-led B2B business, execution means advancing a deal. In a hospital or diagnostics chain it flips entirely: there is no deal to close, the revenue is already walking through the door, and execution means capturing all of it, through charge capture, clean coding and denial management. In D2C, execution is the checkout funnel and the return rate. In manufacturing, it is order-to-delivery reliability and realization against the price list.
Different mechanics, identical logic: find the step where value earned fails to become value collected, and instrument it.
Where to start
Take your current pipeline. Re-stage it against buyer-verifiable criteria rather than seller activity. Then look at two things: which gate loses the most deals, and which stage holds them longest.
That exercise takes a morning and it will tell you more about your revenue engine than a quarter of forecast meetings.
For the wider picture, ROSA gives you an honest read across all five pillars of a revenue operating system, so you can see whether execution is genuinely your binding constraint, or whether the pipeline that isn't closing was never fed properly in the first place.
How useful was this article?
One tap. It tells us what to write more of.
The next one
Get what we publish next, by email.
Working notes on raising, borrowing, protecting, growing and structuring capital in India. One email a week at most, and you can leave any time.
We use your address only to send this. See our privacy policy.
We store your address to send you these emails and nothing else. See our privacy policy.
Related reading
