Start a build →

// handover & upkeep

The part most agencies skip

An automation only you can’t see inside is one you can’t safely keep. Here’s what we hand over, why, and what looking after it involves.

A The handover package, item by item

Accounts in your name

The automation runs in your Microsoft 365 or Google Workspace, your accounting and CRM accounts, and service accounts your business controls. If any third-party service is needed, it’s set up under your business with your billing, or we tell you in writing why it isn’t.

Every instruction, in plain text

The prompts and rules the AI follows are the most important part of the build. You get them all, annotated: “this line exists because invoices from supplier X put the total in the footer.” Without them nobody can safely change the build.

The runbook

A short document for non-technical staff: what it does, what it never does, how to pause it, what a bad output looks like, and who to contact.

Permissions register

Every permission the build uses, why it needs it, and how to remove it. Your IT provider will want this, and so will anyone doing a security review.

Test set

The sample inputs and accepted outputs from the build. When anything changes — a prompt, a model, a supplier’s layout — re-run the set and compare.

Measurement report

The before number, the after number, the running cost, and our honest read on whether it’s worth keeping.

B Why AI builds drift

Ordinary software does the same thing until someone changes it. AI builds are different in three ways worth knowing about:

  1. The model changes underneath. AI providers update and retire models. A newer model is usually better overall but can behave differently on your specific task. The test set is how you catch it.
  2. The inputs change. New suppliers, new form layouts, a new kind of customer request. The build may handle them, or may quietly do worse.
  3. Your rules change. Prices go up, a policy changes, a new approver joins. The build needs to be told.

None of these is dramatic. They show up as a slowly rising correction rate, which is why the most useful maintenance habit is simply watching that number.

C Three ways to maintain it

Keep us on

Monthly review of approvals, corrections and failures; prompt and rule adjustments; re-testing after model updates; and new processes when you’re ready. Priced to the scope of what you run.

Hand it to your IT provider

With the runbook, permissions register and test set, a capable IT provider can monitor and make small changes. We’re happy to brief them at handover.

Run it yourself

For simpler builds, an owner or office manager can watch the correction rate and call for help when it rises. The runbook tells you what to watch.

D Questions to ask any agency about handover

If an agency can’t answer these clearly, ask before you sign — not after.

Want to see a sample runbook outline?

Ask on the scoping call and we’ll walk you through one.

Book 15 minutes