Rémi Kokabi | September 4, 2026 | 19 min read

Writing Email Sequences That Convert Sales Managers and Team Leads

What the copywriting manager sequence skill does

The copywriting manager sequence is a Claude Code skill built to write three cold emails aimed at manager-level buyers: Sales Managers, RevOps Managers, Marketing Managers, and Team Leads. A “skill” in Claude Code is a saved prompt file that lives in a local folder. Once it’s there, Claude applies it automatically whenever you ask for manager-focused email copy.
The output includes a two-word lowercase subject line for each email, a body between 50 and 100 words, personalization placeholders, and sequence notes explaining the reasoning behind each message. You get a finished sequence, not a rough draft you have to rebuild from scratch.
  • Persona targeting: written specifically for manager-level roles, not adapted from generic outbound copy
  • Structured output: a 3-email arc with subject lines, body copy, and placeholders ready to fill in
  • Copywriting rules baked in: length limits, tone constraints, and formatting rules that keep the output from reading like filler
  • Variable placeholders: fields for prospect name, company, role, and pain point so you can personalize with real data

Why manager-level buyers need a different email sequence

Managers sit in an odd spot in the org chart. They don’t set strategy (that’s the VP’s job), and they don’t do the daily task work (that’s the rep or IC). They translate directives into results and feel every broken process firsthand, which means the copy that lands with a VP usually falls flat with them.
Here’s how the angle shifts by seniority:
VP / Director
Manager / Team Lead
Individual Contributor
Primary concern
Revenue targets, board-level metrics
Team output, process gaps, tool adoption
Personal quota, daily workflow
Buying trigger
Strategic initiative or budget cycle
Operational bottleneck or team complaint
Personal pain with current tool
Email angle that works
ROI and competitive positioning
Workflow friction and team efficiency
Feature-specific and fast
You might read this and think the differences sound minor. They’re not. A sales manager who gets an email about “driving 30% revenue growth” will file it under “that’s my VP’s problem.” An email that names the exact friction their reps hit during pipeline review, though? That gets read.
The skill targets pain points that show up at the team level, week after week:
  • Reps losing hours to manual tasks instead of selling
  • Inconsistent outreach quality across the team, with no shared playbook
  • Too many disconnected tools, each creating its own data silo
  • Reporting gaps that make it hard to show results upward

The 3-email sequence structure for manager personas

The skill follows a fixed arc. Email 1 names the friction. Email 2 explains what’s causing it. Email 3 shifts to consequence and closes the loop. Each one gets shorter as the sequence moves forward.
Email 1 does one job: recognition. It names something specific that happens in the manager’s world every week, with no product mention and no pitch. The goal is a reaction closer to “how do they know that” than “here’s another vendor.”
Email 2 goes one layer deeper and explains why the problem keeps happening, usually by pointing at a process issue rather than a people issue. This email also carries a P.S. with a behavioral reference (“Teams like those at [Company] often find…”) instead of a fabricated stat or case study.
Email 3 reframes the friction around what it means for the manager’s credibility with their own VP, then closes with a clear yes-or-no question. The skill always ends this one with a specific line: “won’t message again, hope I didn’t do something wrong!” Breakup emails like this tend to get strong reply rates from managers, mostly because they signal respect for the person’s time.

Copywriting rules the skill follows

The skill functions less like a prompt and more like a style guide with teeth. It enforces constraints that catch the most common problems in AI-written outbound copy, whether or not you’re the one running the skill.
  • Subject lines: exactly two words, lowercase, no clickbait
  • Body copy: 50 to 100 words, not counting variables or the P.S.
  • Formatting: plain text only, no HTML, no bullet lists inside the email itself
  • Tone: written peer to peer, no exclamation marks, no “I,” no superlatives like “best” or “leading”
Personalization fields cover company name, prospect name, title, pain point, and a reference company where relevant. Without personalization data on hand, the skill adapts and writes without it rather than dropping in a placeholder that reads as hollow.
The skill also blocks a specific list of habits: fabricated metrics, generic value props, feature lists disconnected from a real pain point, links or attachments in early emails, and filler phrases like “just following up.”
Quote Icon
Tip: Borrow the accuracy rule even if you’re writing by hand. A line like “Teams like those at [Company] often find…” reads as credible without committing you to proof you can’t produce on demand.

