Needs more than a quick edit9 of 11 checks passed
The memo is factually strong and gives a clear go/no-go call, but its 'instead' is generic and misses the commercial cash-flow/faster-payout opportunity from the interviews. A PM would need to add that alternative reasoning rather than just edit wording.
Output
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.1 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.
What a PM had to fix
1OtherFix itTargeted repair
What we’d changeThese assumptions produce an illustrative $4.5M–$10M envelope, not a validated revenue range. They assume customer adoption translates proportionally into invoice volume and the modelled payments route through Pay. Rebuild by segment: accessible invoice value × volume-weighted adoption × routing share × payment-method economics, excluding contracted volume.
Check by check
Got wrong · 1
- Reshapes the bet from the evidenceThe recommendation is a generic stage-gate/narrow-to-segments move and does not propose the specific alternative the evidence supports, such as residential card focus or commercial cash-flow/faster payout.
Mixed · 1
- Uses the supplied evidence correctlyAll facts and arithmetic trace to the supplied pack, with no invented current-state figures found.The two graders disagreed on this one.
Got right · 9
- Addresses the actual decisionThe memo commits clearly to not committing now, proposes a stage-gated test, and states what would change the call.
- Respects explicit constraintsIt is a memo addressed to Priya, within the requested length, and covers the four required elements.
- Identifies material uncertaintyIt names payment-mix, adoption, contract lock-in, and pilot skew as unknowns and says how a six-week test would resolve them.
- Avoids unsupported claimsEstimates are labelled as scenarios/bounds, and generalizations are tied to interview and sales evidence rather than asserted as fact.
- Produces the required deliverableThe memo is a complete, usable pre-read for the exec audience with a clear recommendation and supporting analysis.
- Finds the load-bearing assumptionIt makes the take-rate/payment-mix mismatch the central challenge, using the card, ACH, and check/cash unit economics from the pack.
- Re-estimates the revenue correctlyIt recalculates revenue from the payment mix and pilot, lands in the $4.5-10M range, and explains why the pilot is an upper bound.
- Says what would prove it wrongIt specifies a six-week stratified cohort test with net revenue per adopter approaching $14,700 as the threshold to change its mind.
- Tigers, not paper tigersIt triages the take-rate mismatch as the sink, dismisses Tradesly as a weak comparator, and surfaces the scheduling-rewrite churn risk.
Grades and run details
Decision model 86 · LLM judge 10 of 12 checks
Decision model checks
- failUses the supplied evidence correctly3%
- passAddresses the actual decision95%
- passRespects explicit constraints57%
- passIdentifies material uncertainty98%
- passAvoids unsupported claims31%
- passProduces the required deliverable57%
- passFinds the load-bearing assumption97%
- passRe-estimates the revenue correctly82%
- passSays what would prove it wrong79%
- partialReshapes the bet from the evidence44%
- passTigers, not paper tigers89%
Run
- Run
- #1
- API response time
- 73 s
- Submitted
- 29 Sept 2026