# Cold B2b Email En

> 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.

- Skill: `yanaproduct-hub/cold-b2b-email-en` (Agent Skill, multi-file: 6 files)
- Install (CLI): `npx skillmds@latest add yanaproduct-hub/cold-b2b-email-en`
- Raw SKILL.md: https://api.skillmd.com/api/skills/yanaproduct-hub/cold-b2b-email-en/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: yanaproduct-hub (https://skillmd.com/u/yanaproduct-hub)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/yanaproduct-hub/cold-b2b-email-en

---


# 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:

1. What is the goal of the email?
2. 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:

1. The final email or sequence.
2. A short explanation: hook, business pain, CTA logic, and what should happen after a reply.
3. 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

1. Define the job of the email: reply, routing, call, demo, pilot permission, or silence reactivation.
2. Pick the buyer lens: HR/People, CEO/founder, operator, technical buyer, procurement, or another role.
3. Identify the strongest business trigger: hiring, growth, overload, retention, productivity, leadership load, cost pressure, quality, sales performance, delivery risk.
4. Lead with the prospect's world, not the sender's product.
5. Use one specific reason for reaching out.
6. Bridge to one business consequence.
7. Use one credible proof point only if allowed.
8. Make one low-friction CTA.
9. For sequences, each follow-up must add a new angle. Never rely on "just checking in".
10. 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.