Write a GTM plan

To: Executive Team & Head of Marketing From: PM, Ledgerly Payroll Date: October 18 Subject: Revised GTM Plan: Ledgerly Payroll Launch (3 November)

The draft marketing plan targets a generic market with high-level branding. That’s a mistake. We are launching an add-on to an existing base of 8,000 accounting customers. Our unfair advantage isn't that we're a "Financial Operating System"—it's that we already hold their financial data.

We need to scrap the broad acquisition play for November, refocus entirely on our existing base, and lead with our strongest asset: penalty anxiety and accuracy, not speed.

Here are the critical changes I am making to our launch plan.

---

1. Who We Go After First (The Wedge)

The data and customer calls tell a clear story.

• Ignore: The 1-4 employee segment doing payroll in spreadsheets (Retail shop: "Annoying, but free"). They don't feel enough pain to switch or pay $6/mo.
• Ignore: Mid-year switchers currently using dedicated payroll tools (Café group: "Switching sounds like a nightmare").
• Target (Our Wedge): Small businesses with 5–25 employees who currently rely on an accountant or a spreadsheet, and are bleeding money/stress on penalties.

Look at the data: 5–25 employee businesses using accountants or spreadsheets suffer 19% to 23% penalty rates annually. Furthermore, customer calls highlight deep resentment toward accountant-driven payroll failures ($1,400 fines, $180/mo fees for mistakes).

We will segment our 8,000 customers on Day 1 and suppress micro-businesses (1-4) from our primary payroll marketing to protect email reputation and conversion relevance.

2. What We Say to Them (The Message)

Marketing’s draft leads with: "Run payroll in minutes."

Our beta test proved this is the wrong hook. Look at the `betaheadlinetest.csv` data: * "Run payroll in minutes..." generated only 38 completed payrolls. * "Never get a payroll penalty again" generated 117 completed payrolls (more than 3x the activation rate).

Time isn't the primary enemy; fear is (Plumbing firm: "I'm scared of getting it wrong. The tax office letter was the worst week of my year").

Our Core Value Proposition: “Keep payroll inside Ledgerly. Zero manual data entry from your books, guaranteed accurate tax calculations, or we cover the penalty.” (Note: We should seriously explore a penalty-reimbursement guarantee as a killer differentiator).

3. Through Which Channels

We are shifting $50,000 of the proposed November budget away from broad paid social/search targeting cold prospects. Acquiring cold payroll customers is expensive and slow; cross-selling our 8,000 warm customers is high-margin.

• Channel 1: Targeted In-App Real Estate (Nov 3): Replace the generic banner with a dynamic state. If the user has 5–25 employees and uses an accountant/spreadsheet, show the "Never get a payroll penalty again" headline.
• Channel 2: Founder/PM Email Campaign (Nov 4–10): A direct, non-marketing-sounding email sent from me (PM) and the CEO to the 5–25 segment. Focus on the hidden costs of accountant errors and spreadsheet slip-ups. Include a 1-click "Import my data" preview.
• Channel 3: The "Fire Your Accountant's Payroll Bill" Playbook: A targeted retargeting campaign (using the remaining $10k of paid budget) aimed strictly at custom matched lists of our 5-25 employee segment, highlighting how much they can save by bringing payroll into Ledgerly alongside their bookkeeping.

4. How We’ll Measure Success (Months 1–3)

Marketing’s draft relies on vanity metrics: press mentions and launch-week sign-ups. We care about retention and activation. Ledgerly Payroll is priced at $6/employee/month; a sign-up that doesn’t run payroll is worthless.

Over the next three months, we will track four strict OKRs:

