Skip to main content

How to Choose a Django Development Agency in the UK: 12 Questions to Ask

In this article

A Django development agency builds and runs web platforms in Django, the Python framework behind sites from small booking systems to large online services. Choosing one is mostly a matter of asking the right questions before you sign, because the answers show you how the work will actually go: who writes the code, what you own at the end, what happens when something breaks at 2am, and what the agency will not do. This guide lists the twelve questions we would ask in your position, with the answers we give ourselves, so you can hold any agency to the same standard.

The short answer

  • Ask who writes the code. The people who sell the project should be the people who build it, or you should know exactly who will.
  • Ask to see platforms they built and still run. A live product with real customers is worth more than any portfolio page.
  • Ask what you own. The code, the database, the hosting account and the domain should be yours once the project is paid for.
  • Ask what happens after launch. Hosting, backups that have been restored for real, monitoring and a fixed period of free fixes should be in writing.
  • Ask what they will not do. An agency that says no to something is telling you where its standards are.

Twelve questions to ask a Django development agency

1. Who will write the code?

Some agencies sell with senior people and build with whoever is free. Ask for the names of the developers who will work on your platform, and whether the people on the call are among them. Ours are: both founders are hands-on developers and work directly on every client project.

2. Can I see a Django platform you built and still run?

Anyone can show screenshots. Ask for a live platform with real customers that the agency runs day to day, and try it. UK Name Change is ours: an online deed poll service built in Django, taking orders and generating documents since it launched.

3. Which Django version do you build on, and how do you handle upgrades?

Django releases a long-term support version every two years. Django 4.2 stopped receiving security updates on 7 April 2026; 5.2 LTS is supported until April 2028. A new platform should start on the current LTS, and the agency should say how and when it will move you to the next one, and what that costs. Our Django vs Laravel comparison sets out both frameworks' support windows.

4. How do you scope the first version?

The answer you want is a first version built around one journey that makes or saves money, delivered in weeks, then grown in stages on the same codebase. The answer to be wary of is a six-month specification before anything is built. Our guide to planning a custom web app shows what a good first conversation covers.

5. Who owns the code, the data and the accounts?

Once the project is paid for, the code the agency wrote, the database, the hosting account, the domain and the payment accounts should all be in your name, with no per-user licence fees and nothing rented. If any of those will stay in the agency's name, ask why.

6. How do you handle payments?

If the platform takes money, ask how the agency confirms a payment and what stops a customer being charged twice. The right answer involves the payment provider's own confirmation message to the server, handled once however many times it arrives, rather than trusting the browser. Our guide to secure payment integration explains what that looks like.

7. What happens after launch?

Hosting, daily backups, monitoring and security updates should be offered as a plan, with a fixed period of free fixes for faults in the agency's own work. Ask one detail: when did you last restore a backup for real? An agency that restores backups to prove they work is the one whose backups will work.

8. How will I see progress?

You should be able to click through the platform on a staging site as it takes shape, not wait for a demo at the end. If the agency has no staging site, you will find the problems after launch.

9. What security do you build in by default?

Two-factor authentication on admin accounts, HTTPS with the security headers browsers expect, encrypted documents, logged actions and dependency updates before every deploy. Our website security checklist is the list we work through; ask any agency for theirs.

10. How do you move data from my current system?

Most platforms replace a spreadsheet, an old system or another database. Ask how the existing data will be brought across, how it will be checked, and whether the old system can run alongside the new one until you are sure. Our guide to moving a database without downtime shows how seriously that checking should be taken.

11. What will it cost, and when will I know?

A platform is priced on what the first version has to do, so expect a conversation before a number. What you should get is a written quote for the first stage before any work starts, and a price for each later stage before it begins. An agency that quotes a platform from a one-line brief is guessing.

12. What will you not do?

Every good agency has limits, and the honest ones say so. Ours: we only look after platforms we built ourselves, because taking on someone else's code means guessing at decisions we did not make, and we would rather rebuild in stages than look after a platform badly. Ask the agency you are talking to what it turns away.

Agency, freelancer or in-house?

A freelancer can be the right choice for a small platform with one journey, as long as you know what happens when they are on holiday or unavailable. In-house makes sense once the platform is the business and there is a year or more of work in the backlog. A small agency sits between the two: more than one developer who knows the code, without a payroll. Whichever you choose, the twelve questions above apply; only the answers change.

Red flags

  • A fixed price for the whole platform before anyone has asked what it does.
  • No live platform the agency runs itself.
  • Code, hosting or domains that stay in the agency's name.
  • A build on an unsupported Django version, or no answer on upgrades.
  • No staging site, and no plan for what happens after launch.

If what you need is a business website rather than a platform, the questions are simpler and the budget is smaller; our comparison of WordPress and Django helps decide which you are buying.

Questions people ask

What does a Django development agency do?

It designs, builds and usually runs web platforms in Django: the accounts, payments, documents, dashboards and integrations that make a website into a product or an internal system. A good one also hosts, monitors and maintains what it builds, and adds features in stages after launch.

How much does Django development cost in the UK?

It depends on what the first version has to do, so it is quoted after a short conversation rather than from a price list. Building in stages keeps the cost down: you pay for what the business needs now, not every feature at once. For a business website rather than a platform, our UK website cost guide gives rough ranges.

Should I hire a Django agency or a freelancer?

A freelancer suits a small platform with one journey and a clear end; an agency suits a platform that will keep growing and needs more than one person who knows the code. Ask both the same twelve questions and compare the answers rather than the day rates.

Do you take over Django projects other agencies built?

No. We only look after platforms we build, because taking on someone else's code means guessing at decisions we did not make. If your platform needs a new home, we can rebuild it in Django in stages, move your data across, and look after it from there.

Where to start

Write down the one journey your platform has to handle end to end, then put the twelve questions to every agency on your list. Our Django development and web platform page sets out how we answer them, and a free 30-minute call is the quickest way to hear the answers for your project.