Forecasting Pipeline Coverage

• Source: Report research library
• Frameworks applied: Clari pipeline coverage ratio (required coverage = 1 / win rate), weighted coverage, four-criteria pipeline qualification, Clari seven sales forecasting methods (historical, opportunity-stage, sales-cycle-length, lead-driven, intuitive, multivariable, AI), bottoms-up versus top-down reconciliation, gap-to-plan attribution

Tightest structure in the batch: workflow leads immediately, formulas are explicit, and the four gap causes give the agent a diagnosis rather than a list of remedies.

Known weakness, published as found: Add a filled example of the forecast memo with real numbers so the reconciliation logic is demonstrated, not just specified. The 'do not average when the two forecasts diverge by more than 10%' rule needs a stated tie-break procedure for the case where neither side has better evidence.

1. 1.Copy the SKILL.md text below, or download the raw file.
2. 2.Create a folder named exactly forecasting-pipeline-coverage in your agent's skills directory.
3. 3.Save the file inside that folder as SKILL.md.
4. 4.Ask the agent one of the trigger requests below.
5. 5.Check the output against what you already know before it leaves your desk.

• Our enterprise win rate is 17% - is 3x pipeline coverage actually enough for next quarter?
• Here is the open opportunity export against a $4M target. Run a gap-to-plan by stage and segment and give me a forecast range
• The rep roll-up says $3.2M but the capacity model says $2.4M - how do I reconcile bottoms-up and top-down before the board call?

• Calculate our net revenue retention and CAC payback for the annual investor update
• Audit the CRM for duplicate accounts and missing required fields and give me a cleanup plan

---
name: forecasting-pipeline-coverage
description: >-
  Derives required pipeline coverage from actual win rate, tests qualified
  pipeline against that target by stage and segment, runs gap-to-plan analysis,
  and reconciles a bottoms-up deal roll-up against a top-down capacity or
  historical forecast into one committed number with a stated range. Use when
  the user says pipeline coverage, coverage ratio, how much pipeline do we need,
  3x pipeline, gap to plan, pipeline gap, forecast call, forecast accuracy,
  weighted pipeline, commit versus best case, bottoms-up versus top-down,
  stage-weighted forecast, are we going to hit the quarter, or hands over an
  open-opportunity export to assess against a quota. Do NOT use for computing
  retention or efficiency metrics like NRR and CAC payback (see
  modeling-saas-revenue-metrics), for setting quotas or carving territories (see
  designing-territories-and-quotas), or for fixing CRM field and duplicate
  problems (see auditing-crm-data-hygiene).
metadata:
  version: "1.0"
---

# Forecasting pipeline coverage

Convert win rate, open pipeline, and a revenue target into a coverage
requirement, a stage-and-segment gap-to-plan, and one reconciled forecast number
with a range. One job: coverage and forecast reconciliation for a defined period.
Quota assignment, territory carving, and record-level CRM cleanup are out of
scope.

## Workflow

Copy this checklist into your reply and tick items as you finish:

```
- [ ] 1. Fix the target, period, and window type
- [ ] 2. Qualify what counts as pipeline; exclude the rest
- [ ] 3. Compute actual win rate by segment
- [ ] 4. Derive required coverage and compare to raw and weighted actual
- [ ] 5. Run gap-to-plan by stage and segment
- [ ] 6. Build bottoms-up and top-down forecasts, then reconcile
- [ ] 7. Validate against the checks; fix inputs and re-run until clean
- [ ] 8. Write the forecast memo
```

