solobuild
Chasing money is the part of solo work nobody warns you about. You finish the project, you send the invoice, and then you spend the next six weeks wondering whether to send a polite nudge or just eat the loss. A Bonsai study covering more than 100,000 freelancers found that 29 percent of freelance invoices get paid at least a day late, and surveys of small operators put the share of people dealing with late payments at least occasionally north of 80 percent. The money usually arrives. It just arrives after you have spent hours of your week thinking about it.
The fix is not a better spreadsheet or more discipline. It is removing yourself from the follow-up loop entirely, so that an unpaid invoice generates its own reminders on a schedule you set once. This article walks through how to do that with tools that mostly cost nothing, starting with the reminders already built into your invoicing software and moving to a custom sequence when the built-in version runs out of room.
Turn on the reminders your invoicing tool already has
Before you build anything, check what you are already paying for. Most invoicing platforms ship with automatic reminders and most solo operators never switch them on, usually because the setting is buried two menus deep in a billing preferences screen.
Stripe Invoicing supports scheduled email reminders that fire before the due date, on the due date, and at intervals after it. You configure the schedule once at the account level and it applies to every invoice you send afterward. Stripe also runs automatic retries on failed card payments, which matters more than people expect, since a meaningful share of overdue invoices are not clients ignoring you but expired cards nobody noticed. Pricing is usage based: Invoicing Starter runs 0.4 percent per paid invoice capped at $2, and you only pay when the invoice actually gets paid.
Zoho Invoice is the strongest free option in this category and it has been free with no paid tier for years. You get unlimited invoices, unlimited customers, recurring invoices, expense and time tracking, a client portal, and automated payment reminders, all at no cost. The catch is that Zoho does not process payments itself, so you connect an outside gateway like Stripe and pay that gateway's processing fee. For a solo consultant sending a handful of invoices a month, that combination is hard to beat on cost.
Wave is the other common free choice. The Starter plan covers unlimited invoices and basic bookkeeping without a subscription, and card processing runs 2.9 percent plus $0.60 per transaction on the free tier. Wave's Pro plan at $19 per month drops the per transaction surcharge on your first batch of payments each month and unlocks more automation around reminders. Whether Pro pays for itself depends almost entirely on your invoice volume.
Whichever one you use, set the same basic schedule: a friendly heads up three days before the due date, a notice on the due date, and follow ups at seven and fourteen days past due. That schedule alone will collect a large chunk of what you are currently chasing by hand, because most late invoices are not disputes. They are invoices sitting in an inbox that somebody forgot to forward to accounts payable.
Where built-in reminders stop being enough
Built-in reminders are good at one job, which is emailing the same person the same message on a fixed cadence. They start to fall down as soon as your follow-up needs to branch, escalate, or reach somewhere other than the client's inbox.
A few specific gaps show up over and over. The reminder always goes to the billing contact on the invoice, even when the person who actually approves payment is your project contact. The tone never changes, so day 45 reads exactly like day 3, which teaches clients that your reminders carry no weight. You get no signal on your own side, meaning nothing lands in your task list or your phone when an invoice crosses the line from late to genuinely overdue. And the reminders keep running on autopilot for a client who called last week and told you the check is already in the mail.
That last one causes real damage. Automated nagging aimed at a client who has already sorted things out makes you look disorganized at exactly the moment you want to look easy to work with. Any follow-up system you build needs a way to pause a specific invoice without switching off the whole thing.
Build the escalation sequence in Make
This is where a general automation tool earns its place. Make connects apps visually, so you drag modules onto a canvas, wire them together, and set conditions on each branch without writing code. The free plan includes 1,000 credits a month and two active scenarios, with paid plans starting around $9 to $12 per month for 10,000 credits and unlimited scenarios. In 2026 Make renamed its billing unit from operations to credits, though the math did not change for standard automations, where one module run still equals one credit.
The invoice follow-up scenario has four parts. A scheduled trigger runs the whole thing once a day, usually early morning. A data step pulls your list of unpaid invoices, either from Stripe directly or from a Google Sheet you keep as your accounts receivable log. A router splits that list into branches based on how many days past due each invoice is. Each branch sends a different message through Gmail or your email tool of choice.
Set the branches to escalate in tone rather than volume. Day 3 past due is a short note assuming the invoice got lost, with the PDF attached again and the payment link right in the body. Day 10 is direct and asks for a specific date, because a question that requires a date in the reply gets answered more often than one that asks whether everything is okay. Day 21 mentions your late fee or your policy on pausing work, stated plainly and without apology. Day 30 stops emailing and instead sends you a task or a text message, since an invoice a month overdue needs a phone call from a human, not another automated email.
Two implementation details matter more than the rest. Give your router a final catch-all branch with no filter on it, so invoices that do not match any of your day ranges surface somewhere instead of vanishing silently. And add a status column to your source data with a value like "hold" that every branch checks before sending. When a client tells you payment is coming Friday, you set that one row to hold and the sequence leaves them alone while the rest keeps running.
Watch your credit usage while you are testing. A daily scenario that touches ten open invoices and runs four modules per invoice will burn through a free plan faster than you would guess, so pull the trigger schedule back to once a day rather than hourly. Invoice follow-up is not a real-time problem and nothing improves when the check runs every fifteen minutes.
Automate the invoice itself, not just the chasing
Reminders solve the back half of the problem. The front half is that invoices go out late, and an invoice sent on the 9th instead of the 1st is a payment that arrives eight days later for reasons that have nothing to do with the client.
Recurring invoices handle this for retainer work. Both Zoho and Stripe will generate and send the same invoice on a schedule with no involvement from you, which means the client sees the same amount arriving on the same day every month. That predictability quietly improves your collection rate, because finance teams process expected invoices faster than surprise ones.
Project work needs a slightly different approach, since the amount changes. The pattern that works well is a Make scenario watching for a trigger you already generate: a project marked complete in Notion, a form submission, a row added to a sheet. That trigger creates a draft invoice with the line items filled in and notifies you to review and send. Keeping a human approval step here is deliberate. Fully automatic invoicing on variable amounts creates the one error you cannot automate your way out of, which is billing a client the wrong number and having to walk it back.
The tools compared
| Tool | Best For | Free Tier | Starting Price |
|---|---|---|---|
| Zoho Invoice | Solo operators who want full invoicing at zero cost | Yes, unlimited invoices and reminders | Free, no paid tier |
| Stripe Invoicing | Anyone already taking card payments through Stripe | No, usage based | 0.4% per paid invoice, capped at $2 |
| Wave | Simple invoicing plus light bookkeeping in one place | Yes, unlimited invoices | Pro at $19/month |
| Make | Custom escalation sequences and cross-app workflows | Yes, 1,000 credits and 2 scenarios | Around $9 to $12/month |
Prices reflect published rates at the time of writing and processing fees are separate from invoicing fees on every platform listed. Check current pricing before committing, since payment processors adjust their rates more often than they announce it.
What to keep doing yourself
Automation works best when it handles the repetitive middle and leaves the ends to you. The first invoice to a new client is worth sending by hand with a short personal note, partly because it sets expectations and partly because it confirms you have the right billing contact before any automated sequence starts firing at the wrong address.
The other manual piece is the phone call at the 30 day mark. Every operator who has collected a genuinely stuck invoice will tell you the same thing, which is that the money moved after a real conversation, not after email number six. Your automation should reliably tell you when that call is due. It should not try to make the call for you.
Terms are worth revisiting too, since no reminder system fixes bad ones. Net 30 on a $500 invoice from a small client is generous to the point of being self-defeating. Shorter terms, deposits on larger projects, and a stated late fee do more for your cash flow than any sequence you build, and the automation simply enforces what your terms already say.
FAQ
How do I automate invoice reminders for free?
Use Zoho Invoice, which includes automated payment reminders on its permanently free plan with no invoice limit, and connect Stripe as the payment gateway so clients can pay by card. If you need reminders that branch or escalate, Make's free plan covers 1,000 credits and two scenarios a month, which is enough for one daily follow-up scenario handling a modest invoice load.
How many payment reminders should I send before following up personally?
Three or four automated emails spread across roughly the first month is the range most solo operators land on, typically at three, ten, and twenty-one days past due. After thirty days, switch to a phone call. Additional emails past that point rarely change the outcome and start to read as noise the client has learned to ignore.
Can Stripe send payment reminders automatically?
Yes. Stripe Invoicing supports scheduled reminder emails before the due date, on the due date, and at set intervals afterward, configured once in your invoicing settings. Stripe also retries failed card charges automatically, which recovers a share of payments that were never really late so much as technically broken.
What is the difference between using Make and just using my invoicing tool's reminders?
Your invoicing tool sends the same message to the same contact on a fixed schedule. Make lets you change the message as the invoice ages, route later reminders to a different person, pause specific invoices without stopping the system, and alert yourself when something needs a call. If your built-in reminders are collecting well enough, you do not need the extra layer.
Where to start
If you are currently chasing invoices by hand, do the cheap thing first. Open your invoicing tool, turn on automatic reminders, and set the schedule at three days before due, on the due date, then seven and fourteen days after. That takes about ten minutes and will handle most of what you are chasing, since the majority of late invoices are simple oversights rather than refusals.
Give that a full billing cycle before you build anything else. If invoices are still sitting past thirty days, or you keep needing to reach a second contact, or you want a real alert when something goes genuinely bad, then add a Make scenario on top with escalating messages and a hold flag. Build it around one client's typical payment behavior first, watch it run for a month, and expand from there.
The goal is not a perfect system. It is getting invoice follow-up out of your head and off your weekly task list, so the only time you think about an unpaid invoice is when your automation tells you to pick up the phone.