A tour of the follow-up loop

Six stops from messy receivables to a calm weekly routine. The demo workspace follows this exact path with fictional data.

1. 1

   The dashboard: your money, in six buckets

   Outstanding total, collected total, reminders waiting for your approval, and an ageing strip from 'upcoming' to '45+ days overdue'. Every number is a link to the invoices behind it — nothing on this screen is decorative.

2. 2

   Import: reconcile, don't retype

   Upload the receivables CSV your accounting tool exports. Columns are auto-mapped (and correctable), every row is validated with a downloadable error report, and invoices match by number — so re-importing next week updates balances instead of creating duplicates.

3. 3

   The reminder policy you can actually read

   Four stages with plain templates: a courtesy note 3 days before due, a friendly nudge at 3 days over, a firm follow-up at 10, a final reminder at 25. Change the timing, tone and wording per stage. Placeholders pull invoice facts; nothing is invented.

4. 4

   Approve, then send

   A scan drafts reminders for every stage that's fallen due. Each draft shows exactly what will be sent; you edit and approve, and the approval is recorded with your name. Paid, disputed, held or do-not-contact invoices are re-checked at the moment of sending.

5. 5

   The customer status page

   Every reminder links to a secure, unguessable page where your customer sees the invoice status, can pay (Stripe when configured; a clearly-labelled test payment in demo mode), promise a date, or flag a problem — which pauses reminders and notifies you.

6. 6

   Reports that don't flatter

   Collected-after-follow-up is labelled as attribution, not causation. Average days-late at payment tells you if things are improving. The ageing table is the one you used to build by hand.