Automate Collections Before Marketing: Chase Money You Already Earned

The first automation you build should chase money you have already earned. Not leads. Not content. Not a chatbot that answers enquiries at two in the morning. A payment follow-up sequence, running against your own ageing report, on your own invoices, to your own customers.

The reason is unglamorous: you already know what it is worth. Open your receivables ledger and the number is sitting there, named, dated and attributable to a specific person who has already agreed to pay you. Nobody has to model anything. If the sequence pulls forward a chunk of that money, you can point at the invoices and say which ones moved.

Now open a proposal for a lead-generation bot. Every figure in it is a guess multiplied by another guess. Leads captured, times a conversion rate you have assumed, times an average order value that is really a range, times a close rate that depends on a salesperson who may not be here next quarter. Four assumptions stacked on top of each other, and the output is a number with a decimal point in it, which is how you know it is fiction.

Both projects cost roughly the same to build. Only one of them lets you check afterwards whether you were right.

The ledger is the only honest brief you will get

Most automation projects start with someone describing a problem. Collections starts with a spreadsheet that describes it for you.

Pull your ageing report. Sort by days outstanding. Almost every business I have looked at finds the same shape: a long tail of invoices sitting well past terms, most of them belonging to customers who are neither disputing the amount nor in any distress. They simply have not been asked recently, and nobody in your office wants to be the one to ask.

That last part is the actual problem. It is not a process problem. Your accounts person knows the invoice is overdue. They can see it on the same screen you can. What they do not have is a comfortable way to raise it for the fifth time with a distributor whose owner your father knows, or a client whose next order is worth more than this bill.

Automation solves that specific discomfort well, because a scheduled system does not feel awkward. It sends on day seven whether or not anyone is in the mood. And when the customer rings up annoyed, the answer is structural rather than personal: the system flags everything past terms, it is not aimed at you. That sentence has repaired more relationships than any softening of the wording ever did.

What the sequence actually looks like

Keep it duller than you want to.

A trigger on invoice due date. A polite reminder a few days before it falls due, which is the single highest-yield message in the whole sequence and the one most businesses skip entirely, because it feels like nagging someone who has not yet done anything wrong. It is not nagging. It is the message that catches the invoice that never reached the right person, that went to a mailbox nobody reads, that arrived without a purchase order number and got parked.

Then a message on the due date. Then a short escalation ladder afterwards, each step slightly firmer, each one carrying the invoice number, the amount and a payment link or UPI QR in the message itself. Not "please find attached". Attached is where money goes to die. The customer is reading on a phone, standing in a warehouse, and if paying you requires opening a laptop, they will do it later and later means never.

Every step logs to one place so you can see, per customer, exactly what has gone out and when. And there is a hard stop: the moment a human replies, the sequence pauses and a person takes over. A reminder that keeps firing at somebody who has already said "cheque is ready, courier tomorrow" does more damage than the delay ever did.

That is the whole system. Six or seven messages, one condition, one kill switch. You can build it on WhatsApp Business with your accounting software's export, and if your Tally or Zoho or Busy data has to be pulled by hand into a sheet every Monday morning, that is fine. A manual export feeding an automated sequence still works. Do not let the integration become the project.

The distributor example

Take a manufacturer selling through distributors on thirty-day credit. Orders come in on WhatsApp, invoices go out on email, and payments arrive whenever the distributor's own collections happen to land. The owner knows which parties are slow. Everyone knows.

What actually happens in that business: the sales person who owns the distributor relationship is also the person expected to chase payment. Those two jobs are in direct conflict. He is asking for the next order and last month's money in the same conversation, so he asks for the order and lets the money slide, because his incentive is measured on the order.

The reminder sequence removes the collections job from him entirely. He keeps the relationship. The system keeps the calendar. When something genuinely needs a conversation — a disputed quantity, a damaged consignment, a real cash crunch at the distributor's end — the reply arrives, the sequence stops, and now he is having a useful conversation about one specific problem rather than an uncomfortable one about a general pattern.

The same shape applies if you are a services firm invoicing monthly retainers, a clinic with insurance claims, or an agency waiting on milestone payments. Wherever the person who owns the relationship is also the person expected to chase the money, the chasing loses.

Where this does not work, and you should not build it

I would rather tell you this now than after you have paid for something.

Your invoices are wrong or late. If bills go out days after delivery, if amounts get disputed regularly, if GST details are frequently incorrect and invoices come back for revision, do not automate reminders. You will be automating an argument. Every reminder will trigger a correction cycle, your accounts person will end up with more work than before, and your customers will learn that your messages are noise. Fix invoice accuracy and timing first. That is a process job, not a software job, and it is usually one person and one checklist.

You have very few customers. If your entire receivables ledger fits on one screen and your top handful of accounts make up most of the money, you do not need a system. You need one person to make a few phone calls on the first working day of the month. Automation earns its keep on volume and repetition. Below a certain count, the setup and maintenance cost more than the calls.

The money is stuck for structural reasons. Government contracts held up in sanction, insurance claims stuck in adjudication, an enterprise client whose vendor portal is the real bottleneck — none of these are affected by a reminder. The delay is not attention. It is process, somewhere you cannot reach. Sending five WhatsApp messages into that will change nothing except how your contact feels about you.

One relationship dominates. If a single customer's goodwill decides whether your year works, do not point an automated ladder at them. Handle it personally. Automate the rest.

There is also a fifth case worth naming: if your business genuinely gets paid up front, in full, before delivery, then you have no collections problem and this entire argument does not apply to you. Go build the lead-gen bot. You are the exception.

Why marketing automation keeps jumping the queue

Because it is more fun to build and easier to sell.

Marketing automation has a story. Collections automation has a spreadsheet. When you build a lead capture system, you get dashboards, funnel diagrams and a sense of momentum. When you build a reminder sequence, you get a WhatsApp thread and some slightly awkward customers. Nobody puts a payment reminder ladder in a case study.

It is also unfalsifiable, which is a feature if you are the one selling it. Leads went up? The bot worked. Leads went nowhere? The market was soft, the creative was wrong, we need more top-of-funnel. There is no state of the world in which a lead-gen automation is clearly shown to have failed. Collections does not offer that cover. The receivables number either moved or it did not, and it is visible in the ledger by the end of the month.

I have built both. The marketing systems were more interesting to build. The collections systems were the ones owners still had running a year later, because the value never became ambiguous. A thing you can measure is a thing you keep paying for.

And there is a sequencing argument beyond measurement. More leads with unchanged collections gives you more revenue you have not been paid for yet — more working capital tied up in the same slow customers, at a scale you now have to fund. Sorting out the money side first means every additional sale that follows converts to cash faster. Do the demand generation second, on top of a collections process that works. Do it first, and you are pouring water into a bucket you have not checked for holes.

Do this week

Export your receivables ageing report and sort it by days past due. Take the invoices that are past terms and belong to customers who are not disputing anything and are not in trouble — the ones that are simply old because nobody asked. Add up the total.

That number is the budget and the business case for your first automation, and it took you twenty minutes to find. Anything a lead-gen proposal quotes at you will take a quarter to prove and will still be arguable.

If the number is meaningful, write out the seven messages by hand this week and have someone send them manually to the ten oldest invoices. Do not build anything yet. Watch what comes back — the disputes you did not know about, the invoices that never arrived, the ones that pay within a day of being asked. That fortnight of manual sending is what tells you whether to automate at all, and it costs nothing but a person's afternoon.