Setting up to consult on AI in the UK: the practical checklist
6 minute read. Updated 2026-08-08.
Before taking a first AI contract, get 4 things in place: a company structure that suits how you plan to work, professional indemnity and public liability insurance, a written contract for every engagement, and an accountant who understands IR35. Set them up in that order. This describes mechanics, not tax or legal advice; get a solicitor and an accountant to check your specific position before you sign anything or take money.
Structure first, clients second
Many people take their first AI contract as a sole trader by default, because it needs no paperwork and that's fine for a short first job. If you plan to do this for more than a few months, though, a limited company is the more common route for contractors of this kind. That's mainly because a client's procurement or legal team may require it before they'll pay an invoice, regardless of how good the work is.
Setting one up is a Companies House filing, a company name, a registered address, and a business bank account separate from your personal one. None of that is difficult, but the choice between sole trader and limited company is not a decision to make from a blog post. It depends on your income, your plans, and how much admin you're willing to carry, and an accountant will answer that faster and more accurately than any general guide. Book that conversation before your first invoice goes out, not after.
Insurance before the first invoice
Once you're paid to advise on or build AI systems, you're exposed to claims if the work goes wrong. Professional indemnity insurance covers claims that your advice or work caused a client financial loss, which is the cover most relevant to this kind of work. Public liability covers different ground, mainly physical harm or damage, which matters less if you never set foot on a client site, but some client contracts require it regardless.
Clients increasingly write a minimum sum insured into the contract itself before they'll sign. Get a policy in place before you sign anything that names a figure, because retrofitting cover to match a contract you've already agreed puts you in a weak position with the insurer, not the client. A broker who works regularly with contractors, rather than a general small business insurer, will price a policy that matches how AI consulting work is actually described on a proposal.
A contract for every engagement, no exceptions
Verbal agreements and email chains are not contracts, and clients who hire on that basis are often the ones who dispute scope, payment or ownership later. A short statement of work for every engagement should cover what deliverable will be built, a fixed fee or day rate, and payment terms including when invoices are due and what happens if they're paid late.
In AI work, 2 clauses matter more than in generic consulting: who owns the model, code, prompts and data produced during the engagement, and what your liability is capped at if the model behaves in a way that causes loss. Neither should be left to a generic freelancer template pulled from the internet. Get a solicitor to check the IP and liability wording at least once, then reuse the pattern for future contracts.
Termination terms matter too. How much notice either side must give, and what happens to part-finished deliverables if the contract ends early, should both be written down before you start work, not negotiated after a relationship has already gone wrong.
IR35 changes who decides, not whether you can work
IR35, formally the off-payroll working rules, decides whether an engagement is taxed as employment. Since April 2021, for medium and large private sector clients, the client makes that determination, not you. It affects how you're paid and whether deductions run through an umbrella company, but it does not affect whether you're allowed to take the contract in the first place.
Where an engagement is determined to fall inside IR35, payment through an umbrella company brings deductions that substantially reduce take-home pay. That's worth knowing before you agree a day rate, because a rate that looks attractive outside IR35 may need renegotiating once the determination is known. Ask the client for their determination in writing before you start, not after the first invoice has already gone out.
Accounting admin sits underneath all of this
Invoicing, expense tracking and VAT registration status are ongoing admin, not a one-off setup task. Decide your invoicing cadence, monthly is standard for longer engagements, and get a basic accounting system running before the first contract starts, rather than scrambling to reconstruct records at year end.
Whether you should register for VAT, and when, is a specific calculation based on your turnover and structure, and that's a question for an accountant, not a general guide. What matters mechanically is knowing the answer before you issue your first invoice, because retrofitting VAT onto invoices you've already sent creates unnecessary work for you and your client's accounts team alike.
The order to do it in
Talk to an accountant about structure first. Set up the company, or confirm sole trader status suits you, second. Get insurance in place third, before any contract names a required sum insured. Get a contract template checked by a solicitor fourth, covering IP, liability and termination. Only then take the first client call about money.
Skipping steps to get to a contract faster is the most common mistake in a first year of independent AI consulting. It rarely causes a problem on the first contract. It becomes a problem on the third, when a client's legal team asks a question your paperwork can't answer.
What to do about it
- Get accountant advice on structure before setting up a company, not after.
- Have professional indemnity insurance in place before any contract names a required sum insured.
- Never start work on an email exchange; get a written statement of work signed first.
- Get IP ownership and liability caps checked by a solicitor at least once, then reuse the wording.
- Ask for a client's IR35 determination in writing before you start work.
- Set up invoicing and confirm your VAT registration position before your first invoice.
Questions people also ask
Do I need a limited company to work as an AI contractor in the UK?
Not necessarily. Some contractors work as sole traders, especially for short or part-time engagements. Many clients, though, particularly larger companies with procurement processes, expect to contract with a limited company rather than an individual. Whether sole trader or limited company suits you better depends on your income, your plans and your admin appetite; an accountant can answer that specific to your circumstances faster than any general checklist.
How much professional indemnity insurance do I need?
There is no fixed figure; it depends on the size and risk of the engagements you take. Contracts increasingly state a minimum sum insured the client expects, so check the contract before assuming your existing policy is sufficient. A broker used to contractor cover, rather than a general small business insurer, can size a policy against how AI consulting work is actually described in your contracts.
Does IR35 stop me working as an independent AI contractor?
No. IR35 decides how an engagement is taxed, not whether you can take it. Since April 2021, medium and large private sector clients make that determination rather than the contractor. It affects your pay and whether deductions come through an umbrella company, so get the determination in writing before starting, but it is not a barrier to the work itself.
What should a first AI consulting contract cover?
At minimum: a description of the deliverable, a day rate or fixed fee with payment terms, who owns the code, models, prompts and data produced, a liability cap, and a termination notice period. Get a solicitor to check the IP and liability wording at least once before reusing it as a template; those two clauses cause more disputes in AI work than in generic consulting.
Where the figures come from
Every rate and salary quoted in this article is a median or percentile of figures advertised in UK job postings over the six months to 8 August 2026. They are not rates paid, and the gap widens at the top of a range.
- IT Jobs Watch, UK contract rates, 6 months to 8 August 2026, read 2026-08-08.
- IT Jobs Watch, UK permanent salaries, 6 months to 8 August 2026, read 2026-08-08.