← Back to Stories

Story · Solution

The owner chases who owes, firmly or gently, never anyone who has paid

I own a small coffee roaster that sells wholesale to cafés, hotels and offices.

Sound familiar?

When invoices go overdue I either send everyone the same stiff reminder or put it off, and once I chased a customer who had already paid.

Why it hurts

I own a small coffee roaster that sells wholesale to cafés, hotels and offices. When invoices go past due I have two bad choices: send everyone the same stiff reminder and upset the customers who nearly always pay on time, or put it off and let the money drift. Worse, I once chased a customer who had already paid; the payment had come in through another system and never reached the books.

How it is solved

Chase every overdue customer once, in the tone their own payment record calls for, and chase no one who has already paid.

  1. The bookkeeper lists who is overdue. The overdue customers are ranked by what chasing each one is worth. Each carries a payer score drawn from their own history and the tone that score calls for: firm for a customer who is late again and again, gentle for a good payer who has slipped once. The oldest debt is aged and marked red, so it cannot be missed.
  2. The bookkeeper checks payments made elsewhere first. An invoice can be open in the books while a payment system shows a settlement that covers it. The app marks such an invoice possibly paid, shows the settlement beside it, and keeps it out of the drafts, so the bookkeeper verifies it instead of chasing it.
  3. The owner sees that a new customer is not judged on too little history. For a customer with only a few invoices, the owner sees the history marked as thin and a default score, rather than a pattern the app has invented. An invoice that is not yet overdue is not chased.
  4. The owner gets one reminder drafted per customer, in the right tone. The cash advisor, an AI agent, words each reminder, and the app fills in every figure. A customer who owes several invoices gets one reminder covering all of them, with a date to pay by. Drafting sends nothing and stores nothing.
  5. The owner chooses who to chase and approves each reminder. The owner ticks the customers to chase; an invoice that may already be paid cannot be ticked. The owner then reads each reminder, edits it if needed, holds any that should not go, and approves the rest. The approval is recorded with who gave it and when, and in the demo the send is simulated and labelled as such.

Works with

QuickBooks, Stripe, PayPal

The result

A set of reminders the owner has approved, one per customer, each in the tone that customer's record calls for and covering all of their overdue invoices. Invoices that may already be paid are set aside to verify, with the settlement that covers them, and the oldest debt is named.

  • If a customer pays late again and again, one firm reminder covers everything they owe, with a date to pay by.
  • If a good customer has slipped once, a gentle reminder keeps the relationship intact.
  • If a payment has already come in through another system, the invoice is set aside to verify, and no reminder is drafted.
  • If a customer is too new to judge, they get a default score, and are chased only once an invoice is overdue.

Try it

The demo runs on WidgetCo Coffee Roasters, an example business: a coffee roaster with an online store and a wholesale side. You will see it as Dana, the owner.

Connected to this story