L6. Follow-up
Outputs doc: outputs.md, L6 section. Fill it in as you work through the steps below. Raw progression data and trust conversations go in captures.md. L7 reads the L6 section before starting.
Jump to: Diagnostic · Step 1 · Step 2 · Step 3 · Step 4 · Step 5 · Step 6 · Step 7 · Summary · Assumption sweep
What this layer is: The structured path that carries a captured lead from first contact to sales-ready, without selling. It is the layer between the lead L5 produced and the deal L7 helps close, and its whole job is to move a person who raised their hand but is not ready to buy across the gap to where a sales conversation makes sense. This is where the promise from L2 gets proven or thrown away, and it is where selling happens without selling: you earn the next step by being useful and trustworthy, not by pitching early. The output is a deliberate sequence of touches, each with a purpose, plus a way to tell when a lead has actually become ready, so the handoff to sales is a warm lead and not a cold name.
Why it comes after L5 and before L7: L5 captured leads and told you which ones are qualified and which are fit-but-cold. L6 is what happens to those people next: the nurture that turns interest into readiness. It cannot run before L5, because follow-up has nothing to follow up without captured leads. And it must come before L7, because sales enablement arms a salesperson to convert a sales-ready lead; if L6 hands over leads that are not actually ready, the best sales materials in the world are being pointed at people who are not listening yet. Most of the real work here is beating the L1 blocker, the inertia that L1 named and L2 had to argue against. A lead does not go quiet because they forgot you; they go quiet because doing nothing is still winning. Follow-up is the sustained, patient case against doing nothing, made through usefulness rather than pressure. If leads consistently stall and never reach sales, the cause is sometimes a weak sequence here, but it is just as often a lead that was never really qualified in L5 or a value proposition that never beat inertia in L2.
What finishing this layer produces: A written follow-up system in the L6 section of outputs.md: a clear definition of sales-ready, a map of what has to change in the lead’s mind to get there, a sequence of value-first touches built to close that gap and answer the L1 blocker, a progression model that signals when a lead is ready, and the identified stall point with its fix. Backed by a live run with real leads, not by a drip sequence that was never measured.
Diagnostic: is L6 actually done?
Before building anything, answer these questions in writing. Vague answers mean the layer is not finished.
1. Have you defined what sales-ready actually means, the bar a lead clears before sales gets them? Not “they seem interested.” A specific, observable bar: what the lead believes, has done, and has signalled that says a sales conversation is now warranted. If sales-ready is a feeling, the handoff to L7 will be a guess, and sales will get people who are not ready.
2. Do you know what has to change in the lead’s head between first contact and ready? A captured lead is curious; a sales-ready lead trusts you, believes the L2 claim, feels the cost of inaction, and, in B2B, has begun to bring others along. If you cannot name the specific shifts follow-up has to produce, your sequence is touches without a destination.
3. Is there a structured sequence where each touch has a purpose, or do leads get a generic drip and otherwise get forgotten? The two most common failures are opposite: a bland automated drip that adds no value, and simply going silent after first contact. If you cannot say what each touch is for and which shift it produces, you have activity, not a system.
4. Does the follow-up prove the L2 promise and answer the L1 blocker, without pitching too early? Selling without selling means earning the next step by being useful. If the sequence pitches the product in touch one, or never makes the case against doing nothing, it is either too pushy to trust or too soft to move anyone.
5. Can you tell when a lead has become sales-ready by a signal, not a hunch, and is the handoff to L7 clean? If readiness is judged by gut, good leads get passed too early and cold ones get passed at all. There should be an observable trigger that advances a lead, and a defined moment and method for handing them to sales.
If you answered all five clearly and in writing, L6 may already be done. Jump to the L6 section of outputs.md, fill in the fields, check the checklist, and move to L7. If not, work through the steps below.
Step 1. Pull the inputs from L5 (and above)
Duration: 30 minutes
L6 does not start from a blank page. It starts from the leads L5 captured, the bar they did or did not clear, and the blocker L1 named that follow-up now has to beat. The fastest route to a working sequence is to design backward from where the lead needs to end up, using L5’s qualification work as the starting line and L2’s proof as the ammunition.
What to do:
-
Open the L5, L2, and L1 sections of
outputs.mdand copy the following into the “Inputs from L5 and above” field in the L6 section:- From L5: the qualified leads and the qualification bar, the fit-but-cold leads and their routing, the offer and what the lead already received, the measured funnel rates and the bottleneck, and each lead’s source channel and awareness level. Follow-up continues the conversation L5 started; it must know what the lead already took and how warm they arrived.
- From L2: the final value proposition, the proof buyers said they would need, and the alternative it beats including doing nothing. The sequence proves this claim and argues against this alternative.
- From L1: the blocker, the buying context (who else has to be brought along), and the decision the lead faces. Beating the blocker is most of follow-up’s job, and the buying context decides whether the sequence has to help the champion sell internally.
-
Write one sentence: “These leads took [offer] in [channel], arriving [warm or cold]; to become sales-ready they have to move from [current state] to [ready state], and the main thing in the way is [the L1 blocker].” It frames the whole layer as a gap to close.
-
If L5’s qualified leads barely clear the bar, or the bar was set low to flatter the numbers, that weakness lands here: follow-up will be nurturing people who were never really fit. Note it in the L6 scope notes in
outputs.mdand log it inassumptions.md(Layer: L6, Status: Untested). If the leads are mostly unqualified, the honest move is to fix the bar in L5 before building a sequence on top of it.
Step 2. Define sales-ready, the exit
Duration: 30-45 minutes
Follow-up is a journey with a destination, and you cannot design the journey until you have named the destination. Sales-ready is the precise state a lead is in when handing them to a salesperson is justified: not merely interested, but trusting enough, convinced enough, and intent enough that a sales conversation will land. Defining this first, before the sequence, is what keeps follow-up from running forever or ending too soon. It is also the single thing L7 most needs from this layer, because it is the definition of who sales should and should not get.
What to do:
-
In the L6 section of
outputs.md, under “Sales-ready definition,” write the bar as observable criteria, not feelings. Build it across the dimensions below and fill the table (it is also inoutputs.md). A lead is sales-ready when it clears the bar on all the rows that matter for your case.Dimension What sales-ready looks like How you would observe it Trust (believes you, not just aware of you) Belief in the L2 claim (over the alternative) Urgency (the blocker is cracking) Buying-group progress (others being brought along) Explicit intent (a signal they want to talk) -
Make each criterion observable. “They trust us” is not observable; “they replied to two touches and asked a substantive question” is. “They have urgency” is not; “they mentioned a deadline or a recent painful incident” is. The whole point of the definition is that someone other than you could look at a lead and agree it is or is not ready.
-
Set the bar at the level where a sales conversation has a real chance, judged against the L1 segment and the L2 claim. Too low and L7 inherits people who will waste the salesperson’s time and sour the handoff; too high and leads sit in nurture forever while competitors talk to them. The right level is where the cost of a sales touch is justified by the odds.
-
The criteria are a hypothesis about what predicts a good sales conversation until the data shows otherwise. Log the sales-ready bar in
assumptions.md(Layer: L6, Status: Untested). Step 6 and L7’s later results show whether leads clearing this bar actually convert.
Step 3. Map the gap from first contact to ready
Duration: 45 minutes
Between the captured lead and the sales-ready lead is a gap: a set of things that have to change in the person’s mind and situation. Naming these is what turns a sequence from a random series of emails into a path with a job at each step. Most of the gap is the L1 blocker in disguise: the reasons the lead is not acting are the reasons doing nothing still wins, and follow-up’s touches exist to erode them one at a time.
What to do:
-
In the L6 section of
outputs.md, under “The gap to close,” fill in the table below (it is also inoutputs.md). For each shift the lead has to make, note the current state, the ready state, and what would actually move them, pulling directly from the L1 blocker and the L2 proof buyers said they would need.Shift the lead has to make Current state (why they are not ready) Ready state What moves them (proof, insight, experience) From unsure they can trust you From doubting the L2 claim From “doing nothing is fine” From deciding alone to bringing others (B2B) -
Anchor the “doing nothing is fine” row on the L1 blocker, because it is usually the largest part of the gap. If the blocker was “the current mess is survivable and nobody owns the fix,” follow-up has to make the cost of the mess visible and give the champion a reason and a way to own the fix. The touches that close this row are the most important in the whole sequence.
-
For the buying-group row, use the L1 buying context. If the champion you reached cannot authorise the purchase, part of follow-up’s job is to arm them to convince the economic buyer, which previews L7. Note what the champion would need (a number for the founder, a one-pager, a risk answer) to take the case upward.
-
Mark which shift is the hardest and most decisive for your segment. That shift is where the sequence should spend the most touches and the strongest proof. A sequence that spreads evenly across easy and hard shifts under-invests in the one that actually stalls people.
-
Each “what moves them” is an assumption until a lead confirms it. Whether a particular proof or insight actually changes the lead’s mind is what Step 6 tests. Log the moves you are least sure of in
assumptions.md(Layer: L6, Status: Untested).
Step 4. Design the follow-up sequence
Duration: 60-90 minutes
Now build the sequence that carries the lead across the gap. Each touch exists to produce one of the shifts from Step 3, delivered as something useful rather than a pitch. This is the craft of selling without selling: you earn attention and the right to the next step by teaching, proving, and helping, so that by the time a sales conversation happens the lead is already most of the way there. A good sequence is patient and value-dense; a bad one is either a bland drip that adds nothing or a series of “just checking in” nudges that ask for the sale without earning it.
What to do:
-
In the L6 section of
outputs.md, under “Follow-up sequence,” map the touches in the table below (it is also inoutputs.md). Each row is one touch. Tie every touch to the shift from Step 3 it is meant to produce; a touch that closes no gap should not exist.Touch Shift it produces (from Step 3) Format and channel Timing or trigger What the lead gets from it -
Lead with value, not the product. Early touches should teach the lead something true and useful about their own problem (the cost of the gap, how the best teams handle it, a benchmark, a relevant story), which both builds trust and quietly proves the L2 claim. The product enters as the obvious answer once the problem is well understood, not before. Teaching the buyer something they did not know is one of the most reliable ways to earn trust without pitching.
-
Make the case against doing nothing explicitly, somewhere in the middle of the sequence. Show the cost of the status quo in concrete terms, ideally through a story of someone like them who waited and what it cost, or who acted and what changed. This is the touch aimed squarely at the L1 blocker, and it is the one most sequences omit because it feels less comfortable than talking about features.
-
Set the cadence deliberately: enough touches to stay present through a slow decision, spaced so you are useful rather than annoying. The right number is more than most people send and fewer than a daily barrage; the test is whether each touch would be welcome on its own merits. Branch the sequence on behavior where you can: a lead who engages gets a faster, warmer path; a lead who goes quiet gets a lighter, longer one.
-
Design the path for the fit-but-cold leads L5 routed here, not just the hot ones. These are L6’s long game: people who are right but not ready. They need a slower, lower-pressure nurture that keeps you present and useful until their trigger arrives, plus a re-engagement touch and an honest exit for those who never warm. Note this track separately.
-
Build the anti-touch list. Some touches are tempting and quietly corrosive. Capture them in the table below (also in
outputs.md).Tempting touch Why it looks fine Why it hurts Common entries: the “just checking in” email that gives nothing, the early hard pitch that breaks trust, the touch that adds no value and only asks, and the over-frequent cadence that trains people to ignore you. Naming them keeps them out when the pressure for pipeline rises.
-
The sequence is a set of bets about what moves leads until it runs. Log the sequence design, especially the cadence and the anti-doing-nothing touch, in
assumptions.md(Layer: L6, Status: Untested).
Example (continuing the L0 to L5 example):
Leads took the deal-decay teardown on LinkedIn. The sequence: (1) deliver the teardown with one surprising benchmark, building trust; (2) a short piece on why rep discipline always decays, proving the L2 claim without pitching; (3) a customer story of a VP who waited two quarters and counted the lost deals, aimed at the blocker; (4) a two-minute look at how the cadence runs on its own and reps cannot quietly ignore it, answering the founder’s specific fear; (5) a one-pager the VP can forward to the founder, arming the champion; (6) an invitation to a working session once they engage. Fit-but-cold leads get touches 1 to 3 spaced over weeks, then a quarterly useful check-in. Anti-touches: “just following up on my last email,” and a feature-list pitch in touch one.
Step 5. Build the progression model
Duration: 45 minutes
A sequence moves leads; the progression model tells you that it is working and when a lead has arrived. It is how you separate a lead who is drifting through touches from one who is genuinely warming, and how you know the precise moment to hand someone to sales. Without it, follow-up either passes leads on a hunch or never passes them at all. The model reads behavior against the sales-ready bar from Step 2 and the shifts from Step 3, and turns them into a signal anyone can act on.
What to do:
-
In the L6 section of
outputs.md, under “Progression model,” fill in the table below (it is also inoutputs.md). List the observable signals that a lead is advancing, what each one suggests, and what it should trigger. Pull fit signals from L1 and readiness signals from your Step 2 definition.Signal (observable behavior) What it indicates Score or weight What it triggers -
Separate engagement from readiness. Opens and clicks show attention, not intent; replies, substantive questions, pricing or implementation queries, and forwarding to a colleague show readiness. Weight the readiness signals far more heavily. A lead can open every email and never be ready; a lead who asks “how would this work for a team of three” in one reply may be closer than all of them.
-
Define the advance triggers precisely. Name the signal or combination that moves a lead from cold to active nurture, and the one that marks them sales-ready and hands them to L7. The sales-ready trigger should map directly to the Step 2 bar, so the handoff is the bar being cleared, not a mood.
-
Define the other exits too. A lead who stalls goes to the slow fit-but-cold track; a lead who signals they are wrong-fit or asks to stop is exited honestly. A clean exit is part of the model, not a failure of it: holding dead leads in an active sequence wastes effort and erodes your sender reputation and goodwill.
-
Keep the model as simple as it can be while still predicting readiness. An elaborate scoring system that nobody trusts is worse than three clear triggers that everyone acts on. Start simple; let the Step 6 data tell you which signals actually predict a good sales conversation.
-
The predictive power of each signal is an assumption until the run and L7’s results confirm it. Log the model, especially the sales-ready trigger, in
assumptions.md(Layer: L6, Status: Untested).
Step 6. Run the sequence and find the stall
Duration: 2-6 weeks calendar time, depending on the decision cycle | Target: enough leads through the sequence to see where they stall
A follow-up system is a hypothesis until real leads move through it. Step 6 runs the sequence with the leads L5 is producing, measures how many progress and how far, and finds the stall: the point where leads stop advancing toward sales-ready. You are looking for where trust fails to build, where the L2 claim fails to land, or where the case against doing nothing fails to bite. And as in every layer, when leads stall you have to judge whether the fault is the sequence (an L6 fix) or something upstream: leads that were never qualified (L5), a value proposition that never beat inertia (L2), or an audience that does not really have the problem (L1).
There are two halves to L6 validation: the progression data (how leads move) and conversations with leads about what built or failed to build their trust and readiness (why they move or stall). The data finds the stall; the conversations explain it.
6a. Run the sequence and measure progression
Duration: the bulk of the time
Put the real leads from L5 through the sequence and instrument it. Because B2B decisions are slow, give it enough calendar time that leads can realistically progress, and do not judge a long-cycle sequence on a week of data.
What to measure:
- How far each lead progresses through the gap from Step 3, not just opens. Use the progression signals from Step 5 to place each lead.
- The share of leads that reach sales-ready, and how long it takes them (time-to-ready). A sequence that produces ready leads slowly is different from one that produces few, and the fixes differ.
- The stall point: the touch or shift where most leads stop advancing. This is the equivalent of L5’s bottleneck, and it is where you work first.
- The quality of leads reaching sales-ready: when L7 and sales get them, do they hold up, or were they passed too early? This closes the loop on the Step 2 bar.
Find the stall and name it specifically: not “the sequence underperforms” but “leads engage through touch three and go quiet at the case against doing nothing,” which points at a specific shift and a specific fix.
6b. Ask leads what built or broke their readiness
Duration: light, a handful of short conversations
The progression data shows where leads stall; conversations show why. Talk to a few who reached sales-ready and, more valuably, a few who stalled or went quiet. Recruit from the same leads, and keep it honest and low-pressure, in keeping with the layer.
What to ask those who progressed:
- What in the follow-up made you take it more seriously? Was there a moment it clicked?
- What nearly made you tune out?
What to ask those who stalled:
- You engaged early and then went quiet. What changed, or what got in the way?
- Was there anything you needed to hear that you did not?
- Be honest: was it the timing, the trust, the case for changing, or just not a priority?
You are listening for whether the stall is a fixable L6 problem (a missing proof, a weak case against doing nothing, wrong cadence) or an upstream signal (they never really had the problem, the value never landed, they were not qualified). That judgement decides whether you revise the sequence or go back a layer.
6c. Capture immediately after the run and conversations
Do this while the data and quotes are fresh. Add entries to the L6 section of captures.md using this structure:
Sequence run [number] | Lead source + offer:
Dates / number of leads:
Progression (how far leads got, by shift; share reaching sales-ready; time-to-ready):
The stall point (which touch or shift leads stop at):
Quality of sales-ready leads (did they hold up in L7 / sales?):
---
Lead conversation [number] | Progressed / stalled:
Lead (role, segment fit):
What built or broke their readiness (verbatim):
What they needed and did not get (verbatim):
Is the stall an L6 fix or an upstream signal?:
Surprises (anything you did not expect):
Any L6 assumptions this confirmed or challenged:
The progression-by-shift data and the verbatim “what I needed and did not get” are the most valuable output. The first locates the stall; the second tells you whether to fix the sequence or go back a layer. Capture both exactly.
6d. Synthesise and fix the stall
Do this once enough leads have moved through. Go through your captures in captures.md and update the Sequence synthesis fields in the L6 section of outputs.md, covering:
Progression vs the gap. Which shifts from Step 3 did the sequence actually produce, and which did it fail to? Map the drop-off to specific shifts, not just to touches. A stall at a shift tells you what is missing better than a stall at a touch.
The stall and its likely cause. Name the point most leads stall and what the conversations suggest is behind it. Be specific about L6 versus upstream: a missing proof or weak anti-inertia case is an L6 fix; leads who never had the problem or never believed the value are not. This judgement is the most important output of the layer.
Time-to-ready and patience. How long did ready leads take, and is your cadence and sequence length matched to that reality? B2B follow-up often fails by quitting too early, going silent before the slow decision matures.
Sales-ready quality. Did the leads that cleared the Step 2 bar hold up when sales got them? If they did not, the bar is too low or the wrong signals are weighted; tighten Step 2 and Step 5. If sales wanted more of them, the bar may be too high.
Is the constraint upstream. If leads stall at a shift no sequence change improves, and conversations point to people who do not really have the problem or never bought the value, the constraint is above L6. Say so and go back. The loud stall in follow-up is often a quiet fault in L5, L2, or L1.
The fix and the re-test. State the one change you are making to the stall point and what you expect it to do, then re-run. One change at a time.
After synthesis, mark the relevant rows in assumptions.md as Validated or Invalidated, and note what the evidence showed. If the system was invalidated by an upstream cause, fix it there, not in the sequence.
6e. If you genuinely cannot run a live sequence
If you cannot run the sequence with real leads in the time available, reduce the unknowns and mark the gap.
- Run a manual version. Send the touches by hand to the handful of leads you do have. Hand-sent follow-up to ten real leads teaches more than an automated sequence to nobody.
- Walk the sequence past people in the segment. Show a few segment-fit people the sequence and ask which touches would build trust and which would make them tune out. Trust problems surface even without a live run.
- Pressure-test against the blocker. For each touch, ask honestly whether it gives a lead a reason to act against the L1 blocker, or just asks for their time. Cut the ones that only ask.
Document each in the L6 section of captures.md, noting it is secondary. Log the absence of a live run as an assumption in assumptions.md. A sequence never run with real leads is a draft; L7 should know it is receiving leads warmed by an untested process.
Step 7. Write the final follow-up system
Duration: 30-45 minutes
You now have a sales-ready definition, a gap map, a sequence, a progression model, and a diagnosed stall. Lock the system.
A complete L6 output has six parts. Write a line or two for each:
- The sales-ready definition: the observable bar a lead clears before sales gets them.
- The gap and the moves: the shifts follow-up produces, anchored on the L1 blocker, and what moves each.
- The sequence: the touches, each tied to a shift, value-first, with the explicit case against doing nothing and the cadence, plus the separate fit-but-cold track.
- The progression model: the signals, the advance triggers, the sales-ready trigger, and the honest exits.
- The stall and the fix: the weakest point, its likely cause (L6 or upstream), and the change you made.
- The upstream finding, if any: whether the run revealed a constraint in L1, L2, or L5 that follow-up cannot solve, so it is visible.
Keep it as structured fields. Format does not matter. A purpose behind every touch does: this is the layer where “we send some follow-up emails” is not good enough.
What to do:
- Write the final system directly into the matching fields in the L6 section of
outputs.md. - Read it once as a skeptical lead receiving the sequence. Does each touch earn the next, or does it just ask? Would you trust the sender more after touch three, or less?
- Run the diagnostic from the top of this page one more time. If all five questions now have clear written answers, L6 is done.
What you’ve built
After completing the steps above, the L6 section of outputs.md should contain:
| Field | What it proves |
|---|---|
| Inputs from L5 and above | You designed backward from the lead, the value, and the blocker, not a blank page |
| Sales-ready definition | The exit is an observable bar, not a feeling, so the handoff to L7 is honest |
| The gap to close | You know the specific shifts follow-up has to produce, anchored on the L1 blocker |
| Follow-up sequence | Every touch has a purpose and leads with value, not a pitch |
| Anti-touch list | The corrosive touches you named, so they do not return under pipeline pressure |
| Progression model | Readiness is signalled, not guessed, with clean triggers and exits |
Sequence-test captures (in captures.md) | Real progression data and verbatim reasons for moving or stalling |
| Sequence synthesis | The stall, its cause, time-to-ready, and whether the constraint is upstream |
| Final follow-up system | A purpose-built, measured sequence with a known stall, ready for L7 |
| Scope notes | Decisions about what is in, out, and deferred |
This is not a deliverable for anyone else. It is a constraint on L7.
Assumption sweep
Before moving on, scan the L6 section of outputs.md for any field you filled in from reasoning rather than evidence. Common ones at L6:
- The sales-ready bar (did leads clearing it actually convert, or did you set it by intuition?)
- What moves each shift (did a lead say the proof or insight changed their mind, or did you assume it would?)
- The cadence and length (did ready leads need this many touches over this long, or is it a guess?)
- The progression signals (do they predict readiness, or are they just the behavior that is easy to track?)
- That the leads are qualified enough to nurture (did L5’s bar hold up, or are you nurturing the wrong people?)
Each unconfirmed field is an assumption. Log it in assumptions.md now if you have not already. The sales-ready bar and the case against doing nothing are usually the highest-impact assumptions in the layer; if untested, mark them leap-of-faith and run Step 6 before trusting the handoff.
What this layer hands off to L7
Before moving on, confirm the L6 section of outputs.md is complete. L7 opens by reading it. Specifically, L7 needs:
- The sales-ready definition, because it is the contract for the handoff: it tells sales exactly what kind of lead they are getting and what is already true about them. L7’s materials are built for a lead in this state, not a cold one.
- The gap that is already closed and the one shift that remains, because by sales-ready the lead believes much of the L2 claim already; L7 should reinforce and finish that case, not restart it. Knowing what follow-up already proved stops sales from re-pitching what the lead accepted weeks ago.
- The buying-group progress and what the champion still needs, because L7’s core job is arming the champion to win over the economic buyer and the blockers they cannot reach. L6’s notes on what the champion needed (a number, a one-pager, a risk answer) are the brief for L7’s materials.
- The objections and trust gaps that surfaced in the run, because the objection a lead raised in follow-up is the one sales will meet again, and L7 should have an answer ready.
- The lead’s source, awareness, and what they already received, so sales continues the relationship instead of starting over.
The quality of your L6 follow-up sets how warm the lead is when sales gets them, which sets the ceiling on what L7 can do. Sales enablement cannot warm a cold lead; it can only help convert one that follow-up already brought close. If deals stall at the sales stage, check whether the leads were genuinely sales-ready by the L6 bar, and whether a stall that looks like a sales problem actually originates in a follow-up that quit too early, a value proposition that never beat inertia, or an audience that never had the problem. The handoff is where small misalignments from L2 and L3 become loudly visible; the cause is usually behind the handoff, not at it.
Common failure modes
There is no follow-up; leads go silent after first contact. The lead raised a hand, got one reply or none, and was forgotten. Most leads are not ready on first contact, and a layer that does not exist cannot move them. Build the sequence; presence over time is most of the job.
The follow-up is a bland drip that adds no value. A generic automated sequence that asks for attention and gives nothing erodes trust with every send. Lead with usefulness; each touch should be welcome on its own merits or it should not exist.
It pitches too early and breaks trust. Touch one is a feature list and a demo request, before the lead has any reason to trust you. Selling without selling means earning the next step; the pitch comes after the problem is well understood, not before.
It never makes the case against doing nothing. The sequence talks about the product and never about the cost of the status quo, so the L1 blocker, the real competitor, goes unanswered. The lead stays comfortable and drifts. Put the explicit, concrete case against inertia in the middle of the sequence.
Sales-ready is a feeling, so the handoff is a guess. With no observable bar, good leads get passed too early and cold ones get passed at all, and sales learns to distrust marketing’s leads. Define the bar as observable criteria and make the handoff the bar being cleared.
It quits too early on a slow decision. The sequence ends after three touches while the real decision takes a quarter, so you go silent exactly when patience would have won. Match the cadence and length to the actual decision cycle from L1.
The fit-but-cold leads are dropped or over-pressured. The right-but-not-ready leads, often the majority, are either abandoned or pushed too hard and lost. Give them a slow, useful nurture and an honest exit; they are the long game.
You optimised the sequence while the fault was upstream. Leads stall, so you rewrite touch four endlessly while the real problem is leads L5 never qualified or a value proposition L2 never sharpened. When a stall resists every sequence change, check the layer above before rewriting the email again.
“We nurture our leads.” Said with an automated drip nobody has measured and a handoff run on gut. If you cannot point to a sequence where each touch has a purpose and a progression model that signals readiness, it is activity, not a system.
Sources
- Influence by Robert Cialdini. The psychology that makes selling without selling work: reciprocity (lead with value), commitment and consistency (small steps before large ones), social proof (others like them who acted), and liking and trust built over a sequence. Behind Steps 4 and 5.
- The JOLT Effect by Matthew Dixon and Ted McKenna. On why qualified buyers who acknowledge a problem still do nothing, and how to overcome indecision rather than just establish value. The foundation for treating the L1 blocker as follow-up’s main adversary in Steps 3 and 4.
- The Challenger Sale by Matthew Dixon and Brent Adamson. On teaching the buyer something new about their own problem to build trust and reframe the status quo, the engine of value-first follow-up that proves the claim without pitching. Behind the teaching touches in Step 4.
- They Ask, You Answer by Marcus Sheridan. On earning trust by honestly answering the buyer’s real questions and educating rather than selling, and on content as the substance of nurture. Background for the value-first sequence in Step 4.
- Invisible Selling Machine by Ryan Deiss. On the mechanics of a structured follow-up sequence: the stages from first contact to ready, behavior-based triggers, cadence, and re-engagement. Behind the sequence and progression model in Steps 4 and 5.