What 40+ B2B SaaS Deals Actually Look Like: A Pipeline Benchmark Report
Most pipeline advice is recycled intuition dressed up as strategy. "Shorten your sales cycle." "Improve win rates." "Accelerate velocity." Great. But compared to what? For most revenue teams, there's no external reference point. You're navigating by feel, benchmarking against last quarter, or trusting a consultant's war stories.
That's the gap this report is designed to fill.
Domestique compiled data across 40+ client engagements to build an honest, ARR-segmented picture of pipeline health across B2B SaaS. The result is a benchmark study that breaks down pipeline velocity, win rates, and time-to-close by revenue stage: $1M to $5M ARR, $5M to $20M ARR, and $20M to $50M ARR. What follows are some of the most instructive findings, and what they mean for teams trying to grow into the next band.
Why ARR segmentation changes everything
The biggest mistake in pipeline benchmarking is treating a $3M ARR company the same as a $35M ARR company. The deal motions, buyer psychology, team structures, and process maturity are fundamentally different. Averaging across all of them produces numbers that are technically accurate and practically useless.
When you segment by ARR, patterns emerge that actually help revenue leaders make decisions. Win rates at the $1M to $5M stage are often higher on a percentage basis but masking a small denominator and inconsistent qualification. Companies in the $5M to $20M band frequently hit a velocity wall as they try to scale a founder-led motion without the process infrastructure to support it. And at the $20M to $50M stage, the companies that are winning have almost always invested ahead of the curve in RevOps, not after the fact.
The velocity problem nobody talks about
Pipeline velocity is a function of four variables: the number of qualified opportunities, average deal size, win rate, and length of the sales cycle. Most teams focus on win rate and deal size because those feel controllable. Sales cycle length gets less attention, partly because it's harder to influence and partly because it requires admitting how long deals actually take versus how long CRM says they take.
Across the engagements in our study, reported time-to-close and actual time-to-close diverged significantly, particularly in the $5M to $20M range. The gap usually traces back to when opportunity creation is logged, whether free trials or proof-of-concept periods are counted, and how late-stage stalls are categorized. Before you can improve your sales cycle, you have to measure it honestly.
Win rates by ARR band: what the data shows
At the $1M to $5M stage, win rates tend to be volatile. They look healthy in good quarters and collapse in slow ones, often because the pipeline itself is thin and a handful of deals can swing the metric dramatically. The issue is rarely the close rate. It's funnel volume and qualification discipline upstream.
In the $5M to $20M band, win rates often decline as companies expand their ICP too aggressively, go-to-market motion adds headcount before adding process, and deals become more complex without a corresponding improvement in deal management. This is the stage where RevOps infrastructure, if it exists at all, is usually under-resourced for what the business actually needs.
By $20M to $50M, the companies with strong win rates share a few characteristics: they have tight ICP definitions, consistent qualification criteria that are actually enforced, and pipeline review processes that surface risk early rather than late. The mechanics are not complicated. The discipline to maintain them consistently is harder.
What stage transitions reveal
Some of the most useful data in this study comes from companies mid-transition between ARR bands. The move from $5M to $20M is where the most organizations get stuck. The playbook that got them to $5M stops working, but the infrastructure to support the next stage of growth is not yet in place. Win rates drop. Cycle length increases. Velocity stalls.
The organizations that navigate this transition well tend to have one thing in common: they invested in revenue operations before they needed it, not in response to a growth plateau. They did not wait for pipeline to break before building the systems to manage it.
Using this data
These benchmarks are most useful as a diagnostic, not a scorecard. If your win rate is below the median for your ARR band, that tells you something is worth investigating. If your time-to-close is significantly longer, that is a signal worth tracing back through the funnel. The numbers do not tell you what to fix. They tell you where to look.
The goal is not to hit a benchmark. The goal is to understand where your revenue engine is losing efficiency and close the gap before it compounds.