Cold Email Sequence Agent

Writes a four-touch B2B cold email sequence for one ICP and one offer: subject lines, 60-110 word bodies, a different angle on every touch, and a low-friction CTA. Paste your value proposition and proof points and a rep can load the result into a sequencer today.

A Markdown cold email sequence containing: (1) four touches, each with a subject line of six words or fewer and a body of 60-110 words; (2) a stated angle and suggested send day per touch; (3) {{first_name}}/{{company}} merge fields; (4) one low-friction CTA per email; (5) a 'Why this sequence' section of 4-6 bullets covering the angle progression and the first A/B test to run.

## Sequence

### Touch 1 — Problem (day 1)
Subject: forecast built on guesses

{{first_name}}, most VPs at {{company}}'s stage are forecasting off a CRM their AEs update on Friday afternoon from memory. The pipeline looks fine until the quarter closes 15% under it. We auto-capture every call and email into Salesforce so the forecast reflects what actually happened, not what someone remembered. Is forecast accuracy something you are actively working on this quarter?

### Touch 2 — Proof (day 4)
Subject: 62% to 81% in a quarter

{{first_name}}, following up with a number rather than a pitch. Northwind runs 30 AEs on Salesforce and had the same manual-logging problem. After switching activity capture on, forecast accuracy moved from 62% to 81% inside one quarter and reps got back about 4.5 hours a week. No process change, no new tab for the team. Worth me sending the two-page write-up?

### Touch 3 — Peer pattern (day 9)
Subject: the Friday CRM ritual

{{first_name}}, a pattern I keep seeing at 50-400 person SaaS companies: the CRM is technically adopted, but the data lands in a batch every Friday, so every pipeline review is a week stale and no amount of inspection fixes it. The teams that break the pattern stop asking reps to log and capture it automatically instead. Is that the shape of it at {{company}}, or have you solved it another way?

### Touch 4 — Break-up (day 16)
Subject: closing the loop

{{first_name}}, I have not heard back, so I will assume CRM data quality is not on the list this quarter and stop emailing. If it moves up — usually right after a forecast miss — the Northwind write-up is yours for the asking. Good luck with the quarter.

## Why this sequence
- The angle moves problem to proof to peer pattern to release, so a prospect who ignores touch 1 meets a different argument rather than a louder one.
- Touch 1 opens on the forecast, not the reps: the VP of Sales owns forecast credibility, and rep hours are a benefit for a different buyer.
- Touch 2 carries the only hard number in the sequence. Spending it early beats saving it for an email nobody opens.
- Every CTA is a question. A calendar link in touch 1 asks for 30 minutes before you have earned 30 seconds.
- The break-up names the trigger (a forecast miss) so the email is worth keeping even when the answer is no.
- A/B test first: touch 1 subject line. 'forecast built on guesses' (problem) against 'your CRM is a week stale' (mechanism) will separate the two buying motivations faster than any body copy test.