How to install and use the skill in Claude Code

Setup takes a couple of minutes. Run npx skills add l3mpire/claude-skills/copywriting-manager-sequence in your terminal, and the .md file lands in your local skills directory (the folder Claude Code checks for reusable prompts).
Once it’s there, Claude Code picks it up automatically. Ask for a sequence directly (“write a 3-email sequence for a RevOps Manager at a 200-person SaaS company”), or let Claude invoke the skill on its own when it recognizes a matching request. Either way, you pass in the persona details and the skill handles the rest.

Customizing sequences for sales managers, RevOps managers, and team leads

The skill writes manager-level copy by default, but the output improves once you point it at a specific title. It accepts role-specific inputs and shifts the angle accordingly.
  • Sales managers: pipeline velocity, rep coaching, forecast accuracy, and quota attainment with existing headcount
  • RevOps and operations managers: tool sprawl, data quality, and process consistency across the GTM stack
  • Marketing managers: campaign execution, lead quality, and MQL-to-SQL conversion
  • Customer success managers: renewals, escalations, and early churn signals
The vocabulary changes with the role. RevOps copy leans on infrastructure language; sales manager copy leans on team performance. Specifying the title upfront saves a round of edits later.

Launching your manager sequence in a multichannel campaign

Copy on its own doesn’t book meetings. It has to reach the right inbox, alongside the right channels, at the right pace.
  1. Import your manager-level lead list. Pull from your CRM, upload a CSV, or build a list with role and seniority filters (lemlist’s database covers 450M+ contacts for this).
  2. Enrich contacts with verified data. Confirmed emails and phone numbers protect your sender reputation from bouncing off dead addresses.
  3. Load the sequence and add LinkedIn or call steps. Paste in the skill’s output, then layer in connection requests or call tasks between emails to keep timing tight.
  4. Activate and monitor replies. Track opens, replies, and bounces from one inbox, especially useful when multiple reps run the same sequence across different territories.
Start a 14-day free trial to load your manager sequences into multichannel campaigns with built-in deliverability tools and lead enrichment.

Common mistakes when writing outbound sequences for managers

A few habits tend to flatten reply rates, even when the copy itself is solid:
  • Writing to the VP instead of the manager: strategic language about revenue lands better with a VP than with someone focused on team execution
  • Pitching in the first email: leading with features before showing you understand the problem
  • Making every email the same length: each one in the sequence carries a different job and gets shorter as it goes
  • Skipping personalization fields: sending raw skill output without filling in prospect details reads as generic
  • Relying on email alone: managers, especially in tech, often respond faster on LinkedIn

Turn AI-generated sequences into booked meetings

The skill hands you strong copy. It doesn’t hand you the infrastructure to send that copy at scale, track what’s working, or adjust across channels, and that’s usually where teams lose momentum.
lemlist connects lead discovery, enrichment, multichannel sequencing, and deliverability monitoring in one place. Load your manager sequences, enrich contacts with verified data, add LinkedIn and call steps next to your emails, and watch it all from a single dashboard.
Start a 14-day free trial to see how it works. No credit card required.

FAQs about the copywriting manager sequence skill

How many emails does the copywriting manager sequence skill generate?
Three. Email 1 names the friction, Email 2 diagnoses the cause, and Email 3 shifts to consequence and closes the loop, with sequence notes explaining the logic behind each message.
Can the skill output be used outside of Claude Code?
Yes. The output is plain text with standard formatting, so it drops into any outbound platform, CRM, or email tool without modification.
What’s the difference between the manager sequence skill and a VP sequence skill?
The manager skill focuses on operational pain and team-level friction, while a VP skill leans on strategic outcomes and business metrics. Tone, proof points, and CTA style shift to match how each persona actually evaluates a new tool.
Can the skill be edited to match a specific brand voice?
Yes. The skill file is a plain-text markdown document, so tone rules, length constraints, and pain point language are all editable, and changes stay in your local skills directory.

