SalesGSS Newsletter

Revenue Operating Intelligence for B2B Tech Leaders

Systems for Predictable Revenue at $5M–$50M ARR | June 25, 2026

Part 4 of 6 — The Pipeline Decay System™

Verified Pipeline

Subtract What’s Decayed, Single-Threaded, and Unowned — What’s Left Is the Only Number a CRO Can Defend

The Exportable Insight

Most revenue teams report one pipeline number. Elite teams report two — and only trust the second.

Verified Pipeline Ratio = Verified Pipeline ÷ Reported Pipeline

A single metric for how much of your reported pipeline survives inspection — the one number a CRO can put on a dashboard Monday morning. Elite teams work to improve the ratio. Average teams work to inflate the denominator.

Your reported pipeline is a gross figure your company reads as net.

Reported pipeline counts every qualified deal at face value. Verified Pipeline counts only the dollars that survive inspection.

The gap between them isn’t pessimism. It’s the slippage you’ve already booked as coverage — three quarters running.

What’s Actually Happening

For three weeks this series has inspected pipeline quality one failure at a time. Week 1 asked whether the deal was still qualified. Week 2 asked whether the relationship structure could survive. Week 3 asked whether the relationships were actually yours. Three audits, three different ways a deal that reads as “qualified” isn’t.

This week does the arithmetic. Each audit doesn’t just flag risk — it removes dollars. A deal past its “last verified” date isn’t 60% likely; it’s decayed. A deal with one load-bearing relationship isn’t coverage; it’s exposure. A partner-run deal with zero owned relationships isn’t yours; it’s borrowed. Subtract all three from your reported number and what’s left is your Verified Pipeline — the only figure on the board that means what the dashboard says it means.

That’s why it matters: every dollar above Verified Pipeline is being read as real by someone who can’t see the decay. The CRO commits it. The board models off it. The hiring plan is built on it. The dashboard is still reporting a future outcome the underlying deal quality may no longer support.

The Operator Math

Verified Pipeline = Reported Pipeline − Decayed − Single-Threaded Exposure − Unowned

Three subtractions, one rule that keeps them honest: subtract each dollar once. A deal that’s both single-threaded and unowned is a single subtraction — counted at its most severe failure, not twice. Otherwise the math punishes your worst deals double and flatters the number you’re trying to correct.

One clarification heads off the obvious objection. Verified Pipeline intentionally uses a stricter standard than win probability: it asks whether a deal survives inspection, not whether it might still close. The subtraction is a governance exercise, not a probability model. A single-threaded deal isn’t zero percent to close — it’s a dollar your forecast shouldn’t count at full weight until you’ve built the second thread. You don’t delete it; you stop crediting it until it earns its way back.

The Subtraction

Run your reported qualified pipeline through the three audits you already built, in order of severity:

Decay Audit (Week 1). Every deal past its “last verified” date, Qualified State unconfirmed. Subtract.

Thread Audit (Week 2). Of what remains, every deal resting on a single load-bearing relationship. Subtract.

Ownership Audit (Week 3). Of what’s left, every deal with zero owned load-bearing relationships. Subtract.

What survives all three is Verified Pipeline. A worked example on $20M reported:

Start: $20M reported qualified pipeline.

− $3M decayed — past “last verified,” Qualified State lapsed.

− $5M single-threaded — one load-bearing relationship, no second thread.

− $4M unowned — partner-run, zero owned relationships.

= $8M Verified Pipeline.

Verified Pipeline Ratio: 40%.

The other $12M isn’t fraud, and it isn’t gone. It’s unverified — dollars you’re carrying at full weight that haven’t earned it. Ebsta’s analysis of millions of opportunities keeps finding the same thing: most pipeline that enters a quarter committed doesn’t close in it. The subtraction is how you find out which dollars, before the quarter does it for you.

What Elite Teams Do Differently

Average teams defend the reported number. Elite teams defend the verified one. Four principles:

Two numbers, always. Reported pipeline is the input; Verified Pipeline is the output. Show both, forecast off the second. A single number hides the one subtraction that matters most.

Subtract once, at the deepest failure. Decay before single-thread before unowned. A deal failing two audits is counted at its worst, once — so the number stays honest and you fix the deepest problem first.

