Updated September 28, 2026 | 13 min read

3 Emails, One Framework: How I Write Cold Sequences ICs Actually Reply To

Most cold email templates are written for VPs. The subject lines sound like a board deck. The CTAs assume budget authority. And the proof points reference revenue milestones the recipient had zero hand in.
The problem? When you send that same email to the SDR who actually lives inside the tool you’re selling, it reads like spam from someone who never bothered to look up their job title.
I’ve spent the last year building and testing IC-targeted sequences at lemlist, and we turned the framework into an open-source Claude skill anyone can use. In this post, I’ll walk you through the exact 3-email structure, the role-specific angles, subject line patterns, and the mistakes I see kill reply rates over and over. lemlist scores 4.6 out of 5 on G2 with 1,500-plus reviews (Lemlist Review 2026: Is It Still the Best Cold Email Tool for Personalized Outreach? - Ecommerce Paradise – Build & Scale High-Ticket Ecommerce Businesses), and a big reason is that our users write copy that matches the person reading it.

What is a copywriting IC sequence

A copywriting IC sequence is a three-email outbound sequence written specifically for individual contributors, the people who do the actual daily work rather than sign off on budget. This includes SDRs, AEs, RevOps analysts, engineers, and designers. Most cold email templates are built with a VP in mind, and that mismatch is exactly why IC-targeted campaigns fall flat.
“IC” means someone who uses the product day to day, feels the friction it solves, and influences a purchase decision without approving the spend. That distinction changes almost everything about how the copy needs to read.
We turned this framework into an open-source Claude skill, so a sequence like this can be generated on demand instead of built from a blank page each time.
Quote Icon
Tip: If the same template goes to a VP and an SDR, one of those two emails is probably headed straight for the trash.

Where traditional copywriting frameworks fall short for ICs

If you’ve studied cold email copywriting at all, you’ve seen PAS (Problem-Agitate-Solution), AIDA (Attention-Interest-Desire-Action), and BAB (Before-After-Bridge). These are legitimate general frameworks, and I still use elements of each.
But here’s the thing: they were designed for broad audiences and top-of-funnel marketing, not for one-to-one outbound to an individual contributor. PAS assumes you can agitate a pain the reader already acknowledges. AIDA assumes you have enough attention runway to build desire. BAB works best when you can paint a clear “after” state the reader controls.
ICs often can’t act on the “after” you describe. They don’t own the buying decision. So the framework needs to be rebuilt around what an IC can actually feel, recognize, and do. That’s what the 3-email IC sequence structure does: it borrows the psychological logic of these frameworks (recognize a pain, reframe it, offer a next step) but calibrates every element for someone without budget authority.

Why individual contributors need different outbound copy

Most outbound sequences are written with a decision-maker in mind, and that’s usually the first place they go wrong with ICs. A VP thinks about pipeline and forecast accuracy. An SDR thinks about why yesterday’s sixty emails produced one reply.

ICs respond to workflow pain, not strategy language

Phrases like “drive revenue” or “align cross-functional stakeholders” don’t register with someone knee-deep in a spreadsheet. What tends to get read is a description of the exact task they repeated four times before lunch.

Budget authority changes what you can ask for

An IC can’t sign a contract, so a “book a demo” ask is asking for something outside their control. The CTA needs to match what they can actually do: reply, forward, or try a free resource.

Proof points ICs actually trust

A logo wall might impress a VP, but an IC wants to know whether someone in their exact role solved the same problem. A peer quote or a specific before-and-after workflow tends to land better than a generic case study.
Proof type
Works for VPs
Works for ICs
Customer logo wall
Yes
Rarely
Revenue or pipeline stat
Yes
No
Peer quote, same role
Sometimes
Yes
Specific workflow outcome
Sometimes
Yes
Free resource or template
Rarely
Yes

The 3-email IC sequence structure

Each email in this sequence carries a different job, so none of them repeats the others. Email one hooks with a recognizable problem, email two reframes it with proof, and email three closes with a low-friction ask.

Email 1 hooks with a day-in-the-life problem

This one opens with a specific moment the IC would recognize from their own day, no product mention yet. The goal is simple: make them think, “this person gets my job.” For an SDR, that might read: “Sixty emails out by lunch. Two replies, both out of office.”

Email 2 reframes the root cause with peer proof

