Co-Founder Programme We co-found three products a year for 10 to 15 per cent equity. Next cycle: January 2027. Next cycle Jan 2027 Booking projects for Q1 2027
Buying guide

How to choose a software development agency in the UK: 12 questions to ask first.

Most UK small businesses choose a technology provider within a month, and ease of use, cost and compatibility top their list (Department for Business and Trade, July 2025). Choosing a development partner can move at the same pace, but it needs sharper questions.

How UK businesses usually choose

Government research on how UK SMEs adopt technology found that 59 per cent chose a provider in under a month. When deciding, they put ease of use first (37 per cent), then cost (17 per cent) and compatibility with what they already use (15 per cent). They looked for information on review and advice sites, asked trusted peers and existing IT providers, and checked suppliers' own websites (Department for Business and Trade and Ipsos, July 2025).

The same research found SMEs wary of hype and overselling, keen on transparent pricing with no hidden costs, and frustrated by generic replies, long waits and having to chase for updates. Those are good instincts. The twelve questions below turn them into checks you can make before you sign.

Ownership and exit

1. Will the IP be assigned to my company in writing?

Under UK law, the copyright in code a supplier writes stays with the supplier unless it is assigned to you in writing and signed. Paying the invoice is not enough on its own. Ask to see the assignment clause before you sign. Our guide to who owns the code explains why.

2. Whose name will the domain, hosting and accounts be in?

Yours. The developer who disappears holding the domain, the hosting and the logins is a story UK businesses tell more often than you might think (Herefordshire and Worcestershire Chamber of Commerce, April 2026).

3. What happens if we stop working together?

A good answer covers a clean handover of code, credentials and documentation, and a sensible notice period. Be wary of any arrangement that only works while you keep paying the same supplier.

People and experience

4. Who will actually do the work?

Ask to meet the people who will build it, not just the people who pitch it, and ask whether anyone else will be brought in after you sign.

5. Have you built something like this before?

Ask for case studies from similar businesses and, if you can, a reference you can call. Check reviews somewhere other than the supplier's own website.

Price and scope

6. Is the quote fixed, and what counts as a change?

A fixed quote is only useful if the scope behind it is written down. Ask how changes are costed and approved, and make sure each change is approved before it is built.

7. What will it cost to run each month?

Hosting, licences, app store fees, AI model usage and support continue after launch. Ask for those costs in writing, separately from the build, so the total cost of ownership is clear.

8. How will I be billed?

Milestones tied to working software protect you better than large payments up front. Ask how the payment schedule maps to what you will actually see working.

Working together

9. How will I see progress?

Look for a demo of working software every week or two, a project board you can open whenever you like and a named lead who replies to you.

10. How do you handle data and security?

Ask for a data processing agreement under UK GDPR, and ask where your data will be hosted and how access to your systems is controlled. Larger customers may ask you the same questions about your suppliers.

After launch

11. Who looks after it, and how fast do you respond?

Ask for the support terms in writing: what is covered, the response time for each level of problem and whether out-of-hours cover is included.

12. What would you tell me not to build?

A good partner will sometimes recommend something smaller, an off-the-shelf tool or not building at all. If every answer is yes, be careful.

Red flags

  • No written scope, only a price.
  • The supplier holds the code, domain or accounts in its own name.
  • Promises of guaranteed search rankings, AI mentions or revenue.
  • Pressure to sign quickly, or to pay most of the fee up front.
  • Reviews that only appear on the supplier's own website.
  • Vague answers about who will do the work.

How we answer these

We publish our answers: our process, our terms, how we handle security and data and how our support plans work. Ask us the same twelve questions on a free call and judge the answers for yourself.

Sources

  1. Department for Business and Trade and Ipsos, Understanding technology adoption among UK SMEs, 31 July 2025
  2. Herefordshire and Worcestershire Chamber of Commerce, What to do when your web developer disappears, 15 April 2026
  3. GOV.UK, Ownership of copyright works

General information, not legal, tax or financial advice. Figures were checked on the publication date and can change, so confirm the current position with the source or a qualified adviser before you act.

Free 30-minute call

Want this applied to your project? Ask an engineer.

Thirty minutes with a senior engineer, free and with no obligation. Bring the problem, not a brief.

Questions, answered

Frequently asked questions.

How many quotes should I get for a software project?

Enough to compare like with like. Two or three detailed quotes written against the same brief are usually more useful than many vague ones, because you can see what each supplier includes, what they leave out and how they plan to handle changes.

Does a development agency need to be local?

What matters more than location is whether you can reach the people doing the work, in your working hours, and whether the contract, data handling and support terms follow UK law. Ask how you will be kept up to date and who you will speak to.

Is the cheapest quote a false economy?

Not always, but compare what each quote includes: discovery, testing, documentation, security, handover and support. A low price that leaves those out often costs more later. Ask each supplier to list what is not included, in writing.

What should a software development contract include?

A written scope, a fixed price or a clear pricing method, how changes are approved, a milestone payment schedule, a written IP assignment, a data processing agreement where personal data is involved, support terms and what happens when the work ends.

Still have a question? Ring 07723 431000 and speak to an engineer.

Ask us the twelve questions. Judge the answers.

Thirty minutes with a senior engineer, free and with no obligation.

Or ring us07723 431000

What happens next

  1. A free 30-minute callWith a senior engineer, at a time that suits you. No obligation.
  2. A short discoveryWhat it covers is agreed in writing before it starts.
  3. A written scope and a fixed quoteIn pounds, before you commit to a build.

A senior engineer replies within one working day, in UK hours.

Cookie preferences

Choose which cookies we may use. You can change this at any time using the Cookie settings link at the bottom of every page.

Strictly necessary Always on

Keep the site secure and working, and remember this choice.

Count visits and show which pages are useful, so we can improve the site. Google Analytics.

Measure our advertising and show relevant ads on other sites. Google Ads, Meta and LinkedIn.

Cookie Policy · Privacy Policy