Leaving a full-time AI role to go independent: the checklist
7 minute read. Updated 2026-08-08.
Read your current contract for non-compete and IP clauses before resigning, and save enough to cover 3 to 4 months without income, since a day rate carries no holiday, sick pay or pension. Quote your actual discipline's rate rather than the broad AI figure, settle who determines IR35 status in the first client conversation, never start before a contract is signed, and keep selling through the first 90 days.
Before you hand in your notice
Read your existing contract before you resign, not after. Look for a non-compete clause, an IP assignment clause that reaches beyond your working hours, and the actual notice period, not the one you remember from when you signed it. None of these is unusual to hold. Discovering them after you've told your manager is simply the wrong order to find out.
Build a runway before your first invoice arrives, not after you've handed in notice. A contract day rate carries no holiday pay, no sick pay, no pension contribution, and no payment for the weeks between engagements, so the headline number is not directly comparable to a permanent salary at the same figure. Work out what you need to cover 3 to 4 months without income, because your first client rarely starts the week your notice period ends.
Tell a small number of people you trust that you're going independent before you've announced it publicly. Not because you need permission, but because the first client conversation often starts from a contact you already had, and it starts weeks earlier if people know you're available.
Price yourself against your actual table, not the broad one
Don't quote the broad 'Artificial Intelligence' figure and stop there. Advertised UK contract day rates over the six months to August 2026 put that broad category at a median of £551, but your actual discipline has its own number, and a client who has done their own homework will notice if you quote the wrong one. Data Engineer sits at a median of £500, Machine Learning Engineer at £575, Data Scientist at £600, MLOps at £575, and Generative AI at £550.
If your work sits in governance, risk and compliance, safety and evaluation, product, or training and enablement, there's nothing published for you at all under those titles in the UK advertised market. That's not a hole in the data, it's a fact about how this work actually gets bought: under borrowed titles such as 'Machine Learning Engineer' or plain 'AI'. It means you set your own anchor, and the client has nothing published to check it against, so the burden of justifying the number out loud sits with you.
Keep in mind that these are advertised figures, not agreed ones, and the gap between what's advertised and what's actually paid widens the higher up the range you sit. Build your runway calculation on something closer to the median than the 90th percentile.
The first conversation with a prospective client
This is the conversation people prepare for least and need most. Know your day rate before the client asks for it, not while they're asking. Hesitate on the number and they hear a negotiating position, not a professional one.
Ask early who is making the IR35 determination, and don't treat it as an awkward question to raise on a first call. Since April 2021, medium and large private-sector clients make that determination, not the contractor, and it changes your take-home substantially if the engagement is caught inside it, particularly where deductions run through an umbrella company. Settling this in the first conversation avoids a second conversation three weeks later that opens with 'actually, about your rate'.
Don't agree a start date before there's a signed contract, however much a client pushes for a handshake start while paperwork catches up. And don't discuss your rate until the scope is described in enough detail to know what you're actually pricing. A vague scope agreed alongside an early rate almost always ends with you doing more work than you quoted for.
The admin that isn't optional
Set up professional indemnity insurance before your first client, not after your first invoice. Most clients ask for evidence of it before they'll sign anything, and scrambling to arrange it holds up a start date that's already been agreed on both sides.
Decide your company structure and line up an accountant before you need to send an invoice. Whether you operate through your own limited company or an umbrella depends heavily on how your engagements are likely to be classified under IR35, so this decision follows from the conversation above, not the other way round.
Build an invoice template and a set of payment terms before you send the first one. 30 days is standard. Anything longer should be a term you negotiate deliberately, not one you accept because nobody thought to raise it.
The pipeline mistake
The most common late realisation is treating the first client as proof the model works, and quietly stopping the search for a second one. The first 90 days are still a selling period, whatever work has already landed. A single client who fills your whole diary is a single point of failure, not a success.
Keep a short list of people who'd take your call if the first engagement ended tomorrow. Build that list while your main client is happy and paying, because building it while that client is winding down is a much harder conversation to have.
Things people leave too late
Beyond the admin above, the recurring one is a rate review. People set a day rate on the first call and don't revisit it for a year, even as the evidence for charging more accumulates with every engagement they deliver. Revisit the number after each contract ends, not once a year on a fixed date.
The other is a written record of what was actually delivered. Keep a short account of scope, outcome, and any figure you can defend, for every engagement, starting with the first one. You'll need it for the next pitch, and reconstructing it from memory two years later is far harder than writing three sentences the week the contract ends.
What to do about it
- Read your current contract for non-compete and IP clauses before resigning.
- Save enough runway to cover 3 to 4 months without income, since a day rate has no holiday, sick pay or pension.
- Quote the rate for your actual discipline, not the broad 'Artificial Intelligence' figure.
- Settle who determines your IR35 status in the first conversation, not after you've started.
- Never agree a start date before the contract is signed.
- Keep selling for the first 90 days even after your first contract lands.
Questions people also ask
How much should I save before going independent?
There's no single figure that fits everyone, but plan for at least 3 to 4 months without income, because a day rate has no holiday pay, no sick pay, no pension, and no payment for the gap before your first invoice clears. Your first client rarely starts the week your notice period ends, and the search for that client usually takes longer than people expect while they're still employed and not fully looking.
What rate should I quote for my first contract?
Quote against the advertised figures for your actual discipline, not the broad 'Artificial Intelligence' median. Data Engineer, Machine Learning Engineer, Data Scientist, MLOps and Generative AI all have their own published medians for UK contract day rates, and a client who has checked will notice if you quote the wrong table. If your title is one where nothing is published, such as AI governance or AI risk, expect to justify your number without a market figure to point to.
Who decides if my contract falls inside IR35?
Since April 2021, medium and large private-sector clients make that determination, not the contractor. Ask which way they intend to classify the engagement in your first conversation, not once terms are agreed. If it's caught inside IR35 and deductions run through an umbrella company, your take-home drops substantially compared with the headline day rate, so it changes whether the number on the table actually works for you.
Should I take my first client's rate as the going market rate?
No. Treat your first contract as one data point, not a benchmark. Keep talking to other prospective clients through the first 90 days even after work lands, because a single client filling your whole diary is a risk, not a result. Revisit your rate after each engagement rather than leaving it fixed at whatever you agreed under pressure on the first call.
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.