How much pipeline do you need when you enter a new segment?
More than you need in your core segment, because your win rate there is unknown and probably lower. Start from the revenue target for the segment, divide by a cautious win rate, and adjust for a longer sales cycle. The result is your coverage target, and it is usually higher than the ratio your team is used to.
Pipeline coverage is the ratio of open pipeline to the revenue target for a period. Many B2B teams carry a rule of thumb for their main market, often a multiple like three times target. That multiple quietly encodes a win rate. When you move into a new segment, such as a new industry, a larger company size, or a new region, the old multiple stops being true.
This article walks through calculating coverage for a segment you have little history in, without pretending to precision you do not have.
What does a coverage ratio actually assume?
A coverage ratio assumes a win rate and a cycle length. If you close about one in three qualified opportunities within the period, you need roughly three times the target in pipeline. The ratio is just the inverse of your win rate, adjusted for how much pipeline will close inside the period at all.
That is why borrowed ratios mislead. A three times rule works for a team that wins about a third of its qualified deals inside the quarter. A team that wins one in five needs about five times. A team selling into a segment where deals take two quarters needs pipeline built well before the quarter starts.
I covered what the coverage number does and does not tell you in what a pipeline coverage number actually means. For a new segment, the key point is simple: the ratio is a function of win rate, and you do not yet know your win rate.
Why is the win rate in a new segment usually lower?
Because almost everything that helps you win in your core market is weaker in a new one. You have fewer references, less proof, a less tuned pitch, and reps who are still learning the buyer. Competitors may be more established there. Each of those gaps pulls the win rate down, at least at first.
A new segment also changes who you lose to. In your core market, you may mostly lose to doing nothing or to one familiar rival. In a new segment, you may face incumbents you have never sold against, internal tools, or a buying committee you do not understand yet. Each new loss reason lowers the rate.
None of this means the segment is a bad bet. It means your plan should assume a lower win rate until real data proves otherwise. Optimistic assumptions here create the most common failure: a segment that looks behind plan in month three and gets abandoned before it had a fair chance.
How do you estimate a win rate without history?
Use your core win rate as a ceiling, then discount it. A reasonable starting point is somewhere between half and three quarters of your core rate, depending on how similar the new segment is. Then replace that estimate with real numbers as soon as you have enough closed deals to count.
Similarity matters. Moving from mid-market SaaS companies to slightly larger SaaS companies is a small step, so a modest discount may be fair. Moving from SaaS to healthcare, or from founders to procurement-led enterprise buyers, is a large step, and a heavier discount is safer.
If you have any early signals, use them. Pilot deals, design partners, or a handful of opportunities from the segment that came in through inbound can give you a rough read. Treat that read cautiously, since early deals are often warmer than what outbound will bring later.
How do you calculate the coverage target step by step?
Take the segment's revenue target for the period, divide it by your estimated win rate, and you have the qualified pipeline needed. Then adjust for timing: if only part of that pipeline will close inside the period, raise the target or start building earlier. The math is simple. The assumptions are the work.
Here is an example in prose. Say the new segment has a target of 200,000 in new annual recurring revenue for the quarter. Your core win rate is about 30 percent, and you discount it to 20 percent for the new segment. Dividing 200,000 by 0.2 gives 1,000,000 in qualified pipeline, which is five times coverage.
Now adjust for cycle length. If deals in the new segment take about twice as long as your core deals, much of the pipeline created during the quarter will close next quarter. That means you need the pipeline built a quarter ahead, not just in the quarter. Coverage targets for new segments are as much about timing as about size.
How do you work backward to activity targets?
Divide the pipeline target by your expected average deal size to get the number of qualified opportunities needed. Then divide by your conversion rates from meeting to opportunity and from outreach to meeting. That gives you the meetings and outreach volume the segment needs, which is what the team can actually manage day to day.
Continuing the example, if the average deal size is 25,000, the 1,000,000 target means about 40 qualified opportunities. If roughly half of first meetings become qualified opportunities, you need about 80 first meetings. From there, your outbound and inbound conversion rates tell you how much activity it takes to book those meetings.
These numbers often reveal that the segment plan is not realistic with current capacity. That is a useful finding. It is far better to see the gap on paper before the quarter than to discover it in the pipeline review halfway through.
How should you track coverage once the segment is live?
Track it separately from your core pipeline, weekly, with the win rate assumption written next to it. As deals close or are lost, replace the assumed win rate with the real one and recalculate coverage. Blending the new segment into your main pipeline report hides both its progress and its problems.
Review stage progression, not just totals. A new segment may have plenty of early-stage pipeline that never moves. If deals pile up at the first stage, the segment may have an interest problem rather than a volume problem. I described how to run reviews that surface this in how to run a pipeline review that changes behavior.
Write down loss reasons from the start. In a new segment, every loss teaches you something about fit, messaging, or competition. After 15 to 20 closed deals, those reasons often matter more than the coverage ratio itself.
When should you decide the segment is not working?
Set the decision point before you start, based on a number of closed deals rather than a date. For example, after 20 closed opportunities, compare the real win rate and cycle length against your assumptions. If both are far worse with no improving trend, rethink the segment. If they are close, keep investing.
Deciding on a deal count protects you from two mistakes. Quitting too early, after a few losses that may be noise, and continuing too long, because "it is still early" can excuse anything. A pre-agreed threshold makes the decision less emotional for everyone involved.
Also check whether the segment is really one segment. Sometimes a new market contains two different buyers with different win rates, and averaging them hides a strong niche inside a weak whole. I covered that situation in how to pick an ICP when two segments both buy.
What should you do next?
Write down the revenue target for the new segment, discount your core win rate for that segment, and divide to get the pipeline target. Adjust for a longer sales cycle, work back to meetings and outreach, and track the segment separately each week. Agree on a deal-count checkpoint before you begin.
Entering a new segment is a bet. Coverage math does not remove the risk, but it makes the bet visible, so you can size it, staff it, and judge it on evidence instead of hope.
If you want help building the pipeline model or the GTM systems for a new segment, reach out and let's chat.
Get found, cited and the back office automated
Let's make your site the source AI engines quote and wire up the systems behind it.
Read more blogs
Let's get your website found and cited by AI
Tell me what you're working on, whether AI search is skipping your product, your back office is buried in manual work, or you need a build that does both.