Xcelerate
Menu
Get in touch
All articles on ai integration

AI integration

An AI model exit plan that survives a provider change

Scope AI model portability for a New Zealand organisation, from exporting prompts and source documents to retesting outputs and keeping staff working.

Two engineers compare model outputs during a software handover.
AI-generated editorial image.

A supplier announces that the model behind your internal drafting tool will retire. The contract allows you to download conversation histories. Can another provider actually run the service from those files? Buy a practicable exit by identifying the assets the next operator needs and rehearsing one end-to-end task on a replacement before the original service disappears.

What needs to travel with the application?

Inventory the input format, prompt versions, permitted tools, data permissions, source documents, review steps and accepted output format. Record who owns each item, how to export it and which parts depend on the current provider. NZ Digital Government’s procurement guidance explicitly includes exit strategy in GenAI evaluation. Treat that strategy as a deliverable with a named owner.

Take an assisted correspondence tool. Its prompts may live in a vendor console while policy text sits in a document library. Review decisions may exist only as feedback buttons. A download of finished letters captures none of the instructions, permissions or examples that reproduce the workflow. Ask another developer to recreate a draft from the listed materials.

Ask where the search index comes from if the application retrieves guidance to write its replies. Some indexes depend on the original provider’s numerical representation of text. The replacement may have to rebuild them from the authorised source collection. Include that time, the source permissions and a way to verify the rebuilt index in the transfer estimate.

What makes a replacement good enough?

Test the job against agreed criteria. Different models will phrase a draft differently. Ask whether the replacement cites the correct policy version, retains the facts a staff member supplied and leaves uncertain details for review. Include a missing attachment and a retired source in the exercises. Measure what a reviewer must change before approving the output.

Check the integration separately. A downstream case system might expect a fixed set of fields or a known date format. Run both providers against the same synthetic cases and show each difference to the application owner. A new model that writes better prose can still interrupt a process if the integration silently drops an unfamiliar field.

How would staff work during the switch?

List a manual route for each essential task. For the letters example, staff could open the approved templates and policy library, prepare a response and record sign-off in the existing case system. Test access for an ordinary service adviser. Time the fallback and agree how the team will manage a temporary queue.

Ask for a witnessed transfer exercise and dated evidence of what was exported, rebuilt and tested. The handover should show where the new operator obtains support, which old credentials can be withdrawn and how copies still held by the outgoing provider are dealt with under the agreement. Keep the final acceptance decision with the service owner. An explicit limit, such as a specialist document type that still needs manual drafting, is something that owner can plan around.

Sources and further reading