What the copywriting manager sequence skill does

The copywriting manager sequence is a Claude Code skill (a reusable prompt file stored in your local skills directory) that writes a complete 3-email outbound sequence targeting manager-level buyers: Sales Managers, Marketing Managers, RevOps Managers, Team Leads, and Operations Managers. Think of a Claude Code skill as a saved set of instructions that Claude automatically follows when a relevant request comes in. You ask it to write emails for a manager persona, and the skill handles the structure, tone, and rules without you re-prompting every time.
The skill produces a complete 3-email campaign following strict copywriting rules, calibrated for operational, team-focused manager messaging. Each email comes with a two-word lowercase subject line, a 50–100 word body, personalization variable placeholders, and sequence notes explaining the logic behind each message.
Here’s what the skill gives you:
  • Persona-specific targeting: writes specifically for the daily reality of manager-level roles, not generic outbound
  • Structured 3-email arc: each email has a distinct job in the sequence (friction, root cause, consequence)
  • Built-in copywriting constraints: enforces length limits, tone rules, and formatting so the output doesn’t read like AI-generated filler
  • Variable placeholders: includes fields for prospect name, company, role, and specific pain points you fill in with real data
  • Sequence notes: explains the friction named, root cause diagnosed, CTA progression, and what to A/B test

Why manager-level buyers need a different email sequence

Managers occupy an unusual position. They don’t set the strategy (that’s the VP) and they don’t do the individual task work (that’s the rep or IC). Managers live between strategy and execution. They translate VP directives into team results, manage daily operations, and feel the friction of broken processes firsthand.
This means the same cold email that works on a VP or an individual contributor will almost always miss a manager. The language, the angle, and even the proof points all change based on where someone sits in the org chart.
VP / Director
Manager / Team Lead
Individual Contributor
Primary concern
Revenue targets, board-level metrics
Team output, process gaps, tool adoption
Personal quota, daily workflow
Buying trigger
Strategic initiative or budget cycle
Operational bottleneck or team complaint
Personal pain with current tool
Email angle that works
ROI and competitive positioning
Workflow friction and team efficiency
Feature-specific, speed-focused
You might look at this and think the differences are subtle. They’re not. A sales manager who reads an email about “driving 30% revenue growth” will mentally file it as “that’s my VP’s problem.” But an email that names the specific friction their reps hit during pipeline reviews? That gets attention.

What managers care about vs. VPs and individual contributors

The skill’s prompt internationalizes how managers are wired before writing a single word. Managers don’t read about broken processes in reports. They live them. A sales manager watches reps struggle with the same objections every week. A RevOps manager manually fixes the same data issues every month.
They are squeezed from both sides. Above: pressure from their VP to hit targets, report results, and scale without adding headcount. Below: their team asking for better tools, clearer processes, and more support. The best email angles sit right in that double squeeze, because that’s where the urgency lives.
Managers often drive the research and evaluation process but then build a case for their VP. So your email doesn’t just have to be interesting. It has to give the manager something worth investigating, and ideally something easy to bring upstairs.

The operational pain points that get managers to reply

The skill targets friction points that are specific, recurring, and felt at the team level:
  • Reps spending hours on manual tasks instead of selling
  • Inconsistent outreach quality across the team, with no repeatable playbook
  • Too many disconnected tools in the stack, each creating its own data silo
  • Reporting gaps that make it hard to show results to leadership
Each of these pain points maps directly to the type of language the skill uses in generated emails. You’ll notice the output never talks about “transforming your business.” It talks about what happened in last Tuesday’s pipeline review.

The 3-email sequence structure for manager personas

The skill follows a specific arc: Email 1 names the daily friction. Email 2 shows what’s causing it with proof at the team level. Email 3 shifts to the consequence for their VP or their team, plus a breakup. Each email has a distinct purpose, and the sequence gets shorter and more direct as it progresses.

1. Email 1 names the operational problem

