Start with the problem, not the tech stack
Most teams open a search with a shopping list: React, a bit of AI on top, maybe an app while we're at it. It feels productive. It's also backwards. The right build depends on what you're actually trying to fix, not on whichever framework is having a moment this quarter. A good agency will poke holes in your brief before they quote it. When you talk to your shortlist, notice who asks sharper questions than you walked in with - that tells you more than any case study.
Questions that actually tell you something
Skip "how many years have you been in business." It sounds reassuring and means almost nothing. Ask these instead:
- Who actually writes the code - the people I'm talking to now, or a team I'll never meet?
- Show me something you shipped that broke, and walk me through how you handled it.
- What happens after launch? Who do I call when checkout goes down at 9pm?
- Can I speak to a client you worked with two years ago - not two months ago?
That last one carries the most weight. Anyone can look brilliant during the honeymoon. You want to know how the work held up once the excitement wore off.
Red flags worth walking away from
A firm quote with no discovery is the big one. If someone prices a build before they understand it, they're guessing - and you're the one who pays for a wrong guess later. Watch for vague ownership of code and IP too; you should own what you pay for, and it should say so in writing. Be wary of anyone who never mentions maintenance, because software isn't a painting you hang on the wall and forget. And if everything you ask is met with "no problem, easy" - be careful. Engineers who know their craft will happily tell you what's hard.
A few things worth checking about UK agencies specifically
If your users or their data live in the UK or EU, GDPR isn't a box to tick at the end - it shapes how the thing gets built. A UK-based team tends to have that baked in rather than bolted on. Shared working hours help more than people expect, as well: a bug you raise at 2pm and a bug you fire into a timezone twelve hours behind are very different days. It's also fair to want a registered company you can look up on Companies House. It's a small thing, but it's a real one.
Fixed price or day rate?
Both can work and both can burn you. Fixed price suits a tightly scoped job with clear edges - a marketing site, a defined integration. A day rate or monthly retainer suits work that will shift as you learn, which, if we're honest, is most software. Whichever you pick, the thing that protects you is short feedback loops. If you're only seeing the product every eight weeks, something has already gone quietly wrong.
Where a team like ours fits
For context on how we think about all this: Invoclouds is a UK software development agency. We build websites, SaaS platforms, AI and workflow automation, and custom dashboards. If you just want to sanity-check a brief or get a second read before you sign with anyone, get in touch- even if we're not the ones who end up building it.