Challenge an idea

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.

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: US launch plan, challenge review To: CEO | From: VP Product

Bottom line: The direction is defensible, but the plan isn't ready for the board. The market is about a fifth the size the deck claims, the Q1 launch date conflicts with our own engineering estimate, and the $5M year-one target is unreachable. I'd take a staged version instead.

---

What the plan gets wrong

1. The $5B market is wrong by roughly 5x. The deck multiplies all 33.2M US small businesses by $150. But 27.1M of them have no employees, so they have no payroll to run. Our own UK data shows how little this segment is worth to us:

• Sole traders are 41% of UK customers but only about 20% of revenue, and just 18% are still with us at 12 months.
• Firms with 10+ staff are 23% of customers but about 63% of revenue, with 71–78% retention.

Our proven segment in the US is the 1.1M firms with 10–249 employees. At our UK blended revenue for that group (about $870 per customer), that's roughly $1B. "Even 1%" is about $10M, not $50M. I'd exclude the ~5M micro-employers. In the UK, 2–9 staff firms pay $150 and only 33% stay a year.

2. The timeline contradicts itself. The team estimates 9 months of work for the first 10 states. A Q1 launch means selling a product that doesn't exist, or one that only works in a few states. Ten states is also only about half the US population, by my rough estimate, so a national sales team would be pitching to prospects we can't serve.

3. $5M ARR in year one is out of reach. It exceeds the ARR we built in five years in the UK. At ~$870 per customer it needs about 5,700 customers, roughly 950 per rep from a standing start. With a 9-month build, year-one revenue would be close to zero.

4. "A competitor raised" isn't a reason to launch now. We can't win a spending race with $2.5M against a funded rival. Payroll is also a sticky, slow-switching category, so launching early earns us little. Launching with wrong tax calculations would cost us far more.

What would sink it

• Compliance failures. A wrong withholding or a missed filing means customers pay penalties and blame us. In the UK, rules are built in and we know them. In the US we'd face federal, state and local rules, each with its own filings. One bad quarter in the first cohort could end our reputation with the segment we need.
• Targeting the wrong customer. If the sales team chases volume, it will sign small firms that churn at UK micro-segment rates. Acquisition cost would never pay back.
• Draining the UK business. Nine months of engineering on tax rules comes out of the roadmap for the business that funds everything. UK retention in the smallest segments is already weak, and we'd be neglecting it.
• Burning the budget before learning anything. Six hires plus a 9-month build could consume most of $2.5M, about 64% of current ARR, before we know whether US customers retain like UK ones. I need to confirm whether the $2.5M includes the engineering cost. If it doesn't, the real ask is larger.
• Missing the target. A $5M goal that slips will damage board confidence in everything else we present.

What's less scary than it looks

• The smaller market is still big. About $1B is over 200x our current ARR. We don't need $5B to justify the US.
• The competitor raise. It validates demand, but funding doesn't fix the state-by-state build, which slows them as well. Nothing here is lost by launching in 12–18 months instead of 3.
• The 9-month estimate. It's a well-scoped build with a known end date, and a tax-calculation partner or API might shorten it. I'd evaluate build vs. buy before committing.
• UK retention in micro-segments. It looks alarming, but it's a UK issue we'd avoid importing by targeting 10–249 staff firms, where our retention is strongest.

What I'd propose instead

Phase 0 (now to ~Q3, ~$0.5–0.7M): - Decide build vs. buy for the tax engine. - Pick 3–4 launch states by density of 10–249 staff firms. - Recruit 15–20 design-partner customers. - Hire a US head of sales/GTM and one compliance specialist, not six reps.

Phase 1 (launch in 3–5 states once compliance is proven, ~$1M): - Sell only to 10–249 staff firms with 2 reps and dedicated onboarding. - Set the target at about 300 customers and ~$0.25–0.3M ARR twelve months after launch. That's my estimate, based on UK segment pricing.

Phase 2 (release the remaining ~$1M, expand states and team) only if we hit gates: - 12-month retention of at least 70% in the first cohort. - Zero material filing errors. - Acquisition cost paying back within an agreed window.

This puts about $0.5–0.7M at risk before we learn anything, rather than $2.5M, and it gives the board a credible plan with checkpoints.

Before the board meeting

1. Reconcile ARR. Our segment table implies about $4.66M (customers × average revenue), but the deck and company profile say $3.9M. A board member will do this multiplication. We need to know whether the gap is discounting, churn timing, or stale data.
2. Confirm what the $2.5M covers, particularly engineering and compliance.
3. Restate the market as ~$1B core, with the logic shown.
4. Check price transfer. UK per-segment pricing may not hold in the US, so the design-partner phase should test willingness to pay.

I'm happy to walk through the numbers before you finalize the deck.