Open your forecast. Find the row for champion-sourced pipeline.
Most RevOps teams cannot, because there isn’t one. The deals exist, reps work them, some of them close. But they were logged as outbound, or inbound, or whatever the rep picked from the dropdown that morning. The motion has no row, so it has no number, so at planning time it has no budget.
That is a measurement problem, not a performance problem. Deals that start with a champion who already bought from you close at a 2.7x higher probability, in roughly half the sales cycle. A source that performs like that should be a named line in the forecast, not a rounding error inside general outbound.
Here is how to instrument it.
Why it deserves its own category
A forecast category earns its place when it behaves differently from the categories around it. Champion-sourced pipeline does, in three ways that matter to anyone building a model.
It converts differently. You have a 60 to 70% chance of selling to an existing relationship, against 5 to 20% for a new prospect. Blending those two into one outbound number gives you a conversion rate that describes neither.
It closes on a different clock. Roughly half the cycle length changes how the pipeline ages. If your stage-duration assumptions come from cold deals, every champion-sourced deal in the model looks stalled when it is actually early.
Its supply is predictable. This is the part most teams miss. Cold outbound volume is a function of headcount and effort. Champion-sourced volume is a function of how many relationships you already have and how fast people move, and people move at a steady rate: 2 to 3% of B2B contacts change jobs every month. That is a supply curve you can actually forecast, which is rare.
The catch is that the supply is invisible by default. Only about 6% of customer contacts tell a vendor they changed jobs. The other 94% move without telling anyone, so if your only detection method is a rep noticing, you are measuring 6% of the channel and concluding it is small.
The six metrics to report
Keep the set small enough that it fits on one slide and survives a quarter.
1. Detected moves per month. The raw signal count: how many contacts in your CRM changed jobs. This is your top of funnel, and it should track close to the 2 to 3% monthly rate against your contactable database. If it does not, your detection is the problem, not your market.
2. Signal-to-touch rate. Of the detected moves, what percentage got worked within your SLA. This is the single most diagnostic number in the set. A high detection count with a low touch rate means you bought a signal and threw it away, and it is the most common failure mode in this motion.
3. Time to first touch. Measured in days from detection to outreach. The window matters because a buyer in a new seat is choosing tools early, and that window closes. Track the median, not the average, so one ignored lead from last quarter does not hide a good week.
4. Champion-sourced pipeline created. Dollar value of opportunities where the originating contact was a tracked job change. This is the number that wins the budget argument, and it only exists if you stamped the source correctly at creation.
5. Win rate and cycle length, split out. Report these against your blended numbers side by side. The gap is the entire case for the channel. If your own data does not show a gap, you want to know that before you scale the motion, not after.
6. Coverage. What share of your customer and closed-won contacts are actually monitored. Pipeline you never had a chance at is not a performance miss, it is a coverage gap, and the two get confused constantly in QBRs.
Two metrics deliberately left off: anything about champions who told you they moved, which is self-selection and tells you nothing, and raw email open rates, which will look great on warm outreach and tempt you to declare victory well before revenue.
Instrumenting it in the CRM
The metrics above are all downstream of one decision: stamping the source at the moment the lead is created. Get that wrong and you spend the next two quarters reconstructing attribution by hand.
- Add a dedicated source value. Not a note, not a campaign tag a rep can overwrite. A distinct picklist value on lead and opportunity, set programmatically, so champion-sourced pipeline can be filtered without anyone’s cooperation.
- Keep a pointer to the original relationship. Record which existing contact the move came from, and which account they left. Without it you cannot answer the obvious follow-up: which customers generate the most downstream pipeline when their people move.
- Preserve the detection timestamp. Store when the move was detected, separately from when the record was created. Metrics 2 and 3 are impossible to compute without it, and it is the field teams forget.
- Route to the relationship, not the territory. The rep who knows the person should get the lead. This is a routing rule, but it is also a measurement decision, because misrouted warm leads get worked cold and quietly destroy the win-rate gap you are trying to prove.
- Hold the full picture. Report departures alongside arrivals. A champion leaving a customer account is a churn signal your CS team should be working, and it belongs in the same instrumentation even though it never shows up as new pipeline.
Steps 1 through 3 are a half-day of admin work. Step 4 is a routing conversation. The hard part is none of these: it is the detection that feeds them, which is why most teams stall before metric 1.
Sizing the channel before you build it
You can estimate the supply before you commit to the motion, which makes this an easy business case to pressure-test.
On a 10,000-contact CRM, roughly 20% surface as hot leads on day one. That is about 2,000 people who already know your product sitting in seats you are not currently selling to. After that initial backlog clears, expect 200 to 300 new warm leads every month as the 2 to 3% rate keeps running.
Run your own blended opportunity rate and average deal size against those numbers and you have a defensible forecast line. Use your blended rate, not the 60 to 70% relationship figure, for the first pass. If the motion works, the gap shows up in metric 5 and the model gets better next quarter. A conservative case you beat is worth more than an optimistic one you miss.
Worth adding to the same business case: the detection also repairs the database. The contacts moving out of your CRM are the same contacts rotting in it, which is the data decay problem most RevOps teams are already paying someone to clean up.
Where the data comes from
All six metrics depend on detecting moves reliably across your whole contact base, not on the 6% who write in. Champions watches the contacts already in your CRM and writes the move back into Salesforce, HubSpot, Pipedrive, Zoho and others, with the source stamp, the originating relationship and the detection timestamp already populated. There is no app to install and no logins for reps, which matters for measurement: a signal that requires reps to log into a second tool produces an attribution gap by design. That write-back is the whole point of the RevOps use case. For how the available tools compare on detection, see the job change tracking comparison.
Because the channel is measurable, we are willing to be measured on it. Champions backs the signal with a contractual ROI guarantee: if champion-sourced revenue does not reach 2x your annual service fee, you are covered under our terms. Among the compared tools, only Champions puts that in writing.
Make it a row
An unnamed channel cannot be funded, staffed or defended. Give champion-sourced pipeline a source value, a detection timestamp and six metrics, and within a quarter you will know what it is worth, in your numbers rather than anyone else’s.
Want to see the supply side before you instrument anything? Book a demo and we will run it against your own CRM live, then show you how many of your contacts have already moved and what that backlog is worth. Prefer to ask a question first? Email [email protected] and a human will answer.