The first email’s job is recognition, not persuasion. It names something specific that happens in the manager’s role every week. It feels like you’ve been watching their team, without being creepy. No product mention. No pitch. Just a signal that you understand their daily reality.
The skill enforces plain-text formatting, no links, no images, and a body capped at 50–100 words. The subject line is exactly two words, all lowercase, designed to look like an internal email rather than a marketing blast.

2. Email 2 diagnoses the root cause

Where Email 1 names the symptom, Email 2 goes one layer deeper. It diagnoses WHY the problem keeps recurring at team level. The root cause is structural (“it’s not a people problem, it’s a process problem”).
This email also adds a P.S. with a relevant resource or team-level reference. The skill is careful here: it uses behavioral social proof (“Teams like those at [Company] often find…”) and never fabricates outcomes or metrics.

3. Email 3 shifts the lens and breaks up

The final email changes the frame. It shows what the friction means for the manager’s VP’s view of their team, or for their own credibility. This is the shortest email in the sequence, with a clear yes-or-no CTA.
Breakup emails typically get strong reply rates from manager personas because they respect the manager’s time. The skill always closes Email 3 with a specific breakup line: “won’t message again, hope I didn’t do something wrong!”

Copywriting rules the skill enforces

The skill isn’t just a prompt. It’s a set of writing constraints designed to prevent the most common mistakes in AI-generated outbound copy. Even if you write sequences manually, these rules are worth borrowing.

Length and formatting constraints

  • Subject lines: exactly two words, all lowercase, no clickbait
  • Body copy: 50–100 words per email, excluding variables and P.S.
  • Paragraphs: short sentences, one line on mobile
  • Format: plain text only, no HTML, no bullet lists inside the email

Tone and language rules

  • Write like a peer: practitioner-to-practitioner, not vendor-to-prospect
  • No exclamation marks: ever
  • No superlatives: “best,” “leading,” and “top” are all banned
  • No “I”: the emails use “you,” “your team,” “your reps,” “your process”
  • Read-aloud test: each email has to flow naturally in 15 seconds

Personalization variables

The skill expects you to fill in specific fields: company name, prospect name, title, the pain point you’re targeting, and any relevant reference company. These variables are what make the output feel researched rather than templated. If you don’t have personalization data, the skill adapts and writes without fake personalization rather than inserting hollow placeholders.

What the skill forbids

The skill never fabricates metrics, case studies, or customer results. It also blocks generic value props with no specificity, feature lists disconnected from pain points, attachments or links in early emails, jargon the prospect wouldn’t use, and weak filler phrases like “just following up” or “imagine if.”
Quote Icon
Tip: If you’re writing manager sequences by hand, borrow the skill’s accuracy rules. Use behavioral references (“Teams like those at [Company] often find…”) instead of fabricated results. It sounds more credible and doesn’t put you in a position where a prospect asks for proof you can’t provide.

How to install and use the skill in Claude Code

Setting up the skill takes about two minutes. A “skills directory” is simply the local folder where Claude Code stores reusable prompt files. Once a skill file is in that directory, Claude Code auto-detects it.

1. Get the skill file

Run the install command in your terminal: npx skills add l3mpire/claude-skills/copywriting-manager-sequence. This pulls the .md file from GitHub and places it in the right directory.

2. Start Claude Code and invoke the skill

Open Claude Code in your project. The skill is automatically detected. You can ask Claude to use it explicitly (“write a 3-email sequence for a RevOps Manager at a 200-person SaaS company”) or Claude will invoke it automatically when it recognizes a relevant request. Pass in the persona details, and the skill handles the rest.

Customizing sequences for different manager roles

While the skill generates manager-level copy by default, you’ll get better output if you adjust the pain points and language for the specific manager title. The skill accepts role-specific inputs and adapts its angle accordingly.

Sales managers

Focus on pipeline velocity, rep consistency, and quota attainment. The language references team selling motions, coaching gaps, and forecast accuracy. The skill’s pain taxonomy for sales managers includes: rep coaching, pipeline reviews, forecast calls, ramp time, and meeting quota with existing headcount.

RevOps and operations managers

Focus on tool sprawl, data quality, and process consistency across the GTM org. RevOps managers deal with stack sprawl, bad data, manual processes, and cross-team alignment. These buyers care about systems working together, so the skill uses language about infrastructure rather than individual productivity.

