Introduce a client, earn up to 20% of our fees for two years. No cap, on every matter they instruct.The referral programme →
BVI · Agencies and unregulated services

A BVI company for an AI automation agency.

Building agents, chatbots and workflow automations for clients is unregulated work, and a BVI Business Company is a perfectly ordinary wrapper for it. The difficulty is not the licence, because there is none. It is ownership of what you build, responsibility for the data you touch, the terms of the model providers underneath you, and who carries the loss when a model gets something wrong.

No licence required

Unregulated work, with one caveat.

The BVI Financial Services Commission licenses businesses that handle other people's money or assets: investment business under SIBA, virtual asset services under the VASP Act 2022, banking, insurance, trust and company services, and money services under the Financing and Money Services Act. Writing software, configuring automations and delivering AI systems to commercial clients appears nowhere on that list. A BVI Business Company can carry on the work from incorporation, with no application, no regulatory capital and no waiting period, subject only to the standard obligations: a licensed registered agent, a registered office, beneficial ownership filed through the VIRRGIN portal, an annual Economic Substance notification, and a financial return filed privately with the agent within nine months of year end. Year-one cost is USD 8,500 all-in, from USD 2,750 a year thereafter, and incorporation runs 5 to 7 working days. The full boundary is in what a BVI company can do without a licence.

The caveat is worth stating precisely, because it is the one place AI agencies drift into regulated territory without noticing. Licensing follows the activity, not the technology. Selling a client a workflow that summarises documents is unregulated. Operating, on your own account and for reward, a service that gives personalised investment recommendations to end users, takes custody of client funds or crypto, or executes transactions on other people's behalf is regulated activity in most serious jurisdictions, and building it in Python does not change that. If a prospective build involves anyone's money moving or anyone's investment decision being made, take the boundary question seriously first; our guides to BVI investment business licensing and BVI fund types mark where the line sits. For everything else, which is the overwhelming majority of automation work, you are building an ordinary services business and the questions that follow are contractual.

Which is also the honest answer to why you should incorporate at all. Not tax. Ring-fencing. An AI agency connects to a client's CRM, email, billing system and customer records, and pushes actions into production on the client's behalf. When an automation misfires, sends the wrong thing to the wrong list, or acts on a hallucinated value, the claim goes to the party that built it. A sole trader answers that claim with everything they own. A company answers it with the company, provided the contracting party is the company, the client agreement caps liability, and the founder has not personally guaranteed the work. That single structural point is worth more to most founders than every offshore tax argument put together. Comparable structures across other trades are catalogued in 120 uses of a BVI company.

The client agreement

Who owns the prompts, and who carries the error.

Ownership is the first argument and the one most agencies lose because nobody wrote anything down. A build is rarely one artefact: it is prompt libraries, orchestration logic, connectors and glue code, evaluation sets, documentation, and sometimes a model fine-tuned on the client's own data. The workable default, and the one we draft unless a client instructs otherwise, is client owns the deliverable and agency owns the toolkit. The client receives ownership or a perpetual, irrevocable licence of the automation built for its business, of anything derived from its data, and of any fine-tune trained on its records. The agency retains its reusable framework: generic prompt patterns, internal libraries, connectors, templates and accumulated know-how, licensed into the deliverable so the client can keep using it. Both sides get what they actually care about, and neither is trapped. Where the agency's own libraries become genuinely valuable, holding them in a separate entity is the next step, covered in our guide to a BVI company for IP holding.

Data is the second. An automation agency is almost always a processor of someone else's personal data, and incorporating offshore does not change that analysis by one word. Where a client is established in the EU or the UK, or is serving customers there, the agency needs a data processing agreement containing the clauses those regimes require, a lawful transfer mechanism such as standard contractual clauses for moving data outside the EEA or UK, defined security measures, a sub-processor list that honestly names the model providers and hosting you pass data through, assistance obligations for data subject requests, breach notification timelines, and deletion or return on termination. Two practical habits matter more than the paperwork: do not send client personal data to a consumer-grade chat interface, and use provider tiers with zero-retention or no-training terms where the client data is sensitive. Getting this wrong is the fastest way for a well-paid enterprise build to become an incident.

