Write a GTM plan

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

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.

Critique of the Marketing Draft

The marketing team’s launch plan has three fatal flaws: 1. Wrong audience for the budget: Spending $60,000 on paid acquisition to cold prospects for a new add-on is wasteful. We have 8,000 existing, engaged accounting customers. Our CAC here should be close to zero. 2. Ignoring empirical data on messaging: The draft uses "Run payroll in minutes" and PR buzzwords ("Financial Operating System"). Our beta test proved this fails: "Never get a payroll penalty again" drove 3.1x more completed payrolls (2.81% conversion vs. 0.90%). Customers don't care about speed—they fear tax penalties and accountant errors. 3. Vanity metrics: Press mentions and launch-week signups tell us nothing about adoption, product usage, or recurring revenue.

Here is the revised go-to-market plan.

---

1. Target Audience: Who We Go After First

We must prioritize based on revenue potential ($6/employee/month) and pain intensity (penalty notices):

``` Target Tier Segment (Size & Method) Base Penalty % Priority Tier 1 (Core) 5–25 emp: Accountant runs it 1,480 23% Immediate (Day 1) 5–25 emp: Spreadsheet 690 19% Immediate (Day 1) Tier 2 (Secondary)5–25 emp: Another payroll tool 1,210 7% Prep for Jan 1 Switch 1–4 emp: Accountant runs it 1,020 6% Nurture Deprioritize 1–4 emp: Spreadsheet (3,140) 3,140 4% Self-serve banner only 26–50 emp: Another tool (460) 460 5% Later phase ```

• Primary Beachhead (Tier 1: 2,170 customers): Businesses with 5–25 employees doing payroll via spreadsheets or accountants. They suffer a massive 19–23% penalty rate, generate $30–$150/month each in add-on revenue, and are actively frustrated by accountant fees and errors (e.g., customer paying $180/month for late filings).
• Secondary Opportunity (Tier 2): Those using other payroll tools (1,210 customers) are hesitant to switch mid-year. We target them in late November/December for a clean transition on January 1 (start of the new tax year).
• Deprioritized: 1–4 employee spreadsheet users (3,140 customers) are complacent ("spreadsheet is fine/free") with low penalty exposure. We will expose them to in-app banners, but spend zero outbound effort on them.

---

2. Positioning & Messaging: What We Say

• The Core Hook: "Never get a payroll penalty again. Guaranteed accuracy, right inside Ledgerly."
• The Value Proposition: Ledgerly automates tax calculations, filings, and direct deposits directly from your books—eliminating accountant errors, late tax notices, and Sunday-night spreadsheet anxiety.
• Segment Angles:
• For Accountant-run payroll: "Fire the $180/month bill and the filing mistakes. Automate accurate payroll in Ledgerly for a fraction of the cost."
• For Spreadsheet users: "One tax office notice costs more than three years of Ledgerly Payroll. Get automated tax filings and sleep easy."
• For Competitor switchers: "Make January 1 your fresh start: switch to unified bookkeeping + payroll in 15 minutes."

---

3. Channel Strategy & Execution

Reallocate the $60,000 paid budget into onboarding support and switching incentives.

#### A. In-App Contextual Triggers (November 3) * Deploy the winning headline ("Never get a payroll penalty again") across dashboard real estate. * Trigger contextual prompts when users categorize payroll-related expenses (e.g., bank feed lines showing accountant payroll fees or tax payments): "Paying an accountant for payroll? Automate it error-free in Ledgerly for $6/employee."

#### B. Direct Outbound & Email Drips (Segmented) * Tier 1 (Accountant & Spreadsheet, 5–25 emp): Send a 3-part sequence focused on penalty protection, automatic tax filing, and reconciliation. Include a penalty-risk calculator. * Concierge Migration: Offer dedicated, white-glove onboarding for 5–25 employee accounts to import employee tax files and YTD data.

#### C. Education, Not a Feature Webinar * Replace the generic product demo with an expert session: "Avoiding Payroll Penalties in Q4 and Prepping for the 2025 Tax Year." Feature a customer testimonial sharing the pain of a tax notice.

#### D. The "January 1 Fresh Start" Campaign (Mid-November – December) * Target competitor users (1,210 customers) with an early-bird onboarding offer: "Set up your company before December 15; your first payroll run on January 1 is free."

---

4. 3-Month Success Metrics

We will track activation and usage, not press mentions.

#### Leading Indicators (Operational) * Setup-to-Run Conversion: >45% of users who start setup complete their first payroll run within 30 days (up from beta's 43.6%). * Tier 1 Activation: >12% of the 5–25 employee accountant/spreadsheet cohort (260 accounts) activate by Day 90.

#### 3-Month Milestones

• Month 1 (November): Initial Adoption
• 150 businesses run their first payroll.
• Concierge migration processes 50+ businesses with >5 employees.
• Target MRR added: ~$9,000.

• Month 2 (December): Pipeline & Retention
• 100% of Month 1 users run their second payroll cycle (0% churn).
• 200 additional competitor-switch businesses pre-configure payroll to go live on January 1.
• Target cumulative MRR: ~$18,000.

• Month 3 (January): The Tax Year Switch Surge
• Over 450 total active customers running payroll by Jan 31.
• Blended average of 8 employees/account = 3,600 employees on platform.
• Run-Rate Target: $21,600 MRR (~$260,000 ARR) achieved within 90 days of launch.
• Zero filing penalties incurred by customers using Ledgerly Payroll.