How to choose a software development company in London

Search for software companies in London and you’ll see hundreds of agencies, most describing themselves as award-winning and trusted, alongside directories and “top 10” lists. Many list positions are sponsored or self-submitted, so treat them as a starting point for names, not as a recommendation. This guide covers how to narrow things down, including what to ask us if we’re on your list.

Start by being clear about what you’re buying

Agencies differ more than their websites suggest. Before contacting anyone, write a page or two covering the problem you’re solving, who’ll use the software, what systems it has to work with, your rough budget and any fixed dates. You don’t need a full specification. In fact, a long specification written before you’ve spoken to anyone is often wrong. But a clear brief helps agencies tell you if you’re a good fit, and it makes quotes comparable.

Share your budget, even if it’s only a range. Holding it back rarely gets you a better price, and it means agencies can’t tell you what’s realistic. Without it, you’ll get proposals for very different projects, and you won’t be able to compare them.

Does it matter if they’re in London?

Being in the same city can help during discovery workshops and when things go wrong, and a London firm understands your market and regulations. It isn’t essential, though, as most project work happens remotely anyway. Check where the work will actually be done, since many agencies with a London address deliver from elsewhere. Offshore delivery can be perfectly good and considerably cheaper, but you should know about it and consider time zones, how data is handled, and who’ll be on your calls. Ask directly.

Check evidence, not claims

• Relevant case studies. Look for work that’s similar in complexity to yours, not just in sector. Ask what went wrong, as every real project has something.
• References you can call. Ask to speak to a client whose project is live and has been running for at least a year. Ask them what happened when there was a problem.
• Companies House. It’s free to check how long the company has existed, who runs it and whether its accounts are up to date. Many claims can be checked here in minutes.
• Accreditations. If they claim to be a partner or hold a certification, check the issuer’s directory. Cyber Essentials has a public search facility.
• Review sites. Clutch and similar sites can help, but look at dates and details, and remember that the agency usually asks clients for those reviews.

Questions worth asking

A good agency will welcome these. Vague answers are useful information too.

• Who will actually work on my project, and can I meet them? The people in the sales meeting often aren’t the ones writing the code.
• Will I own the code and intellectual property, and when does it transfer? Get this in writing.
• Whose name will the hosting, domain, repository and app store accounts be in? They should be in yours.
• How do you handle changes to scope? Requirements always change, so what matters is the process.
• How often will I see working software? If the answer is “at the end”, walk away.
• How do you test? Ask specifically about automated tests.
• What happens after launch? Find out about support costs before you sign, not after.
• What would you advise against in my brief? An agency that disagrees with nothing is just taking your order.

Fixed price or time and materials?

Fixed price feels safer, and it can suit small, well-defined work. The catch is that the agency has to build in a contingency, and each change becomes a negotiation, which can create a tense relationship when you learn something new. Time and materials offers flexibility and tends to suit projects where you’ll learn as you go, but it needs trust and active budget tracking. A sensible middle ground is a paid discovery phase, followed by a fixed budget for a defined release, with priorities adjusted within it. Either way, you should always be able to see where the money’s going.

Red flags

• Guaranteed timelines and prices quoted before they’ve understood your project.
• No questions about your business, or eagerness to agree with everything you say.
• Reluctance to let you speak to the developers or to past clients.
• Contracts where the agency keeps the code or hosting until some later date, or where exit costs are unclear.
• Proprietary frameworks that only they can maintain, which lock you in.
• A price far below the others. Ask why. Something’s been left out, or someone’s misunderstood.

Compare quotes carefully

When quotes vary widely, the difference is usually scope or assumptions. Put them side by side and compare what’s included: discovery, design, testing, deployment, documentation, project management and post-launch support. Hourly rates can also mislead, because a slower team on a low rate may well cost more overall. Published guides suggest what custom software tends to cost in the UK, which is helpful for checking whether a quote’s in a sensible range.

Consider starting small

You don’t have to bet the whole budget on a first impression. A short paid discovery project, or a small first phase, shows you how a team communicates and handles problems. Treat it as a test on both sides. If it goes well, carry on. If not, you’ll have useful documentation, and you’ve risked relatively little. If you’d like to talk through your own shortlist, including whether we belong on it, here’s how we work with London businesses.