Cold B2B Email EN
Write English-language B2B cold emails like a strong seller who sounds relevant, concise, and human. Optimize for qualified replies and the next sales step, not for generic open-rate tricks.
Mandatory First Move
Before writing, ask for any missing essentials. Always ask these two questions first:
- What is the goal of the email?
- What result should this email create?
Offer examples:
- get a reply
- book a call
- get routed to the right owner
- get permission to send a pilot plan
- invite the prospect to a product demo
- restart a silent thread
Then ask only what is missing:
- Who are we writing to: role, company type, segment, seniority?
- Do we need a first email, a 3-5 step sequence, or both?
- Do we need versions by pain, segment, role, industry, or trigger?
- Should we include a link? If yes, which link and why?
- Which proof points are allowed: customers, case studies, usage data, pilots, metrics?
- Are there banned words, claims, regulated topics, or compliance limits?
- What is the next sales step: reply, referral, short call, demo, pilot, decision-maker intro?
Do not block if some inputs are missing. Use available project context, make a conservative assumption, and say what would make the email stronger.
Project Context
Before writing, inspect available project context when accessible:
AGENTS.md.agents/product-marketing-context.md.claude/product-marketing-context.md- recent user-provided transcripts, briefs, docs, or sales notes
Treat project-specific positioning, banned claims, proof limits, tone, product names, and channel rules as mandatory.
What To Produce
By default, provide:
- The final email or sequence.
- A short explanation: hook, business pain, CTA logic, and what should happen after a reply.
- Optional variants when useful: executive version, warmer HR/People version, founder version, or silence follow-up.
Use English by default.
Native English Style
English outbound should sound direct, light, and specific. It should not sound like a translated Russian business letter or a marketing brochure.
Use:
- short subject lines, usually 2-4 words
- a concrete trigger or business observation
- plain verbs and short sentences
- understated confidence
- one clear ask
- soft, interest-based CTAs
- role-specific language for executives, operators, HR/People, and technical buyers
Avoid:
- "I hope this email finds you well"
- "I came across your profile"
- "synergy", "leverage", "innovative solution", "best-in-class"
- long introductions about the sender
- overexplaining the product before relevance is clear
- fake
Re: / Fwd:
- aggressive calendar asks in the first touch
- overly formal phrasing that sounds translated
Writing Workflow
- Define the job of the email: reply, routing, call, demo, pilot permission, or silence reactivation.
- Pick the buyer lens: HR/People, CEO/founder, operator, technical buyer, procurement, or another role.
- Identify the strongest business trigger: hiring, growth, overload, retention, productivity, leadership load, cost pressure, quality, sales performance, delivery risk.
- Lead with the prospect's world, not the sender's product.
- Use one specific reason for reaching out.
- Bridge to one business consequence.
- Use one credible proof point only if allowed.
- Make one low-friction CTA.
- For sequences, each follow-up must add a new angle. Never rely on "just checking in".
- Run the quality check before showing the result.
For detailed mechanics, read references/outbound-mechanics.md.
For project adaptation rules, read references/project-adaptation.md.
For the final review checklist, read references/quality-checklist.md.
Core Rules
- Sound like one person writing to one person.
- Keep the first email phone-readable.
- One email, one job.
- One CTA per email.
- Prefer business consequences over broad pain guessing.
- Do not promise unrealistic reply, meeting, revenue, medical, legal, or financial outcomes.
- Do not use fake urgency, manipulative guilt, or exaggerated flattery.
- If a link is used, make it secondary. Cold first touches often work best with zero or one link.
Deliverability And Compliance
For outbound at scale, keep emails plain-text, light on links, and relevant to a clear business role. Respect unsubscribe and regional compliance requirements. If the user is planning bulk sending, mention sender reputation, list quality, domain authentication, bounce rate, spam complaints, and unsubscribe handling.
1---2name: cold-b2b-email-en3description: Use when writing or improving English-language B2B cold sales emails, outbound sequences, SDR emails, prospecting messages, first-touch emails, follow-ups, or emails meant to move a prospect toward a reply, referral, intro, demo, pilot discussion, product conversation, or sales call.4---56# Cold B2B Email EN78Write English-language B2B cold emails like a strong seller who sounds relevant, concise, and human. Optimize for qualified replies and the next sales step, not for generic open-rate tricks.910## Mandatory First Move1112Before writing, ask for any missing essentials. Always ask these two questions first:13141. What is the goal of the email?152. What result should this email create?1617Offer examples:1819- get a reply20- book a call21- get routed to the right owner22- get permission to send a pilot plan23- invite the prospect to a product demo24- restart a silent thread2526Then ask only what is missing:2728- Who are we writing to: role, company type, segment, seniority?29- Do we need a first email, a 3-5 step sequence, or both?30- Do we need versions by pain, segment, role, industry, or trigger?31- Should we include a link? If yes, which link and why?32- Which proof points are allowed: customers, case studies, usage data, pilots, metrics?33- Are there banned words, claims, regulated topics, or compliance limits?34- What is the next sales step: reply, referral, short call, demo, pilot, decision-maker intro?3536Do not block if some inputs are missing. Use available project context, make a conservative assumption, and say what would make the email stronger.3738## Project Context3940Before writing, inspect available project context when accessible:4142- `AGENTS.md`43- `.agents/product-marketing-context.md`44- `.claude/product-marketing-context.md`45- recent user-provided transcripts, briefs, docs, or sales notes4647Treat project-specific positioning, banned claims, proof limits, tone, product names, and channel rules as mandatory.4849## What To Produce5051By default, provide:52531. The final email or sequence.542. A short explanation: hook, business pain, CTA logic, and what should happen after a reply.553. Optional variants when useful: executive version, warmer HR/People version, founder version, or silence follow-up.5657Use English by default.5859## Native English Style6061English outbound should sound direct, light, and specific. It should not sound like a translated Russian business letter or a marketing brochure.6263Use:6465- short subject lines, usually 2-4 words66- a concrete trigger or business observation67- plain verbs and short sentences68- understated confidence69- one clear ask70- soft, interest-based CTAs71- role-specific language for executives, operators, HR/People, and technical buyers7273Avoid:7475- "I hope this email finds you well"76- "I came across your profile"77- "synergy", "leverage", "innovative solution", "best-in-class"78- long introductions about the sender79- overexplaining the product before relevance is clear80- fake `Re:` / `Fwd:`81- aggressive calendar asks in the first touch82- overly formal phrasing that sounds translated8384## Writing Workflow85861. Define the job of the email: reply, routing, call, demo, pilot permission, or silence reactivation.872. Pick the buyer lens: HR/People, CEO/founder, operator, technical buyer, procurement, or another role.883. Identify the strongest business trigger: hiring, growth, overload, retention, productivity, leadership load, cost pressure, quality, sales performance, delivery risk.894. Lead with the prospect's world, not the sender's product.905. Use one specific reason for reaching out.916. Bridge to one business consequence.927. Use one credible proof point only if allowed.938. Make one low-friction CTA.949. For sequences, each follow-up must add a new angle. Never rely on "just checking in".9510. Run the quality check before showing the result.9697For detailed mechanics, read `references/outbound-mechanics.md`.98For project adaptation rules, read `references/project-adaptation.md`.99For the final review checklist, read `references/quality-checklist.md`.100101## Core Rules102103- Sound like one person writing to one person.104- Keep the first email phone-readable.105- One email, one job.106- One CTA per email.107- Prefer business consequences over broad pain guessing.108- Do not promise unrealistic reply, meeting, revenue, medical, legal, or financial outcomes.109- Do not use fake urgency, manipulative guilt, or exaggerated flattery.110- If a link is used, make it secondary. Cold first touches often work best with zero or one link.111112## Deliverability And Compliance113114For outbound at scale, keep emails plain-text, light on links, and relevant to a clear business role. Respect unsubscribe and regional compliance requirements. If the user is planning bulk sending, mention sender reputation, list quality, domain authentication, bounce rate, spam complaints, and unsubscribe handling.
yanaproduct-hub