**1. Fix the target, period, and window type.** Non-negotiable, because coverage
is meaningless across mismatched periods. State the revenue target, the period,
and whether the pipeline is measured in-period or on a rolling window. Teams with
sales cycles of 120 days or longer compute coverage on a rolling two-quarter
window, because an in-quarter snapshot cannot contain the deals that will close
in it ([Clari](https://www.clari.com/blog/pipeline-coverage-best-practices/)).

**2. Qualify pipeline.** Count an opportunity only if it has all four:
documented buying intent, identified need, a realistic timeline, and active
stakeholder engagement. Everything else is excluded, because including
unqualified deals is the most common coverage calculation error
([Clari](https://www.clari.com/blog/pipeline-coverage-best-practices/)). Also
discount or remove any deal aged beyond 2x the average sales-cycle length for its
segment (same source). Report the excluded amount as an explicit line, so the
audience sees what was removed rather than suspecting it.

**3. Compute actual win rate.** Segment first, then compute:

```
Win rate = Closed-won opportunities / (Closed-won + Closed-lost) in the period
```

Compute win rate on closed cohorts only. Dividing wins by all opportunities
including still-open ones understates win rate and inflates the coverage
requirement. Compute it per segment when cycle length or deal size differs by
segment, because averaging a single-decision-maker deal with a six-person-committee
deal breaks the math
([Clari](https://www.clari.com/blog/sales-forecasting-methods/)).

**4. Derive required coverage.** Use these formulas:

```
Required coverage      = 1 / Win rate
Actual coverage        = Total qualified pipeline value / Revenue target
Weighted coverage      = Sum(deal value x stage close probability) / Revenue target
Qualified pipeline needed = Revenue target x Required coverage
Coverage surplus/gap   = Actual qualified pipeline - Qualified pipeline needed
```

Required coverage of 1 divided by win rate is the mechanic that replaces "3x" as
a universal rule; weighted coverage is the more honest signal because it prices
stage distribution
([Clari](https://www.clari.com/blog/pipeline-coverage-best-practices/)). Report
raw and weighted coverage side by side; never report only one.

| Win rate | Required coverage |
|---|---|
| 50% | 2x |
| 33% | 3x |
| 25% | 4x |
| 20% | 5x |
| 15-25% (enterprise) | 4x-7x |

Source: [Clari](https://www.clari.com/blog/pipeline-coverage-best-practices/).
Most B2B teams target 3x-5x; enterprise teams with longer cycles and lower win
rates may need 5x-7x; high-velocity SMB teams closing more than half of qualified
deals need less than 3x (same source).

**5. Run gap-to-plan by stage and segment.** Build a matrix of stage by segment
holding open value, stage probability, weighted value, and average days in stage.
Then attribute the gap to a cause. Judgment step: pick the dominant cause and
justify it from the matrix rather than listing all four.

- Volume gap: qualified pipeline is below target x required coverage. Fix is
  creation, and it only helps if the remaining time exceeds one sales cycle.
- Conversion gap: coverage is adequate but stage-to-stage conversion is below
  trailing average. Fix is deal execution in the failing stage.
- Velocity gap: weighted value is adequate but average days in stage exceeds
  trailing average, so deals will land after period end. Fix is close-plan
  compression on the specific late-stage deals.
- Mix gap: coverage sits in early stages or in a low-win-rate segment. Fix is
  reallocating rep time, not adding more of the same pipeline.

**6. Build both forecasts and reconcile.** Produce two independent numbers, then
converge:

```
Bottoms-up  = Sum over open deals of (deal value x probability to close)
              + already-closed-won in period
Top-down    = Reps x Quota x Expected attainment rate  (capacity view)
              or Prior comparable period x Expected growth  (historical view)
Reconciliation gap = Bottoms-up - Top-down
Forecast range = [Closed-won + high-confidence late stage,
                 Closed-won + all weighted open pipeline]
```

Select the probability source by data maturity
([Clari](https://www.clari.com/blog/sales-forecasting-methods/)). With two or
more years of clean segmented data, historical, multivariable, or AI forecasting
are viable; with less, start with stage-based plus rep-submitted while building
the data foundation. Add cycle-length forecasting when cycles are predictable,
segment before applying cycle math when cycles vary by buyer, use lead-driven
conversion modeling for high-velocity SMB, and use segmented roll-ups rather than
one aggregate number when regions, segments, or deal sizes differ (same source).
Forecast new business and renewals with separate models and separate inputs;
renewal and expansion forecasting requires contract end dates, health scores,
product-usage signals, expansion indicators, and NRR targets, and expansion is
modeled separately because it has its own conversion patterns and cycle lengths
(same source).

When the two numbers disagree by more than 10% of target, do not average them.
Name the specific deals or assumptions driving the divergence and pick one side
with a stated reason, because a split-the-difference forecast hides which input
was wrong and blocks learning after the period closes.

**7. Validate, fix, re-validate.** Run all six checks. If any fails, correct the
input and recompute coverage, gap, and both forecasts, then re-run all six. Only
publish the memo once every check passes.

```
- [ ] Pipeline and target cover the same period (or a stated rolling window)
- [ ] Win rate computed on closed deals only, per segment
- [ ] Required coverage = 1 / win rate, using that segment's own win rate
- [ ] Deals aged beyond 2x cycle length removed or explicitly discounted
- [ ] Stage probabilities sourced from historical win rates, not rep opinion
- [ ] Stage assignments verified against activity (meetings held, next step
      set, stakeholders engaged), not just the CRM stage field
```

**8. Write the memo** using the template below.

## Output format

Use this exact section order, because the roll-up is compared week over week.
Adapt commentary wording inside sections.

```
## Forecast: <segment/team> - <period>  (as of <date>)
Target                     <value>
Closed-won to date         <value>
Actual win rate            <x>%   (closed cohort, n=<count>)
Required coverage          <1/win rate>x
Qualified pipeline         <value>   (excluded as unqualified/stale: <value>)
Actual coverage            <x>x     Weighted coverage: <y>x
Pipeline needed            <value>   Surplus/(gap): <value>

## Gap-to-plan by stage and segment
| Segment | Stage | Open value | Stage prob | Weighted | Avg days in stage | Gap driver |

## Forecast reconciliation
Bottoms-up   <value>
Top-down     <value>   (method: capacity | historical)
Committed    <value>   Range: <low> to <high>
Divergence explained by: <named deals or assumptions>

## Actions with owners
- <action> - <owner> - <date>
```

State strictness: the header block field order is fixed; the actions table may
be extended.

## Gotchas

- Applying a 3x rule to an enterprise motion with a 15% win rate can mean
  missing the number by 40%, since 15% win rate requires closer to 7x
  ([Clari](https://www.clari.com/blog/pipeline-coverage-best-practices/)).
- Stale deals silently destroy reported coverage: a team reporting 4x with 30%
  stale deals actually has 2.8x qualified coverage
  ([Clari](https://www.clari.com/blog/pipeline-coverage-best-practices/)).
- Reviewing coverage in week 10 of a 13-week quarter leaves insufficient runway
  to correct, so schedule the coverage review at least one full sales cycle before
  period end ([Clari](https://www.clari.com/blog/pipeline-coverage-best-practices/)).
- Stage-based forecasting fails when reps inflate stages, when deals are pushed
  forward to protect pipeline, or when there is no activity-verification layer, so
  treat an unverified stage as one stage lower
  ([Clari](https://www.clari.com/blog/sales-forecasting-methods/)).
- The default broken process is reps submitting commits, a manager rolling up, an
  optimism adjustment applied by someone, the quarter closing, and the miss being
  explained. Anchor on documented conversion history instead of the adjustment
  ([Clari](https://www.clari.com/blog/sales-forecasting-methods/)).
- Historical forecasting needs 2-3 years of clean segmented data and breaks in
  high growth, after a major launch, or when team composition shifts, so do not use
  it as the top-down anchor right after a headcount or pricing change
  ([Clari](https://www.clari.com/blog/sales-forecasting-methods/)).
- Coverage improves instantly when someone raises stage probabilities or
  re-dates deals into the period. Snapshot pipeline at period start and diff
  against the current snapshot, because otherwise the gap closes on paper only.
- A single deal larger than the remaining gap makes weighted coverage
  meaningless. Pull deals above roughly 10% of target out and forecast them
  individually with named close plans.
- AI and multivariable forecasts fail when the output is black-box or lives in a
  separate analytics layer disconnected from deals, calls, and next steps, so
  require that a manager can interrogate the model's reasoning before the score
  enters the committed number
  ([Clari](https://www.clari.com/blog/sales-forecasting-methods/)).

What does the Forecasting Pipeline Coverage skill do?

Derives coverage targets from win rate, runs gap-to-plan by stage and segment, and reconciles bottoms-up against top-down forecasts

Where does the Forecasting Pipeline Coverage skill come from?

Report research library. It was written by The Revenue AI Report against a 12 criterion quality rubric and graded in an independent scoring pass.

Why was the Forecasting Pipeline Coverage skill chosen for this library?

Tightest structure in the batch: workflow leads immediately, formulas are explicit, and the four gap causes give the agent a diagnosis rather than a list of remedies.

When should the Forecasting Pipeline Coverage skill not be used?

Do not use it for: Calculate our net revenue retention and CAC payback for the annual investor update Or: Audit the CRM for duplicate accounts and missing required fields and give me a cleanup plan

How do I install the Forecasting Pipeline Coverage SKILL.md file?

Download the file, create a folder named exactly forecasting-pipeline-coverage inside your agent's skills directory, and save the file inside it as SKILL.md. The agent loads it when a request matches the description.