Challenge an idea

To: Priya Raman and the executive team Subject: Fieldline Pay: validate the revenue engine before committing three squads

Recommendation: do not approve three squads for three quarters. Authorise a six-week commercial validation using the existing pilot and protect the scheduling rewrite. Payments may be a useful extension, but the supplied evidence supports an illustrative annual revenue range of $3.3M–$7.2M¹, with substantial uncertainty. It does not support underwriting $24M or making that figure central to our next raise.

The assumption the plan depends on

The unsupported assumption is that customer adoption translates into monetising those customers’ entire invoice value at a 0.7% net yield.

The model multiplies customer count by average invoicing and card economics. Each component hides a material constraint:

• Adoption is not payment capture. Enabling Fieldline Pay does not mean every payer switches. In the reporting sample, 81% of invoice value is currently paid without cards.
• 0.7% is card economics, not blended economics. ACH earns $1.60 per payment. On a $3,800 commercial invoice, that is 0.042%, around one-seventeenth of the assumed yield. Checks and cash earn nothing.
• Customer count is a poor proxy for accessible volume. The largest 5% generate 48% of invoicing. Of those 115 customers, 71 have processor contracts running mostly to 2028. Seventy per cent adoption among smaller customers could leave much of the revenue pool untouched.

Our mix compounds the problem. Commercial work represents 58% of invoice value. Commercial card share barely changed in the pilot, from 5% to 6%, despite pay-by-link on every invoice. Residential card share increased to 71%, but the pilot was 64% residential against 42% across Fieldline.

The customer problem is also different from the proposed solution. Seventeen of 22 interviewees identified slow commercial payment as their biggest cash problem. Offering another payment method does not establish that property managers will abandon net-45 or net-60 terms.

Tradesly shows payments can work for a business with approximately 80% residential customers. Its 22% revenue contribution does not validate our volume, adoption or margin assumptions.

What the supplied numbers support

Use:

Annual revenue = eligible invoice value × adopting share of that value × realised net yield.

The following are scenarios, not statistical bounds. Neither the exact invoicing of the 71 contracted accounts nor representative payment capture is supplied.

Working:

Lower yield:

`19% × 0.7% + 44% × $1.60 × (42% ÷ $410 + 58% ÷ $3,800) = 0.216%`

`$2.51B × 61% × 0.216% = $3.3M`

Upper yield:

`33.3% × 0.7% + $1.60 × (42% × 29% ÷ $410 + 58% × 94% ÷ $3,800) = 0.304%`

`$3.40B × 70% × 0.304% = $7.2M`

These calculations assume eligible customers retain the overall residential/commercial mix and that adoption rates by customer also apply by value. The lower scenario assumes 44% ACH within both job types. Both assume full capture of the payment streams modelled. The upper scenario additionally interprets the pilot’s card shares as shares of value; if they are transaction counts, that extrapolation is unsupported. It also assumes complete conversion of checks and cash to ACH.

Consequently, $3.3M is not a floor. The reporting sample covers only 30% of customers, and actual volume concentration or capture could reduce revenue further.

A separate check points in the same direction: scaling the pilot’s $5,630 annual revenue per adopter to 61–70% of 2,300 customers produces $7.9M–$9.1M, before correcting its residential bias or account availability.

On the upper scenario’s eligible volume and 70% adoption, $23.7M would require approximately 1.0% net revenue on every adopted invoice dollar, above even the quoted card margin. Growth could alter this, but the pack supplies no growth assumptions to bridge the gap.

These are annualised net payments revenues under the partner terms, not profit or contracted software ARR.

What would prove this challenge wrong

We would need evidence that accessible customers generate materially more net revenue per total invoiced dollar than these scenarios imply, at sufficient committed volume to support $24M. That could come from much greater accessible volume, different economics or a demonstrably valuable paid service. Enthusiasm and payment-feature activation would not suffice.

The cheapest six-week test is to extend the existing pilot, with analyst, sales and limited engineering support:

1. Establish the accessible denominator. Match the 71 processor contracts to actual invoice value, expiry dates and any permitted carve-outs. Replace the equal-volume assumption with account-level evidence.
2. Recruit a stratified cohort. Include commercial-heavy businesses and large uncontracted accounts, alongside residential firms. Count refusals in adoption results and weight findings to eligible invoice value.
3. Measure actual money movement. Track total invoicing, activated volume, captured volume, payment methods, realised fees and net revenue. Report residential and commercial results separately. Use existing receivables approaching their due dates to observe commercial payments within six weeks.

Before recruitment, agree that expanding investment requires a volume-weighted model supported by observed payments and credible customer commitments. To justify the original commitment, that model must show a defensible route to $24M by month 24. Six weeks cannot establish mature adoption or commercial collection cycles; an inconclusive result should not trigger automatic approval.

How the bet should change

If validation confirms residential economics, pursue a narrower residential payments offering with staged staffing and revenue gates. Separately test whether commercial customers will make concrete commitments to a faster-payment proposition. Nine expressions of willingness to pay justify discovery, not a financing product.

Keep the scheduling rewrite funded. The affected segment lost $1.9M ARR last year, with scheduling the top-cited churn reason. That is not all recoverable, but pausing the work has a documented cost against a speculative upside.

We should update the board with a scenario range and validation milestones. With the raise approximately 14 months away, protecting credibility and existing revenue matters more than preserving an unsupported headline.

To: Priya Raman; CEO; CFO; Head of Sales From: Staff PM Subject: Fieldline Pay: challenge the revenue thesis before committing three squads

Recommendation

Do not commit three squads for three quarters or pause the scheduling rewrite. Authorize a six-week commercial test using the existing pilot product and partner.

