Copyable template
Follow-up 1 (send 3-4 business days later in the same thread): Subject: Re: [Original Subject] Hi [First Name], Quick follow-up in case my note from [day] got buried. Since then, I put together a [small concrete asset, e.g., 60-second clip showing how it handles X / quick breakdown of Y] here: [Short URL]. Still happy to [original small ask, e.g., set up a sandbox account] if [specific pain point] is on your radar this quarter. If not, just say the word and I will leave you alone. Best, [Your Name] --- Follow-up 2 (send 5-7 business days after Follow-up 1, final message): Subject: Re: [Original Subject] Hi [First Name], I will assume [specific problem] is not a priority right now, so this is my last note on [Product Name]. If it ever comes up later, you can try the self-serve demo anytime at [Product URL]. Wishing you a smooth rest of the month. Best, [Your Name]
When to use this template
Use this two-step follow-up whenever an initial cold outreach email (such as a beta invite, newsletter pitch, podcast pitch, or partnership note) goes unanswered after three to four business days. Busy founders, editors, and engineering leads often intend to reply to a short relevant note and simply lose it under fifty newer emails.
Keep both follow-ups inside the original email thread so the recipient has full context without searching their inbox. Stop after Follow-up 2. Two respectful nudges catch missed messages without tipping into spam.
How to fill each placeholder
- Reply in the same thread ('Re: [Original Subject]'): Keeping the original message quoted underneath lets the reader skim your first pitch in two seconds and decide whether to respond.
- [small concrete asset]: Give Follow-up 1 a real reason to exist beyond 'just bumping this.' A 60-second silent screen recording, a one-page example, or a tiny relevant observation adds value without asking for extra time.
- [original small ask]: Restate the exact low-effort next step from email one so they do not have to scroll down to remember what you wanted.
- Follow-up 2 closing line: Make it a genuine final message with zero passive-aggressive guilt. Leaving a clean door open preserves your reputation if they need your tool six months later.
Filled example (made-up product)
Example using a made-up database migration monitor called SchemaWatch: Follow-up 1 (sent 4 business days later): Subject: Re: Quick invite to test SchemaWatch (catching risky Postgres migrations) Hi David, Quick follow-up in case my note from Tuesday got buried. Since then, I recorded a 45-second silent clip showing how SchemaWatch flags an unindexed foreign-key lock inside a GitHub PR before merge: https://schemawatch.example/clip Still happy to send a staging invite if migration safety is on your radar this quarter. If not, just say the word and I will leave you alone. Best, Kiran --- Follow-up 2 (sent 6 business days after Follow-up 1): Subject: Re: Quick invite to test SchemaWatch (catching risky Postgres migrations) Hi David, I will assume migration checks are not a priority right now, so this is my last note on SchemaWatch. If it ever comes up later, you can paste a sample SQL migration into the public sandbox anytime at https://schemawatch.example/try. Wishing you a smooth rest of the month. Best, Kiran
Mistakes to avoid
- Using passive-aggressive breakup lines like 'I guess you are too busy to save time' or 'Are you being chased by a bear?' Cute guilt trips get your domain marked as spam.
- Sending six automated follow-ups over three weeks. If someone ignores an initial pitch and two short replies, more emails only hurt your sender reputation.
- Writing 'Just checking in!' with nothing new. Every follow-up should stay under sixty words and either add one useful link or cleanly close the loop.
- Following up the very next morning. Give busy recipients at least three business days before your first bump.
Related tools and guides
Free tool
Cold DM & Early Adopter Outreach GeneratorGenerate high-converting, non-spammy direct outreach templates for X, LinkedIn, and email to land your first 20 beta users.Free tool
UTM Link BuilderBuild a tagged link for every place you launch, so your analytics shows what each one sent.Founder guide
Cold Email for Solo Founders: How to Land Your First 10 B2B CustomersA plain outreach framework that doesn't feel pushy, protects your domain and doesn't need expensive lead lists.Founder guide
How to Find Beta Testers for Your App (2026)What to ask of a beta, how many testers you need, where to find them, how to invite them, and how to turn the best ones into your first customers.More templates
Pritam Ghosh runs Hauntboard and maintains these templates.
Published · Updated
Ready to put your launch in front of real visitors?
A person reviews every launch on Hauntboard, and every view and visit it sends your site is published on your launch page. Free to submit.