Challenge an idea

To: Priya Raman (CPO), CEO, CFO, Head of Sales From: Staff Product Manager, Fieldline Date: September 25, 2026 Subject: Pre-read: Strategic Challenge to the Fieldline Pay Plan ($24M Revenue Target)

---

Executive Summary

Committing three squads for three quarters to Fieldline Pay to capture $24M in new revenue within two years is a high-risk bet that relies on a structural distortion in our financial model.

The plan’s core vulnerability is not execution; it is a misallocation of our customer base's economic reality. By using the mean invoice value ($2.1M) rather than the median ($640k), the model assumes our average customer mirrors our largest commercial accounts¹, while simultaneously ignoring entrenched enterprise contracts and commercial payment norms.

Executing this plan requires pausing the scheduling rewrite, which risks $1.9M in annual churn from our largest, most valuable accounts. Below is the evidence-based challenge, a revised revenue range, an inexpensive six-week test, and a recommended alternative path.

---

1. The Dependent Assumption and Why the Evidence Fails It

> The Plan's Single Dependent Assumption: That we can achieve a $23.7M–$24M revenue run-rate by month 24 by applying a blended 0.7% net take rate across a homogenous $2.1M annual invoice volume per adopted customer.

The evidence flatly refutes this assumption in three ways:

• The Mean vs. Median Distortion: The CEO's model relies on a mean invoice value of $2.1M. However, the median customer invoices just $640k. Our distribution is heavily skewed: the top 5% of customers (115 accounts) drive 48% ($2.32B) of our total invoiced value.
• Enterprise Lock-in: Of those 115 largest customers, 71 are locked into multi-year contracts with existing payment processors running through 2028. As the Head of Sales noted, none will migrate early.
• The Commercial Wall: Commercial jobs comprise 58% of our invoiced value ($2.80B). The average commercial invoice is $3,800 and is paid on net-45/net-60 terms (averaging 52 days). Property managers and facility contractors will not pay a 2.9% card surcharge on a $3,800 invoice. They pay via ACH ($2.00 flat fee, netting us $1.60) or check ($0 revenue), exactly as they always have.

Applying a 0.7% card take-rate model to commercial volume is fundamentally flawed because commercial clients do not use cards (card share is only 5% for commercial, vs. 38% for residential).

---

2. Re-Estimated Revenue Range (Working Included)

To model realistic revenue, we must segment our base by customer type, recognizing that residential and commercial segments have radically different payment behaviors and take rates.

#### Step-by-Step Working: 1. Customer Base: 2,300 total customers. 2. Adoption Rate: Pilot adoption was 61% (close to the 70% target). Let's model a realistic 60% adoption rate by month 24 = $1,380$ adopting customers. 3. Segmentation Split: Based on overall volume, 42% of value is residential ($2.03B) and 58% is commercial ($2.80B). Total invoiced value = $4.83B. * Total Residential Invoiced: $2.03B ($\approx$ $882k$ per customer across 2,300) * Total Commercial Invoiced: $2.80B ($\approx$ $1.22M$ per customer across 2,300) 4. Take Rates & Behavior: * Residential: 71% card adoption via pay-by-link. Net take rate on card is 0.7%. ACH/Check take rate is near zero (flat $1.60 net on ACH, negligible volume). Effective blended take rate on residential volume $\approx$ $0.7\% \times 71\% \approx \mathbf{0.50\%}$. * Commercial: 6% card adoption, 94% ACH/Check/Terms. Card take rate is 0.7%; ACH nets a flat $1.60 per transaction (on a $3,800 invoice, $1.60 is a 0.04% effective take rate). Effective blended take rate on commercial volume $\approx$ $\mathbf{0.08\%}$.

#### The Realistic Range (Month 24 Run-Rate): * Bear Case ($3.2M ARR): Commercial customers reject card fees entirely, sticking strictly to ACH/checks; residential adoption stalls at 45% due to surcharge pushback. * Base Case ($6.1M ARR): 60% overall adoption. Residential volume yields a 0.50% blended take ($2.03B $\times$ 60% adoption $\times$ 0.50% = $6.09M). Commercial yields minimal flat-fee ACH revenue. * Bull Case ($9.8M ARR):³ 70% adoption matches the CEO's target, and we successfully introduce a B2B "accelerated payout" fee (drawing on the 9 customers out of 22 who said they would pay a fee to solve their $200k payroll float).

