Building an AI finance department for a one-person business

I wanted agents to take on the bookkeeping, invoices, and follow-ups that keep interrupting a solo business. Asking for a summary is only part of that request. I also want the work carried through after I answer a question.

I would start with one finance coordinator: an agent responsible for the recurring job and any narrower tasks it delegates. You give it the outcome and agreed boundaries. It carries the case forward, checks what happened, and returns a precise question when those boundaries no longer cover the situation.

Start with a complete job, not a finance inbox

Consider a common request: send an agreed invoice, follow up if it remains unpaid, and update the picture once money arrives.

Before the work begins, the owner gives it a small operating frame: approved customer terms, the records it may use, where payments and commitments are visible, routine messages it may send, and the circumstances that require a return to the owner. Those facts let an agent distinguish ordinary collection work from a change in the commercial relationship.

Now imagine a customer pays part of an invoice. The coordinator compares the payment reference, amount, open balance, and prior conversation. With tools connected for these jobs, and a clear match within its authority, it can record the partial payment and check the invoice again to confirm the remaining balance. That result goes into the short-term cash view and the follow-up task, so the next message does not ask for money already received. If an update fails, the coordinator reports which part remains unfinished.

If two open invoices could fit the same payment, the coordinator should not choose whichever record is easiest to close. It returns the case with the relevant options and asks which invoice the payment belongs to. Once you answer, it resumes from that answer rather than making you reconstruct the situation in a second conversation.

Here, agentic work means following the case through: using connected inputs, choosing the next permitted step, checking the result, and preserving an open question when the work cannot continue.

The coordinator owns the case; specialists can be behind it

In this setup, one coordinator owns the owner-facing case and calls on narrower help as needed:

• A receipt task can retain the original document, extract available details, check a likely duplicate, and return the missing business-purpose question.
• A bookkeeping task can assemble period inputs and isolate transactions that do not fit the existing information.
• An invoice task can prepare or send an invoice only from agreed terms and the authority you gave it.
• A collection task can keep payment, invoice, customer context, and follow-up state together.
• A cashflow task can refresh a near-term view from known expected receipts and commitments while leaving uncertainty visible.
• A tax-preparation task can organize records and unanswered questions for qualified review; it does not interpret tax treatment, file a return, or replace professional advice.

The owner should experience this as one conversation: “What needs attention this week?” The coordinator brings the work back together. Otherwise the entrepreneur becomes the integration layer, pasting context between a receipt agent, an invoice agent, and a cashflow agent.

Decide what the agent may finish without you

A better boundary than approving every keystroke is explicit permission. An owner might authorize the coordinator to save an original receipt, prepare a routine invoice from fixed terms, send a previously approved reminder, record an unambiguous payment, or update a cash view from existing inputs. The owner keeps decisions that change price, scope, customer commitments, disputed payments, ambiguous business purpose, or spending priorities. A qualified professional keeps professional accounting, tax, and legal judgment.

Different businesses will choose different boundaries. The important thing is that the agent can see the boundary while it has the case in hand. “Ask me when something feels unusual” is not a reliable instruction. “Ask before changing agreed terms, contacting a customer after a dispute, or assigning a payment with more than one plausible invoice” gives it a usable stopping rule.

Give it a real starting point and a way to continue

An agent cannot take over recurring work from a paragraph of wishes. It needs a configured way to begin: an owner-started weekly run, a receipt delivered through the chosen intake channel, or an enabled scheduled check. It also needs a designated place to read current records and leave the result for the next step.

Start with one repetitive path, the information it may consult, the actions it may take, and the questions that must come back to you. Test ordinary and awkward cases: a blurred receipt, changed client agreement, partial payment, or uncertain commitment. The test is whether you can see what happened, correct it when needed, and let the next run continue without a scavenger hunt.

The first finance coordinator may handle only invoice follow-up or receipt intake. After resolving an unclear case, return in a fresh session and ask what remains open. Check whether the agent retrieves your decision, shows the confirmed result, and continues the permitted work without asking you to explain the case again.