Hire an AI Developer or Use an Agency? The UK Cost

Advertised UK salaries for AI engineers jumped by £10,000 in a year. If you want to hire an AI developer this autumn, ITJobsWatch puts the median advertised salary at £87,500 for the six months to 17 October 2026, across 498 quoted salaries. The same window in 2025 was £77,500. And the advert figure is only the start of what the role costs you.

Below we add the gov.uk employer rates for 2026/27 line by line, set the result against a freelancer, an agency project and a fractional team, then look at the costs that never reach payroll and the cases where hiring is still the better move.

What one UK AI engineer really costs in 2026/27

Start with the salary and add what the employer pays on top. For 2026/27, employer Class 1 National Insurance is 15% (category A) on earnings above a secondary threshold of £5,000 a year, collected through your PAYE bill. Auto-enrolment adds a minimum employer pension contribution of 3%, and gov.uk says contributions are based on earnings between £6,240 and £50,270 a year. The 3% is a minimum, so treat it as a floor.

If you use a recruiter, Agency Central says standard UK fees run between 15% and 20% of first-year salary, and up to 30% for hard-to-fill roles. Get any rebate terms in writing before the candidate starts.

Tooling is the awkward line. We priced one seat: GitHub Copilot Business is $19 USD per seat per month, so $228 a year. That's a dollar price and we haven't sourced an exchange rate, so the model lists it separately and leaves it out of the sterling total. At that size it won't change the decision.

{
  "role": "AI engineer, UK, median advertised salary",
  "salary_gbp": 87500,
  "employer_ni": {
    "rate": 0.15,
    "secondary_threshold_gbp": 5000,
    "calc": "(87500 - 5000) * 0.15",
    "gbp": 12375.00
  },
  "pension_employer_minimum": {
    "rate": 0.03,
    "qualifying_band_gbp": [6240, 50270],
    "calc": "(50270 - 6240) * 0.03",
    "gbp": 1320.90
  },
  "recurring_annual_gbp": {
    "calc": "87500 + 12375 + 1320.90",
    "gbp": 101195.90,
    "monthly_gbp": "101195.90 / 12 = 8433"
  },
  "tooling_excluded_from_gbp_total": {
    "item": "GitHub Copilot Business, one seat",
    "calc": "19 * 12",
    "usd_per_year": 228,
    "note": "USD list price; not converted, not in recurring_annual_gbp"
  },
  "recruiter_fee_one_off_gbp": {
    "at_15pct": "87500 * 0.15 = 13125",
    "at_20pct": "87500 * 0.20 = 17500"
  },
  "year_one_with_20pct_fee_gbp": "101195.90 + 17500 = 118695.90",
  "fractional_team_comparison": {
    "day_rate_gbp": 600,
    "vat": "excluded",
    "people": "3-4",
    "days_per_week": 3,
    "weekly_gbp": "600 * 3 = 1800",
    "annual_gbp": "52 * 1800 = 93600",
    "monthly_gbp": "93600 / 12 = 7800"
  },
  "not_counted": ["laptop", "office", "benefits", "training", "LLM API usage"]
}

The last block in the JSON is our fractional AI team at its typical three days a week. Our prices exclude VAT.

That's not a like-for-like swap. One employee works five days and the team works three, so we're not claiming the output is equal. The decision turns on things other than price.

The four to six months nobody puts in the spreadsheet

The JSON above has no line for waiting. La Fosse, a UK tech recruiter, says in its H2 2026 guide that four to six months from open requirement to start date "is now normal, before notice periods". Take that with the caution you'd apply to any recruiter talking about how hard recruiting is. The same guide puts the typical band at £80,000 to £150,000 from mid-level to principal, which is why we used the ITJobsWatch median instead of a recruiter range.

Six months of search is six months of the problem you wanted solved still sitting there. If the job was chasing leads that go cold overnight, or rekeying invoices into Xero, the delay costs you something real even though it never shows up as a payroll line.

Then there's key-person risk. With one engineer, every design decision, credential, prompt and workaround lives in one head. When they hand in their notice, you're back at the start of the hiring clock with a system nobody else understands. A builder on r/AI_Agents who said they had built more than 25 agents replied to a sceptical commenter: "The value isn't the prompt it's the implementation, reliability, and ongoing ownership."

One hire has to be architect and builder

Designing an AI system and building it are different jobs. Someone has to decide what the agent should do, which systems it reads and writes, and what happens when it gets something wrong; someone else, or the same person on a different day, has to write and test the code. Our view is that an SME hiring its first AI developer usually needs both, and one person rarely covers both well. A founder on r/ClaudeCode asking how others hire AI engineers said the ones they had worked with were "very good at repeatable tasks or coding stuff rather than seeing the big picture". Replies pointed out that the big picture is an architect's job, which is the point: you would be hiring for two roles.

The integration work widens the gap. A useful agent in a UK SME almost never stands alone. Here's what a single hire may have to touch in one project:

