AI Handover

Who this is for

Businesses that already have an AI workflow but depend on one individual or supplier to understand it.

What is included

• Review of one accessible workflow using up to two tools.

• An inventory of accounts, permissions, prompts and running costs.

• Editable operating and troubleshooting notes.

• Export of available configuration and a record of platform dependencies.

• A 60-minute handover with one internal owner, including an observed operating exercise.

• A checklist for testing changes and moving to another supplier.

How it works

We first check that the workflow is accessible and fits the scope. You arrange authorised access and nominate an owner. Target: five working days after the required information is available.

What you take away

A practical handover pack and an internal owner who has practised using the workflow. Any remaining gaps or restrictions are documented.

Price

£395 one-off for the defined handover. 50% at booking and 50% after the walkthrough, before final delivery.

When you need a different scope

Migration, redevelopment and recovery of inaccessible accounts are separate work. Exports depend on platform capabilities and licences. Handover is already included in new Labs builds and pilots, so this service is for an existing system.

Ownership, costs and next step

Start with a short fit call. We confirm the scope, total price, access needed and delivery dates in writing before work begins. Prices are in GBP, excluding VAT where applicable. Software subscriptions, hosting and AI usage are separate and disclosed before you commit. A Hub subscription is only needed if it is the platform you choose. Ongoing support is optional.

You keep the agreed deliverables and editable documentation. Bespoke code transfers after payment, subject to third-party licences; existing platforms remain licensed. We explain any limitations on export or moving providers. Results depend on the process and how the tools are used; no particular savings are guaranteed.

Before we begin

Choose the internal owner who will use the handover pack and take part in the operating exercise. Gather the account names, existing notes and any prompt or configuration material you are authorised to share. Confirm that the workflow is accessible; this service cannot recover an account you cannot legitimately access.

Describe the everyday questions the owner needs to answer. Where does a request begin? Which tool contains the editable prompt? Who receives a failure notification? What costs continue each month? Listing those questions helps distinguish a knowledge gap from a change that would require rebuilding or migrating the workflow.

An illustrative walkthrough

Imagine an existing workflow that summarises approved material before a colleague checks it. In this illustrative example, the internal owner knows the output but is unsure which account runs the task or where its instructions are stored. An inventory and operating notes make those dependencies visible.

During the observed exercise, the owner can follow the agreed operating steps and explain the checks they perform. Where a platform does not expose a useful export or a licence restricts portability, that limitation needs to stay in the handover record. Documentation should make the boundary clear rather than imply that every system can be moved unchanged.

Using the result

Keep the editable notes with the workflow's owner and update them when an account, prompt or operating step changes. The checklist gives the team a starting point for testing a change or briefing another supplier. A useful handover pack should help someone locate the configuration and understand the process without relying on the original author being available.

Use the documented gaps to decide whether you need a separate migration, redevelopment or support scope. The handover explains the accessible system; it does not quietly turn into a replacement build. New Labs builds already include a normal handover, so this standalone service is intended for an existing workflow.