How to choose a software development company in the UK: 12 questions to ask

Choosing a software developer is one of the more consequential decisions a business makes and one of the hardest to get right, because the thing you are buying does not exist yet. The portfolio helps, but what you really need to know is how they work. These twelve questions reveal that.

1. Who will own the code and the intellectual property?

The answer should be "you, on payment, in writing". If it is anything else, understand exactly what you are getting. See who owns the code.

2. How do you run discovery?

A good developer will want to understand your business before quoting. Workshops, a written specification you sign off, and a quote based on it. If they quote from a phone call, the quote is a guess. See how to write a software brief for what you should bring.

3. Is the price fixed, and for what?

Fixed price for defined scope gives certainty. Ask what happens if requirements change, how changes are priced, and what is explicitly out of scope. Our cost guide explains the pricing models.

4. How will we see progress?

Demos every two weeks of working software is the standard to expect. If the answer is "we will show you when it is finished", walk away. See agile and sprints explained.

5. Who will we actually talk to?

The person who sold you the project is not always the person who runs it. Ask who your day-to-day contact is, whether they are technical, and how quickly they respond.

6. Who does the work, and where?

In-house team, subcontractors, or an offshore partner? All can be fine; you should know. If it is offshore, who manages them and who is accountable to you? See offshore vs UK development.

7. What testing do you do?

Automated tests, manual testing against real scenarios, security testing, testing on real devices. Ask for specifics. "We test everything" is not an answer.

8. What happens after launch?

Warranty period for bugs, then support: what it covers, how it is priced, response times. A developer with no support offering is planning to be gone.

9. What will we receive at the end?

Source code in a repository you control, documentation, hosting and service credentials in your name, a list of third-party components. If the answer is "a working system", ask again.

10. Have you built something like this before?

Not identical, but similar in kind: same sort of integration, same platform, same industry. Then ask for two references and call them.

11. What would you not build?

A good developer will tell you when off-the-shelf software would serve you better, or when a feature is not worth its cost. If every answer is "yes, we can build that", they are selling, not advising. See custom software vs off-the-shelf.

12. What do you need from us?

The answer tells you whether they understand how projects succeed. The right answer involves a decision maker on your side, time for discovery and testing, and prompt feedback. If they need nothing from you, they have not thought about it.

Reading the answers

You are listening for clarity, specifics and honesty. Vague answers to precise questions are the warning sign. So is a developer who asks you nothing: the best ones interrogate your brief, challenge assumptions and tell you things you did not want to hear. That is what you are paying for.

Comparing quotes

Only compare quotes for the same scope, with the same inclusions. Lay them side by side: discovery, design, build, testing, migration, training, warranty, support, ownership. The cheapest total is often the most expensive project, because the gaps get filled later at a premium.

We are happy to be asked all twelve, and our answers are on our services and about pages. If you would like to put them to us directly, book a free discovery call. Request a quote.

Frequently asked questions