Most teams describe their sales development process as a sequence. A sequence is one stage of it. What happens before the first email decides more about the outcome than the email does, and what happens after the meeting is booked decides whether the meeting was worth booking.
Six stages, each with one thing a manager can inspect. If a stage has no inspection point, it is not a process step, it is a hope.
1. Select the account
The reps do not choose. The system does, from the ICP and a tier.
Selection failures are invisible because they look like message failures: a perfect email to the wrong company produces the same silence as a bad email to the right one. Teams then rewrite the email.
Inspect: pull ten accounts a rep worked last week and check each against the ICP, including the disqualifiers. If more than two fail, the problem is upstream of everything else the team is doing.
Related: ICP development workshop.
2. Read the signal
An account on the list is not an account to call today. Something has to make it current: a funding event, a leadership hire, a job posting for a role your product touches, a competitor mention, a technology change.
Two rules make signal usable:
- A signal has a decay window. Define it per signal type. A leadership hire
is live for a quarter; a job posting for weeks; a website change for days. Most teams never set the window and work triggers that went cold.
- A signal without an action is noise. If nobody can say what you do
differently because of it, stop paying for it.
Inspect: ask a rep why this account, today. If the answer is "it was next on the list", the signal stage does not exist.
3. Research the hook
Five minutes, one hook, written down. The output is a single specific sentence that could only be said to this account.
The common failure is depth without a decision. A rep reads the 10-K, the founder's podcast, and three press releases, and still opens with "I saw you are growing fast." That is thirty minutes producing nothing.
Inspect: read the hook without the account name attached. If you cannot tell which company it is for, the research did not happen.
4. Make the first touch
Now the sequence. Channel mix, cadence, and volume belong here, and only here.
Two things that matter more than the copy:
- Timing against the signal. A touch inside the decay window beats a better
touch outside it.
- Whether the sequence was sent by a human at all. A rep who never edits
the drafted message is not running a sequence, the tool is.
HubSpot's framing of a sequence as a defined series of touches over a set period is the useful one: the series and the period are both design decisions, not defaults.
Inspect: pull one sequence a rep sent and one they received a reply to. Compare the first line.
Related: the first ten seconds of a cold call and cold calling tips.
5. Qualify
The stage most often skipped under quota pressure, and the one that determines whether the pipeline is real.
Qualification is not an interrogation against a framework. It is finding out whether there is a problem worth solving, someone who owns it, and a reason to act this quarter. BANT, MEDDIC, and the rest are checklists for what to learn, not scripts for how to ask.
Count the disqualifications. A team that never disqualifies is not qualifying. If a rep booked twelve meetings and disqualified nobody, the twelve are suspect.
Inspect: for each booked meeting, the one sentence describing the problem the prospect has. If it is generic, the meeting will be too.
6. Hand off
The stage nobody owns, which is why it fails.
A good handoff carries what the AE would otherwise rediscover in the first ten minutes: the trigger, the hook that worked, the problem stated in the prospect's words, who else was mentioned, and what was promised.
Salesforce puts the split plainly: SDRs open conversations and account executives close them. The seam between the two is where context is lost.
Inspect: meeting-held rate, not meetings booked. Then whether the meeting produced a real next step. Those two numbers grade this stage and stage five together.
Related: revenue alignment.
Where the process usually breaks
In order of how often, and how invisibly:
- Selection, because it fails silently and looks like a messaging problem.
- Handoff, because no single person owns it.
- Qualification, because quota pressure eats it first.
- Signal, because the decay window is never defined.
Messaging gets rewritten constantly and is rarely the actual constraint.
How this maps to the standard
The six stages sit across the pillars of the Tenbound Pipeline Architecture Standard: selection is Market, signal is Signal, research and first touch are Message, sequence and handoff are Motion, coaching the whole thing is Mastery, and the inspection points are Measurement.
Place your team on the ladder with the maturity model, then read SDR training for the curriculum that makes each stage executable.
Free to copy into your own process doc. The one ask is attribution.