Worked example
The monthly arithmetic
A sample client on the base plan with two additional automations ($2,997/mo)
Every month, the report leads with arithmetic: what Morthn measurably did, against the fee. Three grades that never blend — confirmed (it happened, at your configured numbers), estimated (identified, not yet banked), and counts (real work we refuse to put invented dollars on). The ledger below is the actual composition engine running on a sample month.
This walkthrough follows a sample business. Where the engine is deterministic (statutory checklists, the filing calendar, the report arithmetic), the artifacts below are its actual output for the sample inputs — your dates and dollars come from your own setup.
The ledger, as the client sees it
Note what it does NOT do: no blended totals, no "industry average" dollars, and when a month falls short it says so plainly — that sentence is generated by the same code.
June — the arithmetic section of the monthly report (sample business)
$4,969 of confirmed + fee-replacement value this period against your $2,997 — before counting $3,840 in the open-chase book.
6 invoice(s) paid after Morthn chased
$4,120
confirmed
Payments that landed after our reminder went out. Some would have been paid anyway — "after", not "because", is the honest word.
3 zombie vendor seat(s) cancelled
$234
confirmed
Seats released for departed workers, at each vendor's seat price on file. Counted ONCE at monthly value — the saving actually recurs every month going forward, so this line understates.
2 warranty claim(s) reimbursed
$615
confirmed
Reimbursements actually paid in-window on claims this ledger tracked to the filing deadline. Money that historically just never appeared.
1 contractual price increase(s) exercised
$3,840
estimated
ANNUALIZED (contract value × the contract's own stated percentage) — the increase lands in your AR across the year, not this month, so it is graded estimated on purpose. Rights your contract granted and would otherwise have expired unexercised.
Counted, not priced
3 license/COI renewal chase(s) sent
No honest dollar exists for a lapse prevented — every circulating figure is vendor marketing, so this stays a count.
1 payment-detail change(s) rejected at the verification gate
A wire that never left has no invoice line — claiming an "average BEC loss avoided" would be inventing a number. Counted, not priced.
4 statutory hire/departure deadline(s) met on time
Final-pay penalties and COBRA fines that were never incurred cannot be honestly priced — the value is the clean audit trail. Counted, not priced.
2 asset(s) recovered from departed workers
No replacement-cost figure is on file per asset, so no dollar is claimed. Counted, not priced.
Why the refusals matter
A vendor that claims "$42,000 of fraud prevented!" is making the number up. We count the blocked change and say why no dollar is attached. Clients keep paying vendors whose arithmetic they can check — that is the retention model.
The takeaway
The fee justifies itself in arithmetic the client can verify — or the report says it didn't, in plain words.
$1,997/mo + $1,997 one-time setup, first automation included · no long-term contract · All examples →