A few months back, a friend running a logistics startup in Birmingham called me up sounding pretty wound up. He had just paid a development agency a chunky deposit and the whole thing was already going sideways. Missed deadlines. Vague status updates. A project manager who kept changing every two weeks. By the time he rang me, he’d burned about £40,000 and had nothing usable to show for it.
His question was simple. How do you actually pick the right one?
So we sat down with a coffee and worked through it. What I’m sharing below is basically that conversation. If you’re a UK business about to hand over a serious budget to a software firm, these are the twelve things you should actually be checking before you sign anything.
The Mistake Most People Make Up Front
Most buyers start by asking about price. That’s the wrong opening question.
The first thing you should be looking at is whether the agency has actually built something similar to what you need. Not just “we do mobile apps.” That’s everyone. I’m talking about a logistics platform if you run logistics. A patient portal if you’re in healthcare. The closer their past work matches your problem, the less money you’ll waste on them learning your industry on your dime.
Second mistake. People assume the big-name agencies are automatically safer. Sometimes they are. Sometimes you’re just paying for the office in Canary Wharf and getting juniors doing the work. So don’t be lazy here. Dig in.
The First Six Checks. The Boring But Essential Stuff
Here’s where I’d start any vendor conversation.
Domain experience. Have they shipped something in your industry? Ask for two case studies. If they hesitate or send you generic decks, that’s a flag. Honestly, this single check rules out half the agencies you’d come across in any roundup of top software companies in the UK.
Team composition. Who’s actually building your software? Get names. Get LinkedIn profiles. You want to see the senior devs, not just the sales lead.
Communication setup. How often will you hear from them? Daily standups? Weekly demos? If they’re vague about this, expect chaos later.
Time zone overlap. A lot of UK firms now have offshore teams in South Asia or Eastern Europe. That’s fine. But check there’s at least 4 hours of overlap with UK working hours. Otherwise you’re stuck waiting overnight for replies.
Code ownership. Make sure the contract spells out that you own the code. Sounds obvious but you’d be surprised how often this gets fudged.
Existing client references. Don’t just read testimonials on their website. Ask to speak to two current clients. A good agency will set this up in a day. A dodgy one will stall.
That gets you through the first round. If they survive these six, move on to the deeper stuff.
The Next Six. Where the Real Differences Show Up
This is where most procurement teams stop digging, and it’s where the real money is made or lost.
Tech stack alignment. If your in-house team uses .NET and the agency only does Node, you’ll have integration headaches forever. Match the stack from day one.
QA and testing process. Ask how they handle bug tracking. What’s their automated testing coverage. If the answer is “we test everything manually,” walk away. That’s 2010 thinking.
Security and compliance practice. GDPR is the baseline. But if you’re in fintech you also want to see they understand FCA rules. In healthcare, NHS Digital and DSPT. Don’t assume. Ask directly.
Project management methodology. Scrum, Kanban, hybrid… whatever they use, make sure they can explain it without buzzwords. If they’re throwing around terms without showing you their actual sprint board, that’s a tell.
Post-launch support. What happens after go-live? A lot of agencies disappear the day the invoice clears. Get a maintenance contract scoped from the beginning, not as an afterthought.
Financial stability. Last one. Quick check on Companies House. How long have they been around? Are they filing accounts on time? You don’t want your vendor going under halfway through your build.
What Actually Goes Wrong in Real UK Projects
I’ll be honest. Most UK software project failures don’t come from technical incompetence. They come from misaligned expectations.
The client thinks they’re buying a finished product. The agency thinks they’re selling a discovery phase that’ll lead into a build. Both sign the same contract and end up in court six months later.
The fix is less exciting than people want it to be. Spend more time on the spec before signing. A two-week paid discovery is way cheaper than a three-month dispute. I’ve seen Manchester startups burn through six-figure sums because they skipped this step. And I’ve seen tiny Bristol outfits ship beautifully because they spent four weeks just nailing the requirements first.
Another thing worth saying. Don’t just look in London. The UK has serious software talent in Edinburgh, Cambridge, Manchester, and Belfast too. Sometimes the rates are better and the engineering quality is the same or higher. London prices reflect London property costs, not always London output.
If you want a starting point, there are a few vetted UK software development partners worth shortlisting before you go to RFP. Worth scanning through to see who actually fits your industry rather than firing off proposals to twenty places at once.
A Word on Pricing. Because Someone Will Ask
UK day rates vary wildly. A senior dev at a London consultancy can run £900 to £1,400 per day. A regional UK firm might be £600 to £900. An offshore team brought in by a UK agency could land at £300 to £500 per day blended.
Just don’t pick the cheapest and don’t pick the most expensive thinking either is a shortcut. The mid-range options usually work out best.
A Quick Note on One Vendor I’d Mention
If you’re scoping a build that needs both UK-side account management and offshore engineering muscle, Brain Station 23 is one firm that does this combination well. They’ve been around since 2006 and the team handles fintech, retail, and enterprise work. Not a paid plug. Just a firm that keeps showing up in shortlists for a reason.
Final Thought
Picking the wrong agency costs more than money. It costs months you can’t get back, team morale, and sometimes the project itself. The 12 checks above aren’t bulletproof. Nothing is. But they’ll filter out about 80% of the wrong choices in your first conversation.
If you want to compare options before talking to anyone, this curated UK software vendor list is a decent place to start. Shortlist three to five names and run them through the framework. By the time you’re done, you’ll know who deserves a meeting and who doesn’t.
And if my friend’s story taught me anything, it’s that an extra week spent picking the right vendor saves about six months of pain later. Worth it.