GASP
Sales Pipeline Metrics Leading

Pipeline Coverage Ratio

Pipeline Coverage Ratio: The ratio of unweighted pipeline value to quota for the period.

Formula

Pipeline Coverage = Unweighted Pipeline Value / Quota for Period

Computable definition

The canonical formula in the GASP formula grammar. The MCP server compiles it to SQL over the datasets listed below.

sum(field.opportunity_amount where field.opportunity_stage not in ('closed_won', 'closed_lost')) / sum(field.quota)

Unit: ratio

Notes: Unweighted open pipeline (the unweighted variant of pipeline_value) over quota. The 3x to 4x benchmarks assume unweighted pipeline, since 1 / win rate already applies the conversion.

Data requirements

Grain: Daily snapshot · Frequency: Daily sync · Aggregation: snapshot (day) · Staged: no · Main source: CRM.

Field Dataset Type
opportunity_amount opportunity decimal
opportunity_stage opportunity string
period_start sales_rep date
quota sales_rep decimal
snapshot_date opportunity date
Example SQL (Postgres)
SELECT (CAST((SELECT COALESCE(SUM(opportunity_amount), 0) FROM opportunity WHERE snapshot_date = :period_end AND opportunity_stage NOT IN ('closed_won', 'closed_lost')) AS DOUBLE PRECISION) / NULLIF((SELECT COALESCE(SUM(quota), 0) FROM sales_rep WHERE period_start >= :period_start AND period_start <= :period_end), 0)) AS pipeline_coverage

Access: recommended sensitivity tier confidential, access scope owner-scoped. Guidance your policy engine enforces.

From an agent: with the GASP MCP server, call lookup_metric({ "name": "Pipeline Coverage Ratio" }) or generate_query({ "metric": "Pipeline Coverage Ratio", "adapter": "<your adapter JSON>" }).

Benchmarks

  • Below 2x: Insufficient pipeline, high risk of missing quota
  • 2-3x: Light, acceptable for high win rate teams
  • 3-4x: Healthy for typical 25-33% win rates
  • Above 4x: Strong, but may indicate pipeline hygiene issues or low win rates

What It Tells You

Whether there's enough pipeline to hit targets given historical conversion rates.

Connected in the GASP relationship graph.

Upstream: what drives this

Downstream: what this drives

Try searching for:

↑↓navigate↵select