SDR outbound rules
Purpose
SDR outbound fails in predictable ways: long emails, several asks in one message, vague claims, and a corporate tone that readers skip. This skill gives every SDR the same standard, a set of frameworks to choose from, and a checklist to run before any message is sent. The rules are a floor for quality. They do not replace judgment about the prospect.
When to use
- Training new SDRs on written outbound.
- Reviewing or rewriting drafts before they are sent.
- Setting tone for a new offer type.
- Checking whether a campaign's copy follows the team's standard.
Route elsewhere when:
- The question is whether the offer is worth making. Use cold-offer-architect.
- The question is the sequence and its timing. Use outbound-cold-email.
- The question is why a campaign is underperforming. Use outbound-performance-diagnosis.
Inputs
- The prospect's name, company, role, and industry.
- The challenge and the goal, if known.
- The trigger or source: why this person, why now.
- The familiarity level: cold, previously engaged, or referred.
- The offer type, which sets the tone.
Procedure
The eight frameworks
Choose one per email. Do not mix two in one message.
- Before and after: the current state, then the state the reader wants.
- Pattern interrupt: break the expected shape of a sales email in a way that is relevant.
- Ask before pitch: open with a question that the reader can answer, then offer value.
- Upfront value: give something useful before asking for anything.
- Do the math: show the impact in numbers the reader can check.
- Comparison with similar companies: name a pattern seen in companies like theirs.
- Neutral insight: share a third-party finding, without pitching, to earn attention.
- Typical problems by role: name a problem that is common for their role, and ask whether it applies.
Step 1: Choose the framework
Choose the framework from the trigger and the familiarity level.
Step 2: Draft within the rules
Draft within the length rule, with one call to action.
Step 3: Run the pre-send checklist
- Under ninety words?
- One call to action?
- Trigger or personalization included, and true?
- Proof specific, with numbers where used?
- Tone right for the offer type?
- No buzzwords, and no fake enthusiasm?
- Would the writer reply to this?
Step 4: Rewrite any failed item
If the draft fails any item, rewrite the failed part and check again.
Output
- The draft, with the framework named.
- The checklist result, item by item.
- For a rewrite: the original, the changes, and the reason for each.
Quality bar
Every draft is within the length rule, has one call to action, and carries a true personalization. Proof is specific or absent. The framework is named. Watch for drafts over a hundred and fifty words, several asks in one message, and invented details.
Rules
Length and structure
- Sixty to ninety words, maximum.
- No bullet points in a cold email.
- One call to action. Clear, direct, respectful of time, and scheduling-oriented where possible.
Personalization
- Use at least one of: a trigger, a specific detail about the company, or a role-specific problem.
- Every personalization must be true and checkable. Never invent a detail to sound relevant.
Proof
- Social proof uses specific numbers and a real comparable, with permission where a name is used.
- Never claim a result that cannot be defended.
Tone by offer type
- Consultative services: calm, strategic, a trusted adviser.
- Accelerator or program: friendly, curious, approachable.
- Outbound cold: a clear pattern interrupt, short and direct, never aggressive.
