GM! I reckon you’re going to like this one…
Pipeline coverage can look healthy while the forecast is already
compromised.
The problem usually isn't the headline number.
It's the mix underneath it.
A team reports 3.4x coverage. Leadership relaxes. Managers push reps to
keep creating. Marketing celebrates sourced pipeline. SDRs hit
opportunity targets.
Then the quarter slips.
The late-stage deals that should have carried the number were thin. New
opportunities were accepted too early. Several "pipeline created"
accounts had no clear business problem, no active buying process, and no
owner beyond a curious champion.
The dashboard wasn't wrong.
It was incomplete.
Most pipeline reviews treat opportunity value as if source quality is a
footnote.
A $50K inbound demo, a $50K outbound account with confirmed pain, a
$50K partner referral with executive access, and a $50K event lead
with vague curiosity all show up as $50K.
Operationally, they are not the same asset.
If leaders want fewer forecast surprises, they need to inspect not just
how much pipeline exists, but what kind of pipeline is being created.
Source is not just attribution. It is a risk profile
Source reporting often gets trapped in attribution debates.
Marketing wants credit. Sales wants credit. Partners want credit. RevOps
gets pulled into source definitions, influence rules, and dashboard
logic.
That work matters.
But it isn't enough.
A source field should not only answer:
"Who gets credit?"
It should also help answer:
"What operating risk does this opportunity carry?"
Different sources tend to create different failure modes:
Inbound can create urgency when the buyer has already named the
problem, but it can also include low-authority research trafficOutbound can create strong ICP fit, but weak timing if the buyer
did not have an active initiativePartner referrals can create access, but not necessarily
ownership of the buying processEvents can create volume, but often need heavier qualification
before sales accepts the opportunityCustomer expansion signals can show high intent, but only if
usage, value, and account health support the handoff
None of those sources are good or bad by default.
They just carry different risks.
And different risks need different inspection.
Use a source-quality ledger
A simple source-quality ledger separates pipeline creation from pipeline
confidence.
For each new opportunity, track five fields:
1. Source type
Inbound, outbound, partner, event, referral, expansion, executive intro,
product signal, or other.
2. Problem evidence
What business problem has the buyer actually confirmed?
Weak:
"Interested in a demo."
Better:
"Manual routing is delaying speed-to-lead, and the VP Sales has asked
RevOps to fix it before the next hiring wave."
Interest is not the same as a problem worth solving.
3. Authority path
Who owns the decision, who influences it, and who is currently engaged?
A source that gives you a user champion is different from one that gives
you the budget owner.
4. Timing evidence
Why now?
Budget cycle. Failed incumbent. Board commitment. Hiring plan.
Compliance deadline. Expansion trigger. Renewal event. Operational pain.
Named internal project.
If there is no credible reason to act now, timing risk is already in the
deal.
5. Next buyer action
What has the buyer committed to doing next?
A meeting booked by the seller is weaker than a buyer agreeing to bring
the problem owner, share current process detail, or confirm evaluation
steps.
This ledger changes the review from:
"How much pipeline did we create?"
to:
"Which sources are creating opportunities with enough evidence to
deserve our confidence?"
That is a much more useful question.
Build acceptance gates by source
Opportunity creation targets create bad behaviour when every booked
meeting can become pipeline.
The answer isn't more bureaucracy.
It's acceptance gates that match the source.
For example:
Inbound demo: Accepted only when the buyer confirms a business
problem, role, and reason for evaluating nowOutbound-generated: Accepted only when there is ICP fit, problem
acknowledgement, and a second-step meeting with a relevant
stakeholderPartner referral: Accepted only when the partner provides buyer
context, an access path, and a reason the account is active nowEvent lead: Accepted only after a post-event conversation
confirms problem, authority path, and next actionExpansion signal: Accepted only when usage and account health
support commercial timing, and CS agrees there is expansion
readiness
The gate should be simple enough that reps can use it.
But strong enough to stop weak interest from becoming pipeline simply
because someone needed to hit an opportunity target.
Review source cohorts, not just source totals
Source dashboards usually show created pipeline, meetings, conversion,
and revenue.
Useful.
But late.
Add cohort inspection.
For opportunities created in the last 30--45 days, review by source:
How many moved past discovery with buyer-confirmed problem evidence?
How many added a second stakeholder?
How many reached proposal with an economic buyer involved?
How many slipped with no buyer-owned next step?
How many were closed-lost for no decision, no budget, or bad timing?
This tells you whether the source is creating real buying motion or just
early-stage CRM volume.
A source can create plenty of pipeline and still be low quality if most
opportunities stall before buyer evidence improves.
A smaller source may be far more valuable if it reliably creates
accounts with authority, urgency, and clean next steps.
Volume tells you how much entered the system.
Quality tells you how much deserves to stay there.
Weekly action
Pull every opportunity created in the last 30 days.
Group them by source.
For each opportunity, add four simple labels:
Problem evidence: clear / weak / missing
Authority path: clear / partial / missing
Timing evidence: clear / weak / missing
Next buyer action: buyer-owned / seller-owned / vague
Then calculate nothing fancy.
Just count how many opportunities in each source have all four labels at
clear or buyer-owned.
That is your source-quality view.
Use it in the next pipeline review before you celebrate coverage.
Pipeline creation is not the goal.
Pipeline that survives inspection is.
— Pipeline Playbook