A sequência de 5 e-mails a frio que agenda reuniões B2B sem soar como um robô de vendas
Why this prompt matters
Cold email is the highest-ROI outbound channel in B2B when done well — and most teams do it badly. The most common failures: emails that are too long, subject lines that telegraph 'sales email,' no social proof, and breakup emails that are passive-aggressive. A well-structured 5-email sequence with the right cadence can generate 8–15% reply rates versus the 1–3% industry average.
What we use it for
A B2B founder or SDR needs to book meetings with VP-level buyers at target accounts. They have a product that works but no battle-tested outbound sequence. They need something they can load into Outreach, Apollo, or HubSpot sequences and start sending by end of day.
Prompt
Act as an expert B2B sales copywriter who has written cold email sequences generating over $10M in pipeline across SaaS, consulting, and professional services. Context: - Company: [YOUR COMPANY NAME] - Product/Service: [1-2 SENTENCE DESCRIPTION — what you sell and who it's for] - Target persona: [JOB TITLE + COMPANY TYPE, e.g., "VP of Engineering at Series B SaaS companies"] - Main pain point you solve: [THE SPECIFIC PROBLEM, e.g., "engineers spending 40% of time on manual code review"] - Proof point: [ONE SPECIFIC RESULT OR CREDENTIAL, e.g., "customers cut review time by 60% in the first month"] - Desired action: [WHAT YOU WANT THEM TO DO, e.g., "book a 20-minute call" or "try a free trial"] - Tone: [CHOOSE: Professional / Conversational / Direct / Challenger] Task: Write a 5-email cold email sequence, one email per numbered section. Each email must include: - Subject line (A + B variants for A/B testing) - Preview text (45 characters max) - Email body Sequence arc: 1. Email 1 — Cold Intro (Day 1): Hook with the specific pain, present the claim, soft CTA 2. Email 2 — Value Add (Day 4): Share a relevant insight, article, or framework — no hard sell 3. Email 3 — Social Proof (Day 8): Customer story or data point, tighten the CTA 4. Email 4 — Different Angle (Day 13): Reframe the problem from a different perspective; assume they've seen the previous emails 5. Email 5 — Breakup (Day 18): Honest, direct. Not passive-aggressive. Leave the door open. Rules: - No subject lines with "Quick question", "Following up", or "touching base" - Each email body: 60-120 words maximum — shorter wins in cold outreach - No buzzwords: "synergies", "value-add", "leverage", "streamline" - Every sentence must earn its place — cut anything that doesn't move the reader forward - Write for someone who has never heard of you and is mildly skeptical Output format: Return all 5 emails in clearly labeled sections. Include a 2-sentence send-timing note at the top explaining the overall strategy.
Result
Send-timing note: This sequence runs over 18 days with deliberate gaps. The goal isn't volume — it's arriving at the right moment with a different message each time, so each email feels like a fresh attempt rather than a nagging reminder.
Email 1 — Cold Intro (Day 1)
Subject A: The reason your engineers hate Mondays
Subject B: {First name}, your code review queue
Preview text: It's not the volume. It's the wait.
Hi {First name},
Most engineering teams I talk to aren't struggling because they write bad code — they're struggling because review cycles take 3-5 days and block everything downstream.
We built Reviewly to cut that to under 4 hours without adding reviewers. Quora's team went from a 4-day median to 3.8 hours in the first month.
Worth a 20-minute look?
[Your name]
Email 2 — Value Add (Day 4)
Subject A: What Google's eng culture got right (that most don't copy)
Subject B: The 2-reviewer rule and why it backfires
Preview text: One finding from 400 engineering orgs.
Hi {First name},
We analyzed review patterns across 400 engineering orgs last quarter. The teams with the fastest cycles share one thing: they separate "blocking" from "non-blocking" feedback at the point of review, not at the point of merge.
Thought it might be useful given what you're scaling. Happy to share the full breakdown — no strings.
[Your name]
Email 3 — Social Proof (Day 8)
Subject A: How Lattice's infra team cut review time by 61%
Subject B: {First name} — one number from a similar team
Preview text: 61% faster. Same team, same headcount.
Hi {First name},
Lattice's infrastructure team was at 4.5-day median review cycles when they started using Reviewly. Three months later: 1.7 days. Same 8-person team, no new hires.
The biggest change was surfacing which PRs were genuinely blocked vs. just waiting. Happy to walk through exactly how they set it up — takes 20 minutes.
[Your name]
Email 4 — Different Angle (Day 13)
Subject A: The hidden cost of slow reviews isn't velocity
Subject B: {First name}, it's a retention problem
Preview text: Senior engineers leave because of this.
Hi {First name},
I've sent a few notes — I'll try a different angle. The teams most motivated to fix review cycles aren't worried about velocity. They're worried about their senior engineers.
SR engineers who spend >30% of their time waiting on reviews are 2.4x more likely to start looking externally within 6 months (our data, n=1,200). That's the real cost.
Happy to talk if the timing's better now. [Calendar link]
[Your name]
Email 5 — Breakup (Day 18)
Subject A: Closing the loop, {First name}
Subject B: Last one from me
Preview text: Not a fit right now — totally fine.
Hi {First name},
I'll stop reaching out after this — I don't want to be another thing cluttering your inbox.
If review cycle time ever becomes a priority, I'd genuinely enjoy the conversation. The door's open whenever.
Either way, good luck with the build.
[Your name]
O e-mail frio tem um problema de reputação. A maior parte merece — muito longo, genérico demais, linhas de assunto que gritam "e-mail de vendas" e mensagens de despedida que parecem um texto passivo-agressivo. O resultado: taxas de resposta estagnadas em 1–3% em toda a indústria.
O prompt acima é construído em torno do único insight que separa as sequências frias de alto desempenho do ruído: cada e-mail na sequência tem uma única função, e essa função muda a cada envio.
A Arquitetura de Cinco E-mails
A maioria dos vendedores envia a mesma mensagem cinco vezes seguidas com uma frase de abertura diferente. Esta sequência é estruturalmente diferente:
- E-mail 1 (Dia 1 — Introdução Fria): Atraia com uma dor específica. Apresente sua proposta. Pergunte uma vez, de forma sutil.
- E-mail 2 (Dia 4 — Agregação de Valor): Ofereça algo útil sem pedir nada em troca. Este é o e-mail que será encaminhado internamente.
- E-mail 3 (Dia 8 — Prova Social): Um resultado de cliente que reflita a situação do lead. Agora o CTA é mais direto, pois você construiu credibilidade em dois contatos anteriores.
- E-mail 4 (Dia 13 — Ângulo Diferente): Reenquadre o problema por uma perspectiva que eles não consideraram. Presume que viram os outros e-mails — não finge o contrário.
- E-mail 5 (Dia 18 — Despedida): Honesto e direto. Sem culpa, sem agressividade passiva. Deixa a porta aberta. Frequentemente obtém a maior taxa de resposta da sequência por ser o mais humano.
Por que as Regras do Prompt Importam
A restrição de "60–120 palavras por e-mail" não é arbitrária. Pesquisas do Boomerang analisando 40 milhões de e-mails descobriram que mensagens entre 50–125 palavras obtêm as maiores taxas de resposta. E-mails mais longos sinalizam que o remetente prioriza a própria necessidade de explicar sobre o tempo do leitor.
A proibição de "Pergunta rápida", "Só um follow-up" e "retomando contato" como linhas de assunto existe porque os filtros de caixa de entrada — humanos e algorítmicos — aprenderam a despriorizá-las. Essas frases são as linhas de assunto de maior volume em e-mails de prospecção, o que significa que também são as mais ignoradas.
Os campos [entre colchetes] não são apenas placeholders — são a instrução do modelo para pedir que você forneça detalhes antes de gerar algo genérico. Se você os preencher com precisão, a saída será precisa. Se os deixar vagos ("ajudamos empresas a crescer receita"), o modelo produzirá e-mails vagos.
Adaptando a Sequência
Esta estrutura funciona em diferentes ciclos de vendas. Para ciclos mais curtos (PME, autoatendimento), comprima o cronograma: Dia 1, Dia 3, Dia 6, Dia 9, Dia 13. Para ciclos corporativos mais longos, estenda-o: Dia 1, Dia 7, Dia 14, Dia 21, Dia 30.
O e-mail de "Ângulo Diferente" (E-mail 4) é o mais adaptável. Alternativas fortes ao ângulo de retenção usado no exemplo de saída: mudança no cenário competitivo, pressão regulatória ou de conformidade, um anúncio recente na empresa deles ou um novo dado de sua pesquisa do setor.