Automation should scale a motion you understand, not hide a motion you haven't learned yet
A sequence is not a list of steps. It is one conversation carried across channels with intention. The Momentum Sequence™: part of the SD Lab Momentum Method™ lineage, gives that conversation an architecture: Connect, Give, Ask, Release.
Original SD Lab framework · Momentum Method™ lineage · expanded for SD Lab V2
What this guide covers
- A sequence is one conversation across channels, not a checklist of touches.
- Momentum = Connect + Give + Ask + Release. Most teams skip Give and never learn Release.
- Match effort to account and persona priority; not every prospect earns the same motion.
- The first touch starts with research, not with a template.
- Automation belongs underneath a proven motion, never in place of one.
A sequence is not a list of steps
Open most sequence tools and you'll find twelve touches that share nothing but a merge field. The buyer experiences them as twelve unrelated interruptions from a stranger. The rep experiences them as tasks. Nobody experiences them as a conversation.
Coordination means each touch knows what the last one said and why the next one exists. That's an architecture problem, not a copywriting problem, and it's why the framework below starts with intent, not templates.
Automation should scale a motion you understand, not hide a motion you haven't learned yet.
Momentum = Connect + Give + Ask + Release
Four phases. Each phase has a job, and each touch inside it carries that job on a specific channel.
- Connect: genuine connection grounded in buyer context. The goal is to be recognized as relevant, not memorable.
- Give: something useful: an insight, a resource, access, a pointed observation about their situation. Give is what separates a sequence from a drip.
- Ask: the intentional transition into a sales conversation. Proportionate to the trust the first two phases built.
- Release: stop active pursuit cleanly. Leave the relationship intact and leave room for later re-engagement.
Most sequences are Connect → Ask → Ask → Ask → Ask. Give is missing, so there's no trust. Release is missing, so the account burns. The framework fails when two of its four phases are treated as optional.
One historical architecture
The historical SD Lab material includes a 14-touch / 20-business-day example built from 6 emails, 4 calls and 4 social touches. It is useful as a picture of proportion, roughly how channel mix and spacing can look when the four phases are respected.
It is not a benchmark, a benchmark cadence, or a promise. Your architecture depends on your sales cycle, your persona's channel habits, and the account's priority tier. Copy the logic, not the numbers.
Match effort to account and persona priority
Not every account earns the same motion. A tiered approach keeps your best effort on your best opportunities and keeps the rest honest.
- Tier 1: named accounts, known signal: full Momentum motion, personalized Connect, bespoke Give, direct Ask.
- Tier 2: in-ICP, plausible timing: the same architecture with segment-level hypotheses instead of per-account research.
- Tier 3: market coverage: lighter touches whose real job is to surface signal for promotion into Tier 2.
The first touch starts with research
Connect only works when it's grounded in something true about the buyer. That means a lightweight research pass before the first touch, enough to form a hypothesis about their situation, not a dossier. The 3×3 research discipline exists for exactly this step; the output of that work is the input to Connect.
Coordinate call + email + social
- Email carries the hypothesis: the fullest statement of why you, why now.
- Calls carry the conversation: referencing the email creates continuity instead of a cold restart.
- Social carries presence: engage with what they post, don't pitch in a connection request.
- Each touch references the thread; none pretends the others didn't happen.
- Spacing follows the buyer's rhythm, not the tool's default.
Where automation belongs
Automation belongs underneath a motion that already works manually. It should handle scheduling, task creation, CRM logging and tier routing. The mechanics: while the thinking stays human.
If you cannot describe why each phase exists and what a good outcome looks like, automating the sequence doesn't scale your outbound. It scales your uncertainty.
Release and nurture instead of endless chasing
Release is a deliberate, professional close: a short note that names the end of the pursuit, leaves the door open, and moves the account into a nurture lane. It protects the relationship, protects your sender reputation, and, done consistently, produces the re-engagements that endless chasing never does.
An account that heard a clean Release in Q1 is a warm conversation in Q3. An account that got fourteen unanswered touches is a spam filter entry.
Signals, workflows, tiering and routing
The modern Momentum motion is signal-led. Intent signals, hiring patterns, technology changes and engagement behavior decide when an account enters the sequence and at which tier. CRM workflows handle the routing; conditional logic handles the exceptions; the rep's judgment handles the conversation.
This is where the framework meets the operating system: the sequence is one component in a larger engine that includes targeting, messaging hypotheses, coaching and inspection.
What this looks like in live engagements
- FusionAuth: cadence and channel coordination installed as part of a live system build: targeting, signal, messaging angle and workflow sequenced together.
- Kustomer: multichannel execution taught as a team skill with manager reinforcement, inside a documented capability build.
- Queryon: channel infrastructure and cadence installed; the honest middle on messaging iteration is documented in the report.
- Visual Identity Group: the cadence built to be operated by a founder, not an agency, capability transfer, not outsourced activity.
Where the sequence sits
Aim decides who. Relevance decides what. The sequence decides how the conversation unfolds over time, and the learning loop decides what changes next. A sequence can't rescue wrong targeting, and no targeting survives a sequence that burns accounts.
Related reading
Install a sequence your team actually understands
The Revenue Rebuild builds the cadence architecture around your motion, channels, tiers, signals and the Release discipline, then teaches your team to run it without the playbook becoming shelfware.