Marketing and customer success managers

Marketing managers get copy focused on campaign execution, lead quality, and MQL-to-SQL conversion. Customer success managers get language about renewals, escalations, and early churn signals. The skill shifts its vocabulary depending on which manager type you specify.

Launching your manager sequence in a multichannel campaign

The skill generates the email copy. But copy alone isn’t a campaign. You still have to load it into an outbound platform, pair it with other channels, and actually send it to the right people.

1. Import your manager-level lead list

Upload from your CRM or a CSV, or build a list using filters for manager-level titles. With lemlist, you can search a database of 450M+ contacts and filter by role and seniority to find the managers who match your ICP.

2. Enrich contacts with verified data

Before launching, enrich leads with verified emails and phone numbers. This prevents you from burning sender reputation on dead addresses. lemlist pulls enrichment from multiple data providers in one step.

3. Load the sequence and add LinkedIn or call steps

Paste the skill’s email output into your campaign steps, then layer in LinkedIn connection requests or call tasks between emails. Running all channels from one workflow (instead of juggling separate tools) keeps your messaging consistent and your timing tight.

4. Activate and monitor replies

Launch the campaign and track opens, replies, and bounces from a unified inbox. If you’re using lemlist, you can manage responses across senders and channels in one place, which is especially useful when multiple reps are running the same manager sequence against different territories.
Start a 14-day free trial to load your manager sequences into multichannel campaigns with built-in deliverability tools and lead enrichment.

Common mistakes when writing outbound sequences for managers

Even with a skill handling the copy, there are pitfalls that can tank your results:
  • Writing to the VP instead of the manager: using strategic language about revenue and market share when the manager cares about team execution
  • Pitching in the first email: leading with product features before establishing that you understand the operational problem
  • Making every email the same length and tone: each email in the sequence has a distinct purpose and gets progressively shorter
  • Skipping personalization fields: sending the raw skill output without filling in prospect-specific details makes the whole sequence feel generic
  • Ignoring the channel mix: relying on email alone when managers are often more responsive on LinkedIn, especially in tech

Turn AI-generated sequences into booked meetings

The copywriting manager sequence skill gives you the copy. What it doesn’t give you is the infrastructure to send it at scale, track what’s working, and iterate across channels.
That’s where the gap usually shows up. Teams generate strong copy, then paste it into a disconnected set of tools, lose visibility, and wonder why reply rates are flat. The fix is straightforward: use one platform that connects lead discovery, enrichment, multichannel sequencing, and deliverability monitoring.
lemlist does exactly that. You can load your manager sequences, enrich leads with verified contact data, add LinkedIn and call steps alongside your emails, and monitor everything from a single dashboard.
Start a 14-day free trial to see how it works. No credit card required.

FAQs about the copywriting manager sequence skill

How many emails does the copywriting manager sequence skill generate?

The skill generates a complete 3-email outbound sequence. Each email has a different job in the arc: Email 1 names friction, Email 2 diagnoses the root cause, and Email 3 shifts to consequence and breaks up. It also outputs sequence notes explaining the logic and what to A/B test.

Can the skill output be used outside of Claude Code?

Yes. The output is plain text with standard formatting. You can copy it into any outbound platform, CRM, or email tool. It’s not locked to Claude Code or any specific sending infrastructure.

What is the difference between the manager sequence skill and a VP sequence skill?

The manager skill targets operational pain points and team-level friction, while a VP skill focuses on strategic outcomes and business-level metrics. The tone, proof points, and CTA style all differ to match each persona’s priorities and how they evaluate new tools.

Can the skill be edited to match a specific brand voice?

The skill file is a plain-text markdown document you can open and modify. You can adjust tone rules, length constraints, pain point taxonomies, and personalization fields to fit your team’s writing style. Any changes persist in your local skills directory.
RémiRémi Kokabi
Hi there, I’m Rémi, co-founder of the GTM Club powered by lemlist & Claap. If you believe Go-To-Market is the new moat in this AI-era, you should apply: https://www.thegtmclub.com/
Share this post