Could your team run the automation after the agency leaves

Two honest delivery models

Handover builds. The provider builds the system and hands over the working setup, including code or workflow definitions, deployment notes and access to hosting. Your team, or another provider, can run and change it later. You take on hosting, monitoring and fixes, or you contract someone for them.

Hosted and managed builds. The provider runs the system on infrastructure it manages. You get admin access, reports and data exports, and the provider handles updates, monitoring and fixes for a fee. Leaving means exporting your data and records, then rebuilding or migrating the workflows elsewhere.

Neither is automatically better. A managed build suits a business that does not want to run software. A handover suits one with technical staff or a plan to bring the work in-house. Our note on AI agency versus in-house team covers that choice. Trouble starts when a buyer assumes one model and has signed the other.

Portability is not the same as ownership

Ownership is defined by your agreement, and the details vary: who owns custom code, configurations, prompts, trained components, and the data generated while the system runs. Do not assume. Ask for project-specific terms and have them read by your own adviser.

Portability is the practical question underneath: if the relationship ended next month, could you keep operating? You can test that without a lawyer, and you should.

An illustrative example: an exit drill at a brokerage

An illustrative example, not a real client or agreement: consider a hypothetical real estate brokerage in Dubai. A provider has built a hosted system that tracks tenancy renewals: it reads lease end dates, prepares renewal notices for agent review, collects documents from tenants and landlords by email and a web portal, and updates the brokerage’s CRM.

Six months in, the managing partner asks for an exit drill. Not because anything is wrong, but to see what leaving would involve. The drill covers:

1. Data export. The provider exports all renewal records, documents and status history. The brokerage checks the format: a structured file with stable IDs that match CRM records, plus document files named by renewal ID. One gap: the activity log is only available as a PDF. The brokerage asks for it in a structured format and the provider adds it to the regular export.

2. Documentation. There is a process description and a list of rules (notice periods, document checklist, who approves). There is no description of how the CRM sync handles duplicates. That is added.

3. Accounts and credentials. The email sending account and the portal domain are registered under the provider. The brokerage decides the domain should be in its own name, with the provider given access.

4. Hosting. The system runs on the provider’s infrastructure. The brokerage accepts that leaving means rebuilding the workflows elsewhere, and records an estimate of how long it would take to run renewals by hand in the meantime.

5. Recovery. The team runs one week’s renewals manually from the export to prove they could. It works, slowly.

6. Notice. The agreement’s notice period and transition support are noted, and the brokerage’s adviser reviews them.

None of this is dramatic. But at the end, the managing partner knows exactly what they have bought, what leaving would cost in time, and which two small gaps to close.

An exit-drill checklist

Ask these before signing, and run them once within the first few months:

1. Is this a handover build or a hosted, managed service? Get the answer in writing.

2. What data can we export, in what format, how often, and with which IDs?

3. Can we export documents, logs and history, not just current records?

4. What documentation exists for business rules, integrations and failure handling?

5. Whose name are the domains, email senders, API keys and cloud accounts in?

6. Can our staff get admin access now, not only at exit?

7. What is the notice period, and what transition help is included?

8. Could we run the process by hand for two weeks from the export?

9. What do the terms say about code, configurations and data? Has our adviser read them?

If the provider is uncomfortable with these questions, that is useful information too.

Where SolvTree fits

This maps to our engagement model. Depending on the build, it may be handed over or hosted and managed, and we will tell you which before you sign, along with export formats, documentation and access. Terms are project-specific, and we would rather you test the exit early than discover it late.

Next step: Book a free 30-minute operational audit and we will review the handover requirements for one proposed build with you. The report is yours to keep.