Checks what's overdue
Faber reads the invoice list you already keep, a spreadsheet, or invoices sent and received by email, and works out what's unpaid and how late.
Use case
You set it up once: where your invoices live, how the reminder should read, and when it runs. From then on Faber runs those same steps, finds what's overdue and drafts the follow-up. You send it. Faber reads the reply and drafts again on the date a customer promised to pay.
How it helps
Faber reads the invoice list you already keep, a spreadsheet, or invoices sent and received by email, and works out what's unpaid and how late.
A customer answers "I'll pay Friday." Faber notes the promise and drafts a follow-up if Friday passes without payment, so nothing slips.
It follows the steps you set, in the same order, on every overdue invoice, so none get missed and no one gets chased twice. A reminder you have not sent yet is never written over.
What happened
After every run, Faber leaves a plain-English record of the reminders it drafted, the ones still waiting in your drafts, and the replies it read.
Good fit when
Invoices are tracked in a spreadsheet, or sent and received by email.
Follow-ups are written by hand today, and slip when things get busy.
Tone matters, and reminders should stay polite and escalate gradually.
You want to read every reminder before it goes, and see what was promised and what's still outstanding.
Describe where your invoices live, how the reminders should read, and when they are drafted.