Choosing a software development agency is one of the highest-stakes decisions a small business makes. Get it right and you have a system that transforms how you operate. Get it wrong and you have spent months and thousands of pounds on something that does not work properly.
This guide gives you a structured framework for evaluating agencies. We are an agency ourselves — SoftwareYeah — and we are publishing this knowing you will use it to evaluate us alongside our competitors. That is the point. We would rather win work by meeting high standards than by keeping buyers uninformed.
The 10 Questions to Ask Every Agency
1. Who owns the code when the project is finished?
This is the single most important question. Some agencies retain intellectual property rights to the code they build for you. This means you cannot take your software to another provider for updates or hosting without their permission — or without paying additional fees.
The answer you want: complete IP transfer upon final payment. You own the source code, the database, the design files, and all project assets. No restrictions on future use, modification, or hosting.
If an agency hesitates or adds conditions to IP transfer, walk away. This is a fundamental dealbreaker.
2. How do you price projects?
There are three common pricing models in UK software development:
- Fixed price: A set cost for a defined scope. Best for projects with clear requirements. Protects your budget but requires good scoping upfront.
- Time and materials: Hourly or daily billing for work done. Flexible but risky without clear estimates and caps. Can spiral if scope is not controlled.
- Retainer: Monthly fee for ongoing access to development time. Suits businesses needing continuous development but can lock you into paying for unused hours.
For most SME projects, fixed-price with milestone payments offers the best balance of cost certainty and quality. For detailed pricing ranges, see our bespoke software cost guide.
3. Can I speak to previous clients?
Any agency worth hiring will happily connect you with previous clients. If they cannot or will not provide references, that is a significant red flag.
When speaking to references, ask specifically about: timeline accuracy (did they deliver on schedule?), communication quality (were you always informed of progress and problems?), post-launch support (how responsive were they after deployment?), and hidden costs (did the final invoice match the original quote?).
4. Who will actually work on my project?
Sales teams are charming. Developers who will build your software may be entirely different people with different skill levels. Ask who specifically will work on your project, what their experience is, and whether they will be dedicated to your project or splitting time across multiple clients.
Some agencies outsource development to offshore teams while maintaining a UK-facing sales office. There is nothing inherently wrong with this, but you deserve to know. Ask directly.
5. How do you handle scope changes?
Every software project evolves during development. Requirements change, new features emerge, and priorities shift. How an agency handles change requests reveals their professionalism.
Good agencies have a formal change request process: new requirements are documented, priced, and approved before work begins. This prevents surprise invoices and keeps both sides aligned.
Bad agencies either say yes to everything (and blow the timeline) or refuse changes entirely (and deliver software that does not fit your actual needs).
6. What happens after launch?
Post-launch support is where many agencies disappoint. The team that built your software moves on to new projects. Bug fixes take weeks instead of days. Feature requests go into a queue that never seems to move.
Ask about: guaranteed response times, support costs (hourly vs retainer), handover documentation quality, and whether the build team or a separate support team handles post-launch work.
7. How do you handle data protection and GDPR?
UK businesses need software that handles personal data correctly. Ask how the agency approaches GDPR compliance during development, not just whether they are aware of it.
Good answers include: privacy by design principles, data minimisation in database architecture, consent management features, and ICO-aligned data processing documentation. For a compliance reference, see our GDPR-compliant software checklist.
The ICO's guidance for organisations outlines what is expected of data controllers — your agency should be familiar with it.
8. What is your technology stack and why?
You do not need to understand every framework, but you should understand why an agency recommends specific technologies for your project. The answer should relate to your requirements, not to what the agency happens to know.
Watch for agencies that use the same technology for every project regardless of requirements. A good agency recommends the right tool for the job, even if that means using something they have less experience with.
9. How do you report progress?
Regular, structured progress reporting is essential. Ask about: reporting frequency (weekly is standard), reporting format (written updates, demos, or both), escalation process (how do they flag problems early?), and access to project management tools.
The best indicator of how communication will work during the project is how it works during the sales process. If getting information out of them is difficult before you have signed, it will only get harder once they have your money.
10. What does your contract look like?
Ask to see a sample contract before engaging. Key clauses to check:
- IP transfer: Complete ownership upon payment
- Payment milestones: Tied to deliverables, not calendar dates
- Scope definition: Clear description of what is and is not included
- Change process: How additions are priced and approved
- Cancellation terms: What happens if either side needs to end the project early
- Warranty period: Bug fixes included post-launch (typically 30–90 days)
Have a solicitor review the contract before signing. This small investment protects against significant risk. The Companies House register lets you verify that the agency is a legitimate registered company.
Red Flags That Predict Project Failure
These warning signs, individually or collectively, strongly predict a problematic engagement:
- No clear process: If the agency cannot explain their development methodology — how they scope, build, test, and deploy — they are likely improvising
- Pressure to sign quickly: Legitimate agencies do not create artificial urgency. Take the time you need to evaluate
- Unrealistic promises: If the quote is dramatically lower than competitors, something is being cut. Usually quality, testing, or post-launch support
- No portfolio relevance: A portfolio of beautiful consumer apps does not prove they can build your internal business tool. Look for projects similar to yours in complexity and purpose
- Vague about team: Reluctance to identify who will work on your project often means junior developers will handle it while seniors focus on bigger accounts
- No client references: The inability to provide references is the clearest red flag of all
Agency vs Freelancer: When Each Makes Sense
Choose a freelancer when: Your project is under £15,000, requires a single primary skillset (e.g., frontend development only), has a well-defined scope, and you can manage the project yourself.
Choose an agency or studio when: Your project requires multiple disciplines (design, backend, frontend, DevOps), has complex integrations, needs structured project management, or requires post-launch support with guaranteed response times.
For context on project sizing and costs, see our MVP development guide for smaller projects or our bespoke software cost guide for larger ones.
How to Run a Good Selection Process
Step 1: Write a clear brief. Even a one-page document describing the problem, the users, and the desired outcomes gives agencies enough to provide meaningful responses.
Step 2: Approach 3 to 5 agencies. Fewer than three limits comparison. More than five wastes everyone's time, including yours.
Step 3: Evaluate proposals on process and understanding, not just price. The cheapest option and the most expensive are both likely wrong for different reasons.
Step 4: Meet the team who will actually build your software. Chemistry and communication style matter more than impressive slide decks.
Step 5: Check references. Speak to at least two previous clients. Ask the uncomfortable questions.
Step 6: Start with a small paid discovery phase before committing to the full project. This lets both sides assess the working relationship before the stakes are high.
Frequently Asked Questions
How much should I expect to pay a software development agency in the UK?
UK agency day rates range from £400–£600 for regional studios to £800–£1,200+ for London-based agencies. Total project costs for SMEs typically fall between £10,000 and £80,000 depending on complexity. Always request fixed-price quotes for defined scope rather than open-ended hourly billing.
Should I hire a freelancer or an agency for software development?
Freelancers suit smaller projects (under £15,000) requiring a single skillset. Agencies bring multiple disciplines under one roof — design, frontend, backend, DevOps, QA — and typically offer better accountability, structured project management, and post-launch support. The trade-off is cost: agencies charge more but reduce coordination risk.
What should be in a software development contract?
Essential clauses: complete IP transfer upon payment, fixed price for defined scope, change request process with pricing, payment milestones tied to deliverables, post-launch support terms and costs, data handling and GDPR responsibilities, cancellation terms, and source code escrow or handover arrangements.
How do I evaluate a software agency's portfolio?
Look beyond visual design. Ask about the business problems each project solved, the technology choices and why they were made, what challenges arose and how they were handled, and whether you can speak to the client directly. A portfolio of pretty screenshots tells you less than one detailed case study with measurable outcomes.
What are the red flags when choosing a software agency?
Key warning signs include: no clear pricing model (hourly without estimates), reluctance to discuss IP ownership, inability to show relevant previous work, no defined project management process, unavailable references, pressure to sign quickly, and promises that sound too good to be true (unrealistically low costs or fast timelines).
Should I choose a UK-based agency or offshore developers?
UK-based agencies cost more but offer same-timezone communication, GDPR compliance understanding, UK contract law protection, and cultural alignment. Offshore teams can work well for clearly defined, well-documented projects where cost is the primary constraint. Hybrid approaches (UK project management with offshore development) can offer a middle ground but add coordination complexity.