How to choose a software development company in the UK

Read the proposal, not the price

A useful proposal states what is included, what is assumed, what is excluded and what happens when something changes. A proposal that is only a number and a timeline is not comparable to anything.

• Does it describe the outcome, or only a list of technologies?
• Are assumptions written down where you can challenge them?
• Is there a plan for the first few weeks, or only for the whole project?
• Does it say who owns the code and the accounts at the end?

What to ask on the first call

Ask them to describe a project that went badly and what they changed afterwards. Ask who will actually do the work and whether you will speak to them. Ask what they would cut if the budget dropped. The answers tell you more than any portfolio page.

Warning signs

Some patterns are worth taking seriously, particularly when several appear together.

• A firm quote given before anyone has asked what your data looks like.
• No mention of testing, handover or what happens after launch.
• Reluctance to give you access to the repository or hosting accounts.
• Case studies with impressive results but no description of the work.

Structure the engagement to reduce risk

A short, paid discovery phase gives both sides a low-cost way to test the working relationship. You end it with a scoped plan and a firmer estimate — and if the fit is wrong, you have lost weeks rather than months.