> Result: The realistic revenue run-rate at Month 24 is $3.2M to $9.8M, falling drastically short of the $24M target.

---

3. Falsification Criteria and a Six-Week Test

#### What would prove us wrong? If a randomized cohort of commercial-heavy customers willingly adopts card payments at >20% volume despite a 2.9% surcharge, or if property managers accept automated card-on-file billing for invoices over $3,000, our commercial pessimism is unfounded.

#### The Six-Week Test ($15k budget, 1 squad for 6 weeks): * The Experiment: Launch a targeted "Fast-Pay Commercial Portal" pilot with 30 mid-market commercial customers currently handling invoices between $2,000 and $5,000. * The Mechanics: Offer them an explicit choice: continue standard net-45 terms via free ACH, or use a discounted commercial card rate (e.g., split-surcharge or 1.9% + $0.30 via a specialized B2B interchange tier)² to get paid in 48 hours. * Success Metric: Do at least 25% of their commercial payors opt-in to the digital card rail over 6 weeks? If not, the commercial card thesis is dead.

---

4. What We Should Do Instead

Pausing the scheduling rewrite to chase an illusory $24M payments figure is a strategic trap. The scheduling rewrite is our defensive moat: losing it costs us $1.9M in high-value churn annually from customers with >50 technicians.

#### Recommended Pivot: 1. Protect Core Engineering: Keep the scheduling rewrite on track. Do not cannibalize the core product teams for a pivot that math shows yields ~$6M, not $24M. Allocate one dedicated squad (not three) to productize payments iteratively. 2. Pivot the Value Proposition: Stop trying to monetize residential card transactions where competition (Tradesly, Stripe) is fierce. Instead, solve the actual pain point identified in customer interviews: commercial cash flow float. 3. Build B2B Working Capital Solutions: Build features that help trades businesses bridge the net-45 gap (e.g., instant payout/invoice factoring models embedded in Fieldline Pay) rather than relying purely on interchange take-rates.

---

Given that our next Series C raise is in 14 months, how comfortable is the board with a realistic payments ARR of $6M built on workflow efficiency, versus an aggressive $24M gamble that risks our core enterprise retention?

To: Priya Raman (for exec offsite pre-read) From: Staff PM Re: The strongest case against committing three squads for three quarters to Fieldline Pay

Bottom line

Payments is a real opportunity, but the $24M is not supported by our own data. Re-estimated from the pack, month-24 run-rate is roughly $1M–$6M, central case about $2.3M. Even the most generous extrapolation of the pilot gives about $9M. The plan would pause the scheduling rewrite, which is tied to $1.9M of churned ARR a year, to fund a payments line that at its central case earns about the same amount after nine squad-quarters. I recommend a smaller, staged bet.

1. The assumption the plan depends on most

The plan assumes a dollar of invoice value is worth 0.7% to us. It is not, because 0.7% is the margin on card payments only.

The term sheet says we net about 0.7% on card value, but ACH nets $1.60 per payment ($2.00 charged, $0.40 cost), and checks and cash earn nothing. The CEO and CFO models apply the card margin to all $4.83B of invoices. What matters is how those invoices get paid.

• Commercial jobs are 58% of invoiced value, and only 5% of that is paid by card. The average commercial invoice is $3,800, so ACH nets $1.60 / $3,800 = 0.04%.
• Residential jobs are 42% of value, and the pilot lifted card share to 71%.

Yield per dollar of volume that actually flows through Fieldline Pay, using pilot card shares and assuming the non-card remainder moves by ACH:

Even if every invoice dollar went through Fieldline Pay, the blended yield would be 0.30%, less than half the modelled 0.7%.

The evidence is consistent with this: - 11 of 14 mostly-commercial customers say their clients require ACH or check. - 6 of 22 won't offer card at all. - Head of Sales expects property managers to refuse 2.9% on a $3,800 invoice.

Pilot revenue is $5,630 per adopting customer, against the $14,700 the CEO's model implies ($2.1M × 0.7%). That is 38% of the claim, from a pilot that was 64% residential, against 42% for the base. This is the best case for the mix.

Two supporting errors compound this: - The $2.1M is a mean. The median customer invoices $640k. The top 115 customers carry 48% of volume, and 71 of them are on multi-year processor contracts, mostly to 2028. Sales expects none to move. - Tradesly is not a comparable. It is about 80% residential, and we are 42%. Its 22% revenue share says little about a base that is mostly commercial by value.

