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.

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.

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

Recommendation: Do not approve the current Q1 launch, six-person sales team, or $5M year-one ARR commitment. The US opportunity deserves investigation, but this plan mistakes a large business population for an addressable payroll market, ignores our strongest customer evidence, and commits to distribution before establishing product readiness.

What the plan gets wrong

1. The market calculation counts the wrong customers at the wrong price.

Of 33.2 million US small businesses, 27.1 million have no employees. They are not a credible default market for an employer payroll product. Some may have relevant needs, but we must establish those rather than count every sole proprietor.

Our UK results argue against prioritizing this population:

Customers with 10–249 staff represent roughly 23% of customers but 76% of annual revenue implied by this data. The relevant starting market is the approximately 1.1 million US employers in that size range, narrowed further by geography, payroll complexity, and product fit.

At our UK segment prices, that population represents $682 million–$2.64 billion in hypothetical annual revenue—not a validated TAM. We lack its size mix, US willingness to pay, and the share we could actually serve. “Even 1%” supplies no acquisition strategy.

2. The year-one target has no operating bridge.

At $150 annually, $5 million ARR requires about 33,333 active customers—more than twice our entire UK customer base after five years. At $620, it requires approximately 8,065; at $2,400, 2,083.

With six sellers, the $620 scenario requires each to acquire about 1,344 customers annually before allowing for ramp time or churn. There is no evidence here for the lead volume, conversion, onboarding capacity, pricing, or retention necessary.

The $2.5 million budget is an allocation, not an acquisition model. We need separate estimates for compliance engineering, operations, support, acquisition, and contingency.

3. “Why now” is competitive anxiety, not customer evidence.

A competitor’s fundraising neither proves demand for Halyard nor makes our product ready. Being first matters less than paying employees correctly and retaining employers.

What would sink it

Compliance failure is the existential risk. Payroll mistakes create customer harm, remediation costs, and reputational damage. The team estimates nine months merely to build rules for the first ten states. Unless work is already sufficiently advanced, that contradicts Q1 readiness. Rule implementation also does not establish filing, remittance, testing, exception handling, or operational readiness.

A state-limited launch must constrain employee locations and payroll complexity—not merely customer headquarters. Multi-state employers can breach that boundary immediately.

Retention could make growth economically hollow. Even our best UK segments lose 22–29% of customers by month twelve. We should investigate whether this reflects business closures, product failures, poor fit, or measurement issues. We cannot assume better US performance while adding regulatory and operational complexity.

Premature hiring could consume the budget before learning occurs. Six sellers cannot compensate for an unready product or an unidentified buyer. Low-price segments are particularly unlikely to support conventional sales-led acquisition.

What is less scary than it looks

We do not need nationwide coverage or millions of customers to establish a worthwhile business. A tightly bounded employer segment offers ample room for a meaningful foothold.

Nor must we automatically build the entire US payroll stack ourselves. A payroll infrastructure partner could reduce time and technical risk. It would not remove our obligations to customers, integration risk, or the need to understand liability and unit economics.

Finally, our UK data contains a genuine positive signal: larger employers pay substantially more and retain substantially better. That is a credible hypothesis to test—not proof that it transfers to the US.

What I propose instead

Approve a staged US validation program, with a first tranche capped at $300,000 and further spending conditional on evidence.

1. Validate the buyer over 8–12 weeks. Start with 10–49-person employers, where we have the strongest combination of customer volume, revenue, and retention. Interview buyers and test paid commitments at US-specific prices. In parallel, diagnose UK churn and compare build-versus-partner economics.

1. Choose one narrowly serviceable footprint. Select geography based on customer demand and compliance feasibility. Explicitly exclude unsupported employee locations and payroll cases. Do not announce a live-payroll date before readiness is independently reviewed.

1. Run a paid, founder-led pilot with 20–30 employers. Hire US payroll/compliance expertise before a sales team. Measure payroll accuracy and timeliness, onboarding effort, support costs, willingness to pay, and early retention. Early results will not substitute for twelve-month retention evidence.

1. Release expansion funding only against gates. Require no unresolved critical payroll defects, demonstrated operational controls, positive contribution economics, and a credible acquisition model targeting under twelve-month CAC payback. Hire sellers only after that motion is repeatable.

Replace $5 million ARR with a conditional first-year objective of 100–200 paying employers after readiness, roughly $62,000–$124,000 annualized at the UK 10–49 price benchmark. That is a learning milestone, not a forecast.

The board should fund the next decision, not an unsupported promise of scale.