Challenge an idea

MEMO

To: CEO From: VP Product Re: US launch plan: challenge before the board

You asked me to push hard, so I have. I think we should go to the US, but not with this plan. As written, the board will find the holes in it quickly, and the market will find the rest.

---

1. What the plan gets wrong

The market size counts businesses that won't buy payroll. Of the 33.2M US small businesses, 27.1M have no employees. A business with no staff has little use for payroll. Our own UK data points the same way: sole traders are 41% of our customers, but only 18% are still with us after 12 months.

The market that fits our product is the 1.1M US businesses with 10–249 employees. In the UK that segment:

• makes up 23% of our customers but about 63% of our revenue;
• keeps 71–78% of customers at 12 months, against 18–33% for smaller firms;
• pays a blended average of about $873 a year, not $150.

That puts the core US opportunity at about 1.1M × $873 ≈ $1B. The 5M employers with 1–9 staff add up to about $750M more at our current price, but UK retention suggests most of that revenue would leave within a year. The real figure is roughly $1–1.7B, not $5B. That is still huge compared with our $3.9M ARR. We simply don't need the inflated number, and leading with it costs us credibility.

The timeline is impossible. The deck says we launch in Q1. Engineering estimates 9 months to build tax rules for the first 10 states. We cannot sell US payroll before it calculates US payroll taxes. Realistically, the earliest launch is Q4, and only in 10 states.

The $5M year-one target fails on its own arithmetic. It took us five years to reach $3.9M in the UK.

At the mid-market price, each rep would need about 950 deals. These are considered purchases, and that volume isn't plausible. It is even less plausible when the product is only live for the last quarter of the year.

The budget is spent in the wrong order. If we hire six salespeople in Q1, we pay them for about nine months while they have nothing to sell. Much of the $2.5M would go on salaries before the product exists.

---

2. What would sink us

1. Payroll tax errors. Getting someone's pay or taxes wrong is not an ordinary bug. It creates penalties for our customers, refunds for us, and reputational damage in a market where nobody knows us yet. Rushing the tax engine to hit a sales date is the single biggest risk in this plan.
2. Selling to the wrong customers. If US sales chases volume at $150 among micro-businesses, UK data says we'd lose 67–82% of them within a year. We would be paying to acquire customers who leave, and the board would see revenue growth that isn't real.
3. Ten states may not cover our best customers. Companies with 10–249 staff are more likely to have employees in several states. If a prospect has people in a state we don't support, we lose the deal. We need data on how many states typical target customers operate in before we finalise the list.
4. Missing a target we set ourselves. If we commit to $5M and deliver a fraction of it, we lose the board's trust for the next fundraise. That is worse than setting a modest target and beating it.
5. Neglecting the UK. The UK business funds this expansion. Moving our best people to the US without a plan to protect UK growth puts our cash engine at risk.

---

3. What's less scary than it looks

• The competitor's raise. The US payroll market is not empty. Well-funded incumbents already exist, so "getting there first" isn't possible for anyone. Another entrant raising money doesn't change our costs, our product gaps or our timing. It is a poor reason to launch before we're ready.
• The 9-month build. It's real work, but it's bounded. We don't need 50 states on day one. We need the 10 states with the most 10–249-employee businesses. We should also assess licensing a US payroll tax engine instead of building one. That could shorten the timeline and reduce compliance risk, and we should know within a month whether it's viable.
• The smaller market size. A $1B core market means we need about 0.4% of it to triple the company. That is a stronger story than "1% of $5B," because it rests on segment data and retention we can prove.
• Our readiness. 71–78% retention in the UK mid-market is real evidence that the product works for these companies. We're not starting from zero. We're moving a proven product into a new market.

---

4. What I'd propose instead

Position: the US launch targets employers with 10–249 staff, priced like our UK mid-market (around $600–2,400 a year, validated with US prospects), not £120.

Phases, with spending released at each milestone:

Year-one targets, replacing $5M ARR: - payroll runs with no tax-filing errors; - 20–30 design partners, then a few hundred paying customers by year end (roughly $0.2–0.4M ARR at mid-market prices); - at least 70% of US customers staying through early renewal checkpoints, matching the UK mid-market; - evidence on deal size and sales cycle, so a year-two ARR target is grounded in data.

In parallel: keep investing in UK customers with 10–249 staff. They are our highest-value, highest-retention segment, and they fund all of this.

Before the board meeting, two housekeeping items: - Our segment table adds up to about $4.7M in revenue, but we report $3.9M ARR. We should reconcile this, likely churn timing or discounting, before the board asks. - We should remove the "1% of $5B" line entirely.

---

Bottom line: the US is the right ambition, but this plan has the wrong market size, the wrong customer, the wrong timeline and the wrong sequence. If we fix those four things, we go to the board with a plan they can approve and we can deliver.

