Worked example
The invoice that chases itself
Meridian Facilities Group — net-30 clients, one owner who hates chasing money
Chasing overdue invoices is awkward, so it happens late or never. Here is the flow where the chasing is nobody's job because it's automatic.
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.
1 · The invoice goes out on completion
Generated from the job record, sent same-day, payable inline.
2 · Overdue triggers a polite, persistent cadence
Firm-but-warm reminders in the client's voice, on a schedule, with payment one tap away. Escalation to the owner before anything strongly worded.
Reminder 2 of 4 (representative) — Invoice #1088, 12 days past due
Hi Sandra — following up on invoice #1088 for June service at Lakeview ($8,000, due Jul 1). You can settle it in one click below. If something's off with the invoice, just reply and we'll fix it.
3 · The report claims only what the chase touched
The monthly ledger counts an invoice only when payment landed AFTER our reminder went out — and the note says plainly that "after" is not "because." On the sample month: 6 invoices, $4,120.
Monthly report line
| Line | Amount | Grade |
|---|---|---|
| 6 invoice(s) paid after Morthn chased | $4,120 | confirmed |
The takeaway
The awkward job gets done every time — and the report is honest about what the chasing did.
$1,997/mo + $1,997 one-time setup, first automation included · no long-term contract · All examples →