01
ICP brief (excerpt)
TARGET — Independent restaurant groups, 2–10 locations, US, using legacy payroll (ADP Run / paper hybrid signals: job posts mentioning manual timesheets).
BUYER — Owner or ops director. Pain window: tip-credit compliance and Friday payroll runs.
DISQUALIFY — Single-location, franchise corporate, existing modern payroll stack visible in job posts.
LIST SOURCE — Scraped + human-verified. We do not send to pattern-guessed addresses; they bounce 6× more and burn the domain.
02
Email 1 — the specific observation
Subject: tip credits across 4 locations
Hi {FirstName},
Saw {Company} is hiring a bookkeeper who "must be comfortable with manual timesheets" — which usually means Fridays are painful.
We build payroll for restaurant groups specifically: tip-credit math, multi-location splits, and the state filings that change every January.
Worth a short email exchange? Reply and I will send a 2-paragraph summary of what switching actually involves — no call required.
{SenderName}
Northbeam PayrollDesign notes
- →Opens with proof we actually looked (their own job post), not 'hope this finds you well'
- →Next step offered in writing, 'no call required': with busy owners this doubles replies
- →One pain, one proof, one ask, about 60 words: respect for the inbox is the strategy
03
Email 2 — the proof point (4 days later)
Subject: re: tip credits across 4 locations
Hi {FirstName},
One number, then I will leave you alone until Thursday: groups your size spend a median 6 hours/week on payroll admin. Our restaurant clients report under 1.
The difference is mostly tip-credit automation and one-click multi-state filing.
If Fridays at {Company} feel like that 6-hour version, reply "summary" and I will send the 2-paragraph switching overview. In writing, at your pace.
{SenderName}04
Email 3 — the polite close (5 days later)
Subject: closing the file
Hi {FirstName},
Last email from me. Either payroll is not a problem at {Company} (genuinely great), or it is not the quarter to fix it (fair).
If it ever becomes one, this address reaches a human who knows restaurants. Until then, I will not write again.
{SenderName}
P.S. The unsubscribe link below works instantly. We are strict about that.05
Reply-handling drafts (delivered with every campaign)
REPLY TYPE: "How much does it cost?"
DRAFT: Straight answer with numbers in the email body, no "let me get you on a call". Pricing transparency doubles response-to-next-step rates in our sends.
REPLY TYPE: "Not now, maybe Q4"
DRAFT: Thank, confirm we will write back the first week of October, tag in CRM. (We actually do.)
REPLY TYPE: Angry / "stop emailing me"
DRAFT: Immediate suppression confirmation + apology. Sent within the hour. Sender reputation is built on how you handle these.
06
Weekly report format
WEEK 3 — SENT 240 (cap respected), DELIVERED 97.5%, BOUNCED 6 (all suppressed).
REPLIES 11 — 4 qualified ("summary" requests), 3 not-now (tagged Q4), 2 referrals to the right person, 2 unsubscribes (suppressed in <1h).
QUALIFIED FORWARDED — 4 threads handed to you with drafted next-step replies awaiting your approval.
COPY NOTE — Email 2 reply rate 2.1% vs Email 1 at 1.4%; the "one number" framing wins again. Next week we test the bookkeeper-hire trigger against a POS-migration trigger.