Here the message shifts entirely instead of restating email one. The angle I’ve seen work best is what we call the “why it keeps happening” reframe: instead of repeating the symptom, you name the underlying reason the problem persists. Then you bring in a peer quote or a specific workflow change as proof. “Another SDR at a similar company cut research time by changing one variable in their sequence” tells the reader that someone in their role found the root cause, not just a workaround. That combination of diagnosis plus peer evidence earns more trust than repeating the pain from email one.

Email 3 makes a closing ask with a breakup frame

The shortest of the three, email three closes the loop with what I call the “internal champion angle plus breakup.” You position the IC as someone who could bring this to their team (the champion frame), and you signal this is your last email (the breakup frame). That combination works because it gives the IC a reason to act now, either by replying or forwarding, without any pressure to commit to a meeting. A reply prompt or forward request outperforms a calendar link here almost every time.

How to use day-in-the-life framing and personal pain messaging

Day-in-the-life framing means opening with a moment from the IC’s actual workday instead of a benefit statement. It’s arguably the biggest lever in this whole framework, since a recognized moment earns attention a value proposition rarely does.
Getting there takes some research before writing a word. A few places worth checking:
  • Posts and comments on LinkedIn reveal what ICs are frustrated by right now, often in their own words
  • Job descriptions for the same role list daily responsibilities and the tools involved, giving you the vocabulary they’d use themselves
  • Role-specific Slack groups, subreddits, and forums are where ICs vent about their day with zero filter
  • Company career pages with open roles nearby can signal team gaps and workload pressure
That kind of research used to eat a rep’s entire morning, one profile at a time. lemlist’s data enrichment agents pull that context automatically from LinkedIn, websites, CRM data, Claap sales recordings, and other internal sources (The only platform you need for outbound | lemlist), so the research step happens in seconds rather than dragging out across dozens of tabs.

How to write subject lines and CTAs for IC-level outreach

Subject lines that sound like a colleague wrote them

The subject lines that tend to work best here are short, lowercase, and carry zero marketing polish. Anything resembling a newsletter usually gets skipped. A few patterns worth testing: “reply rates,” “salesnav exports,” “quick thought,” “your sequences.”
One A/B test I’d recommend running early: send the same email with a lowercase subject line to half your list and a mixed-case subject to the other half. In my experience, lowercase wins for ICs because it reads like an internal Slack message, not a campaign. That single variable can shift open rates enough to change the math on the whole sequence.

CTAs that work without budget authority

Swapping “book a demo” for something an IC can act on changes reply rates more than almost any other line in the email. Here are the patterns I keep coming back to:
  • Ask a question that invites a reply: “Seeing the same thing on your end?” works because it requires no commitment beyond a sentence
  • Link to a free resource that proves your point: “Wrote up how other SDRs handle this, here if you want it” gives value before asking for anything
  • Use a curiosity one-liner for email three: “Worth a look?” keeps the breakup frame lightweight
  • Request a forward if the IC isn’t the buyer: “Mind sending this to your manager if it’s relevant?” turns the IC into an internal champion without asking them to schedule anything

Adapting IC sequences by role

The three-email structure holds steady across roles, but the angle and vocabulary shift depending on who’s reading. lemlist’s lead database filters by exact job title, which makes segmenting before writing straightforward.

SDRs and BDRs

The angle here centers on prospecting speed, reply rates, and the fatigue of switching between several tools just to send one email.

Account executives and account managers

AEs feel deal velocity and missing CRM context; account managers feel renewal risk. Both notice when information falls through the cracks between systems.

Marketing specialists and growth marketers

Campaign reporting friction and attribution confusion sit at the center of this angle, along with the gap between what a dashboard shows and what actually happened.

RevOps analysts and sales ops

Data hygiene, broken automations, and a report that fails every Monday morning are the kinds of details that make this copy land.

Engineers and designers

Context-switching between tools and integration requests stuck in a backlog make up the daily friction here. This audience also tends to be the most skeptical of outbound email overall, so specificity matters even more.

Common IC sequence mistakes that kill reply rates

