Notes / Workers
Who owns your AI Worker—and what can you take with you?
Understand what stays with your business, what belongs to the provider, and what another team would need to continue the work.
By Edu Rigonato and Rich Hill III. Published Oct 28, 2026. 10 min read.
Before an AI Worker can help with renewals, intake or follow-ups, your team has to explain how the work happens. Which information matters? Who checks an exception? When is a task finished? That takes time, and it turns knowledge held by individual people into something the business can use.
If you later change providers, you want to keep that investment.
The useful answer to “Who owns the Worker?” starts with your agreement: it should identify the business materials you retain, how you receive them in a usable form, and which software or services a replacement needs. Keeping your instructions and workflows does not automatically give you the provider’s software or a Worker that runs unchanged elsewhere.
You do not need to understand every technical component to assess the offer. You need a clear answer to a practical question: If we leave, what will we receive, and what would our next team have to do?
What belongs to your business?
Ask the provider to describe the materials your business can retain and use. “Your data is yours” is a starting point, but it leaves out much of the work involved in setting up an AI service.
Consider an illustrative insurance renewal process. Your agency supplies policy records, explains when to follow up, identifies missing documents and decides which issues an account manager must review. Over time, the setup may also capture instructions about unusual cases and corrections your team has made.
Those materials would be useful to the next team even if it chose different software. An ownership discussion should cover:
Questions about AI Worker ownership
Can I keep using the outputs after ending the service?
Check the rights in your agreement and arrange access to the outputs you need before the service ends. The answer may also depend on third-party material used in those outputs. Keeping a report or draft is a separate question from keeping access to the software that created it.
Should the provider give us all its source code?
Ask what your business needs to retain and reuse, then identify any software deliverables and their licenses. Your business rules may be preserved through agreed code, configuration or documentation while the provider retains reusable software. The proposal should make that distinction clear before you commit.
Do we need to own the hosting account?
Account control is one part of the arrangement. A provider can operate hosting as part of a managed service, but you should know what access you have, what materials can be returned and what would need replacing if you leave. An account in your name does not establish that every piece of software in it belongs to you.
How much will it cost to switch providers?
There is no reliable amount to infer from an ownership promise. Ask the current provider about handover assistance and fees, then have the next team assess the materials, dependencies and testing involved. Request an estimate based on that scope before choosing a transition date.
Evidence note: This article draws on provider terms, software export and migration documentation, and HHS guidance. Product examples explain specific tools, not every managed AI service. Healthcare guidance applies to the relevant relationships and agreements. Taurist’s stated ownership approach does not establish that every deployment can be transferred or run independently. Sources were reviewed on October 28, 2026.
Explore AI for your business