Personalized Multi-Touch Outreach Sequence

What you'll produce

A multi-touch outreach sequence — 5–7 coordinated touches across email, LinkedIn, and phone — aimed at booking a first meeting with the top account from your prospect list (Deliverable 1). This is the single most-evaluated artifact in an SDR interview: the work sample that proves you can turn a cold name into a booked discovery call. A great sequence isn't a clever message; it's a system — each touch leads with the prospect's problem (not your product), references a specific "why now," varies the channel and angle so you don't repeat yourself, and ends in one low-friction call to action. This deliverable proves the Topic 5 skills employers pay for: personalize at scale, lead with value, stay brief, persist politely, and drive every touch toward a single booked meeting.

Instructions

1. Anchor to one account and one named contact. Pull your top account and its champion/economic-buyer contact straight from Deliverable 1 (ICP & Prospect List). Write the contact's name, title, company, and the specific "why now" trigger at the top so every touch can lean on it. One sequence = one human. (Look-alike accounts get the same sequence with the trigger swapped — that's the point of a system.)
2. Pick the meeting as your only goal. Decide the single CTA the entire sequence drives toward — a 15-minute discovery call. Write it once and keep it identical (or near-identical) across touches. Do not ask for the sale, a demo, or "a quick chat about our platform." Low-friction, time-boxed, value-framed: "Worth a quick 15 minutes Thursday?"
3. Map the cadence before you write a word. Lay out 5–7 touches over ~12–18 business days, alternating channels so you're never silent and never repetitive. A proven SDR cadence: Day 1 email + LinkedIn connect, Day 3 call + voicemail, Day 5 email (new angle), Day 8 LinkedIn message, Day 11 call, Day 14 "break-up" email. List each touch's day, channel, and angle in a table first.
4. Write each touch to lead with their problem, not your product. Every message opens on the prospect's world — the trigger, the cost of the pain, a peer outcome — before Lumadesk is ever named. Ban the words "I wanted to reach out," "I hope this finds you well," and any feature list. If a touch could be sent to any company, it's not personalized; rewrite it.
5. Keep emails brutally short and skimmable. 50–90 words. A relevance hook in line one, the pain quantified, one outcome/proof point, one CTA. No paragraphs over two sentences. Write subject lines under ~4 words that reference them, not you (e.g., "GearGrid + response times").
6. Vary the angle, not just the channel. Each touch needs a new reason to engage — trigger event, a quantified cost, a peer/result proof point, a relevant insight, a soft "should I close your file?" Repeating the same pitch louder is what gets SDRs ignored.
   • Never invent a named customer or a specific result you can't source. Do not write "[Company X] cut response time from 14 hours to 2" unless that's a published, approved reference you could defend in front of the prospect. A fabricated case study is a fireable claim and an easy way to lose a deal the moment the prospect asks for the source. When you don't have an approved named reference, use an honest proof frame instead: a category benchmark ("teams that hold response times under 2 hours through a volume spike typically…"), an anonymized range ("the DTC teams we work with usually see a 30–40% lift"), or "teams we work with typically…". Defensible and unnamed beats specific and fake — every time.
7. Write a real cold-call opener script. A 30–45 second spoken opener: a permission-based or pattern-interrupt opening line, the reason for the call tied to their trigger, a one-sentence value hook, and the ask for the meeting — plus a scripted response to the #1 brush-off ("I'm not interested" / "send me something"). This is graded live in interviews; write it the way you'd say it out loud.
8. End with a graceful break-up touch. The final email gives the prospect an easy out ("Should I close your file?") — these often pull the highest reply rate of the whole sequence because they create urgency without pressure.
9. Sanity-check against the rubric. Read every touch and ask: Does it lead with their problem? Is there exactly one CTA? Could I send this to a different company unchanged (bad)? Is it under 90 words? Is every proof point one I could defend if the prospect asked "which customer? what's the source?" Fix anything that fails before you submit.

Rubric

The app's AI scores the learner's submission against these criteria and gives feedback. Levels: Needs work (1) / Solid (2) / Excellent (3). Passing = every criterion at Solid or above.

• Personalization & "why now" — 1: generic; could be sent to any company · 2: references the account and a real trigger · 3: every touch is anchored to a specific, researched trigger that couldn't be copy-pasted to another account.
• Leads with the prospect's problem, not the product — 1: opens by pitching features/the company · 2: most touches open on the prospect's pain before naming the product · 3: every touch leads with their problem/value and quantifies the cost; the product appears only as the answer.
• Honest, defensible proof — 1: invents a named customer or a specific result the rep couldn't source (e.g., a made-up "Company X cut response time from 14h to 2h") · 2: proof points avoid fabricated names but lean on vague or unbacked claims · 3: every proof point is defensible — an approved named reference, a category benchmark, an anonymized range, or "teams we work with typically…" — with no invented customers or numbers.
• Single low-friction CTA — 1: no clear ask, or asks for the sale/multiple things · 2: a consistent meeting ask across touches · 3: one identical, time-boxed, value-framed meeting ask in every touch, easy to say yes to.
• Cadence & channel variety — 1: one channel or no plan · 2: 5–7 touches across ≥2 channels over a sensible timeline · 3: a deliberate multi-channel cadence (email + LinkedIn + call) with a clear day-by-day map and a graceful break-up touch.
• Angle variety across touches — 1: the same message repeated louder · 2: touches use somewhat different angles · 3: each touch brings a genuinely new reason to engage (trigger, quantified cost, peer proof, insight, urgency).
• Brevity & skimmability — 1: long, dense, or rambling · 2: mostly short with clear asks · 3: every email 50–90 words, short subject lines, two-sentence-max paragraphs, instantly skimmable.
• Cold-call opener quality — 1: missing, or a feature dump · 2: a usable spoken opener with a reason for the call and an ask · 3: a tight, say-it-out-loud opener with a permission/pattern-interrupt open, trigger-based reason, value hook, meeting ask, and a scripted brush-off handler.