Usable with a quick edit10 of 11 checks passed
A PM could use it with light edits, mainly tightening the revenue range to align with the expected $5–10M upper-bound framing. The evidence and reasoning are otherwise strong and actionable.
Output
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:
| Card | ACH | Yield | |
|---|---|---|---|
| Residential ($410 avg) | 71% × 0.70% = 0.50% | 29% × ($1.60/$410 = 0.39%) = 0.11% | 0.61% |
| Commercial ($3,800 avg) | 6% × 0.70% = 0.04% | 94% × 0.042% = 0.04% | 0.08% |
| Whole base (42/58 mix) | 0.30% |
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.
| Low | Base | High | |
|---|---|---|---|
| Adoption (by volume) | 30% | 45% | 61% (pilot rate) |
| Share of adopter volume routed | 30% | 50% | 70% |
| Blended yield | 0.25% | 0.30% | 0.40% |
| Run-rate | $0.8M | $2.3M | $5.8M |
- 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.
Check by check
Got wrong · 1
- Re-estimates the revenue correctlyIt shows working but lands on a central $2.3M and $1M–$6M range, not roughly the $5–10M range required by the grading rubric, and its $9.1M pilot upper bound is not used as the main re-estimate.
Got right · 10
- Uses the supplied evidence correctlyThe memo’s factual statements about the current situation are drawn from the pack or follow by arithmetic, with assumptions labelled.
- Addresses the actual decisionIt clearly recommends not committing three squads and instead funding a staged one-squad bet, with gates and a six-week test that would change the call.
- Respects explicit constraintsIt is a memo under 1,200 words, addressed to Priya for the exec offsite, and covers all four requested elements.
- Identifies material uncertaintyIt names material unknowns such as payment-method reporting coverage, pilot mix, routing share, commercial card acceptance, and fast-pay uptake, and proposes tests to resolve them.
- Avoids unsupported claimsMost interpretations are labelled as assumptions or estimates; the few rhetorical characterisations do not drive the core analysis.
- Produces the required deliverableThe deliverable is complete, usable, and written for the named executive audience within the requested length.
- Finds the load-bearing assumptionThe central challenge is explicitly the 0.7% blended take rate being applied to all invoice value despite the actual payment mix and unit economics.
- Says what would prove it wrongIt specifies a six-week commercial cohort and fast-pay test with concrete thresholds, including commercial card share above 25% or 0.3% net on routed commercial volume.
- Reshapes the bet from the evidenceIt keeps residential card payments and proposes a commercial cash-flow/fast-payout alternative grounded in interview and pilot evidence.
- Tigers, not paper tigersIt ranks the take-rate/payment-mix flaw as primary, treats Tradesly and lock-ins as supporting evidence, and surfaces the churn/rewrite tradeoff as the uncomfortable issue.
Grades and run details
Decision model 95 · LLM judge 11 of 12 checks
Decision model checks
- passUses the supplied evidence correctly21%
- passAddresses the actual decision100%
- passRespects explicit constraints43%
- passIdentifies material uncertainty100%
- passAvoids unsupported claims35%
- passProduces the required deliverable89%
- passFinds the load-bearing assumption100%
- partialRe-estimates the revenue correctly3%
- passSays what would prove it wrong100%
- passReshapes the bet from the evidence100%
- passTigers, not paper tigers99%
Run
- Run
- #1
- API response time
- 70 s
- Submitted
- 29 Sept 2026