Find what drives outbound pipeline
Pipeline broken down by signal, persona, segment, channel and rep, from the CRM and the outreach records, so the next quarter is planned on what worked rather than on what felt busy.
The conversation
Sample accounts and numbers, for illustrationYouFor this quarter, take every opportunity that came from outbound, trace it to the outreach that created it, and break the pipeline down by signal, persona, segment, channel and rep, with deal count beside value, so I can see what produced pipeline and what only produced activity.
Unify3 checks · CRM, outreach records and mailbox
- Read every opportunity with an outbound source created this quarter from Salesforce, with value, stage and contacts.
- Matched each to the sequence enrollment and the reply that produced it, through Gmail and the outreach record.
- Read the signal, persona, segment, channel and rep on each matched outreach.
Outbound created $2.6m of pipeline this quarter across 64 opportunities. Fifty-nine traced back to a specific outreach; five are unattributed and listed as such.
- $2.6m
- outbound pipeline 64 opportunities
- 59
- traced to outreach
- 5
- unattributed listed, not guessed
- $41k
- average deal
- Week 1 to 4$620k from 18 opportunitiesMostly leadership-change signals worked in enterprise. Email got the reply on 14 of 18.
- Week 5 to 8$1.1m from 27 opportunitiesThe hiring-plus-leader play launched; 11 of the 27 came from it. Calls got the reply on 9.
- Week 9 to 12$880k from 19 opportunitiesWebsite intent with a second signal produced 7; website intent alone produced 1.
Value, dates and sources are read from the CRM and the outreach record. Which combination caused what is the reading, and the deal counts are there so a single large deal does not pass for a trend.
YouBreak it down by the five dimensions and tell me what actually produced pipeline.
UnifyTwo signal combinations, one persona and the email-then-call channel produced most of it. One rep’s number is a territory story, not a method story.
- 1Signal: new leader + hiring$940k · 22 deals
- 2Persona: VP Operations$1.2m · 24 deals
- 3Channel: email reply, then call$1.5m · 33 deals
- 4Segment: mid-market$1.4m · 39 deals
- 5Rep: Ana$1.1m · 25 deals
- Method or territory
- Ana’s pipeline follows the signals her territory produced. Chris, with a third of the signals, converted them at a higher rate. Both facts are in the read.
- Activity without pipeline
- Website intent alone: 1,100 people contacted, one opportunity. Hiring alone in enterprise: 400 contacted, two opportunities. Both were the busiest plays in week 1 to 4.
YouStay on channel: how much came from email, calls and connection requests, and which path produced the most meetings?
UnifyAn email reply followed by a call within two days produced the most meetings and the most pipeline. Connection requests created nothing alone, but they were the first touch on twelve of those 33 deals.
| Channel path | Pipeline | Deals | Meetings |
|---|---|---|---|
| Email reply, then a call within two days | $1.5m | 33 | 58 |
| Email only | $700k | 19 | 31 |
| Call only | $260k | 7 | 12 |
| Connection request only | $0 | 0 | 3 |
The five unattributed opportunities, $140k between them, sit outside every row.
YouNow by persona: who turned into pipeline, and who replied but never became a deal?
UnifyThree personas account for all 59 traced deals. Two others replied often and never became an opportunity.
$1.2m from 24 deals. Half the pipeline from one persona, mostly on the leader-plus-hiring play.
$610k from 16 deals and $650k from 19. Smaller deals, shorter cycles.
140 replies, most of them passing the email to someone else. No opportunity.
95 replies and 11 meetings, no opportunity. Interested, without the budget.
YouTurn this into the plan for next quarter and keep the report running.
UnifyThe plan is one page: three combinations to do more of, two to stop, and the numbers behind each. The breakdown reruns monthly.
Plan · next quarter
More: new leader plus hiring, VP Operations persona, email reply followed by a call within two days. Stop: website intent alone; hiring alone in enterprise. Watch: Chris’s conversion rate applied to a fuller territory. Treat IT manager replies as referrals to the VP, not as leads.
Set up
- Monthly breakdown Outbound pipeline is traced and broken down on the first of each month, and the read is written to the reporting view.
- Plays adjusted The website-visitor play now requires a second signal. The leader-plus-hiring play runs in every territory, not only West.
- Unattributed list kept The five opportunities with no matching outreach stay listed so the source field gets fixed in the CRM.
Pipeline created is what the CRM can support. Closed revenue is not attributed here; the sales cycle is longer than the quarter.
Pipeline drivers, with and without Unify
The quarter ends with a pipeline number. The question is what produced it, so the next one can be planned.
| Without Unify | With Unify |
|---|---|
| Outbound pipeline is one line in the forecast, with no view of what created it | Every outbound opportunity is traced to the outreach, the signal, the persona and the channel that created it |
| Signals, personas and channels are judged by activity, because outcomes are not joined back | Pipeline is broken down by each of those, with deal count beside value |
| The rep with the most pipeline is assumed to have the best method, whatever the territory gave them | Rep results are read against what the territory offered, so method and luck separate |
| Next quarter's plan repeats this quarter's activity, plus ten percent | The read ends in a plan: more of the signal, persona and channel combinations that produced pipeline |
Start from this prompt
Make it your own in Unify, then review the results.
For this quarter, take every opportunity that came from outbound, trace it to the outreach that created it, and break the pipeline down by signal, persona, segment, channel and rep, with deal count beside value, so I can see what produced pipeline and what only produced activity.
What else you can ask for
The walkthrough is one path through this workflow. These are the turns people take most often.
- By channelHow much outbound pipeline came from email, calls and connection requests this quarter, and which combination produced the most meetings?Try in Unify
- By personaWhich personas turned into pipeline this quarter, and which got replies but never became a deal?Try in Unify
- Compare quartersCompare this quarter's outbound pipeline drivers with last quarter's and tell me what changed and why.Try in Unify
How it changes by who you sell to
- Software
- Software outbound runs on many signals at once, and the report should say which ones produced pipeline by segment. Ask for pipeline by signal and segment together, since a signal that works in mid-market often does nothing in enterprise.
- Financial services
- At banks and insurers pipeline is few and large, so one deal can swing a quarter's read. Ask for deal count beside value in every breakdown, and for two quarters rather than one.
- Healthcare
- Health-system pipeline arrives through long cycles, so this quarter's pipeline came from last quarter's outreach. Ask for a 120-day window between outreach and opportunity, and break down by department persona.
- Manufacturing
- Plant deals come from calls more than emails. Ask for pipeline by channel with the call step separated, and by region, since a signal that works in one region reflects one rep's territory.
- Professional services
- Firms produce pipeline through partner-level personas and referrals. Ask for pipeline by persona and by whether the outreach followed a warm path, and keep website intent out of the read if it never converts there.
Next in pipeline intelligence and coaching
+2Activity versus fitCheck whether reps work the right accountsActivity is easy to count. Whether it landed on accounts that fit the ICP and showed intent is the question, and the answer is different for every rep.
+2Coverage gapsFind pipeline coverage gapsCoverage by rep, segment and territory against the number, and the accounts that could fill each gap, so the fix is a list of names rather than a bigger target.- Sequence performanceFind what your best sequences do differentlyReply rates say which sequences win. The steps, timing and audience behind them say why, and that is what the rest of the team can copy.
Connect what this workflow uses
Each guide covers the connection, what Unify reads and writes, and what to check before the first run.
- Connect SalesforceAuthorize Salesforce in Unify, configure CRM field mappings, and choose when to enable writing.
- Connect HubSpotConnect HubSpot to Unify, map Company and Person fields, and plan CRM exclusions and supported write-back.
- Connect GmailConnect Gmail to Unify for sequence emails and replies.
- Connect OutlookConnect Microsoft Outlook directly to Unify.
Questions about this workflow
How does Unify know an opportunity came from outbound?
From the source field on the opportunity in your CRM, and from the match between the opportunity's contacts and the sequence enrollments and replies in Unify. An opportunity with no matching outreach is listed as unattributed rather than guessed.
What does the breakdown include?
Signal, persona, segment, channel and rep, each with pipeline value and deal count. Combinations are shown too, so a signal that works only with one persona is visible.
Does it claim closed revenue?
No. It reports opportunities created and their value, which the CRM supports. Closed revenue depends on the sales cycle and is added only when the cycle is short enough to attribute honestly.
How is this different from signals to meetings?
That page ranks signals by meetings per hundred contacted. This one starts from pipeline value in the CRM and breaks it down across five dimensions, so it answers what to plan rather than what to write about.