01 · The shift
The traditional funnel ends at Closed-Won. The bowtie treats that moment as the center knot — the handoff — and gives equal weight to what happens after: onboarding, adoption, renewal, and expansion.
Because recurring revenue follows compound math — not the linear "add more reps → more deals" logic that breaks at scale — the highest-leverage growth usually lives on the right side of the bowtie, where retention and expansion cost far less than net-new acquisition.
Why operators care
Fix the system, not the people. Shared stages + shared metrics + shared language is what turns a room of siloed contributors into a predictable revenue engine.
Net-new acquisition is linear and expensive. Retention and expansion compound — the same base grows itself when the right-side mechanisms exist.
02 · The architecture
Three are strategic — design decisions you make once. Three are operational — they run continuously. You design top-down, then operate bottom-up. Select any model to open it.
Strategic — design once ↓
Operational — run daily ↓
03 · The data model
It replaces the funnel and standardizes three metric types across the full lifecycle — so Marketing, Sales, and CS all measure the same things the same way. Select any milestone to see its impact definition, the industry benchmark, and how it fails.
Volume
How many units sit at each stage.
Prospects, MQLs, SQLs, wins, active accounts.
Time (Δt)
How long units take to move — velocity.
Days in stage, sales-cycle length, time-to-first-value.
Conversion (CR)
The rate units move milestone to milestone.
CR1–CR7 across the bowtie.
Build a separate bowtie per segment. Win rates, conversion, and cycle times differ sharply between a self-serve velocity segment and an enterprise motion — averaging them together hides the truth and breaks your growth formula. (Marketing also lives on both sides — lifecycle and demand drive adoption, renewal, and expansion, not just top-of-funnel.)
04 · The common language
SPICED replaces BANT / MEDDIC and works across the entire lifecycle — prospecting, selling, onboarding, expansion. Because it is impact-first, it becomes the shared language for every handoff: BDR→AE, Sales→CS. Select an element.
05 · The math
Once the data model is stable, the revenue factory becomes a specification: feed in leads, apply the conversion rates, and committed output is arithmetic — not argument. Change the inputs and watch the machine respond.
Your inputs
Defaults reflect a high-velocity ~$12K-ACV SaaS motion. Replace with your own numbers — derive real conversion rates from your CRM, never from these benchmarks.
06 · Benchmarks
Orientation ranges from the 2024–2026 benchmark literature. Use them to locate roughly where you sit — then derive your real targets from your own data, per segment. A blended number averages two different businesses and tells you nothing precise.
GRR is the honest floor — below 90% is a structural pricing or fit problem no expansion can mask. NRR above 100% means the base grows with zero new logos. But a 100% NRR can still hide 20% churn offset by 20% expansion — always read GRR and NRR together, split by ACV segment.
07 · The go-to-market model
Your ACV dictates the motion — not the other way around. Staff a motion the deal size can't pay for and the math never closes. Enter a typical ACV to see the motion it supports.
These are best practices, not gospel. A high-touch motion in a low-ACV band can be right when the market needs heavy education — it simply demands a longer customer lifetime to pay back. The point is to make the trade deliberately, on the math.
08 · Implementation
There's an existing business with existing habits. Confirm what already works before you change anything, then roll out in sequence.
Inside step 1
Define the model → adopt the framework → craft the data model → assign clear ownership.
The last one is where most implementations fail. Ambiguous handovers at the knot — who owns expansion for a no-touch account: CS, support, or marketing? — quietly leak revenue for years.
09 · Failure modes
Implementations rarely fail on strategy. They fail in the seams — the handoffs, the definitions, the unowned stages. Here are the eight we see most, and the fix for each.
One honest caveat: these frameworks are recurring-revenue-native. Translate carefully for services or one-time-sale models — the bowtie and SPICED still hold, but the right-side economics change shape.
10 · Diagnose
Rate each statement for your business. The gaps are the diagnosis — and they map directly to the failure modes above.
11 · How we run it
This is our repeatable play for standing up — or fixing — a revenue engine. Process design before automation, every time.
From chaos to clarity
Bring your bowtie — or let us build it. We'll map the leaks against these benchmarks and hand you a prioritized plan in the first working session.
We engineer growth systems. JayOh builds the RevOps architecture, GTM execution and data infrastructure that turn messy revenue operations into predictable pipeline for B2B SaaS and PE-backed teams.
