If you are about to hire a software agency in the UK, the most expensive mistake is not picking the wrong technology. It is signing a contract before you understand who will do the work, what you actually own at the end, and what happens when something goes wrong. A polished sales call tells you very little about any of those things.
This guide is for founders and managers buying software for the first time, or looking for a cleaner experience than the last project. It covers the questions to ask before you sign, what to expect on price and process, and the red flags that should make you slow down.
Start with the outcome, not the feature list
Before comparing agencies, be clear about the result you are paying for. “We need an app” is not a brief. “We need customers to book and pay for appointments without calling the office” is. Agencies quote on what you ask for, so the vaguer the brief, the wider and less useful the quotes.
Also ask what the agency would not build: a team that pushes back on a costly feature with no user behind it is telling you something good about how they work.
Who will actually work on your project?
Agency websites show senior people, but projects are sometimes staffed by whoever is free. Ask directly who will work on yours: how many people, how senior they are, and whether they have built something similar.
You do not need a large team: a small product often needs one lead developer, one designer, and someone to manage the project and talk to you. What you need is a team that will be there for the whole project, not one that rotates every few weeks. Ask who owns decisions on your project, and who you will talk to week to week.
How pricing really works
Pricing confuses buyers because the same word can mean different things: a fixed price, an estimate, or a range that moves with scope. Before you compare numbers, find out which one a quote is, and what would make it change.
Ask these questions, in plain language, and get the answers in writing:
- What exactly is included in the price, and what is explicitly excluded?
- How are changes handled once work has started?
- What happens if the project runs over, and who carries that cost?
- Are hosting, licences, app store fees, and third-party services included or billed separately?
- What does support cost after launch, and what does it cover?
A fixed price suits a clear scope, because the agency carries overrun risk, but only if scope is genuinely clear. If the brief is still evolving, a time-and-materials model with a weekly cap may be fairer, because it avoids the agency padding a fixed price for uncertainty. Either way, agree on a change process before the project starts, so a new request does not quietly become an invoice.
Finally, be wary of a quote dramatically cheaper than every other one. It can mean junior staff, missing items, or an assumption that you will accept a much smaller scope. A low price is only a bargain if the delivery matches.
Who owns the code, the data, and the accounts?
This is the question buyers forget most often, and regret forgetting. Before signing, confirm you will own the code, the design, and the documentation at the end, and that you can walk away with them. If the agency builds on its own platform or keeps the code in its own account, ask what happens if the relationship ends.
Ask where the code lives during the project, and whether you have access to it from day one. Ask who owns the accounts for hosting, app stores, and third-party services: they should be in your name, or in an account you control. An agency that hesitates on ownership is a red flag.
The same applies to data. If the software holds customer data, ask how it is stored, who can access it, and how it is protected. If you are a UK business, you need to be comfortable with how the agency handles data protection and where the data sits.
What does the process look like week to week?
Good software is built in small, visible steps, not delivered as a surprise after months of silence. Ask how often you will see progress, what a demo looks like, and how you will raise concerns. If an agency cannot describe a week on your project, they may not have a process at all.
In our experience, a weekly rhythm works well: a short demo, a plain-language summary of what changed, and a chance to steer the next week’s work. If an agency’s only communication is a monthly invoice, expect the product to drift from what you imagined.
Ask how decisions are made and recorded: who approves a change, and where is it written down? That paper trail matters when the project is reviewed at the end.
What happens after launch?
Launch day starts the product’s life, not ends the relationship. Software needs updates and fixes, and most projects need changes in the first months as real users find the rough edges.
Clarify the difference between a bug and a new feature. Bugs in delivered work should be fixed under the original agreement; new features are extra. Get that distinction in writing, with a window, say 30 to 90 days, for post-launch fixes.
Ask about response times, not just availability: a reply within one working day for a serious problem, and a plan for urgent issues, matters more than a promise that someone is “on call”.
Hiring a software agency in the UK: points worth checking
Ask how the agency handles data protection, including UK GDPR, and where customer data is stored and processed. If the agency works outside the UK, ask where its team is and whether that affects communication or data handling.
Ask which law governs the agreement and how disputes are handled. If you are a UK company signing with a UK agency, that should be straightforward; if the agency is elsewhere, it matters more.
Check that the agency has appropriate insurance, including professional indemnity insurance, and ask about it directly. It is a routine question, and a professional agency will answer without hesitation.
References, red flags, and the final gut check
Ask for two or three references from clients with similar-sized projects, and actually call them. Ask what went wrong, not just what went well: the answer tells you more about how the agency handles difficulty.
Look at live work, not just screenshots: visit the websites and apps the agency built and check whether they are still running, still maintained, and still pleasant to use. A portfolio of abandoned projects is a warning sign.
Finally, trust your experience of the sales process. If calls are slow to be returned, answers are vague, or you feel rushed into signing, that is how the project is likely to feel. A good agency will welcome scrutiny, answer in plain language, and leave you time to decide.
Frequently asked questions
How long should choosing an agency take?
Typically two to four weeks: shortlist three or four agencies, call each, get written proposals from two, and call references. Rushing it rarely saves time, because a wrong choice costs months.
Should I choose a UK agency or a remote team?
It depends on what you value. A UK agency may offer easier meetings, shared hours, and a familiar legal framework. A remote team may be cheaper, but you will need to manage time zones and communication. There is no universal right answer, only the right fit for your project.
Is a fixed price always safer than hourly billing?
Not always. Fixed price is safer when scope is clear; hourly billing can suit a product that will evolve. Either way, get the change process and the post-launch support in writing before you start.
What should I have ready before I approach agencies?
A one-page brief is enough: what the product must do, who will use it, what success looks like, your budget range, and your timeline. That is enough for a serious agency to quote and for you to compare quotes fairly.
Talk to us before you sign anything
Choosing an agency is a decision you will live with for the life of your product. If you are weighing agencies, or wondering whether a quote is fair, it is worth a conversation before you commit.
Book a free strategy call through our contact page and tell us what you are building. We will talk through your options, including whether we are the right team for the job. If you want to see how a project would run week to week, read our app development process guide, the same process we would follow on your project.
Top comments (0)