2. Re-estimate of month-24 run-rate

Formula: addressable volume × adoption × share of adopters' invoice value routed through Pay × blended yield.

Addressable volume. I remove the locked-in accounts, assuming the 71 are typical of the top 115: 71/115 × $2.32B ≈ $1.43B. That leaves $3.40B.

• Adoption. The pilot's 61% came from invited customers over four months, so I treat it as a ceiling.
• Routing. The CEO's model implicitly assumes 100%. Customers who adopt still get paid by check and cash on many invoices, and payers choose the method.
• Yield. Base is the whole-base mix. High approaches the pilot's residential-heavy 0.42%. Low assumes the locked-in accounts are commercial-heavy, so the remainder skews slightly more residential and the low case is harsher than it needs to be.

Cross-check against the pilot. The base case implies about $2,300 per adopting customer, against $5,630 in a residential-skewed, hand-picked pilot. That is plausible. The most generous version applies the pilot's $5,630 to 1,610 customers, giving $9.1M. That ignores the lock-ins and the pilot's mix, and it is still 38% of the claim.

Implication for the board. At $2–6M, payments would be roughly 5–12% of revenue, not 35% by 2028. Reaching $24M would need about a 3% yield on the volume in my base case, which is not available on this term sheet.

Caveats: - Payment-method data comes from only 690 self-reporting customers (30%). - The pilot ran four months. - I have not modelled ramp, disputes or chargebacks, or upside from a paid fast-payout product. That last one is the most interesting missing piece.

3. What would prove me wrong, and the cheapest test

To vindicate the plan, we would need to show that commercial volume can yield at least ~0.5% net, with at least 60% of adopters' volume routed through Pay. That would put the total near $15M or more. On a $3,800 invoice, 0.5% is about $19 net per invoice. That requires either much higher commercial card share, or a fee people will pay, such as faster payout.

A six-week constraint: commercial invoices take 52 days on average to be paid, longer than the test window. We cannot wait to observe commercial cash-in, so the test must use leading indicators and data we already hold.

The test (roughly one PM, one analyst and one engineer, using existing pilot plumbing): 1. Week 1: re-cut the existing pilot. Split the 38 customers by commercial share and compute yield per dollar of volume for the commercial-heavy ones. Their older invoices are already paid, so this costs nothing and tells us quickly whether 0.08% is right. 2. Weeks 1–6: a commercial-heavy cohort. Recruit about 20 mostly-commercial, non-locked-in customers, drawn from the 11 who said their clients require ACH or check. Turn on pay-by-link and measure the share of payers who choose card and the share of invoice value routed via link. 3. Weeks 2–6: price a fast-pay offer. Offer these customers accelerated payout, funded by a fee, as a real priced offer with sign-up. Nine of 22 said they would pay to be paid faster, and this is the only route I see to meaningful commercial yield. Measure conversion at the stated price.

Thresholds, set now: commercial card share above 25%, or fast-pay uptake implying at least 0.3% net on routed commercial volume. Below both, the base case stands and the bet should be sized to it.

4. What we should do instead

Don't commit three squads for three quarters, and don't pause the scheduling rewrite. The rewrite addresses the top-cited churn reason in the >50-technician segment, which lost $1.9M ARR last year. Those are also the accounts with the most volume and the ones payments can't reach. Cutting the rewrite risks retention at the top of the base to chase payments revenue the top can't deliver.

A staged alternative: 1. Fund one squad for two quarters, focused on residential-heavy and small customers, where the pilot works (71% card share, ~0.6% yield). Ship pay-by-link, card and ACH broadly, and track net revenue per adopting customer and routed share. 2. Run the six-week commercial test above. Its result decides whether a second and third squad get funded for a commercial cash-flow product (fast payout or early pay). That product fits the real pain: 17 of 22 customers named getting paid on commercial jobs as their biggest cash problem. 3. Set gates. Add squads only when the test or the first quarter's data shows blended yield above 0.4% on routed volume. Revisit the locked-in accounts as contracts approach expiry in 2028. 4. Reset the board narrative from "$24M / 35% of revenue" to a $2–6M range with a clear path to more if commercial monetisation works. For the raise in about 14 months, a measured payments attach rate and net revenue per customer will be more credible to investors than a projection that unravels in diligence.

