estie.net

Every unpaid invoice gets a next step.

I build an AI agent for invoice follow-through. It does not send a reminder just because an invoice looks overdue. It checks payment notices, promised dates, and replies, then sends or holds the next routine reminder. Possible payments, disputes, changed contacts, and anything unclear come to you. It never marks an invoice paid or changes your books.

Most of the setup happens in writing, on your schedule.

Write to me

Does this keep happening?

An invoice goes out. The due date passes. You know you should follow up, but the line between professional and annoying can be hard to judge. So you leave it for later—and later depends on remembering. Some customers get three reminders. Others get none. A customer texts, “I’ll send it Sunday.” By the next Sunday, that promise is buried under forty other messages.

Payments arrive by Zelle or check and get recorded when there’s time. The open-invoice list can include people who already paid. You’d rather skip the follow-up entirely than remind someone who paid two weeks ago.

This is for businesses where customers generally intend to pay and the invoices come from one main system. You want the routine reminders to keep moving while payment questions and bookkeeping stay with you.

Your bookkeeper keeps the books; I don’t reconcile accounts or move money. Collections and disputes stay outside this work, along with cleanup of an old backlog.

What gets built

  1. Plan

    I map what happens after an invoice is sent, including how Zelle or check payments become visible and which customers you already handle yourself. I keep the parts of your current setup that can support those checks and replace only what cannot. You decide when a reminder waits and when it comes to you. We agree on the reminder voice and timing before I build.

  2. Build and test

    I build the agent and tracker, then test it with sample invoices, including the situations that should stop a reminder. With your approval, I send one real message by email and one through the other method while you watch.

  3. Hand over

    After both contact methods work as planned, I give you the agent, tracker, guide, and recording in accounts you control. Then I remove my access.

An invoice needs follow-up. The agent checks the invoice, payment notices, and replies, then sends, waits, stops, and keeps watching. Every routine step starts with your check. After you watch that step work, you can turn it on or off. A possible payment, dispute or question, changed contact, unclear reply, or anything outside that step comes to you. You confirm payment, update the books, and handle the customer decision.

You keep control

Routine follow-through can keep moving.

Nothing runs on its own at first. After you watch one routine step work, you can turn that step on or off. A promised date makes the reminder wait, and a possible payment holds it for you.

Your books stay with you.

Possible payments, disputes, changed contacts, and anything unclear come to you. The agent never marks an invoice paid, changes your books, moves money, or decides a dispute.

Your accounts stay yours.

I use access you invite me into, never a shared password. I remove my access when I hand it over. You keep the finished setup and everything needed to run it. There is no required retainer or subscription to me.

What the sample showed

In the sample build, sending an invoice back to a person put it straight into follow-up again. I changed the timing so it stays with that person for the rest of the day and returns on the next day’s refresh. Then I checked the send-back and the next-day return separately.

A paid invoice should stay out. If the next reminder could be wrong, it should wait and show you what needs deciding.

Investment

$750 for this setup, paid in two $375 installments.

Founding rate for the first three clients across these services.

Write to me
Included:

The price covers one invoice-reminder process using one invoicing system and one place for payment notices. Before you sign, I confirm where replies from email and the other contact method will arrive. Customers hear from it by email and one other method chosen before work begins. You approve the reminder voice and timing. You decide which tested steps may run and get a record of what happened.The price also includes the written guide, recorded walkthrough, one round of changes, and 30 days of fixes after handoff.

Not included:

Reading from another place or connecting another tool is separate work. So is contacting customers another way or giving the agent a new job. The $750 does not cover old-invoice cleanup, bookkeeping, collections, or disputes. It also does not cover moving your data to a new system.

Terms:

$375 is due to begin. The second $375 is due after you approve the plan, before I build.If any part of the setup needs a paid account, I tell you the expected cost before you sign. That cost is separate from the $750, and the account stays yours.

Questions

Will this work with my current setup?

QuickBooks Online and most common invoicing setups work. This may work alongside your current reminder tool or replace its reminders, depending on your setup. Tell me what you use and how else you want to contact customers, and I'll confirm the fit before you commit.

What happens with Zelle or check payments?

That's most of the point. A Zelle or check can sit invisible until someone enters it, which is how a paid customer ends up looking overdue. If a payment notice might belong to the invoice, the reminder holds and comes to you. The agent never marks an invoice paid or writes to your books.

What happens when a customer replies?

The agent reads the reply with the invoice and reminder thread it belongs to. A possible payment, dispute, changed contact, or unclear reply comes to you. After you watch one routine reply step work, you can turn it on. That may mean waiting until a promised date or sending an acknowledgement you approved.

How much of my time does this take?

You answer a few written questions and decide what the agent may read and do. Later, you review the finished setup and walkthrough. Once it is running, you handle payment questions or anything unusual instead of checking every routine reminder.

What customer information does it use?

It uses the customer's contact details and the invoice number, amount, due date, and status. It also uses any payment notice that may match and the relevant reminder thread. It does not need invoice line items or unrelated customer messages. Before I connect anything, I show you what it may read and which outside services will receive that information.

Write to me

A few lines is enough. I’ll tell you whether this setup fits.

By submitting, you agree to the Privacy Policy.