Django

Hiring a Django consultant: what they do and UK rates

A Django consultant fixes one defined problem, such as an upgrade or a slow site. UK Django contract rates have a median of £625 a day.

What a Django consultant actually does

A Django consultant is a senior engineer you bring in for one problem your own team can't solve quickly, or doesn't have time for. The work has a clear end. When it's done, they leave, and your team carries on.

Typical jobs:

  • An upgrade that keeps slipping. The site is on a Django release that no longer gets security fixes, and nobody wants to touch it. Right now the supported series are 5.2 LTS, 6.0 and 6.1, and 5.2 gets security fixes until April 2028 (Django's supported versions table). Anything older is on its own.
  • A slow application. Pages that were quick at launch now take seconds to load, often because of database queries that grew with the data.
  • A stalled project. The original developer has gone, there are no tests, and every change breaks something else.
  • A second opinion before you build. Architecture, hosting and data model checked before the money is spent.
  • An audit before a handover or a sale. Someone is buying the company, or taking over the code, and wants to know what they are getting.

What these have in common is a question you can write down in one sentence. If you can't, you probably need a team rather than a consultant.

Consultant, contractor or agency

The words overlap, and the people selling the service use them loosely. The useful difference is what you are paying for.

  • A consultant is paid for judgement. They diagnose, recommend and often fix, over days or weeks.
  • A contractor is paid for capacity. They join your team for months and take tickets like anyone else.
  • An agency is paid for an outcome. It takes on a project or a product, with its own process, cover for holidays and more than one pair of eyes on the code.

In practice one person can be all three in a single year. Ask which one you are buying this time, because it changes how you should judge the result. A consultant who writes a good report and fixes the two worst problems has done the job. A contractor who writes reports instead of shipping has not. If you are weighing up whole teams, our guide on how to choose a Django development agency covers that decision.

What a Django consultant costs in the UK

The best public benchmark is ITJobsWatch, which tracks the rates quoted in UK job adverts. For the six months to 18 November 2026, the median daily rate for Django contracts in the UK was £625, from 187 quoted rates. A year earlier the same figure was £500. London runs higher, with a median of £700 a day from 96 quoted rates.

Django contract day rates, six months to 18 November 2026 (source: ITJobsWatch, checked 18 November 2026)
PercentileUKLondon
10th£320£391
25th£441£478
Median£625£700
75th£713£741
90th£750£750

Three things to keep in mind when you read that table.

  1. These are advertised rates, not invoices. They come from job adverts and include roles where Django is one skill among several. Treat them as a range, not a price list.
  2. The top of the range is flat. The 90th percentile is £750 in both columns. Above that, you are paying for a specific reputation or a specific problem, and the market data stops being much help.
  3. A day rate is not a salary. The median permanent Django salary over the same period was £75,000. A consultant at £625 a day for a 20-day month costs £12,500, but you pay nothing between engagements, no recruitment fee and no notice period beyond the contract.

Agencies price differently again. When one quotes you a day rate, ask what is inside it: a second engineer reviewing the code, cover when someone is ill, project management, hosting. Two quotes with the same day rate can buy very different amounts of work.

IR35: who decides the consultant's status

Many UK consultants work through their own limited company. When they do, the off-payroll rules (IR35) apply. Since the rules changed on 6 April 2021, GOV.UK's guidance puts the decision with the client in most cases if you are a public body or a medium or large private company. If you are a small private business, the consultant's own company decides.

For a medium or large company this means real paperwork, so it's worth knowing before you sign. One way to keep it simple is to contract with a company that delivers a defined piece of work, rather than with an individual who takes instructions like an employee. Get your own advice on this; the guidance is detailed, and the answer depends on how the work is actually done, not on what the contract calls it.

When you need a consultant, and when you don't

Bring one in when the problem is specific, urgent and outside your team's experience. An upgrade across three major Django versions, a site that falls over under load, a codebase nobody understands: these reward someone who has seen the same thing many times.

Don't hire a consultant for steady feature work. You will pay a premium rate for work a contractor or your own developer can do, and the knowledge leaves when they do. Don't hire one to make a decision you have already made either. If the board has chosen a rewrite, a consultant who tells you to upgrade in place is just an expensive argument.

The middle case is the common one. You need someone senior for three to six months, not three days. That is closer to hiring a developer for a fixed spell, and it should be priced and contracted that way.

Questions to ask before you hire one

Which Django problems like ours have you fixed?

You want specifics: the Django and Python versions, what was wrong, what they changed and how long it took. A consultant who answers in general terms about best practice has probably not done your kind of job.

What will we have at the end?

Agree the deliverable before the start date. Merged pull requests, a written report, a working upgrade on staging, a list of risks with rough costs. If the answer is "we'll see", set a review point after the first week.

Will you work in our repository and our process?

A good consultant opens pull requests against your code, follows your review rules and leaves tests behind. Work done on a private branch and handed over at the end is much harder to trust.

Who does the work?

With a firm, ask whether the person on the sales call is the person writing the code. With an individual, ask what happens if they are ill for a week.

How do we end it?

Notice periods, ownership of the code and documentation, and access being removed. Settle these in writing before you need them.

What the first two weeks should look like

A consultant should be useful within days. In the first week, expect them to get the project running locally, read the code and the deploy setup, and list the risks in order. If you asked for an upgrade, they should know by then which packages block it and roughly how many steps it will take.

By the end of the second week you should have something concrete: a first fix merged, a plan you can take to the board, or a clear statement that the job is bigger than you thought and why. If two weeks pass and you only have questions back, say so early.

For upgrades specifically, our Django upgrade service explains how we move a live application forward one release at a time, without a rewrite.

How we work

Webbyfox is a small, senior Python studio in England. We have built websites and web applications in Python since 2012. The person you talk to is the person who works on your code.

If you need a Django engineer in your team rather than a one-off fix, our Django developers join monthly and on a rolling basis, with two weeks' notice and no recruitment fee. You contract with a company, not an individual. Every engineer is senior.

If you are not sure yet what the problem is, start with a two-week discovery sprint. You get a working prototype, an architecture recommendation, an upgrade or risk report if you already have code, and a cost range with the assumptions written down. Then you decide whether to go ahead.

Summary
  • A Django consultant fixes one defined problem: an upgrade, a slow site, a stalled project or a code audit.
  • UK Django contract rates had a median of £625 a day (London £700) in the six months to 18 November 2026, according to ITJobsWatch.
  • Ask what a quoted day rate includes; two equal rates can buy very different amounts of work.
  • Medium and large clients usually decide IR35 status themselves; small private businesses do not.
  • Agree the deliverable, the repository and the exit terms before the first day.

Questions

How much does a Django consultant cost per day in the UK?

ITJobsWatch puts the median advertised UK rate for Django contracts at £625 a day for the six months to 18 November 2026, with London at £700. The middle half of quoted rates fell between £441 and £713. Agencies may price above or below this depending on what the rate includes.

What is the difference between Django consulting and Django development?

Consulting is a short engagement to diagnose and fix a defined problem, such as an upgrade or slow performance. Development is ongoing work on features. The same engineer can do both, but you should agree up front which one you are paying for.

How long does a Django consulting engagement usually last?

It depends on the problem. A code audit or a performance review can take days; an upgrade across several major versions can take weeks or months. Set a review point after the first week either way.

Does IR35 apply when I hire a Django consultant?

If the consultant works through their own limited company, the off-payroll rules apply. Public bodies and medium or large private companies usually decide the worker's status themselves; for small private businesses the consultant's company decides. See GOV.UK's off-payroll guidance and take your own advice.

Need this on your codebase? Talk to us about Django development.
See Django development
R
Rizwan Mansuri, Technical Director Builds and upgrades Python web applications for UK teams. More about us.

Keep reading