**Subject:** From 8 hours to 2 Hi [Name], Wanted to bring one more data point to my note from last week. Loom's marketing team was spending 8 hours a week pulling reporting together; after switching to us, they're down to 2 and using the time for campaign work instead. Figured it might be relevant given how often SaaS marketing teams get buried in dashboards this time of year. Worth a 15-minute look to see if the same math could work for your team? Thanks, [Your name]
Generate Cold Email Follow-Ups That Convert Prospects
Tested prompts for cold email follow up compared across 5 leading AI models.
BEST BY JUDGE SCORE
Claude Haiku 4.5
8/10
The prompt we tested
You are an expert cold email copywriter specializing in high-converting follow-up sequences. Based on the context below, write a cold email follow-up that re-engages the prospect, adds new value, and moves the conversation forward toward a reply. Follow these rules: Write a single follow-up email under 90 words with a short subject line (max 6 words), a one-line opener that references the prior email without guilt-tripping, one sentence of fresh value or insight, and a low-friction CTA ending in a question; use plain language, no jargon, no exclamation points, and no generic phrases like 'just checking in' or 'circling back'. Context about the previous outreach, prospect, and goal: I sent a cold email 5 days ago to the VP of Marketing at a mid-sized SaaS company pitching our analytics tool that helps cut reporting time by 60%. No response yet. I want to follow up with a softer angle and maybe share a relevant customer result from a similar company (Loom reduced their reporting work from 8 hours to 2 hours per week). Return the follow-up email with a subject line, then the body. Keep it tight, human, and non-pushy.
Model comparison
| Model | Quality | Cost | Latency | Tokens |
|---|---|---|---|---|
| Claude Opus 4.7 | 8 | $0.0183 | 4.3s | 383 / 167 |
| Claude Haiku 4.5 | 8 | $0.0008 | 1.6s | 285 / 96 |
| GPT-5.4 | 8 | $0.0018 | 2.6s | 253 / 80 |
| Gemini 2.5 Pro | 7 | $0.0006 | 15.4s | 261 / 61 |
| Grok 4.1 Fast Reasoning | 6 | $0.0001 | 3.9s | 402 / 38 |
Outputs
**Subject:** One thing we missed Hi [Name], Following up on my last note about cutting reporting time. I was working with a company similar to yours (Loom) who went from 8 hours of weekly reporting to 2 hours—mostly by automating the data pulls and dashboards. Thought that might be relevant. Would that kind of time savings be useful for your team right now? [Your name]
Subject: Quick example Wanted to share one relevant example after my note last week. Loom used our analytics tool to cut weekly reporting work from 8 hours to 2, mainly by pulling campaign and pipeline data into one view instead of stitching it together manually. If reducing reporting time is even a small priority this quarter, would it be worth sending over a 2-minute walkthrough?
Subject: A thought on reporting time I sent a note last week about reducing the time your team spends on reporting. We recently helped another SaaS company, Loom, cut their weekly reporting work from 8 hours down to 2. Is optimizing your team's reporting workflow currently a priority?
Subject: Loom's reporting shortcut I emailed last week about our analytics tool. Loom cut their weekly reporting from 8 hours to 2 with it. Could this help your team?
Related queries
Try it with a real tool
Run this prompt in one of these tools. Affiliate links help keep Gridlyx free.