Write a GTM plan

Ledgerly Payroll: a focused, trust-led launch

Launch on 3 November to existing customers with a pressing payroll problem—not to the whole market with a new category claim. Our goal is sustained, paid payroll usage over the next three months, not launch-week attention.

1. Who we pursue first

Prioritise businesses with 5–25 employees using spreadsheets or an accountant: 2,170 customers.

These customers combine meaningful payroll complexity with substantially higher reported penalty incidence than other segments. The calls reinforce the pattern: fear of mistakes matters more than saving minutes.

The survey does not establish that accountants cause penalties. We should help owners gain confidence and involve their accountants where appropriate, not run an anti-accountant campaign.

Deprioritise: - 1–4 employees: low reported penalty incidence and evidence that free spreadsheets feel adequate. - Customers using another payroll tool: lower reported penalty incidence and explicit switching resistance. - 26–50 employees: revisit after proving onboarding and reliability with smaller teams.

Within the priority segments, recruit customers approaching a suitable payroll-cycle boundary who fit the product’s supported requirements. Don’t push a risky mid-cycle migration.

2. What we say—and must prove

Positioning: “More confidence in payroll, alongside your Ledgerly books.”

Suggested launch message:

> Worried about getting payroll wrong? > Meet Ledgerly Payroll, the new payroll add-on for your Ledgerly account. Check whether it fits your business and get help planning your first run. > $6 per employee per month, additional to your accounting subscription. > CTA: Check your fit and book setup help.

A 12-employee business pays $72 per month. Make pricing concrete without claiming savings unless we know what its current service includes.

The beta strongly favours the risk-reduction motivation: the penalty headline produced 117 first payrolls from 4,160 visits (2.8%), versus 38 from 4,210 (0.9%) for the speed headline—roughly three times the conversion.

But “Never get a payroll penalty again” is an unacceptable guarantee, and the test does not prove a safer alternative will perform equally well. Test qualified confidence-led copy against the speed message, using first payroll—not clicks—as the outcome.

Before publication, verify every supporting claim against the shipped product: supported payroll requirements, calculations, checks, filing responsibilities and support coverage. Demonstrate verified capabilities; don’t substitute reassuring language for evidence.

3. Channels and launch sequence

Before 3 November: establish readiness

• PM, engineering and payroll specialists sign off supported customer types, critical workflows, known limitations and escalation procedures.
• Prepare a migration checklist, pricing page, product demonstration and clear explanation of customer versus Ledgerly responsibilities.
• Recruit a small assisted cohort across both priority segments; expand only when onboarding works reliably.

3 November–2 December: targeted launch

Replace the universal banner with segmented in-app messages and targeted email to the 2,170 eligible accounts. Use different examples for spreadsheet owners and accountant-managed businesses.

Run the webinar as a practical clinic: “Preparing your first Ledgerly payroll.” Show the workflow, explain limitations and answer switching questions. Invite accountants alongside owners.

Offer scheduled onboarding sessions and follow up with customers who start setup but stall. Sequence invitations to match support capacity.

Drop the “first Financial Operating System” press release. It is unsupported and disconnected from the buying need. Publish a straightforward customer announcement instead.

3 December–2 January: remove friction

Review setup abandonment, migration objections and support tickets weekly. Improve the biggest bottleneck before increasing invitation volume.

Build a customer proof point only with consent and verified results. Adapt clinic and support coverage around customers’ payroll schedules and holiday availability.

3 January–2 February: scale selectively

Expand outreach within the priority cohort if reliability and repeat usage hold. Test a small adjacent segment only after reviewing its requirements and switching barriers.

Pause the proposed $60,000 new-prospect advertising spend. Fund onboarding, measurement and targeted customer communications first; release broader acquisition budget only after proving retained adoption and service economics.

4. How we know it works

North star: paying businesses running repeat payroll successfully.

Instrument the account-level funnel by segment and channel:

Eligible → reached → setup started → setup completed → first successful payroll → next scheduled payroll → retained paid account.

Keep a random 10% holdout from proactive promotion, without blocking access, to estimate incremental adoption. Track assisted and self-serve onboarding separately.

