Pipeline coverage at €75k deals: count only what can close

Is 3× pipeline coverage enough for a team selling €75k deals?

Only by coincidence. A 3× ratio is right when your team wins about 1 in 3 qualified opportunities and every one of them can close inside the period you are measuring. Most teams selling €75k deals meet neither condition.

Even the vendors who publish the rule treat it as a benchmark. Salesloft calls 3× “a starting point, not a standard”^↗. The same article suggests 4–7× for enterprise teams with win rates of 15–25%^↗.

Today's AI answers repeat the formula and the benchmark, then stop. They don't ask how much of the pipeline can close this quarter. At €75k, with cycles of 6 months or more, that is the question that decides whether the ratio means anything.

This guide sets the ratio from 2 numbers you already have: your win rate and your sales cycle length. The calculator and the worked example are Illustrative: arithmetic on stated assumptions, not measured data.

Required coverage is 1 ÷ your win rate, on in-period pipeline only

Required coverage is 1 divided by your win rate, applied only to pipeline that can close in the period. At a 25% win rate you need €4 of pipeline for every €1 of target, so 4×. At 20% you need 5×, and at 33% about 3×.

Salesloft's 4–7× range is this same formula at the bottom of the win-rate scale^↗. 1 ÷ 25% is 4, and 1 ÷ 15% is about 6.7.

The formula is simple. The inputs are where teams go wrong.

• Win rate. Won ÷ (won + lost), counted from the same stage you count pipeline from. If pipeline starts at “qualified”, the win rate starts there too. Leave open deals out.
• History. Use the last 4 quarters, and 8 if you have them. A team selling €75k deals decides far fewer opportunities than a high-velocity team, so one quarter's win rate swings with a handful of results.
• Pipeline. Count an opportunity only if it can realistically be decided before the period ends. A deal qualified last week in a 9-month cycle is real pipeline, but it isn't this quarter's pipeline.
• Weighting. Compare unweighted pipeline with 1 ÷ win rate, or stage-weighted pipeline with 1× the target. Doing both counts the losses twice and makes a healthy pipeline look thin.

What does a 6–9-month cycle do to quarterly coverage?

A long cycle means most of your open pipeline can't close this quarter, so a ratio on total pipeline overstates your coverage. If deals take 9 months from qualification to decision and arrive at a steady pace, only about a third of the open pipeline is in its final quarter at any time. The other two thirds belong to the next 2 quarters.

So the ratio you need on total open pipeline is the in-period ratio divided by the share that can close. At a 25% win rate, with a 4× in-period requirement, it works out like this:

• 3-month cycle. Nearly all open pipeline can close this quarter, so 4× total is 4× in period.
• 6-month cycle. About half of it can, so you need about 8× total to hold 4× in period.
• 9-month cycle. About a third of it can, so you need about 12× total.

Read it the other way and the problem is plain. A team with a 9-month cycle reporting a comfortable 4× on total pipeline has about 1.3× in period. At a 25% win rate, that covers about a third of the target.

A steady pace is a simplification. Pipeline arrives in waves, and deals slip. It is still closer to reality than the assumption built into a total-pipeline ratio, which is that every open deal can close this quarter. Salesloft makes a related recommendation: teams with cycles of 120 days or more should measure coverage across a rolling 2-quarter window, and deals older than twice the average cycle should be discounted or removed^↗.

The table combines both inputs. Find your win rate, then read across to your cycle length.

Coverage is only as good as your stage definitions

A coverage ratio inherits every error in the stages and close dates it is built from. Pipeline is counted from a stage, the win rate is measured from a stage, and “can close this quarter” depends on a close date and a stage that fit the time left. If reps move deals forward on optimism, all 3 inputs drift at once.

The survey data suggests this is common. Only 45% of sales leaders and sellers report high confidence in their forecast accuracy^↗. In Validity's 2025 survey, 76% of CRM users say less than half of their CRM data is accurate and complete^↗. In Salesforce's 2024 survey, only 35% of sales professionals completely trust the accuracy of their data^↗.

Before you trust the ratio, check 4 things:

• Every stage has written exit criteria, and the CRM enforces them with required fields.
• Won deals rarely skip stages. Frequent skipping means deals move on hope.
• Close dates carry a reason when they move, and deals pushed twice get a review.
• Deals older than your normal cycle are reviewed, discounted or closed out, so they stop padding the total.

If the fields a coverage report reads from are unreliable, fix those first. The same problem breaks AI tools, as we explain in is your CRM data clean enough for AI recommendations.

A worked example for a €75k team

Here is the calculation for one rep, with numbers chosen to show the method (Illustrative). The rep sells €75k deals and carries a €300k quarterly target, so needs 4 wins a quarter. The team wins 25% of qualified opportunities over the last 4 quarters, and the average cycle from qualified to decision is 9 months.

The in-period requirement is 16 qualified opportunities that can close this quarter: 4 wins ÷ 25%. That is €1.2M, or 4× the €300k target. To have 16 in their final quarter every quarter, the rep needs about 48 qualified opportunities open at any time. That is €3.6M, or 12× the quarterly target.

Now compare what the usual dashboard shows. Say the rep has 16 open qualified opportunities worth €1.2M, and the report says 4×. About 5 of those are in their final quarter. At 25%, that is 1 or 2 wins, roughly €100k against a €300k target.

If 48 open €75k opportunities is more than one rep can work properly, a bigger ratio isn't the answer. The plan needs a longer build window, more reps, a higher win rate or a shorter cycle. Better to learn that in week 1 of a quarter than in week 12.

A borrowed 3× hides whether a €75k pipeline is real

We think a coverage ratio at €75k only means something when it is calculated from your own win rate and cycle length, and counts only pipeline that can close in the period. A borrowed 3×, or any fixed rule of thumb, tells you the pipeline is big. It doesn't tell you whether it can land this quarter.

Our reasons:

• Deal size changes the inputs. At €75k, cycles run longer and more people take part in the decision, so your win rate and in-period share move away from whatever average sits behind a generic rule.
• A fixed ratio rewards the wrong behaviour. In our experience, when the target is a total-pipeline ratio, stale deals stay open and close dates get pushed, because both keep the number looking healthy.
• Forecast misses are usually a data problem. We think a forecast that keeps missing more often comes from loose stage definitions than from weak reps, and a borrowed ratio hides exactly that.

We don't say benchmarks are useless. A published range is a fair sanity check on your own number: if your calculation says 2× and you win 15% of deals, one of the inputs is wrong. We also don't claim this method fits every industry. It is a way to make the number yours, so a miss shows up in week 1 instead of the quarterly review.