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.
它做什麼
寫出沒有銷售範本味的開發信。原則:像同行一樣寫、每句話都要有存在的理由、讓個人化服務於問題、先談對方的世界、只提一個低門檻的請求。提供幾種結構:觀察→問題→證據→請求、提問→價值→請求、觸發事件→洞察→請求、故事→過渡→請求。主旨行簡短樸素(2~4 個詞、小寫)。跟進郵件是 3~5 封、間隔逐漸拉長,每封換一個新角度,最後以「告別郵件」收尾。一份很長的「要避免什麼」清單涵蓋 AI 腔、行話、堆功能、偽造的 “Re:” 主旨與「只是跟進一下」。參考文件包括四級個人化體系、寫作框架、基準資料、主旨行資料與序列範本。
運作方式
- 詢問對方是誰、你想要什麼、你的價值與證據,以及調查到的訊號。
- 寫出第一封郵件與跟進序列,缺少真實資料的地方用合併欄位預留。
- 做品質檢查:你自己收到會回嗎?
適合什麼場景
做 B2B 主動開發的業務開發、創辦人與代理機構。
低風險:純指令檔,沒有腳本,不連網、不寫檔,不會動你的電腦。法律風險要由你自己承擔:這個 Skill 完全沒有提到反垃圾郵件與隱私法律(例如 CAN-SPAM、GDPR、ePrivacy、CASL)、使用者同意、真實的寄件者身分或退訂處理,而這些在許多國家都適用,尤其是你寄信給歐盟、英國或加拿大的人時。寄出前請先查清收件人所在地的規定。回覆率基準資料來自第三方,差異很大。已用一家虛構公司試用過一次。