Challenge an idea

MEMORANDUM

TO: CEO FROM: VP Product DATE: October 24, 2023 SUBJECT: Critique and Alternative Proposal for the US Launch Plan

---

You asked me to challenge the US expansion plan hard before you take it to the board next week. I’ve reviewed the deck excerpt against our UK unit economics and US market data.

If we walk into the boardroom with the current plan, a savvy board will pick it apart—and rightly so. Here is my unvarnished assessment of what the plan gets wrong, what will sink us, what is actually noise, and what we should propose instead.

---

1. What the plan gets wrong (The fatal assumptions)

• The "TAM Fallacy" on Sole Proprietors: The deck multiplies 33 million US small businesses by $150 to claim a $5B market. Government data reveals that 27.1 million of those businesses (82%) have zero employees. In the UK, our data tells a brutal story about sole traders: 41% of our customer base (6,100 accounts) churn within 12 months at an 18% retention rate. They are cheap to acquire, high-churn, high-support-load nightmares who don’t run payroll. Treating the entire 33 million pool as viable is a math error that misleads us on product-market fit.
• The Compliance Mirage: The deck ignores the engineering reality. US payroll is not a monolith; it is federal, state, and local tax compliance across 50 distinct jurisdictions. Our engineering team estimates 9 months of work just to launch the first 10 states. You cannot launch a payroll product in "the US" in Q1 with a generic software wrapper. Without state tax tables, automated filings, and local garnishments, the product is illegal to use.
• The Unit Economics Math: At $150/year, acquiring a customer through a dedicated US sales team of 6 with a $2.5M budget is mathematically impossible. A traditional outbound sales team cannot profitably sell a $150 self-serve product. CAC will dwarf LTV on day one.

---

2. What would sink us

• Regulatory suicide: If we launch prematurely in Q1 to "beat a competitor" without robust state-by-state tax calculation, our first cohort of US customers will face IRS and state tax penalties. In payroll, a software bug doesn't just mean a bad user experience; it means employees don’t get paid or taxes aren't remitted, resulting in immediate churn, devastating brand damage, and potential litigation.
• Reactive strategy: "A competitor raised in the US; we need to get there first" is a panic motivation, not a product strategy. If we rush a half-baked product into a massive market just to plant a flag, we will burn $2.5M in 12 months, fail to hit the $5M ARR target, and lose credibility with the board.

---

3. What’s less scary than it looks

• The total market size: We don't need 33 million businesses. Look at our UK data: our sweet spot is companies with 10–49 staff (20% of our base, but 71% retention, generating significantly higher revenue) and 50–249 staff (78% retention, $2,400+ ARR). In the US, there are 1.1 million businesses in the 10–249 employee bracket. That is a massive, highly qualified, high-retention target market. We don't need the sole traders; we should actively avoid them.
• Geographic concentration: We do not need to launch all 50 states on day one. If we pick 3 to 5 high-density, business-friendly states (e.g., Texas, Florida, Washington—states with no state income tax or straightforward payroll setups), we can drastically reduce engineering scope, bypass the 9-month/10-state bottleneck, and launch a compliant MVP much faster.

---

4. What I propose instead

We should go to the board with a revised, credible strategy that protects our capital and targets the segment we actually know how to monetize.

1. Shift the ICP (Ideal Customer Profile) away from Sole Traders: Ignore the 27.1 million non-employer businesses. Focus exclusively on US small businesses with 10 to 49 employees. They have the budget, they have payroll complexity, and based on our UK experience, they stick around.
2. Pivoting the Go-To-Market (GTM): Scrap the plan for a 6-person outbound sales team on a $150 product. At this price point, the US motion must be product-led growth (PLG) with digital acquisition, augmented by a lightweight, inside-sales motion only for accounts scaling toward 50+ employees.
3. De-risk the Engineering Roadmap: Reallocate the $2.5M budget. Instead of a clumsy nationwide Q1 rush, fund a targeted compliance build for just 3 states to launch a closed beta by Q2. Use the remaining budget for localized digital marketing and product-led onboarding flows.
4. Refrain the Board Narrative: Do not pitch "capturing 1% of a $5B market." Pitch a disciplined land-grab in a profitable sub-segment: “We are entering the US by targeting the 1.1 million businesses with 10–249 employees, starting with a compliant 3-state footprint, leveraging our proven retention playbook to capture high-value employers at a sustainable CAC.”

If we present this, the board will see operators who understand our unit economics, respect regulatory risk, and have a clear path to sustainable growth. Let’s calibrate the deck before Tuesday.

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.

MEMO

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

Bottom line: The market story is wrong, the timeline is not achievable, and the budget can't carry the target. The opportunity is real but much smaller and more specific than $5B. I'd take the board a staged plan with gates, not a Q1 launch.