• Month 1 (Launch & Activation):
• Metric: 500 active payroll accounts set up from the 5–25 employee segment.
• Guardrail Metric: Zero critical calculation support tickets in the first 14 days. Accuracy is our brand promise; a buggy launch kills trust permanently.
• Month 2 (Expansion & Accountant Displacement):
• Metric: 30% of activated users migrating away from their external accountant/spreadsheet for payroll.
• Metric: Average team size of adopting accounts sits solidly in the 8–15 employee range (validating our wedge).
• Month 3 (Monetization & Retention):
• Metric: $15,000 in recurring monthly add-on revenue (MRR).
• Metric: 95% month-two retention for payroll runners (proving they didn't just test it for a month, but integrated it into their operations).

Summary of Changes

We are abandoning the "Financial Operating System" fluff and the broad acquisition spend. On November 3, we laser-focus on our 5–25 employee segment with a message built on fear-relief and accuracy, driving them straight into a high-converting in-app flow.

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.

Ledgerly Payroll: Go-to-Market Plan

Core change: Sell payroll to existing customers who have the most to lose from getting it wrong, lead with accuracy and penalty protection, and hold most of the $60k until we have conversion data.

What I'd change in the draft

• The headline. In the beta, "Never get a payroll penalty again" roughly tripled setup starts (6.4% vs 2.2%) and first payroll runs (2.8% vs 0.9%). But "never" is a promise we can't keep. I'd use claims the product can support, such as "Filing reminders and pre-payroll checks, so fewer penalties," and get legal sign-off before launch.
• "First Financial Operating System." It's unverifiable and means nothing to a bakery owner. Drop it.
• $60k on paid ads to new prospects. We haven't proven the product yet, and our 8,000 customers are cheaper to reach and already trust us. Paid spend should follow proven conversion.
• Success measured by press mentions and launch-week sign-ups. Neither tells us whether customers pay, use payroll, or avoid penalties.

Who we go after, in order

Penalty exposure is concentrated in businesses with 5–25 staff:

• Accountant-run at 5–25 staff: 23% got a penalty notice last year.
• Spreadsheet-run at 5–25 staff: 19%.
• Owner-run at 1–4 staff: 4%.
• Other-tool users: 5–7%.

About 2,170 customers sit in the two high-penalty 5–25 groups, and roughly 470 of them got a notice last year.

Wave 1 (launch, 3 Nov): 5–25 staff, spreadsheet or accountant-run (~2,170 customers). This is where the penalty message earns its keep. Start with the customers who got a notice, using our survey data, then the rest of the segment.

Wave 2 (mid-November): owner-run at 1–4 staff (3,140 customers). This is the largest pool but has low penalty pain, so the message is time saved. Their Sunday-spreadsheet routine is the pitch.

Wave 3 (January): other-tool users (1,670 customers). Don't ask anyone to switch mid-year (customer 4 calls it "a nightmare"). Pitch migration at the start of the new year, and offer to do the import for them.

Later: accountant-run at 1–4 staff (1,020 customers). The accountant makes this decision, so reach them through the accountant channel below.

Skip payroll messaging for businesses with no payroll pain, such as the three-person design studio (customer 3).

What we say

• Accountant-run, 5–25 staff: "Payroll filings checked and reminded before they're due. Keep your accountant and see their work in the same place." This addresses customer 2's fear of getting it wrong and customer 1's question about what they're paying for. The "keep your accountant" line is a hypothesis to test.
• Spreadsheet-run, 5–25 staff: "Stop checking payroll on Sunday night," with penalty protection as the second line.
• Owner-run, 1–4 staff: "Run payroll in minutes, right where you do your books." This is beta headline A, which is fine for a segment that cares about time, not penalties.
• Other-tool users: "We'll move your payroll over for you at the start of the new year."

Accuracy claims have to match what the product does. Customer 8 says "If you can promise it's right, I'm in," so the proof needs to be concrete: which checks run, which reminders fire, and what happens when a figure looks wrong.

Channels

1. In-app, segmented (week 1). Show headline B to the 5–25 segments and headline A to the 1–4 segment. It's free and reaches everyone who logs in.
2. Targeted email and account-manager calls (weeks 1–2). Email wave 1 from named account managers. Have support call the highest-risk accounts, those who got a notice last year, first.
3. Accountant pilot (from launch, ~25 firms). Accountants serve many of our customers, and an accountant-run customer decides with their accountant. Invite the firms that manage the most of our customers to run payroll for clients inside Ledgerly. This means we need to decide up front how partners are paid.
4. Webinar (launch week). "A payroll penalty checklist for businesses with 5–25 staff," invited to wave 1 only. Narrow beats generic.
5. Paid (hold). Spend $10k on retargeting and search from week 3, but only if the wave 1 landing page converts at least as well as beta headline B. Hold the remaining ~$50k until the 60-day numbers justify it.
6. Press (low-key). A short release with a real customer quote and no "first" claim. It's cheap and supports the story without carrying the plan.

Measuring the next three months

Primary metric: payroll customers, meaning customers who have run at least one payroll, by segment, and the revenue from them ($6 per employee per month).

Targets (reset after the 30-day baseline): - Wave 1: 10% of the ~2,170 customers have run a payroll by day 90 (~220 customers, roughly $18k MRR at about 12 employees each). - Wave 2: 4% by day 90. - Wave 3: 10% of other-tool users migrated by end of January.

Decision rules: - If wave 1's first-payroll rate is under 2% after 30 days, pause paid spend and rewrite the messaging. - If it's over 5%, release the held budget to the segments that convert best.

Guardrails (any breach stops the rollout): - Zero filing errors or penalties traced to Ledgerly. - Support tickets per payroll run stay within agreed levels. - No rise in churn or refunds among existing customers.

Penalty outcomes won't show in three months. As a proxy, track on-time filing rates for adopters against matched non-adopters, and report it to the board in February.