Challenge an idea

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.

MEMO

TO: CEO FROM: VP Product DATE: October 24, 2023 SUBJECT: Critical Assessment of Proposed US Expansion Plan

*

You asked me to challenge our US launch plan before next week’s board meeting. While expanding to the US is the right ambition eventually, taking this deck to the board in its current form exposes us to serious credibility and execution risks.

Below is an unvarnished breakdown of where the plan breaks down, the existential risks, what shouldn’t scare us, and an alternative path to present to the board.

---

1. What the Plan Gets Wrong

#### The TAM Calculation is a Fiction The deck calculates our TAM as 33M businesses $\times$ $150 = $5B. * 27.1M (82%) of those businesses are non-employers (sole proprietors). They do not run payroll. Selling payroll to someone with no employees is a non-starter. * Our true addressable market of employer SMBs is 6.1M businesses, not 33M. * The “even 1% is $50M” trope will instantly damage our credibility with board members who understand US market demographics.

#### The Sales Math is Mathematically Impossible Targeting $5M ARR in Year 1 at $150/year requires acquiring 33,333 net new customers. * With a team of 6 sales reps, that equates to 5,555 closed deals per rep per year, or ~23 closed deals per rep every single working day. * Even if we targeted our UK mid-tier ($620/year), each rep would need to close 5.5 deals per business day in a brand-new market with zero brand equity. Inside sales reps for SMB SaaS typically close 20–40 deals per month.

#### It Replicates Our Worst UK Cohort In the UK, micro-businesses ($\le$9 staff) represent 77% of our customers, but they suffer from catastrophic churn: * Sole traders: 18% 12-month retention (82% annual churn). * 2–9 staff: 33% 12-month retention (67% annual churn). Building a US go-to-market strategy around high-churn micro-businesses at $150/year guarantees we burn cash filling a leaky bucket.

---

2. What Would Sink Us

#### The 9-Month Compliance Wall vs. Q1 Launch US payroll is not a single product; it is a federation of 50 distinct state tax codes, local jurisdictions, reciprocity rules, and quarterly filing obligations. * Our engineering estimate is 9 months just to support the first 10 states. * Announcing a Q1 launch leaves product and engineering two options: launch a crippled product covering 2–3 states, or miss the launch date entirely. Selling payroll that cannot support a customer hiring an out-of-state remote worker leads immediately to compliance liability, tax penalties, and reputational ruin.

#### Dilution of UK Momentum & Budget Burn We have $3.9M ARR in the UK. A $2.5M capital outlay represents over 60% of our annual revenue. * Splitting engineering to build state tax engines will freeze UK product development for nearly a year. * $2.5M will vanish rapidly once factoring in 6 US base salaries, sales leadership, US legal/tax compliance, localized infrastructure, and paid customer acquisition. We risk running out of cash with a half-built US engine and a stalled UK business.

---

3. What’s Less Scary Than It Looks

#### The Competitor’s US Funding Round A competitor raising capital in the US does not mean they have won. * The US market is dominated by entrenched incumbents (Gusto, Rippling, ADP, Paychex). A UK competitor raising capital will face the exact same compliance, distribution, and CAC headwinds we would. * Raising money to chase micro-SMBs at low price points usually accelerates a competitor's burn, not their moat. We should let them spend heavily to educate the market while we execute deliberately.

#### Winning Larger SMBs (10–249 Staff) Our UK data shows that moving upmarket works: * 10–49 staff: 71% retention, $620 ARR (4.1x ARPU). * 50–249 staff: 78% retention, $2,400 ARR (16x ARPU). * Combined, these two segments represent only 23% of our UK customer count, but they generate over 60% of our revenue and virtually all of our net lifetime value. * In the US, there are 1.1 million businesses with 10–249 employees. We don’t need 33,000 customers; we need a few thousand high-retention accounts at a realistic US market price ($40–$100/month base + $6–$12/employee/month).

---

4. What We Should Propose Instead

Tell the board we are entering the US with a disciplined, phased strategy focused on high-retention economics rather than low-yield volume.

``` PHASE 1 (Months 1–6): UK Consolidation & US Technical Build ├── Target: Accelerate UK upmarket shift (10-249 staff) to self-fund expansion. ├── Product: Build US tax engines for Top 5 employer states (CA, TX, NY, FL, IL). └── GTM: Do NOT hire US reps yet. Evaluate payroll API partners (e.g., Check, Salsa) to eliminate the 9-month internal build entirely.

PHASE 2 (Months 7–12): Controlled Pilot (The 10–99 Staff Segment) ├── Focus: 10–99 employee segment; price at US parity ($1,500–$3,000/year). ├── Team: 2 senior US AE/consultative sellers + 1 US product compliance lead. └── Target: 250 customers, $500k ARR, >80% 12-month retention intent. ```

#### The Revised Board Pitch 1. Realistic TAM: Present the addressable market as 1.1M US businesses with 10–249 employees, representing a $2.5B–$4B TAM at standard US SaaS pricing ($2,000–$3,500 ARR per account). 2. Rationalized Y1 Goal: Target $500k–$750k ARR in Year 1 from a focused pilot in 3–5 key states, proving product-market fit and retention before scaling headcount. 3. Alternative Delivery Mechanism: Propose exploring white-label/embedded payroll infrastructure partners (e.g., Check Technologies) to compress our 9-month build into 60 days, offloading tax filing liabilities. 4. Capital Efficiency: Cap initial US allocation at $1.0M–$1.2M, tying the remaining budget to hitting retention milestones in the pilot cohort.

Let’s position Halyard to the board as a disciplined leadership team that understands unit economics and enterprise value, not one panicking over a competitor's press release.

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.