WORKED EXAMPLE
Cold outreach, rewritten line by line.
“HireFast AI” is a fictional client — this page shows the method, not a testimonial. The scenario and numbers mirror patterns we see in real SaaS sequences; no real company's data appears here.
A seven-person sales team, 2,400 prospects, eight weeks — and a 0.9% reply rate. The sequence wasn't broken because of the product. It was broken because it read like every other AI vendor in the inbox. Here is the rewrite, and the reasoning behind every change.
Before — the email that got ignored
154 words, ten filler markers (“transformative”, “revolutionizing”, “cutting-edge”…). The kind of email your own inbox deletes on sight.
Hi [First Name],
I hope this email finds you well.
I wanted to reach out regarding HireFast AI, a transformative AI-powered solution that is revolutionizing how HR teams source and screen candidates. We've built a cutting-edge platform that leverages advanced machine learning to unlock significant value for forward-thinking organizations like [Company].
Our solution helps companies: streamline their hiring process · drive 10x improvement in time-to-hire · empower recruiters with AI-powered insights · foster better candidate experiences.
I'd love to schedule a 30-minute call next week to discuss how HireFast AI can help [Company] achieve its hiring goals.
Are you available for a quick chat?
After — the same pitch, done like homework
92 words, zero filler. One concrete observation, one anonymized number a call can stand on, one low-friction ask.
Hi [First Name],
Pulled your careers page this morning. Sr Software Engineer posted 6 weeks ago, still open. That usually means one of three things: spec too narrow, title mismatch in LinkedIn search, or sourcing from lists that were already burned.
We rebuild top-of-funnel for HR teams as a fixed 2-week engagement. One of our clients (anonymized, Series B HR tech) cut time-to-first-interview from 22 days to 9.
Happy to walk through the approach against your actual req, no pitch deck. 15 min Tuesday or Thursday?
The sample emails are shown in English — the language they were written in.
The rest of the sequence
Each followup carries a different frame — a concrete example, a skip-if-fine, a genuine question, a clean exit. The original just repeated itself.
day 3 — one concrete thing we do differently
The thing that separates us from the other ATS vendors in your inbox: we rewrite the job posting itself before we touch candidate scoring. Around 60% of filtering happens before any resume lands. One real example: a client kept rejecting qualified senior engineers because their posting said “Engineer III” instead of “Senior Engineer” — LinkedIn search does not match those two. Want me to audit the posting itself at no cost? 15 min on a call.
day 7 — skip this if hiring is fine
Last check-in. If your Sr Engineer role has moved since I wrote, please ignore. If the req is still stuck, I can walk through three specific changes that usually move the pipe: spec phrasing, sourcing pattern, first-interview flow. Otherwise I'll stop bothering you.
day 14 — 1 question and then I'll go
Genuinely curious, no pitch. When your team has a senior req that sits 45+ days, what's the usual next step internally? Retainer recruiter, raise the comp, rewrite the spec, or keep waiting? We see all four and the outcomes are very different.
day 21 — closing the loop
No reply, so I'll stop here. If a slow-moving req becomes a problem later and you want to see the approach, reply to this thread anytime and I'll jump back in.
Three alternate openers for the A/B week
A — pain-led — why your Sr Engineer req sits open after 47 days
You've had Sr Software Engineer posted for 6 weeks. Not a comment on the role, just a pattern. It's usually one of three things, and two are cheap to fix.
B — curiosity-led — the 60% filtering nobody talks about
Most hiring bottlenecks aren't inside the ATS. They're in the job posting itself, before anyone clicks apply.
C — observation-led — 3 things I noticed on your careers page
Spent 10 minutes on your careers page before writing this. Three things jumped out that usually correlate with slow senior-engineer hiring. None of them are the candidate funnel.
Why each change, in one line each
- Subject: “Partnership opportunity” says nothing; “your Sr Engineer req has been live 47 days” says we did the homework.
- Opener: “I hope this email finds you well” signals zero research — replaced with evidence we read their careers page.
- Claim: “10x faster” is unverifiable vendor-speak; “22 days to 9, anonymized” survives a follow-up question.
- Ask: a 30-minute call is a big first ask; 15 minutes, two named days, “no pitch deck”.
- Filler: every marker word removed — none of them appear in the rewrite.
- Length: 154 words down to 92 — short cold emails get read.
- Voice: a person wrote this, and it reads that way.
- Structure: four followups, four different angles, one polite exit.
What we honestly tell a client to expect
In sequences we've audited, an observation-based subject line alone typically lifts open rates by a third or more, and a full rewrite moves reply rates from under 1% into the 2.5–5% band within two weeks — if the list quality holds. We don't promise specific numbers: every list and every ICP is different. What we commit to is a baseline measurement before, and a review with you after two weeks.
How it was produced
The full sequence ran through the platform's text pipeline: ICP analysis, drafts for each email, a claims-verification pass that flags any statistic without evidence, an anti-filler scan, and a final voice-consistency pass. A person reviewed every line before it left the building. About four hours of work inside a three-day window.
What this example doesn't show
- Real company names, logos or prospect data — the client is fictional by design.
- Our internal prompts, policies and thresholds — the method is shown, the machinery stays ours.
- A guarantee of your numbers — see the paragraph above.
Have a sequence like the “before”?
Send it over. We'll tell you what we'd change and quote the rewrite in writing — and if the honest answer is that copy isn't your bottleneck, we'll say that instead.
contact@castel.studio