Provisional three-month goals—not forecasts: - 200 accounts complete a first successful paid payroll, about 9% of the priority cohort. - At least 80% run their next scheduled payroll when due. - At least 90% paid retention at 60 days among accounts old enough to measure.

Track actual employee counts and payroll MRR, onboarding cost, support load, critical errors and filing exceptions where applicable. Pause expansion for unresolved critical failures.

Review weekly; make monthly scale-or-fix decisions. Monitor penalty complaints, but don’t claim penalty reduction from a three-month window. Press mentions and sign-ups are diagnostics, not success.

Ledgerly Payroll: go-to-market plan

What I'd change in Marketing's draft

Who we go after first

Wave 1 (3 Nov): customers with 5–25 employees who run payroll via spreadsheet (690) or an accountant (1,480). That is 2,170 customers, 27% of the base.

• They have the pain. 19% (spreadsheet) and 23% (accountant) got a payroll penalty notice last year, versus 4–6% for businesses with 1–4 staff and 5–7% for those already on a payroll tool.
• They have the money. At $6 per employee, a 12-person business pays about $72 a month, against the $180 a month one landscaper pays their accountant.
• The calls match the data. The bakery, plumber, physio, landscaper and dental practice all describe fear of mistakes, not lack of time.

Not now: - 1–4 employees (4,160 customers): The spreadsheet is "fine" and "free," and only 4–6% were penalized. Leave payroll available in the product but don't push it. - Other-tool users (1,670 customers): Penalty rates are low (5–7%), and switching mid-year "sounds like a nightmare." Revisit at the start of the next tax year with a migration offer.

What we say

The beta test was randomized. "Never get a payroll penalty again" beat "Run payroll in minutes" on setup starts (6.4% vs 2.2% of visits) and on first payroll runs (2.8% vs 0.9%), about 3x on both. Once people started, completion was similar (44% vs 41%), so the headline drives the decision to begin and the product handles the rest.

Core message: "Payroll filed right and on time, so the tax office letter never arrives."

• Spreadsheet owners: "A spreadsheet won't tell you when you've got it wrong."
• Accountant-run: "Stop paying $180 a month to worry about it." Use this to speak to cost and control without attacking accountants. Offer a way to invite their accountant in as a reviewer.

Accuracy promise: The dental practice said, "If you can promise it's right, I'm in." I'd like to offer a penalty-cover guarantee for errors caused by our software. Legal and Finance must approve it by 24 Oct. If they won't, the copy becomes "filed right and on time, with support to fix problems." We should not promise "never" without backing it. The beta headline did well, but a claim we can't stand behind creates risk.

Channels

1. Targeted in-app card and email to the Wave 1 list only, using the winning headline. This is the main channel, and it costs almost nothing.
2. Personal outreach from Customer Success to Wave 1 customers who told us they got a penalty notice (about 470 people by my estimate from the survey rates). Offer a 20-minute guided setup.
3. Webinar, reframed: "Penalty-proof your payroll" with a live setup walkthrough. Run it in launch week and again in week 4, since the second session catches people who weren't ready the first time.
4. Press: one plain release ("Ledgerly adds payroll, $6 per employee"), with no category claim. Follow with customer stories once we have them.
5. Paid: none to new prospects in November (see Budget).

Budget (the $60k)

• ~$15k: guided setup and migration help (contractor or CS time).
• ~$10k: webinars, email production, and case-study content.
• ~$35k: held until the January gate. If Wave 1 works, spend it on search ads for "payroll penalty" intent, aimed at businesses that would adopt accounting and payroll together.

How we'll know it's working (3 months)

Primary metric: paying accounts that have run at least two payrolls. This replaces sign-ups, press mentions and launch-week anything.

Targets (to be recalibrated after week 2, since the beta is my only baseline): - Month 1: at least 5% of Wave 1 has started setup. At least 45% of those run a first payroll, matching beta's 44%. - End of January: about 250 Wave 1 accounts running payroll (~11% of the segment). I'm assuming a 10-person average, which implies roughly $15k MRR. I'll replace that assumption with real headcount data. - Retention: at least 85% of those accounts run payroll in three consecutive cycles.

Guardrails (any breach pauses expansion): - Payroll errors or penalties caused by us: zero tolerance, reviewed weekly. - Support tickets per payroll run. - Churn of the core accounting subscription, which must not rise among adopters.

