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.

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.

Ledgerly Payroll go-to-market plan | 3 November–31 January

1. Start with customers who have the clearest problem

First priority: existing customers with 5–25 employees who currently run payroll themselves or rely on an accountant. That’s 2,170 customers: 690 spreadsheet users and 1,480 whose accountant runs payroll. In these groups, 19% and 23%, respectively, said they received a payroll penalty notice last year. Treat that as a signal of pain—not proof that Ledgerly would prevent penalties.

Lead with accountant-run customers who want more visibility and control, while making clear Ledgerly isn’t accusing their accountant of poor work. Follow with spreadsheet users in the same size band, for whom a simpler alternative to manual payroll may appeal.

Defer broader prospecting. Among customers with 1–4 employees, reported penalty notices are lower (4–6%); several calls also suggest some are content with free spreadsheets. Customers already using another payroll tool reported fewer notices (7% for 5–25 employees), and one call highlighted switching friction. Test those groups later, after validating onboarding and migration. Don’t prioritize 26–50-employee customers until we know the product and support experience fit their needs.

2. Say what we can support—not what we can’t promise

The beta headline test is a useful directional signal:

• “Never get a payroll penalty again”: 268/4,160 visitors started setup (6.4%); 117 ran first payroll (2.8%).
• “Run payroll in minutes…”: 92/4,210 started (2.2%); 38 ran first payroll (0.9%).

The penalty-focused version performed better, but don’t use “Never get a payroll penalty again” unless Ledgerly can substantiate that guarantee. Instead test responsible variants such as:

• “More confidence in payroll, alongside your books.”
• “Take control of payroll and reduce the risk of costly mistakes.”

Be explicit that payroll is $6 per employee per month. Emphasize control, confidence and working in the same accounting product—not guaranteed outcomes or unverified features. Tailor the message: “Keep a closer eye on payroll” for accountant-run customers; “Move beyond the spreadsheet” for owner-run customers.

3. Use customer channels before buying reach

• Before launch: Segment the 2,170 priority customers and invite a small cohort to try setup. Interview users who start but don’t finish; check readiness, support capacity and any limitations before broad promotion.
• Launch, 3 November: Send segmented email to the priority cohort and show a targeted in-app message when those customers use Ledgerly. Link directly to a clear product and pricing page, not a generic announcement. Offer a live, practical webinar on setup and common payroll concerns, with time for questions.
• During November–January: Follow up based on behavior: a setup reminder for visitors who don’t start, and personal onboarding or support for customers who start but don’t run payroll. Invite accountant-run customers to involve their accountant where appropriate. Expand in-app promotion to other segments only after reviewing early results.
• Earned media: A factual product announcement is fine, but don’t make press mentions the launch objective. Skip the $60,000 broad paid campaign to new prospects until existing-customer activation and retention are proven.

4. Measure adoption and outcomes for three months

Track weekly by customer segment and by funnel step: eligible → reached → product-page visit → setup started → setup completed → first payroll run → repeat payroll run. Report both counts and conversion rates; compare messages with a randomized test where possible.

Use the beta as a benchmark, not a forecast. A reasonable initial goal is to beat its stronger variant’s 6.4% visit-to-setup-start and 2.8% visit-to-first-payroll rates in the priority cohort. Also set a three-month target for repeat payroll runs among first-time users, and review setup abandonment to find where customers get stuck.

Pair adoption metrics with guardrails: payroll-related support contacts, failed or corrected runs, cancellations/refunds, and customer feedback about confidence and accuracy. Review weekly with Product, Support and Marketing. If activation is weak, fix onboarding or clarify the offer before adding spend. If customers run payroll but don’t repeat, investigate reliability, fit and switching friction before expanding the campaign.