---

What the plan gets wrong

1. The TAM is built on the wrong customers. 33M × $150 assumes every US small business buys our product at our UK sole-trader price. But 27.1M of those firms have no employees. Payroll is not their problem. Our own data shows sole traders retain at 18% at twelve months and bring in $150 a year. Our customers who retain are the ones with staff.

2. The right pool is about 1.1M firms, and the "1%" math shrinks accordingly. The government figure is 1.1M businesses with 10–249 employees. Our UK revenue is concentrated in the 10–49 and 50–249 segments: about 23% of customers but roughly 60%+ of revenue, with 71–78% retention. Taking a blended ~$620 ARPU, 1% of 1.1M firms is about 11,000 customers and roughly $7M ARR, not $50M. The deck's own logic, applied to the right segment, gives a much smaller prize.

3. The $5M year-one target is not credible. At $620 ARPU, $5M needs about 8,000 paying US customers in twelve months. It took us five years to reach 14,800 UK customers, with a product that is already built. At $150, it needs 33,000, which only works if we sell to the segment that churns most.

4. Q1 is not feasible. The US needs state-by-state payroll tax rules. Our team estimates nine months for the first ten states alone. Q1 launch means either launching with almost no state coverage or launching with a product we can't legally run for most prospects. A firm with employees in an unsupported state cannot onboard at all.

5. "Get there first" is the wrong reason. US payroll is a crowded market with entrenched incumbents, and a competitor's raise means they face the same state-tax build we do. Being early doesn't create a moat in payroll. Being correct on compliance does.

6. The budget doesn't match the plan. Six US quota-carrying reps at a fully loaded cost of roughly $150–180K each is about $1M a year before marketing, tax build, legal, compliance, or US support. That leaves very little of the $2.5M for everything else. (These are my estimates. Please check them against Finance's hiring costs.)

---

What would sink it

• Compliance liability. Wrong withholding or filing in a state is our error, with penalties landing on our customers. One public failure in an early state would damage referrals across the whole US business.
• Selling to the wrong segment. If sales pursues sole traders and 2–9 employee firms because the TAM looks big, we'll be acquiring customers at $150 ARPU who churn at 67–82% within a year. CAC payback will never work.
• Hiring ahead of proof. Six reps with quotas before we know which buyer, which price, and which state set will produce a pipeline we can't convert.
• Support load. Multi-state questions are hard, and US support can't be staffed from London on a launch timeline.
• Burn without a gate. If US spend starts before UK growth is secure, a US miss would hit our core business's cash position.

---

What's less scary than it looks

• The product already works where it matters. Our best UK segments retain at 71–78%. We don't need a new product thesis, just a US version of what works.
• The tax build is bounded. Nine months for ten states is a real cost, but it's finite. Ten states cover roughly half the US population, so coverage is a sequencing problem. We could also evaluate licensing state tax content from a vendor to cut the timeline.
• The competitor raise is validation. It shows investors believe in US SMB payroll demand. It also shows we'd be competing in a market where a credible challenger still needs years to build coverage.
• We don't need a Q1 launch to have a US business. A focused pilot can prove demand within two quarters at a fraction of the cost.

---

What I'd propose instead

I'd ask the board to approve a staged program with explicit gates.

Redefine the market in the deck. The target customer is a US business with 10–249 employees. That's about 1.1M firms and a credible multi-million-dollar opportunity, and we should say so.

Stage 1: Validate (months 0–6, ~$300K). Sign 40–60 design-partner firms with 10–249 employees across two states, one large state and one with simpler rules. Test activation, willingness to pay at $600+ ARPU, and 90-day engagement. Also test a partner channel: accountants and bookkeepers serve our best-fit firms and may be cheaper to reach than direct sales.

Stage 2: Build (months 6–15, ~$800K). Build or license state coverage for the top ten states. Hire one or two sales and customer success people, with the founder leading enterprise-style deals. Gate: pilot cohort retention tracking to 70%+ and CAC payback under 18 months.

Stage 3: Scale (only after gates). Expand sales headcount and marketing against measured unit economics.

Revised target: $1M US ARR by month 24, which is roughly 1,600 customers at $620 ARPU. That is ambitious but defensible, and it's the number the board should hold us to.

The ask: Approve Stages 1 and 2 (about $1.1M) now, with Stage 3 contingent on gate review. Do not approve a $2.5M Q1 launch with a $5M year-one target.

---

I know this is a harder message than the deck. But a board that approves the current plan will be disappointed in twelve months. A board that approves a gated path will get real evidence before committing the big money. I'd rather take the second case to them.