To: CEO and Board From: VP Product Subject: US expansion: approve validation, not the proposed launch

Recommendation: Do not approve the plan as written. The US may be attractive, but the deck mistakes business counts for demand, imports our weakest UK economics, and commits to distribution before we can reliably deliver the product. Approve a staged validation programme instead, with compliance and commercial gates before releasing the full $2.5M.

What the plan gets wrong

1. The addressable market is not 33 million payroll buyers. Of 33.2 million US small businesses, 27.1 million have no employees. Some owner-only businesses may need payroll, but they are not equivalent to employer businesses. The relevant starting population is approximately 6.1 million employers—and probably the 1.1 million with 10–249 employees, given our UK results.

“Even 1%” is not a strategy. It assumes a reachable segment, competitive differentiation, distribution and retention that we have not demonstrated.

2. Our own data contradicts the proposed price and customer strategy.

Businesses with 10–249 staff represent approximately 23% of customers but 63% of the annual revenue implied by this table. Their weighted retention is approximately 72%, versus 25% for customers below ten staff. Our strongest evidence favours larger employers, not maximum account volume at $150.

Using our UK customer mix within 10–249 staff gives approximately $873 annual revenue per customer. Applied to 1.1 million US businesses, that suggests a roughly $960M segment revenue pool—not a forecast, and not all serviceable by a ten-state product. US willingness to pay remains untested.

There is also a board-data problem: the table implies $4.66M annual revenue, versus the stated $3.9M ARR. Reconcile definitions, dates and cohorts before presenting either figure as the economic baseline.

3. The sales plan and revenue target do not fit. At $150 annually, $5M ARR requires approximately 33,333 active customers: 463 per salesperson per month across six reps over a full year, before churn. Even allocating the entire $2.5M budget to acquisition would allow only $75 per active customer, leaving nothing for engineering, compliance or support.

At the illustrative $873 blend, we still need approximately 5,730 active customers—80 per rep per month. These are workload checks, not sales forecasts, but neither resembles a credible unproven, sales-led launch. A later launch compresses the selling window further.

4. Competitive fundraising is not customer evidence. A competitor’s financing may raise acquisition costs or accelerate competition. It does not establish that our product is ready or that customers will switch. “Get there first” is especially weak when the competitor is already there.

What would sink it

Payroll reliability and coverage. The team estimates nine months for the first ten states. A Q1 launch is unsupported unless substantial work is already complete or we use a proven partner. Ten states also do not automatically mean ten self-contained markets: employee locations, local taxes and multi-state operations affect eligibility. Incorrect wages, filings or remittances can destroy trust faster than sales can rebuild it.

Scaling the wrong economics. At our smallest-customer retention levels, acquisition fills a leaking bucket. Higher retention among larger employers is promising, but customer retention is not revenue retention or gross margin. We lack US acquisition cost, onboarding effort, support burden and contribution-margin evidence.

Starving the UK business. The proposed budget is approximately 64% of current ARR—not a cash-runway calculation, but a material commitment. We need an explicit runway and UK-roadmap impact assessment, including engineering diversion and downside scenarios.

What is less scary than it looks

We do not need nationwide coverage or a large share of the US to build something valuable. A tightly qualified segment can support a meaningful business.

Nor must we necessarily build every payroll component ourselves. A payroll infrastructure partner could shorten time to market, although coverage, margins, accountability and vendor dependence require diligence.

Finally, weak microbusiness retention does not prove Halyard cannot travel. The larger-employer cohorts provide a credible starting hypothesis. They do not yet prove US product-market fit.

What I would propose instead

1. Release up to $400,000 for a 90-day validation phase; hold the remainder. Reconcile the financial baseline, analyse retention by cohort and acquisition channel, and compare partner versus internal-build economics and timelines.

2. Start with 10–49 employees. Recruit 10–20 design partners with simple, geographically supported payroll needs. Validate switching triggers, differentiation, pricing and onboarding. Keep 50–249 as a subsequent hypothesis: better UK retention may come with substantially greater implementation complexity.

3. Gate live payroll on readiness, not the calendar. Require documented coverage, independent compliance review, successful parallel payroll testing, and clear incident ownership. No unsupported employee locations.

4. Run a 30–50-customer paid pilot before hiring six sellers. Use founder-led sales and limited implementation capacity. Measure acquisition cost, onboarding time, support cost, contribution margin and retention. Seek evidence supporting acquisition payback within 12–18 months; early retention is provisional until cohorts mature.

5. Return for scale funding only after those gates. Replace the $5M year-one promise with a bottom-up forecast based on verified price, conversion, launch timing, capacity and churn. The board should fund the next proven step—not an unsupported percentage of America.