La Secuencia de 5 Correos Fríos que Agenda Reuniones B2B Sin Sonar como un Robot de Ventas
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]
El correo en frío tiene un problema de reputación. La mayor parte lo merece: es demasiado extenso, demasiado genérico, con asuntos que gritan "correo de ventas" y mensajes de cierre que parecen un texto pasivo-agresivo. El resultado: tasas de respuesta estancadas en el 1-3% en toda la industria.
El mensaje anterior se basa en una idea que separa las secuencias en frío de alto rendimiento del ruido: cada correo en la secuencia tiene una única función, y esa función cambia cada vez.
La arquitectura de cinco correos
La mayoría de los vendedores envían el mismo mensaje cinco veces seguidas con una frase de apertura diferente. Esta secuencia es estructuralmente distinta:
- Correo 1 (Día 1 — Introducción en frío): Engancha con un dolor específico. Expón tu propuesta. Pregunta una vez, con suavidad.
- Correo 2 (Día 4 — Aporte de valor): Entrega algo útil sin pedir nada a cambio. Este es el correo que se reenvía internamente.
- Correo 3 (Día 8 — Prueba social): Un resultado de un cliente que refleje su situación. Ahora la llamada a la acción es más directa porque has construido credibilidad en dos puntos de contacto previos.
- Correo 4 (Día 13 — Ángulo diferente): Reformula el problema desde una dirección que no han considerado. Asume que han visto los otros correos, no finge lo contrario.
- Correo 5 (Día 18 — Cierre): Honesto y directo. Sin culpa, sin agresividad pasiva. Deja la puerta abierta. A menudo obtiene la tasa de respuesta más alta de la secuencia porque es lo más humano.
Por qué importan las reglas del mensaje
La restricción de "60–120 palabras por correo" no es arbitraria. Una investigación de Boomerang que analizó 40 millones de correos encontró que los mensajes entre 50 y 125 palabras obtienen las tasas de respuesta más altas. Los correos más largos indican que el remitente prioriza su propia necesidad de explicar sobre el tiempo del lector.
La prohibición de "Pregunta rápida", "Dando seguimiento" y "Retomando contacto" como asuntos existe porque los filtros de la bandeja de entrada — humanos y algorítmicos — han aprendido a despriorizarlos. Estas frases son los asuntos de mayor volumen en los correos salientes, lo que significa que también son los más ignorados.
Los campos entre [corchetes] no son solo marcadores de posición: son la instrucción del modelo para que pidas detalles específicos antes de generar algo genérico. Si los completas con precisión, la salida será precisa. Si los dejas vagos ("ayudamos a las empresas a crecer sus ingresos"), el modelo producirá correos vagos.
Adaptación de la secuencia
Esta estructura funciona en distintos ciclos de ventas. Para ciclos más cortos (PYMES, autoservicio), comprime el cronograma: Día 1, Día 3, Día 6, Día 9, Día 13. Para ciclos empresariales más largos, extiéndelo: Día 1, Día 7, Día 14, Día 21, Día 30.
El correo de "Ángulo diferente" (Correo 4) es el más adaptable. Buenas alternativas al ángulo de retención usado en el ejemplo de salida: cambio en el panorama competitivo, presión regulatoria o de cumplimiento, un anuncio reciente en su empresa o un nuevo dato de tu investigación del sector.