The CEO's instinct that payments could make Fieldline stickier is sound, and the pilot's 61% adoption is a good sign. But the current plan assumes we can monetise the volume we don't touch at the rate we monetise the volume we do, and our own numbers say otherwise.

To: Priya Raman Subject: Fieldline Pay: challenge the $24M case before committing three squads

The strongest case against the current plan is not that embedded payments cannot work. It is that the $24M forecast treats invoice volume as if it were payment volume earning a card-like margin.

The critical unsupported assumption: 70% of customers will adopt and route enough of their invoices through Fieldline Pay to earn roughly 0.7% on that value. The 0.7% net take is specifically the card margin. ACH earns $1.60 per payment; checks and cash earn nothing. The CFO’s arithmetic is correct only if essentially every dollar from every adopting customer earns the card margin.

That is a poor fit with our mix. Commercial work is 58% of invoiced value; commercial clients typically require ACH or check, pay after 52 days, and may not accept a card surcharge on a $3,800 invoice. Eleven of 14 interviewed mostly-commercial customers said their clients require ACH or check. By contrast, the pilot’s customers were 64% residential, against 42% for Fieldline overall. And 71 of the 115 largest customers have processor contracts running mostly to 2028; the largest 5% of customers account for 48% of invoiced value. The pilot’s 61% adoption is encouraging, but it does not establish broad adoption or broad monetization. Tradesly’s 22% revenue share is also a weak comparator: its customer base is about 80% residential.

A more defensible annualized revenue range

The following estimates are run-rate scenarios, not a forecast. They use the supplied 61% pilot adoption rate and 70% plan assumption as bounds, and make explicit that the take depends on payment type.

Card revenue: Current recorded payment methods show 19% of invoice value paid by card. In the pilot, the reported card shares imply a 33.3% value-weighted card share if applied to our mix: 42% residential × 71% + 58% commercial × 6% = 33.3%.

At a 0.7% net card take:

• Lower case: $4.83B × 61% adoption × 19% card share × 0.7% = $3.9M
• Upper case: $4.83B × 70% adoption × 33.3% card share × 0.7% = $7.9M

The upper case assumes pilot card behavior transfers to the full customer mix, despite the pilot’s residential skew.

ACH revenue: The recorded-method sample reports ACH at 44% of invoice value, but value share does not tell us the number of $2 ACH payments—and the pilot does not report ACH usage. As an illustrative bound, if that 44% share transferred to adopters, ACH revenue would be about $0.5M–$2.1M after the $0.40 cost: the lower end assumes ACH dollars are mostly $3,800 commercial invoices; the upper end allows the pilot’s card mix and available non-card residential volume. This is uncertain upside, not a reliable forecast.

Together, that supports roughly $4.5M–$10M of annualized revenue, before accounting for contract lock-in or slower adoption among large accounts.¹ The range is still conditional on transferring today’s payment mix and pilot behavior to adopters. As a cross-check, the pilot’s $214K annualized revenue across 38 customers is $5,630 per customer; scaling that to 61%–70% adoption gives $7.9M–$9.1M. That sits within the range, but is not a clean base case because the pilot skewed residential.

The $24M case requires $14,700 per adopting customer per year ($2.1M × 0.7%). That is about 2.6× the pilot’s $5,630, while assuming adoption and monetization across a materially more commercial customer base.

What would change my mind—and the cheapest six-week test

I would support a larger bet if a representative cohort showed both credible adoption and enough net revenue per adopter to approach the $14,700 annualized level the board case requires—especially among commercial customers and larger accounts not locked into existing processors. A high signup rate alone would not prove the economics.

Run a six-week, no-build test using the existing pay-by-link and partner setup. Recruit a small, stratified cohort across residential and commercial customers, including larger unlocked accounts. Track offers accepted, invoice value actually routed, card versus ACH mix, net revenue after costs, and payment timing. Report results by segment; do not annualize a handful of unusually large or residential-heavy customers as if they were representative. Include a holdout or compare with each customer’s recent invoices to distinguish new payment volume from existing behavior.

Recommendation

Do not commit three squads for three quarters or pause the scheduling rewrite on the current evidence. The rewrite addresses the top-cited churn reason among customers with more than 50 technicians, a segment that lost $1.9M ARR last year. Run the six-week test with a small team and existing capabilities, then make a stage-gated decision. If commercial routing and net revenue per adopter are strong, fund the next increment. If not, preserve the scheduling investment and narrow Pay to the segments where the data shows customers can—and will—use it.