The bowtie revenue model is a funnel drawn twice: the familiar narrowing top that ends at a closed deal, mirrored by a widening bottom that tracks what happens after — onboarding, retention, and expansion. It treats a won deal as the middle of the story, not the end of it.
How it differs from the classic funnel
The traditional funnel stops at “closed won”. Everything after the signature is someone else’s problem — usually Customer Success, on a different system, measured differently. The bowtie says that split is the reason revenue leaks quietly on the back half.
Draw it out and the shape is obvious: leads narrow down through MQL, SQL, opportunity, and won on the left. Then it opens back out on the right — activated, retained, expanded. Same customer, one continuous journey, one set of numbers.
Why it matters for pipeline leaks
Most teams instrument the left side heavily and the right side barely at all. You’ll know your MQL-to-SQL rate to a decimal place and have no reliable read on net revenue retention by acquisition source.
That asymmetry hides expensive leaks. A channel that converts beautifully to closed-won but churns at twice the rate isn’t a good channel — it’s a slow leak you’ve been paying to fill. The bowtie forces both halves onto the same page so you can see it.
The common mistake
Teams adopt the bowtie diagram but keep the two halves on separate systems with separate owners and no shared definitions. The picture is unified; the data isn’t. You end up with a nicer slide and the same blind spot.
The fix is unglamorous: agree the stage definitions across the whole shape, and make sure a single source can report left-to-right without a spreadsheet stitching it together.
Related reading
If this was useful, see what pipeline leakage actually is and what closed-loop reporting gives you.
New here? Browse more in Insights.
The bowtie revenue model was developed by Winning by Design.