The gap is the agenda, not the embarrassment. The distance between reported and verified is your highest-leverage list — the exact deals to re-qualify, multithread, or re-thread this week. A 40% ratio isn’t a confession; it’s a work queue.

Verified Pipeline decays too. Run the subtraction on a cadence, not once. Every “last verified” clock, every thread, every owned line resets — so last week’s verified number is this week’s reported number until you re-run it.

Underneath all four is one shift: stop reporting what’s in the pipeline and start reporting what survives inspection.

The Two-Number Test

One question, asked in your next forecast call, before anyone commits:

“What’s our reported number, what’s our verified number — and which one are we putting on the board?”

If they’re the same, nobody has run the subtraction. If the team can’t produce the second number, you’re forecasting off the gross figure and calling it net. The gap is the diagnostic, and it costs you one question.

The Operator Discipline

Four rules. Apply them to your open pipeline this week.

Compute Verified Pipeline before every forecast call. Reported minus decayed minus single-threaded minus unowned, each dollar subtracted once. It’s the number you commit; reported is the number you work down toward it.

Add a Verified Pipeline Ratio to your weekly dashboard. Verified ÷ Reported, one figure. Track the trend — a falling ratio means you’re adding pipeline faster than you’re verifying it.

Forecast off verified, manage off the gap. Commit the verified number. Work the unverified dollars deal by deal, through whichever audit each one failed.

Re-run the subtraction weekly. Verified Pipeline is a snapshot with an expiry date. The three audits feed it; the moment they go stale, so does it.

Forecast off verified. Manage off the gap.

The Verified Pipeline Rule

Reported pipeline is what your CRM says you have. Verified Pipeline is what survives the Decay, Thread, and Ownership audits. A CRO can put a number on a dashboard — but only the second one is safe to defend.

Diagnostic Question

Take your current reported pipeline and run the subtraction once. What’s your Verified Pipeline Ratio — and would you rather learn it now, or on the forecast call where the gap shows up as a miss?

Scaling Signal

A reported number scales effortlessly — every rep adds to it. A verified number doesn’t. Scale headcount and pipeline without scaling the subtraction and you don’t grow coverage; you grow the gap between the number you report and the number that’s real.

Operator Dashboard

🔧 Tool of the Week — The Subtraction. Run your reported qualified pipeline through the three audits in order — Decay, Thread, Ownership — subtracting each dollar once at its most severe failure. What survives is Verified Pipeline. One hour, using the three columns you already built.

📊 Metric That Matters — Verified Pipeline Ratio: Verified ÷ Reported. The share of your reported number that survives inspection. Watch the trend, not the absolute — a ratio falling week over week means new pipeline is outrunning verification.

📈 Benchmark Update — Ebsta × Pavilion’s 2025 GTM data continues to show that deal-level engagement signals — not stage or age — best separate pipeline that closes from pipeline that slips. The subtraction operationalizes that finding: it removes the deals whose engagement has decayed, narrowed, or was never yours.

💡 Implementation Tip — This week, compute one Verified Pipeline number before your next forecast call and bring both figures into the room. The gap is your agenda for the week after — re-qualify the decayed, multithread the single-threaded, re-thread the unowned.

The problem was never that pipeline is dishonest. The problem is that nobody subtracts — so the gross number gets committed as net.

Qualification Decay showed that deals expire. The Single-Thread Death Spiral showed that relationships fail. The Deal You Don’t Control showed that some relationships were never yours. Verified Pipeline does the subtraction — and hands you the one number a CRO can defend.

Next week — The Hidden Pipelines Inside Every CRM: the subtraction leaves you with a smaller, truer number, which makes the next question where growth comes from. The answer is the reverse move — the verified pipeline you already own and aren’t counting, sitting in closed-lost, dormant, and post-sale accounts your reported number never looks at.

Keep Closing,

Steve @ SalesGSS

https://salesgss.kit.com/

→ Forward this to the CRO who just committed a number — then ask what’s left after the subtraction.

Sources

Ebsta × Pavilion — 2025 GTM Benchmarks Report — ebsta.com

Pavilion — Go-to-Market Benchmarks 2025 — joinpavilion.com

Unsubscribe | Update your profile | 600 1st Ave, Ste 330 PMB 92768, Seattle, WA 98104-2246

Built with ConvertKit

​
​