The third is the stack you sit on. Every model provider has terms that constrain what you may build, whether you may resell access, whether you may use output to train competing models, and what you must disclose to end users. Those terms change, sometimes quickly. Read the current version of each provider you depend on, and make the client agreement consistent with them rather than promising something the provider forbids. Commercially, the cleanest pattern is the client holding its own provider account with the agency building on it, which puts usage cost where it belongs and removes the resale question entirely. The alternative, charging for the automation as a managed service with usage billed transparently at cost or at a stated margin, works too, provided the provider's terms allow it and the client knows what it is paying for.

ClauseWhat it must sayWhy it matters
IP ownership splitClient owns the deliverable and data-derived outputs, agency owns reusable toolkit and licenses it inThe single most common dispute at renewal or on exit
Data processing agreementProcessor duties, sub-processor list naming model providers, transfer clauses, security, deletion on exitRequired for EU and UK clients, and expected by enterprise procurement everywhere
Model provider pass-throughClient acknowledges the underlying provider terms, usage billing basis, right to substitute a providerKeeps the agency from promising what the provider prohibits
Output disclaimerAI output is probabilistic, human review required, no professional, legal, medical or financial advice givenRemoves the implied warranty of accuracy a client will otherwise assume
Liability cap and exclusionsCap at fees paid in a defined period, exclude indirect and consequential loss, carve out confidentiality and IP breachesTurns an unbounded automation failure into a quantified commercial risk
Acceptance and change controlDefined acceptance tests, written change requests, hourly or fixed rates for scope beyond the statement of workStops open-ended rebuilds being absorbed at the agency's cost
Contractor flow-downEvery developer assigns IP and accepts the same confidentiality and data dutiesWithout it the agency cannot deliver the ownership it has promised

ArxSetup drafts this set alongside incorporation. Professional fees are fixed and quoted in writing. Figures current September 2026.

Money and limits

Paying developers, getting paid, paying tax.

Automation agencies are contractor businesses: a founder, two or three builders, and specialists pulled in per project across several time zones. Paying them from a BVI company is straightforward through a multi-currency account, and the discipline is the boring kind. Every contractor has a signed agreement with an IP assignment, a confidentiality clause and the data terms flowed down from your client contracts. Every payment has an invoice behind it. Every payment goes to the person named in the agreement. That file is what makes an enterprise client's vendor review pass, and what makes an eventual sale of the agency a valuation exercise rather than an archaeology project.

On receiving money, be realistic. Stripe and PayPal do not onboard BVI incorporated merchants, and nobody has a legitimate workaround. For project and retainer work this is a minor constraint, because enterprise clients pay invoices by transfer anyway, and Airwallex or Currenxie will provide local receiving details in several currencies for a documented BVI service company, with private banks for larger balances. If part of your model is self-serve, a subscription to a hosted automation or a template marketplace, that part needs card acceptance and the honest answer is a merchant-of-record platform contracting as the seller or a UAE or Singapore operating company beneath the BVI parent; the architecture choice is set out in our BVI SaaS company guide. Bank onboarding realities, timelines and refusal reasons are in the BVI company bank account guide.

And the part no offshore video will tell you: the company's 0% rate is not your rate. Salary and dividends you draw are taxable where you are resident. Controlled foreign company rules and place-of-effective-management tests can attribute the company's profits to you personally if you and the decision-making sit in one country, which for a founder-led agency is the normal case rather than the exception. US persons carry their own filing obligations wherever they live, and UK and EU residents should get home-country advice before incorporating. CRS and FATCA reporting reaches your home tax authority through the account bank, so nothing here is hidden and nothing here is meant to be. UAE residents have a specific analysis covering Corporate Tax at 9% above AED 375,000, the free-zone qualifying income tests and place of effective management, in BVI companies for UAE residents. If you live in Dubai and your clients are UAE businesses, an IFZA licence from about USD 10,120 a year is usually the right answer and a BVI company is not, a sorting exercise we run in full in our guide to BVI companies for consultants. Agencies whose work sits closer to content and paid media should read the social media agency guide, and those delivering custom builds with a standing team should read the software development company guide on permanent establishment risk.

