Activity is an input. Pipeline is an outcome
A team can hit every dial, email and task target and still be short on pipeline. When that happens, the problem is rarely effort. It is where the effort is being pointed.
Originally published in GTM Launchpad · expanded for SD Lab V2
What this guide covers
- If activity is green and pipeline is red, the constraint is aim, not effort.
- Activity, aim, opportunity and pipeline are four different things. Most dashboards only show one.
- Five signals tell you it is an aim problem before you raise a single target.
- The Aim Diagnostic: who, why now, why us, what next.
- Inspect account selection and conversation quality before you inspect volume.
Green dashboards, red pipeline
Activity is the easiest thing in outbound to see, and therefore the easiest thing to manage. Dials, sends, tasks completed: all of it is countable by lunchtime. Pipeline is slower, messier and arrives weeks later, so when it comes in light the instinct is to reach for the number you can move today.
That instinct produces a familiar meeting: the activity report is green, the pipeline report is red, and the response is to raise the activity target. The team works harder, the dashboard gets greener, and the pipeline does not move. Nothing about the effort was wrong. The effort was pointed at accounts that were never going to produce a conversation.
High activity is not the problem. High activity against a badly chosen list is. Those look identical on a dashboard and they are completely different problems.
Activity is not opportunity
Four words get used interchangeably in pipeline reviews and they should not be.
- Activity: the actions a rep takes. Countable, controllable, and the weakest predictor of anything on its own.
- Aim: where those actions are pointed. Which accounts, which people, in what order, at what moment.
- Opportunity: whether a real problem exists at that account, at a scale worth solving, with someone who cares about it.
- Pipeline: what happens when aim and opportunity meet a conversation that goes somewhere.
Five signs you have an aim problem
None of these require new tooling to spot. All of them show up in a week of listening and a look at how the list actually gets built.
- A rep cannot explain why a specific account is on today's list. If the answer is that it came from the list, that is not an answer.
- TAM is treated as flat. Every account in the addressable market gets equal claim on attention, which means attention goes to whatever is nearest.
- Personas are too broad. When the target is a title range rather than a role with a problem, the messaging has to be generic to cover the spread.
- Timing and intent signals exist somewhere but change nothing. The data is bought, the dashboard is open, and the sequence still runs the same for everyone.
- Managers inspect volume more than accounts and conversations. What gets inspected is what gets optimised, and volume is the easiest thing to inspect.
The Aim Diagnostic
Four questions. A rep should be able to answer all four about any account before it earns a slot in the day. This is the version we install in live engagements.
- WHO: which accounts and which people deserve attention now, ahead of everything else in the territory?
- WHY NOW: what changed, what triggered, what condition exists that makes this a reasonable moment rather than an arbitrary one?
- WHY US: what problem can we credibly connect to their context, without stretching?
- WHAT NEXT: what is the smallest useful conversation we are actually trying to earn?
If a rep can answer those four, the call has a chance. If they cannot, more dials just spends the day faster.
What to inspect before you raise activity targets
There is an order to this, and activity capacity is last for a reason. Every layer above it multiplies or wastes the layer below.
- ICP and account selection: is the definition tight enough to exclude anything?
- Prioritization: is there a ranked list, or a flat one?
- Persona: is the target a role with a problem, or a title band?
- Signal and timing: do triggers actually change what a rep does today?
- Message relevance: does the outreach connect to their situation or describe ours?
- Conversation conversion: of the conversations that happen, how many go anywhere, and why not?
- Activity capacity: only now. If the six above are sound, more volume is genuinely the answer.
What this looks like in live engagements
Three of the published Field Reports show aim as the starting constraint rather than effort. They are operating context, not proof of a formula.
- FusionAuth: engineering targeting was broad, accounts were not prioritised, and tracking was fragmented enough that outbound execution stayed inconsistent until the system tightened.
- Visual Identity Group: ICP was unclear, the workflow ran manually out of Outlook, and intent data was not being used with any intent.
- S44: a lean build from scratch, where limited capacity makes targeting discipline the difference between a system and a scramble.
Finite attention is the real budget
A rep has a fixed number of meaningful attempts in a week. Not dials: attempts that involve thought. The management question is not whether they are using all of them. It is whether they are spending them on the accounts most likely to produce a conversation worth having.
That reframing changes what a pipeline review sounds like. Instead of asking why the number is down, you ask which accounts got the attention last week and whether they deserved it. The answer is usually specific, and usually fixable without asking anyone to work harder.
Run this before the next quarter's targets
- Pick five accounts from today's list at random and ask the rep why each one matters now.
- Replace the flat TAM export with a ranked list, even if the ranking is imperfect.
- Tighten one persona from a title band to a role with a named problem.
- Name one signal that will change what a rep does the day it fires, then check that it does.
- Have managers review conversations alongside counts, in the same session.
- Trace one week end to end: activity → conversation → meeting → qualified pipeline. The drop-off tells you which layer to fix.
Related reading
More activity is not a strategy. Find the actual constraint.
The Revenue Rebuild starts by diagnosing where attention is going before it touches a single target. If activity is green and pipeline is not, that is where we start.