Can an AI agent chase unpaid invoices for me?

Can an AI agent chase unpaid invoices for me?

Short answer: yes. In our published cases, an agent checks your open invoices on a schedule, sends a polite reminder before the due date, a firmer one as the invoice ages, and stops the moment payment lands. You set the ladder and the tone. In several cases a person still approves each send. A four-person agency's average days to payment fell from 28 to 14 in six weeks, per its builders. (case)

How the chasing works, from the cases

• It checks every day and flags what is open. One owner set up an AI employee named Marcus on Grok Bot, connected to Stripe and Xero, with its own email address. It runs daily routines to check for outstanding invoices and follow up, reporting back to him rather than sending on its own. The morning it flagged an unpaid invoice from the previous week, he approved the reminder with one click and the client paid the same day, per his post. (case)
• It follows a reminder ladder you set. Solo consultant Lilach Bullock's fixed sequence sends a reminder 3 days before the due date, one on the due date, a firmer one at 7 days overdue, and flags the invoice to her at 14 days. The sequence stops when payment lands. (case)
• It writes each email with the details filled in. A four-person creative agency's pipeline lists the open invoices in FreshBooks; the agent picks a tier by days overdue and writes a personal email with the client name, amount, and link, sends it through Resend, and logs each send in a sheet. The builders wired it in under 2 hours, per the case. (case)
• It gets firmer, then hands the account to a person. A mechanical contractor's follow-up agent checks receipt at day 7, sends a friendly reminder with a pay link at day 20, notes the due date at day 30 and adjusts tone to the payer's history, escalates and flags the account for a human at day 37, sends a final notice at day 45, and hands over to a person at day 50 with the full log. After three late payments it flags the account and suggests deposit terms. (case)
• You can keep approvals in the loop. Solo operator Michael Shaimerden's agent chases quiet proposals and unpaid invoices, and every external action passes one approval queue; money and mass sends never go on auto-send, per the case. (case)
• It can sit inside a wider set of systems. In one three-employee service business, automatic invoices and staged payment reminders were one of five plain systems the owner set up, on a stack costing under $100 a month in total, per the owner; the result for that whole stack is in the table below, not a figure for the reminders alone. (case)
• The tone can still miss. In the agency case, one email came out too casual, so the team tightened the prompt for the oldest tier. Read the drafts for your oldest invoices before you let the ladder run, per that case's own fix. (case)

What the sources report it achieved

Each outcome below is quoted as its case reports it, attributed to whoever reported it: an owner, a builder, a consultant, or a vendor. None of these figures are our measurements, and they are not independently verified by us.

The same job at a larger firm

This case is a larger company, not a small shop, and we do not present its figures as small-business results. It shows the same chasing job with more context wired in: the agent reads each invoice's payment history, contract terms, emails, and disputes, sorts it into a class, and acts inside finance policy; write-offs, credit memos, and legal steps stay with human approval.

More direct answers: all Answers · Every case that reports a money figure: Money found · The numbers behind all our cases: Stats