Generate follow-ups
Runs on Cloudflare Workers AI. Free: 10 generations an hour, 25 a day per visitor, and a shared daily allowance for everyone. Nothing you enter is stored.
How it works
Paste the original
The follow-up has to know what was already said so it does not repeat it. Paste the first email, or a summary of it.
Choose step and angle
Step number and days since the last send set the tone. The angle decides what is new: a proof point, a resource, a different pain, a question, or a breakup.
Two options
Each under 70 words, each adding one new thing, each ending with an easy question — or, for a breakup, a graceful permission to close the loop.
Thread it
Send as a reply in the same thread so the original sits underneath; the follow-up does not need to restate it.
Why follow-ups fail
Because they contain no information. “Following up on my email below” asks the reader to re-read something they already skipped and adds nothing to change their mind. The follow-ups that get answered treat each step as a new argument: a number the first email did not have, a customer in the reader's industry, a short resource that is useful whether or not they reply, or a sharper version of the pain. The breakup email works for a different reason — it lowers the cost of saying no, and a “not now, try in Q1” is a real outcome.
Spacing and count
Three to five steps over two to three weeks is the range where reply rates hold and complaint rates stay low. Two days is too soon for step two; a week is about right, then five to seven days between the rest. Every step should be shorter than the one before. The sequence planner lays out the calendar for a fleet; this page writes the words for one step at a time.
How the generator is tuned
The model behind this page is an open-weight model running on Cloudflare's network, and the instructions it follows are mine — the same rules I apply when I edit a client's sequence: short sentences, no marketing words, open with the reader, one question at the end, keep merge tags intact. Those instructions are edited over time as I see what it gets wrong, so the output improves without the page changing. It is a starting draft, not a finished campaign: read it as you would a junior writer's work, cut what does not fit, and run the result through the readability checker and spam word checker before it goes into a sequence.
Limits and privacy
Each visitor gets ten generations an hour and twenty-five a day, and there is a shared daily allowance across the whole site that resets at 00:00 UTC — when it runs out the tool says so rather than failing silently. Inputs are sent to the model and discarded; nothing is stored, logged with your text, or used to train anything. The generated text is yours.
Frequently asked questions
Should follow-ups be in the same thread?
Yes, for steps two to four. The original is visible below, so the follow-up can be short, and a threaded reply looks like a conversation rather than a campaign. Start a new thread only for a genuinely new angle weeks later.
How short is too short?
A one-line follow-up with a real question is fine — “Does the inbox rate drop I mentioned match what you see?” is a complete step two. Under 70 words is the ceiling, not the target.
What if I do not have new value to add?
Choose the breakup angle or skip the step. A follow-up with nothing new hurts more than no follow-up.
Is my original email stored?
No. It is sent to the model for the one request and not kept.
Limits?
Ten generations an hour, twenty-five a day per visitor, plus a site-wide daily allowance that resets at 00:00 UTC.
Last reviewed
What to run next
The checks that most often follow this one.
More in this category
Guides that go deeper
When the tools tell you something is wrong
The diagnostics here are free and always will be. When the fix is bigger than a DNS record, this is the work I do.
Deliverability rescue
Mail landing in spam, replies gone quiet, or a domain suddenly blocked. I find the actual cause rather than guessing, and fix it.
- Authentication and alignment failures
- Blocklist delistings and reputation repair
- Gateway and filter-level blocks
- A written report on what broke and why
Email & sending infrastructure
Sending domains, inboxes, authentication and warmup, built to survive volume instead of burning down in a month.
- Domain and inbox fleets at any scale
- SPF, DKIM, DMARC and tracking domains
- Google Workspace and Microsoft 365 inboxes
- Handover documentation you actually own
Domain, DNS & migration
Changing registrar, mail provider or host without a day of downtime or a week of mail silently failing.
- Registrar and nameserver moves
- Workspace and Microsoft 365 migrations
- MX, SSL and subdomain cutover
- Staged rollout with rollback at every step
Monitoring & retainer
Infrastructure drifts. Records get edited, certificates expire, domains get listed. Ongoing eyes on the fleet.
- Scheduled checks across every domain
- Alerts before your clients notice
- Monthly reporting
- Priority response when something breaks
Start with a call
Bring a domain and the symptom. I will tell you what is actually wrong and whether you need me at all — plenty of people leave that call able to fix it themselves.
Thirty minutes, no pitch
We will run the checks together on your actual domains, and you will leave knowing what is broken, what it takes to fix, and what it should cost. If that is a job you can do in-house, I will say so.