Use case

Chase unpaid invoices without writing another follow-up email.

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

Overdue invoices get followed up every time.

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.

GmailGoogle Sheets

Reads the replies

A customer answers "I'll pay Friday." Faber notes the promise and drafts a follow-up if Friday passes without payment, so nothing slips.

The same way, every time

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

You see what was drafted and what was promised.

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.

What happenedInvoice chasing
  1. Checked the invoice sheet and found 9 overdue.
  2. Drafted 9 polite reminders, escalating by how late.
  3. 2 reminders are still waiting in your drafts.
  4. Read 3 replies and noted 2 "pay Friday" promises.
  5. Scheduled a Friday check on the promised payments.

Good fit when

Invoices go out reliably. Chasing them doesn't.

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.

Stop writing follow-ups by hand.

Describe where your invoices live, how the reminders should read, and when they are drafted.