Embedded payments may be worth building. The evidence does not support presenting $24M as an expected month-24 revenue run-rate. My scenario range is approximately $2–$10M annualized, with $10M an optimistic case—not a base case.

1. The unsupported assumption: adopted invoice dollars yield 0.7%

The plan’s most consequential assumption is that the invoice value belonging to adopting customers becomes payment volume earning a blended 0.7% net take.

That is card economics applied to all invoices. It conflates three things: adopting Fieldline Pay, routing payments through it, and choosing a profitable payment method.

The available evidence contradicts it:

• Only 19% of recorded payment value is card. ACH is 44%; checks and cash are 37%. These observations cover 30% of customers, so representativeness remains unproven.
• ACH does not yield 0.7%. We earn $1.60 per payment. At the average commercial invoice of $3,800, that is 0.042%; at the residential average of $410, 0.390%.
• Commercial work is 58% of invoice value. Even in the pilot, commercial card share reached only 6%, versus 71% for residential. A 2.9% card fee on a $3,800 invoice is about $110, before the fixed charge. Sales and interviews both indicate resistance to that fee.
• The pilot overweights our best payments segment: 64% residential versus 42% across Fieldline. Tradesly’s roughly 80% residential customer mix makes its revenue share a poor benchmark for ours.

Volume concentration compounds the error. The largest 115 customers supply 48% of invoice value; 71 have processor contracts, mostly through 2028. We do not know those 71 customers’ exact volume, but cannot assume their invoices are available.

Consequently, 70% customer adoption does not establish 70% volume capture. The $2.1M average also obscures this concentration: the median is $640k, and customers outside the largest 5% average only $1.15M.

2. Re-estimate: approximately $2–$10M annualized

Use:

Revenue = eligible invoice value × adoption × routed share × payment-method yield.

The following scenarios assume adopters route all eligible invoices through Pay. That is generous. They use today’s customer base, not unsupported customer growth, and are scenarios rather than a statistical confidence interval.

Conservative scenario: approximately $2.3M

Assumptions:

• Exclude the entire largest-5% cohort pending evidence of access. This is a conservative scenario, not a claim that all 115 are contractually blocked.
• Remaining invoice value: $4.83B − $2.32B = $2.51B.
• Adoption: pilot’s 61%.
• Retain today’s 19% card and 44% ACH value shares; checks and cash earn nothing.
• Value ACH at the commercial invoice size. This produces the lower ACH yield.

Blended yield:

19% × 0.7% + 44% × ($1.60 ÷ $3,800) = 0.152%.

Revenue:

$2.51B × 61% × 0.152% ≈ $2.3M.

This assumes the remaining cohort has the overall payment mix; the pack does not provide its actual mix.

Optimistic scenario: approximately $10.3M

Assumptions:

• All $4.83B is accessible, despite processor contracts.
• 70% adoption also captures 70% of invoice value.
• Pilot card conversion transfers to Fieldline’s actual job mix.
• Every non-card dollar becomes ACH: no checks, cash or external payments.

Card value share:

42% × 71% + 58% × 6% = 33.3%.

Blended yield, using job-specific invoice sizes:

33.3% × 0.7% + [42% × 29% × ($1.60 ÷ $410)] + [58% × 94% × ($1.60 ÷ $3,800)] = 0.304%.

Revenue:

$4.83B × 70% × 0.304% ≈ $10.3M.

Even this unusually favorable case is 57% below the CFO’s $23.7M.

A separate cross-check is the pilot’s actual monetization: 1,610 adopters × $5,630 = $9.1M. That is not a forecast: the pilot is residential-heavy, and we lack its invoice-volume denominator. But it does not validate $24M.

The range could fall below $2M if adoption or routing disappoints. We lack the data to assign probabilities.

3. What would prove this challenge wrong?

To generate $24M from $4.83B, Fieldline needs portfolio-wide annual net yield of approximately 0.50%. At 70% volume capture, captured payments must yield approximately 0.71%.

We would need evidence of either:

1. Much more accessible, routed, high-margin card volume than today’s mix and pilot suggest; or
2. A demonstrably profitable additional fee or product customers will actually pay for.

Adoption percentages, enthusiasm and competitor revenue shares would not suffice.

Cheapest six-week test

Use the existing pay-by-link product and partner; no new platform build.

Recruit approximately 50 non-pilot customers, stratified by invoice volume and residential/commercial mix, including a deliberate sample of large accounts with processor contracts. Weight results by invoice dollars, not customer count.

For each, establish contractual access and offer Pay at intended production pricing. Measure:

• Activation and actual routed invoice value;
• Card/ACH/check mix, invoice sizes and realized net revenue;
• Payer refusals, especially commercial surcharge refusals;
• Large-account willingness and ability to switch.

Commercial invoices take 52 days to pay on average. Include existing invoices due during the test, not just newly issued invoices, and report unpaid invoices separately rather than assuming conversion.

The test passes only if observed economics and credible volume-access commitments support a transparent path to $24M. A small test cannot prove 18-month adoption, but it can cheaply falsify the unit economics or access thesis.

4. Change the bet

Keep the scheduling rewrite staffed. It addresses the top-cited churn reason in a segment that lost $1.9M ARR last year; postponing it has a concrete opportunity cost ahead of our raise.

If the test supports attractive economics, fund a narrower, stage-gated residential payments rollout—not the current commitment.

Separately, test commercial customers’ willingness to pay for faster collection. Seventeen of 22 interviewees identified commercial payment delays as their biggest cash problem; nine would pay to get paid faster. Payments acceptance does not itself solve net-60 terms. Explore collections workflows or partner-funded acceleration before underwriting a financing business.

Finally, reset the board’s expectation now: $24M is an unvalidated upside hypothesis, not an evidence-backed plan.