neon-rutger/b2b-revops-skills/pipeline-visibility

Pipeline Visibility for B2B Revenue Operations

Pipeline visibility is the ability to see what's in your pipeline, trust that it's accurate, and act on it before it's too late. Most revenue teams have dashboards. Few have visibility.

The difference: dashboards show numbers; visibility drives decisions.

Stage check: do this before anything else in this skill

This skill was written for a company that already has a repeatable motion and named owners. Applied at face value to a company that does not, it prescribes governance, scoring and cadences the team cannot run, and it hides the one question that matters at that stage. Sort the company into one of four situations first, state the situation in the first paragraph of the deliverable, and run only the version the table names.

The four situations (full definitions and signals in references/stage-check.md):

1. Start-up, pre product-market fit: fewer than roughly 30 comparable customers, wins from the founders' network, no measured win rate, cycle time or retention, nobody on quota. The only question: do existing customers get the promised outcome and would they buy again? Run the minimum version, or do not run it.
2. Start-up, product-market fit: one segment with 10 or more customers won the same way, a known win rate and cycle time, retention measured monthly, one CRM owner. Run the skill for that one motion; thresholds are guidance, not rules.
3. Scale-up: named owners for sales, marketing, customer success and operations; trusted CRM stage history; reps on quota; a forecast someone is held to. Run the full skill.
4. Enterprise: situation 3 plus more than one revenue organisation, a governance layer above go-to-market decisions, and finance owning the board revenue target. Run the full skill with the enterprise deltas in the table.

If the evidence is thin, ask three yes or no questions: Is there a segment with 10 or more customers won the same way? Is retention measured monthly? Does someone own the CRM as part of their job? Three no answers means situation 1. One or two yes answers means situation 2. Three yes answers means situation 3 or 4; then ask three more: Is there more than one business unit or region with its own revenue plan and leader? Do go-to-market decisions pass through a formal governance layer? Does finance own the revenue target for board reporting? Two or more yes answers means situation 4; otherwise situation 3.

The full skill applies to both scale-up and enterprise. Not every skill applies at every stage; the table below says what this skill does at each, and "do not run" is a valid answer.

What this skill does per situation:

Skip before product-market fit: Dashboard Architecture; Pipeline Hygiene Automation; Pipeline Intelligence; AI and Automation Patterns; Forecast Accuracy Reporting.

The Visibility Stack

Pipeline visibility has four layers. Most teams only build the first two and wonder why their forecast is wrong.

Layer 1: Pipeline Structure (Foundation)

What stages exist, what they mean, and what data is required at each.

Stage design principles:

1. Each stage has a verifiable exit criterion (not "rep feels good about it")
2. Stages represent buyer actions, not seller activities
3. 5-8 stages maximum (more creates friction and reduces compliance)
4. Probability increases monotonically (if it doesn't, stages are wrong)

Recommended B2B SaaS stages:

Common SaaS defaults. Replace with your historical stage-to-close conversion rates within 90 days of implementation.

Common B2B SaaS defaults. These probabilities carry no formal research backing. Replace with your historical stage-to-close conversion rates (measure actual close rate per stage from closed deals in the past 12 months) within 90 days of implementation. See "Building Your Historical Baseline" below for how to derive these.

Building Your Historical Baseline

Within your first 90 days, calculate your own stage probabilities from closed opportunities:

1. Query all deals closed in the past 12 months (Won and Lost)
2. For each stage, calculate: Deals closed from this stage / Total deals that entered this stage
3. Plot these as your probability curve; use these numbers instead of the common defaults above
4. Update quarterly as your pipeline matures; probability movements signal changes in sales execution or buyer behavior

Layer 2: Pipeline Reporting (What most teams stop at)

Reports and dashboards that show pipeline state.

Layer 3: Pipeline Hygiene (Where accuracy comes from)

Automated systems that keep pipeline data clean, current, and trustworthy.

Layer 4: Pipeline Intelligence (Where decisions come from)

Alerts, signals, and analysis that surface what needs attention NOW, before humans notice it.

Dashboard Architecture

Design Principles

1. One dashboard per audience: executives, managers, and reps need different views
2. Leading indicators first: pipeline created and activities before closed revenue
3. Exceptions over summaries: surface what's wrong, not what's fine
4. Minimal click depth: the answer should be visible without drilling down
5. Consistent time frames: pick a standard (rolling 90 days, current quarter, etc.)

Executive Dashboard

Audience: CRO, VP Sales, CEO Cadence: Weekly review Purpose: "Are we going to hit the number?"

RAG thresholds for Pipeline Coverage:

• Green: ≥3.5x
• Amber: 2.5-3.4x
• Red: <2.5x

n> Based on Clari's vetted pipeline benchmark of 3.2× (2024-2025) and the 3-5× industry range. Note: Ebsta's 2025 GTM Benchmarks (655K opportunities) suggest effective coverage may need to be as high as 5.3× given declining win rates. Calibrate to your historical win rate: required coverage = quota ÷ win rate.

Sales Manager Dashboard

Audience: Front-line sales managers Cadence: Daily Purpose: "Which deals need my attention today?"

Individual Rep Dashboard

Audience: AEs, SDRs Cadence: Daily Purpose: "What should I work on right now?"

RevOps Operational Dashboard

Audience: RevOps team Cadence: Weekly Purpose: "Is the system healthy?"

Pipeline Hygiene Automation

The Hygiene Problem

Pipeline rots silently. Deals go stale, close dates pass without update, amounts stay at placeholder values. Without automated hygiene, your "$5M pipeline" might be worth $2M in reality.

Stale Deal Detection

Definition: An opportunity with no logged activity for a configurable threshold.

Recommended starting thresholds by stage (practice-based):