• the CRM: HubSpot, Salesforce, Pipedrive or Dynamics 365
• Microsoft 365, Teams and SharePoint
• Copilot Studio, with Power Automate or Azure Functions behind it
• Xero for anything finance-side
• Slack, or an n8n, Make or Zapier workflow that glues the rest together

Each of those has its own API limits, permission model and odd behaviour. A UK solo HubSpot platinum partner on r/hubspot said HubSpot is "often poorly set up", so your engineer may have to tidy the data before building.

Copilot Studio shows the same thing from the Microsoft side. A builder on r/copilotstudio described building a small M365 agent, a timesheet and sign-in log tool. To make it work they pushed the heavy processing into Azure Functions and AI Foundry exposed as HTTP connectors, kept memory in Blob Storage, and version-controlled the YAML in GitHub. Their verdict was that it's "not ready for non-technical users".

Our view is that Copilot Studio is the right front end if your staff live in Teams, and the hard parts sit behind it. Whoever you hire has to be good at both the front end and everything behind it. The LinkedIn AI SDR build in our portfolio gives a sense of the spread: a prospecting system that started as Make.com workflows, moved to n8n and grew into a full platform with CRM integrations.

In-house hire vs freelancer vs agency project vs fractional team

Where we have no sourced figure, the cell says so.

The freelancer column carries a compliance task people forget. If the contractor works through their own limited company, HMRC's off-payroll working (IR35) guidance says that "in most cases, the client will be responsible for determining the employment status of the worker". Follow HMRC's client size guidance, linked from that page, to see whether the decision sits with you.

The agency column is ours too, so read it with that in mind. Our custom projects are a fixed price quoted after a free 30-minute audit, with a written proposal within 48 hours. We agree a success metric at kickoff; if we miss it, we rebuild for free or refund the build fee. If you want to see how a UK AI automation agency scopes that kind of work, that page goes through it.

When hiring an AI engineer in-house is the right call

There are good reasons to hire, and we'd rather you hire for the right reasons than buy from us for the wrong ones. The UK government's AI Playbook is written for departments, but its principle carries over: "You and your team should gain the skills needed to use, design, build and maintain AI solutions."

Hire in-house when:

• AI is your product. If the model, the data pipeline or the agent is what customers pay for, it's a permanent capability and it belongs on payroll.
• You already have someone setting technical direction. If a CTO or lead engineer can own the architecture, the hire only needs to build, which narrows what you are hiring for.
• The backlog never empties. Five days a week of one person beats three days of a team if there's years of continuous work queued up.
• You want the knowledge on your own books. Avoiding supplier lock-in is a legitimate reason to pay more.

For a lot of SMEs our suggested sequence is: get an outside team to build and prove the first system, then hire someone to own and extend it once you know what the job actually is. If you're not sure which camp you're in, AI consultants who also build can help you write the job description before you pay a recruiter to fill it.

What works and what doesn't when you hire an AI developer

What works:

• Scope first and hire second. Write down the workflows you want automated and which systems they touch. That list tells you whether you need a builder, an integrator or both.
• Start with simple agents. The r/AI_Agents builder said the agents that earned money for them were simple: an email-to-CRM updater, an FAQ agent, a parser. Hire or buy for that, not for a moonshot.
• Price the full model. Use the JSON above with your own salary figure, and compare it with what the same months would buy elsewhere.

What doesn't:

• Vibe-coding the product. A post on r/startups described a non-technical founder who vibe-coded an entire MVP and got hacked before a bank deal. One reply put the lesson as "vibe code a demo not a full product."
• Picking a freelancer on the proposal alone. One commenter on r/Upwork said AI project posts there each get "over 50 proposals within around 30 minutes". Without someone technical to review the shortlist, you're choosing on how well people write proposals, not on how well they build.
• Having no plan for after launch. If nobody owns the agent once it's live, it drifts as your CRM fields, prompts and APIs change underneath it.

What changed in 2026

Employer NI for 2026/27 is 15% above £5,000 a year, so every pound of salary above the threshold carries 15p of NI, and a pay rise to win a candidate costs more than the headline. Employment Allowance for 2026/27 is £10,500. If you're eligible and haven't already used it against existing payroll, it can absorb most of the NI on one new hire. If existing staff already use it up, the new hire carries the full £12,375.

For scale, the ONS put median full-time annual earnings at £39,039 in April 2025, so the median AI engineer advert is about 2.2 times the national median. The recruiter guide we quoted above is dated H2 2026, and its phrase "now normal" for a four-to-six-month search is the recruiter's own read of this year's market. We used the same fully loaded method in our human SDR vs AI SDR cost per meeting breakdown, and the pattern held there too: the advertised salary understates the bill.

Run the numbers on your own role

Take the JSON block, swap in the salary you'd actually offer, and add the fee your recruiter quotes. Then set it against the two routes above: a fixed-price project for one defined system, or a team on retainer for a rolling backlog. If the in-house number still wins, hire, and hire someone senior enough to own the architecture.

If you'd like a second opinion on the scope before you decide, book a 30-minute audit. We'll look at the workflows and systems involved, and you'll get a fixed-price proposal for the project within 48 hours if a project makes sense.