A handful of recurring mistakes tend to flatten results no matter how solid the structure is:
  • Writing to the IC as if they’re a VP is the fastest way to get ignored. ROI language and “strategic alignment” signal that you didn’t research the actual recipient.
  • Asking for a meeting in email one almost always backfires. ICs are wary of calendar invites from strangers, so the reply needs to come before the ask for time.
  • Repeating the same angle across all three emails makes the sequence read like one email sent three times. Each email needs a distinct hook or the IC checks out after email one.
  • Referencing personal details beyond the professional often feels invasive rather than relevant. Stick to role and workflow context.
  • Using generic copy that fits any job title gets spotted instantly. ICs recognize mass outreach almost immediately.
  • Trusting AI-generated personalization without verifying the source is a mistake I see more often now. If your AI tool fabricates a detail (a conference the IC never attended, a blog post they never wrote), you lose credibility permanently. This is why we built lemlist’s enrichment to pull from verified, source-grounded data rather than letting a model guess. Always check that any personalization detail traces back to a real, findable source.

How to install and use the copywriting IC sequence Claude skill

Get the skill file from GitHub

The skill lives in lemlist’s Claude Skills repository as a markdown file containing the full prompt: role framing, structure rules, and output format.

Load the skill into your AI client

Claude Desktop users can add the file to a Project’s knowledge base. This is the no-setup path: upload the file and start prompting. Claude Code, Cursor, and Windsurf detect it automatically once it’s placed in the project directory.
For power users who want the skill wired into a local AI setup, lemlist MCP connects the same actions through a server URL, but it requires generating an API key from your workspace settings and pasting the MCP server URL into your preferred client. Setup takes under 2 minutes. (lemlist MCP | Connect AI Agents to Sales Outreach & Lead Data) (lemlist MCP | Connect AI Agents to Sales Outreach & Lead Data)

Run your first IC sequence prompt

Provide the target role and product, plus any ICP detail the skill needs. It asks for anything else it requires. The output is three emails complete with subject lines, CTAs, and notes explaining the reasoning behind each choice.
Start a 14-day free trial to try the copywriting IC sequence skill inside your own workflow.

Personalizing IC sequences at scale

Writing one strong IC sequence by hand can take a meaningful chunk of time per lead. Writing fifty that way isn’t realistic, which is where automation earns its keep.
  • lemlist’s data enrichment agents pull role-specific context (tools used, team size, recent activity) from sources including URLs, LinkedIn, past calls, and CRM (lemlist AI agentic enrichment), then return it as ready-to-use variables you plug into your sequence
  • Intent signals time your outreach to moments like a new hire in the target role or a tech stack change, so the email lands when the problem is fresh
  • Multichannel delivery runs the same IC-targeted messaging across email and LinkedIn from a single campaign, keeping the experience consistent regardless of channel

Final thoughts

The IC sequence framework gives you the structure and role-specific angles you need to write outbound copy that matches what individual contributors actually care about. Pair it with the Claude skill and you can go from a blank page to a finished, reasoned sequence in minutes.
I’ll be honest: this won’t fix bad targeting. If you’re emailing the wrong people, no framework saves you. But if you’ve got the right list and you’re still getting silence, the problem is almost certainly that your copy reads like it was written for someone else’s boss. (Been there.)
Start a 14-day free trial to build your first IC sequence and launch it across email and LinkedIn in one workflow. No credit card required.

FAQs about copywriting IC sequences

How many emails should an outbound IC sequence have?

Three tends to be the right number for IC-level outreach. ICs disengage from longer sequences quickly, and three touchpoints give enough room to shift angle, add proof, and close with a breakup ask.

Can the IC sequence framework work for LinkedIn DMs?

Yes, the day-in-the-life framing translates well to LinkedIn DMs, though shorter copy and no subject line usually fit the format better.

What reply rate should IC-level outreach produce?

Reply rates vary by industry, role, and list quality, so there’s no single benchmark worth chasing. A better signal is whether ICs respond with real engagement, questions or forwards to a manager, rather than a quick opt-out.

Does the copywriting IC sequence Claude skill work with Cursor and Windsurf?

Yes, the skill file is a plain markdown prompt compatible with any MCP-compatible client. That includes Claude Desktop, Claude Code, Cursor, and Windsurf. For power users who want deeper integration, lemlist MCP connects 40+ outbound actions through a server URL, though it requires generating an API key and adding a JSON config to your client. Claude Skills is the simpler, no-setup alternative for most users. Anthropic describes MCP as “an open standard for connecting AI assistants to the systems where data lives”.
Share this post