Write a GTM plan

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.

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: existing-customer launch plan

3 November–2 February

1. Start with customers who fear mistakes—not everyone who dislikes admin

Prioritise the 2,170 existing customers with 5–25 employees whose payroll is run in spreadsheets or by an accountant. They represent 27% of our customer base:

• 690 spreadsheet users: 19% reported a payroll penalty notice last year. Start here: they control the buying decision and have no incumbent software to replace.
• 1,480 accountant-run customers: 23% reported a penalty notice. Approach alongside the first group, but qualify who controls payroll and whether the accountant should participate.

These penalty rates are much higher than the 4–7% reported by the other segments. Customer interviews reinforce the problem: owners want confidence that payroll is right, not merely faster.

Deprioritise the 4,160 customers with 1–4 employees: several see spreadsheets as sufficient, and willingness to pay looks weaker. Also defer broad outreach to the 1,670 customers using another payroll tool: their reported penalty rates are lower, and switching creates friction.

Within the priority segments, invite customers with known concerns or upcoming payroll runs first. Don’t assume a segment-level penalty rate means any particular customer received a notice.

2. Sell confidence and control, without promising immunity

Replace “the first Financial Operating System” and the generic speed headline with:

> Feel more confident about payroll, right alongside your books. > Ledgerly Payroll costs $6 per employee per month. See whether it fits your business and get help setting up your first payroll.

Use separate supporting messages:

• Spreadsheet users: “Move beyond manual payroll spreadsheets. See how Ledgerly Payroll works before your next pay run.”
• Accountant-run customers: “Get a clearer view of payroll—and decide how you and your accountant will manage it.”

The beta provides strong directional evidence for this positioning. The penalty headline generated first-payroll completions equal to 2.8% of page visits versus 0.9% for the speed headline—roughly three times higher. Setup starts also increased, while setup-to-first-payroll conversion remained similar, around 42–44%. The message attracts interest; onboarding still needs work.

However, do not ship “Never get a payroll penalty again.” It is an absolute guarantee the evidence cannot support. Test truthful reassurance against the speed message, with legal review.

Before launch, confirm exactly which calculations, checks, deadlines and filing responsibilities Ledgerly supports. Demonstrate only verified capabilities and clearly explain customer responsibilities. For price context, a 10-person business pays $60/month; don’t claim universal savings versus accountants.

3. Use owned channels and assisted onboarding before acquisition spend

Replace the $60,000 November prospecting campaign with a focused existing-customer rollout. Hold that spend until activation, retention and support economics justify expansion.

Before 3 November - Prepare segment-specific emails, in-app pages, eligibility guidance and a clear setup checklist. - Equip support with payroll-specific escalation procedures and capacity for first-run assistance. - Instrument the journey from invitation through paid, successful payroll. - Validate readiness. If a critical workflow is unsafe, narrow launch eligibility rather than market around it.

November: activate the first cohort - Send targeted email and in-app invitations to the priority customers, paced to support capacity—not one banner to all 8,000. - Offer a practical demonstration and bookable setup sessions. Schedule follow-ups around each customer’s next payroll date. - Use the launch-week webinar to show setup, responsibilities and a complete payroll workflow, not deliver a corporate announcement. - Where customers agree, involve their accountants. Position them as collaborators, not the cause of every payroll problem.

December: remove friction - Contact customers who started but stalled; diagnose migration, employee-data, confidence and accountant-approval barriers. - Turn recurring questions into onboarding improvements and help content. - Publish customer proof only with permission and substantiated outcomes.

January–2 February: expand selectively - Broaden outreach once repeat usage and operational quality are sound. - Test customers considering a switch from another tool, with explicit migration guidance. - Consider a small paid acquisition experiment only after establishing acceptable acquisition cost and payback.

4. Measure paid adoption, repeat use and trust—not launch noise

Set these as initial planning targets, not forecasts; recalibrate after November’s first cohort:

• By 2 February: 217 priority customers—10% of the target segment—have completed a successful payroll and become paying add-on customers.
• Repeat use: at least 80% of activated customers complete their next scheduled payroll; separately track third-run retention where enough time has elapsed.
• Commercial performance: report actual payroll MRR, paid employees, cancellations and contribution after onboarding/support costs. Customer count alone does not establish revenue.

Review weekly by segment and channel: invitations delivered, qualified visits, setup starts, setup completion, successful first payroll, paid conversion, time to activation and support effort. Use unique-customer denominators, not just page visits.

Run a controlled headline test and, where feasible, stagger outreach with a holdout to measure incremental adoption.

Track failed runs, product-attributable calculation or filing incidents, and customer confidence after first and repeat runs. Investigate every serious incident; pause the affected rollout if reliability is compromised.

The launch succeeds when customers repeatedly pay staff correctly and keep paying for Ledgerly—not when they read a press release.