Choosing a custom software development company has a lot in common with online dating. Every profile looks great, everyone claims to be "passionate" and "disruptive", and it's only three months in that you discover the truth - in this case, that the truth is a half-built system, a missed launch date, and an invoice for "scope realignment".
We've been on the other side of this. We've inherited codebases from agencies that vanished, picked up projects that "innovation partners" never quite finished, and had more than one client tell us their previous developer's idea of documentation was a WhatsApp thread. So here's our honest, occasionally cheeky, guide to not becoming the next cautionary tale.
The buzzword bingo card you should be worried about
If a proposal reads like it was generated by a corporate jargon machine, that's because - increasingly - it was. None of these phrases are illegal, but each one is a small tax on your patience, and collectively they're a decent predictor of how the project will go.
| What they say | What it usually means |
|---|---|
| "We're a digital transformation partner" | We build websites, but "websites" doesn't justify the day rate |
| "Agile methodology" | There is no fixed scope, no fixed price, and no fixed end date |
| "Bleeding-edge tech stack" | We wanted to try a framework that came out last Tuesday, on your budget |
| "Dedicated account manager" | Someone whose job is to say "great question, let me check" between you and the one developer who actually knows what's going on |
| "Let's jump on a call to discuss pricing" | The price depends on how the call goes |
None of this makes an agency dishonest by default - plenty of good developers write bad marketing copy. But it's a useful smell test. If you can't tell what a company actually does from its homepage, don't expect more clarity once you're a paying client.
The questions that actually separate the good from the bad
Skip "tell me about your culture" and ask things with answers that can be checked:
- "Can I speak to a client from 18 months ago, not last month?" Anyone can produce a happy client mid-project. Long-term retainers and repeat business are the real signal - check our case studies for projects still running years after launch.
- "Who actually writes the code?" If the answer involves three subcontracted layers across two continents, you've found your future support ticket queue.
- "What happens if I want to leave?" A trustworthy partner hands over clean, documented code and full access on request. If this question makes them visibly uncomfortable, that's your answer.
- "What's this actually going to cost, all in?" A number, a fixed-scope quote, or an honest "here's the range and here's why" - not a call booked to "explore that".
- "Can I see their Companies House filing?" Two minutes on the Companies House register tells you how long they've existed and whether the accounts look like a going concern - free, and more reliable than a testimonials page.
Red flags worth walking away from
- No fixed quote, ever. "It depends" is a fine first answer. It's a terrible final one.
- They own your code, domain, or hosting - and won't hand it over. If your "custom software" is hostage to someone else's login details, it isn't really yours.
- Every conversation ends in upsell. A discovery call that's really a sales funnel for six add-on retainers is not discovery.
- They can't explain what they'd build in plain English. If a technical decision can't be explained to a non-technical founder in two sentences, be suspicious - not because you need to understand the code, but because you need to trust that they do.
- Reviews that all sound the same. Real client reviews have specific, slightly awkward details in them. Five-star reviews that all say "professional and innovative" read like they were written by the same person, because they probably were.
Why "boring and honest" is the compliment you're looking for
Nobody puts "refreshingly unremarkable" on a pitch deck, but it's closer to what you actually want from a development partner than "visionary" is. You don't need your CRM to be exciting. You need it to work, to be maintainable by whoever's around in three years, and to cost roughly what you were told it would cost.
That's the whole premise behind how we work at Nimble IO. We're not going to tell you your invoicing system needs blockchain. We're going to ask what's actually broken, quote you a number we can stand behind, and build the thing - then tell you honestly if a cheaper off-the-shelf option would do the job just as well (see our take on bespoke vs off-the-shelf software for when we'd talk you out of a custom build entirely).
We've turned down projects because the honest answer was "you don't need bespoke for this, buy the £30/month tool." We've also told clients considering Salesforce that it was the right call for their situation, even though it meant less work for us. That's not altruism - it's just what happens when you'd rather keep a client for ten years than bill them once.
A shortlist checklist you can actually use
- Read three case studies. Do they mention specific numbers, timelines and outcomes, or just adjectives?
- Ask for a fixed quote on a defined scope. Watch how quickly - and how clearly - it comes back.
- Ask who owns the code and hosting once the project ships. Get it in writing.
- Ask what they'd advise against building. If the answer is "nothing, everything you've described sounds great," that's not a good sign.
- Check they'll still be around. Companies House, LinkedIn tenure, and a portfolio with some grey in its hair all help.
Our honest take
Picking a custom software partner shouldn't require a translator for marketing-speak or a lawyer for the exit clause. It should be a plain conversation about what you need, what it costs, and what happens if it doesn't work out. If a company can't have that conversation with you before you've signed anything, they're unlikely to have it after.
We'd rather earn the work by being straightforward than win it by sounding impressive. If you've got a project you're trying to scope - or you just want a second opinion on a proposal that's landed in your inbox covered in buzzwords - get in touch. We'll give you a straight answer, even if that answer is "go with the other lot".