- Keep your accounting, booking, till and ticketing software as the official record. The agent reads from it and writes only through an approval.
- Build in three layers: connections to your systems, workflow modules on top, and one assistant across them.
- Give the agent three jobs: retrieve, check and route.
- Set access by role, log every question and answer, and keep personal data need-to-know.
- Start read-only, then switch on one workflow a person already checks. Writes come last.
- Before you sign, settle who owns the code, the data and the content if you stop.
Most businesses already run on five or six systems: accounts, bookings, a till, a project tracker, a staff rota, a shared inbox. A new agent has to work with all of them from day one. The design that holds up is simple. The existing systems stay the official record, and the agent adds a layer on top.
Why replacing everything rarely works
Replacing core software means a migration, retraining and a cut-over date. Each is a project, and the agent's value waits behind all three. The software you already pay for also holds years of records that a new system starts without. An agent that works on top of what you have can show results within weeks, and switching it off undoes nothing.
1. Leave the system of record alone
Official figures stay where they are: the ledger, the booking engine, the till, the ticket history. The agent reads from them, and writes to them only through an approval. If the agent is switched off tomorrow, nothing needs migrating back.
2. Build in three layers
- Shared data. Connections to the systems the business already runs on: accounting, bookings, the till, email, the staff rota and website analytics. Each connection stays read-only until a workflow needs to write.
- Workflow modules. One module per job, such as invoicing, staff scheduling, the sales pipeline or capacity planning. Each is scoped, delivered and paid for separately.
- One assistant across everything. A single place to ask questions, get alerts before problems grow, and have actions drafted for a person to approve.
Then map each part of the business to the layer that covers it. For a service business with bookings, a till and a staff rota, the map looks like this:
| Business area | Stays in | Covered by |
|---|---|---|
| Bookings | Your booking system | A connection that feeds every module |
| Finance and invoicing | Your accounting software | Invoicing module |
| On-site sales | Your till | Invoicing module: extras flow into the final invoice |
| Staff scheduling | Your rota | Scheduling module |
| Enquiries and events | Your shared inbox | Sales pipeline module |
| Capacity | Your booking system | Capacity module |
Deliver the modules in the order the business feels the pain. Invoicing usually goes first, because a person already checks every invoice and the result is easy to measure.
3. Three jobs an agent does on top
Retrieve
One searchable record of orders, invoices, delivery notes, bookings and approvals. Ask in plain language, and every answer links to the original document. "Show me the approval, the delivery record and the invoice for this order" should take one message, not a search through five inboxes.
Check
Compare documents before money moves or a change goes out. Three-way matching compares the purchase order, the delivery record and the supplier invoice before payment. The agent flags missing documents, quantity differences and invoices that look like duplicates.
The same pattern works in a service business. A booking, the extras sold on the day and the deposit already paid should add up to one correct final invoice. Where work is claimed in stages, the agent can compare each claim with the agreed scope and the records available, and flag the exceptions for review.
Route
Each discrepancy goes to a named reviewer, with its evidence attached, so the decision takes one screen. The approval, the exception and the decision are recorded, so the audit trail exists without anyone writing it up afterwards.
4. What one assistant across your systems can answer
Once bookings, finance, the rota and the inbox are connected, questions that used to take a spreadsheet and an afternoon take one message:
- Which bookings haven't been invoiced, or haven't been paid?
- How much do extras add per booking, by product?
- Are direct bookings worth more than marketplace bookings after commission?
- Which product earned the most last quarter, after staff, supplies and commission?
- What does an event really earn once the back-and-forth emails are counted?
- Who is working too many weekends, and whose certification expires before the busy season?
- Which slots sell out first, and is anyone free to add capacity?
The useful answers combine two or more systems, which no single piece of software can do on its own. A common finding: the product with the best margin on paper loses much of it to the emails and admin around planning. That only shows up when bookings, finance and the inbox are read together.
The assistant can also send alerts nobody asked for, such as "next month is behind last year, and here is where".
5. Access follows roles
Everyone asks the same assistant. Each person sees only what their role allows:
| Role | What the assistant answers for them |
|---|---|
| Owners and managers | Everything: finance, bookings, scheduling, sales and email |
| Finance | Invoices, payments and till sales |
| Operations | The rota, timesheets and the day's bookings |
| Sales and events | Enquiries, quotes and the events inbox |
| Field staff | Their own shifts, hours and availability |
- The owners decide who gets which role, and can change it at any time.
- Every question and answer is logged, so you can always see who asked what.
- Personal data, such as staff hours or customer details, is visible only to the roles that need it.
6. Roll out read-only first
Start with the assistant answering questions, with no ability to change anything. Then switch on one workflow where the agent drafts and a person approves, such as invoices. Writes to your systems come last, and only through that approval step. Each stage gives the team a reason to trust the next one.
7. What it looks like in production
Cuvama builds software. ZeroLayer built a custom agent inside its existing Jira workflow. It breaks each story into well-sized tasks and hands each task to a coding agent for a first draft. Developers review and ship. No new tools were introduced and the workflow did not change. Cuvama estimates it now ships roughly 40% faster end to end, and states that figure as its own estimate. See the ProductPlease case file.
Chad works the same way on a website. It prepares the change, the change arrives as a preview link, and it goes live only when a person approves it.
8. Settle ownership before you start
Ask three questions before signing: who owns the code, who owns the data and content, and what happens if the vendor stops trading. A good answer has three parts. Your data and content stay yours throughout. If you stop, the connections are switched off and everything is handed back. Either you receive the source code, or there is a written continuity arrangement.
9. Questions to ask any vendor
- Which of our systems does the agent read from, and which can it write to?
- Which actions can it prepare, and who approves each one?
- Where is each approval logged, and can we export the log?
- Can we see who asked what, by role?
- Which module comes first, and how will you measure it?
- What happens to our data and records if we stop?
- Who owns the code, and what happens if you stop trading?
For how to structure the first module as a pilot, see how to scope an AI agent pilot.