Guide · Custom builds

Your systems stay the record.

An agent that replaces your accounting, booking or ticketing software is a migration project. One that reads from them, checks against them and drafts for approval is a pilot you can stop.

In short
  • 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

  1. 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.
  2. 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.
  3. 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 areaStays inCovered by
BookingsYour booking systemA connection that feeds every module
Finance and invoicingYour accounting softwareInvoicing module
On-site salesYour tillInvoicing module: extras flow into the final invoice
Staff schedulingYour rotaScheduling module
Enquiries and eventsYour shared inboxSales pipeline module
CapacityYour booking systemCapacity 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:

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:

RoleWhat the assistant answers for them
Owners and managersEverything: finance, bookings, scheduling, sales and email
FinanceInvoices, payments and till sales
OperationsThe rota, timesheets and the day's bookings
Sales and eventsEnquiries, quotes and the events inbox
Field staffTheir own shifts, hours and availability

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

For how to structure the first module as a pilot, see how to scope an AI agent pilot.

ZeroLayer builds agents that sit on your systems. Your software stays the record. The agent retrieves, checks and routes, and a person approves.
Book a call
FAQ

Common questions

Does an AI agent need to replace our existing software?

No. A well-scoped agent works alongside the systems you already use. They stay the official record, and the agent adds retrieval, checking and approval routing.

What is three-way matching?

Comparing the purchase order, the delivery record and the supplier invoice before payment, so missing documents, quantity differences and duplicate invoices are caught before money moves.

What does human approval mean in practice?

The agent prepares an action, such as a reply, a payment check or a website change, and a named person approves it before it takes effect. The approval is logged.

Who can see what an agent knows?

Access is set by role, the owners can change it at any time, and every question and answer is logged.

Planning an agent build?