Measuring real impact: Hold out a random 10% of Wave 1 from all promotion. If adopters in the promoted group don't clearly exceed the holdout, we're only capturing people who would have found payroll anyway.

Decision gates: - Mid-December: If setup-to-first-payroll is below 35%, fix onboarding before pushing further. - Mid-January: If Wave 1 is at or above target and no guardrail is breached, release the held budget and start Wave 2 (other-tool users, ahead of the tax-year switch window). If it's below target, interview non-adopters before spending anything.

Caveats

• Penalty rates are self-reported, and the eight calls are anecdotes.
• Beta customers may be more enthusiastic than the base.
• I haven't seen average headcount per segment, so the revenue estimates are rough.

Ledgerly Payroll: Go-to-Market Plan (launch 3 November)

The short version

Payroll is an add-on for people who already use Ledgerly, so the launch should be aimed at our existing customers. The draft plan spends most of its effort on new prospects and press, and it uses the headline that lost our own test. I'd make three changes:

• Focus on the customers with the most painful problem.
• Lead with the message that tripled conversion in beta.
• Measure customers actually running payroll and still running it, not launch-week buzz.

1. Who we go after first

Primary: customers with 5–25 employees who run payroll in a spreadsheet or through their accountant. That's 2,170 customers.

• They have the highest penalty rates: 19% for spreadsheet users and 23% for accountant-run payroll, against 4–7% everywhere else.
• They have enough employees to matter. At roughly 12 staff, a customer is worth about $72 a month.
• The calls describe this group exactly: the bakery's $1,400 penalty, the plumber's "scared of getting it wrong", the physio who'd "move tomorrow", and the landscaper paying $180 a month for mistakes.

Second wave: customers with 5–25 employees on another payroll tool (1,210), plus the 460 with 26–50 employees. They're fairly satisfied (5–7% penalties), and switching mid-year "sounds like a nightmare." We should approach them ahead of the next tax-year start, with a migration offer. Until then we just let them know payroll exists.

Not a focus: customers with 1–4 employees (4,160). They have low pain ("a spreadsheet's fine", "annoying, but free") and low revenue per customer. They can find payroll in the product without us pushing it.

2. What we say

The lead message is penalties and accuracy, not speed. In the beta, "Never get a payroll penalty again" won clearly over the speed headline:

That's about three times as many customers running payroll, on comparable traffic of around 4,200 visits each. "Run payroll in minutes" is the losing message, and the calls explain why: "Time isn't the issue."

One important caveat: Legal must approve the penalty claim before we use it. "Never get a penalty again" is a promise. Penalties can still happen if a customer enters bad data or doesn't fund payroll on time. We have two options:

• Back the promise: for example, "If a filing we're responsible for is late or wrong, we pay the penalty." This would be the strongest version, if Finance and Legal agree.
• Soften the wording: for example, "Payroll filed correctly and on time, automatically." We would then re-test this against the winning headline in the first two weeks, because softening may reduce its effect.

Supporting points: - For accountant-run customers: "$6 per employee. For 6 staff, that's $36 a month, not $180." - For everyone: it already lives inside your books, so there's no re-entering data. This is a supporting point, not the headline.

Drop "the first Financial Operating System for small business." No customer has asked for this, it's hard to substantiate, and it says nothing about payroll.

3. Channels

Budget: move the $60,000 away from paid ads to new prospects. New prospects would have to buy accounting before they can buy payroll, so that spend works against our focus. I'd use roughly: - $25,000 for assisted setup staffing and onboarding. - $5,000 for content and the webinar. - The rest held back until December, then released only if setup completion proves to be the bottleneck.

4. How we'll know it's working (November to January)

The main goal is customers who have run at least two payroll cycles. Signing up isn't enough; running payroll repeatedly is what matters.

Check-ins: - Weekly: track the funnel by segment. - Week 2: read the headline re-test, if Legal changes the claim. - End of December: go/no-go on the held-back budget and on starting the switching campaign for customers on other payroll tools.

Caveats

• The beta participants opted in, so real launch conversion will probably be lower than the beta numbers.
• Penalty rates are self-reported.
• The 220 target is a starting estimate, not a forecast. We should revise it after the first month of real data.