Email 1: Day 1
Subject: bookkeeper hiring
Hi {{first_name}},
Saw {{firm}} is hiring two junior bookkeepers. At a 20-person firm that usually means close is eating more hours than anyone wants to admit.
We work with a similar-sized firm that was taking 6 days to close each month. After automating transaction coding and reconciliations with Ledgerly, they close in 3, and they're still deciding whether they need the second hire.
Worth a look before you fill both seats?
{{sender}}
Follow-up 1: Day 4
Subject: re: bookkeeper hiring (use a fresh subject, not a fake "Re:", if your tool allows)
Hi {{first_name}},
One detail on the 6-to-3 day result. Most of the time saved came from bank-feed coding and reconciliation, the work junior bookkeepers usually spend their first year on. Review and sign-off stayed with the senior team.
If you'd like, I can send a one-page breakdown of where those three days came from, so you can compare it against your own close.
Want me to send it?
{{sender}}
Follow-up 2: Day 10
Subject: hiring math
Hi {{first_name}},
Two junior bookkeepers is a real cost once you count salary, training, and the partner time spent reviewing their work. Some firms find that automating the repetitive 60% of the job lets the same people take on more clients without adding headcount.
I'm happy to run your current close through a quick estimate. It takes about 15 minutes, and you'd come away with a number to weigh against the hiring plan, whether or not Ledgerly ends up fitting.
Open to that?
{{sender}}
Follow-up 3 (breakup): Day 18
Subject: closing the loop
Hi {{first_name}},
I'll stop here so I don't clutter your inbox. If automation is ever worth a look for {{firm}}, whether during this hiring round or at next year's busy season, just reply and I'll pick it back up.
Good luck with the new hires.
{{sender}}
Notes
- Placeholders: Replace
{{firm}}with the firm name and confirm the hiring announcement, ideally quoting where you saw it (job post, LinkedIn, press). - Proof point: If you can name the reference firm or get permission to share the quote, add it to Email 1 or Follow-up 1. That will lift replies more than any wording change.
- The "still deciding on the second hire" line: Only keep it if it's true of your reference customer. Otherwise cut it.
- "Repetitive 60%" in Follow-up 2: This is a placeholder figure. Swap in your real number or remove it.
- Cadence: Gaps grow from 3 to 6 to 8 days. Each follow-up adds a new angle (the breakdown, then the hiring cost, then an exit) and reads fine on its own.
Real run in an isolated folder with only this skill installed. Only the Skill and Read tools were enabled, so nothing was fetched from the web and no file was written. The example is fictional. The company and prospect are invented, and the model left merge fields for the real data.
What it does
Writes outbound emails that avoid the sales-template feel. Principles: write like a peer, make every sentence earn its place, connect personalisation to the problem, lead with the reader's world, and make one low-friction ask. It offers shapes such as observation, problem, proof, ask; question, value, ask; trigger, insight, ask; and story, bridge, ask. Subject lines are short and plain (2-4 words, lowercase). Follow-ups are three to five emails with growing gaps, each adding a new angle, ending with a breakup email. A long "what to avoid" list covers AI tells, jargon, feature dumps, fake "Re:" subjects and "just checking in". Reference files hold a four-level personalisation system, frameworks, benchmarks, subject-line data and sequence templates.
How it works
- It asks who the prospect is, what you want, your value and proof, and any research signals.
- It writes the first email and a follow-up sequence, using merge fields where it lacks real data.
- It runs a quality check: would you reply to this yourself?
Good for
SDRs, founders and agencies doing B2B outbound.
Low risk: pure instructions with no scripts, no network access and no file writes, so nothing here touches your machine. Legal risk is on you: the skill says nothing about anti-spam and privacy law (for example CAN-SPAM, GDPR, ePrivacy, CASL), consent, honest sender identity or unsubscribe handling, which apply in many countries, especially when you email people in the EU, UK or Canada. Check the rules for your recipients before sending. The reply-rate benchmarks come from third-party sources and vary widely. Tried once on an invented company.