Engagement

How ArxSetup runs the file.

These files are partner-led and quoted as a fixed fee in writing after a short scoping call, which includes an honest test of whether BVI or a UAE free-zone licence fits your client base. Where BVI is right, we incorporate directly with the FSC through licensed registered-agent partners in 5 to 7 working days, prepare the memorandum and articles and the share structure, draft the master services agreement, statement of work template, data processing agreement and contractor IP assignment set, complete the beneficial ownership and Economic Substance filings, and introduce you to at least two banking or EMI partners with a prepared KYC pack. Year-1 all-in from USD 4,750, and from USD 2,750 a year thereafter.

Reviewed by the ArxSetup editorial team

Reviewed by qualified counsel within ArxSetup and our affiliated practices, Neo Legal (UAE) and Cornwalls (Australia). Figures verified against primary regulator sources. Last reviewed: September 2026. DDA Licence 107229 · Dubai Media City. How we review →

Frequently asked

Common questions.

The questions clients ask most before committing. Current to 2026, reviewed by counsel.

Does an AI automation agency need a BVI licence?

No. The BVI licenses businesses that handle other people's money or assets, such as investment business, virtual asset services, banking, insurance and trust services. Building chatbots, agents and workflow automations for commercial clients is unregulated, so a BVI Business Company can trade from incorporation. The exception is the work you automate: if the deliverable itself is regulated activity, such as giving personalised investment advice or moving client funds, licensing follows the activity and not the software.

Who owns the prompts, workflows and fine-tuned models?

Whoever the contract says, which is why the contract must say. The workable default is client owns the deliverable and the agency owns the toolkit: the client receives ownership or a perpetual licence of the automation built for its business and of anything derived from its data, and the agency keeps its reusable prompt libraries, framework code, connectors and internal templates, with a licence to use them in the deliverable. Fine-tuned models trained on client data should follow the client. Put this in writing before the first build, not at renewal.

Do I have GDPR obligations if my clients are in the EU?

Usually yes, and being incorporated in the BVI does not remove them. Where you process personal data on behalf of an EU or UK client you are acting as a processor, which requires a data processing agreement with the required clauses, a transfer mechanism such as standard contractual clauses for sending data outside the EEA or UK, security obligations, sub-processor disclosure covering the model providers you pass data to, and breach notification to the client. Agree the terms before data starts flowing.

Can I resell API access to the underlying AI models?

Only within the provider's terms, and they differ by provider and change often. Some permit building products on the API while restricting bare resale of raw access, output used to train competing models, or passing your key to a client. The safer commercial model is for the client to hold its own provider account and for the agency to build on it, or for the agency to charge for the automation as a service with usage billed transparently. Read the current terms of each provider you rely on and reflect them in the client agreement.

What if the AI output is wrong and the client loses money?

That is the exposure the whole structure exists to contain. Incorporate so the contracting party is the company and not you personally, then cap liability in the services agreement at fees paid over a defined period, exclude indirect and consequential loss, state plainly that AI output is probabilistic and requires human review, disclaim any professional, legal, medical or financial advice, and require the client to keep a human in the loop for consequential decisions. Professional indemnity cover is worth pricing once contract values pass a meaningful level.

This page is general information, reviewed September 2026, not legal, tax or immigration advice, and it does not create a client relationship. Advice specific to your circumstances is provided only under a signed engagement letter. Government fees are set by the relevant authority and may change without notice. Where local registered agents are required, we coordinate with licensed partners and disclose their role in writing.