Agents · on a schedule
A skill waits to be asked. An agent doesn't. These eight run on their own clock against the books of two businesses — one of them hourly, every hour, every day — mostly while I'm doing something else entirely.
Each one has a short written list of things it is allowed to do, and a longer one of things it isn't. Most prepare the work and stop. The design principle is the same everywhere: automate the routine, never the judgment. When the numbers don't tie, or a rule doesn't clearly apply, the agent stops and asks.
Three of them write to the books, and each is narrow by design. One only creates bills from invoices a teammate has already approved. One only books a deposit when the bank ties to the cent. The third creates only the invoices that don't come off an estimate. Each re-reads its own work afterwards and proves what landed matches what it entered.
Union Square Donuts
two agents, nine sitesVendor invoices arrive by email all day. The spend platform reads each one and creates a draft bill — but the draft lands with no general-ledger account and no location on it. Someone had to open every PDF, work out which of nine sites the delivery went to, split the mixed invoices line by line, and key it all in before the bill could even be approved.
Every hour, Peggy picks up the new drafts, finds the original email, reads the attached invoice to see where the order shipped, and codes each line — ingredients, beverages, packaging, cleaning supplies, rent, utilities — then assigns the location from the ship-to address and the house rules, with cost-of-goods purchases rolling to the commissary. She checks for duplicates three ways: the same invoice number, the same vendor, date and amount under a different number, and bills that may already have been paid by card. Then she slots each coded bill into the weekly cash forecast under the right vendor and payment week.
Carl is the second half of something I'd already built once. The cash deposit app fixed the front of the process: every store now closes out in a tool that counts the drawer, reconciles to expected cash, and emails a structured deposit report instead of a photograph of a deposit slip. That was the hard part, and it stopped at my inbox — the reports arrived clean and then sat there waiting for me to book them.
Booking them meant re-adding the numbers, waiting for the deposit to appear in the bank feed, building the entry with the right location, attaching the backup, and matching it to the bank line. Every store, every deposit, every day. The app had removed the counting error and left the keying.
Every morning Carl reads the new deposit emails and re-checks the email's own arithmetic first — the daily amounts have to sum to the expected total, and the stated variance has to equal deposited minus expected. Then he finds the matching deposit in the bank feed, builds the entry so expected cash clears deposits-in-transit and any difference goes to over/short tagged to that store, and confirms the entry sums to the bank amount before posting. Afterwards he attaches the original email as backup, matches the entry to the bank line, and re-reads both to confirm.
So the cash process now runs end to end without me in it. A manager counts a drawer in Somerville, the app reconciles and reports it, Carl books it and ties it to the bank, and the first time I see any of it is a dashboard telling me the booked amounts equal the bank total. The only cash entries I touch now are the ones that didn't tie.
The marketing agency
six agents, five running todayThe same name doing a different job, which is most of what I'd want someone to take from this site. At the donut shop Peggy codes drafts that a platform created. Here there is no platform in front of her: she finds the vendor invoices in my inbox that a teammate approved by reply, enters each one as a bill coded the way that vendor's last bill was coded, adds client ad spend to that client's spend tracker, and posts the bill link to a channel so I can attach the files.
She is the one agent here that writes to the books unattended, so the approval is the whole control: no teammate approval, no bill. New vendors, unclear client splits and invoices that don't foot go to the channel instead of into the ledger. After every bill she checks her own work — the total ties to the invoice to the cent, and the vendor's balance moved by exactly that amount.
Builds the week's payment run — everything past due plus anything falling due in the next seven days — and splits it between the operating account and the ad spend account. That split is the real work: client ad money is not the agency's money, and paying a media bill out of the wrong account is how a liability account quietly stops meaning anything. He adjusts each side for client cash that hasn't been transferred yet, then drafts the partner approval email with the workbook attached.
He leaves the bank balances blank on purpose. The one number I want coming from the bank rather than from the ledger is how much money is actually there, so I fill those two cells in myself before the email goes.
Ad spend is client money moving through the agency's accounts, which makes it the one balance where the people spending it and the people accounting for it have to agree daily rather than monthly. Alice emails the paid media leads the prior day's ad spend payments — Monday's note covers the weekend — then refreshes the month's ad spend liability tab so the reconciliation is never more than a day stale, and emails me only if something needs a look.
She runs at noon rather than first thing, and the reason is the whole design. Finance posts payments in the morning; an agent reporting at eight would be reporting half a day's work as if it were the whole day, and the leads would learn to distrust the number. Waiting until noon costs nothing and makes the number true.
A receipt chased on Monday for last week's charge gets sent back. The same receipt chased at month end gets a shrug, because nobody remembers the lunch. Beavis finds Brex charges over seventy-five dollars with no receipt attached, groups them by cardholder so nobody gets six separate pings, and drafts a friendly Slack note to each person with how to send theirs in.
Expense reimbursements arrive through payroll, which means they land in the books as payroll unless somebody notices and codes them otherwise. Noticing used to happen at close, by which point the reimbursement is three weeks old and the context is gone. This spots the new ones each morning and lists them with a total, so they get coded the same day while it is still obvious what they were.
Runs the invoice review sweep through billing week and republishes the billing review page, so the findings are current whenever anyone looks rather than as of whenever I last ran it by hand. During billing week the sheet changes hourly — invoices get created, PMs answer questions, rows move — and a review page that is six hours old is worse than none, because people act on it.
She also produces some of the invoices rather than only checking them — the ones that don't come off an estimate, where there's no progress-invoicing problem to work around. So the division of labour runs both ways: sometimes I enter and Billinda reviews, sometimes she enters and I review. The checking is identical either way, which is what makes the order not matter.
She is the one agent here not running today. Between billing weeks there is nothing for her to review, so she stays paused rather than burning a run every two hours to confirm nothing changed.
Three of the eight write to the books, and each is boxed into the part of the job whose correctness can be settled by arithmetic — a bill that has to equal its invoice, a deposit that has to equal the bank, an invoice that doesn't depend on an estimate. A fourth codes drafts somebody still has to submit. The rest prepare the work and stop. Everything needing a judgment call still comes to me, which is the point.
Built alongside the donut shop skills and the agency skills.