How to Choose a Software Development Company UK

A UK buyer’s guide to choosing a software development company: nine criteria, questions, red flags and 2026 prices. Written by a supplier, openly.

Disclosure: we are Magora, a London software development company, so we are one of the companies you might be comparing. This guide is written the way we would want to be assessed: every criterion below can be checked by you, and none of it depends on choosing us. Where we give prices, they are ours, labelled as such. Facts checked on 24 October 2026.

Short answer. Decide what you are buying (a team, a partner or a supplier), shortlist three companies on evidence you can check, ask each the same questions, and pay two of them for a small piece of paid discovery before you commit to the build. Price is the last filter, not the first.

1. Decide what you are buying

Three different purchases hide behind “we need an app” or “we need a system”:

A team. You have a product manager and a plan; you need more hands.
A product partner. You have a business problem and need someone to help decide what to build as well as build it.
A supplier. You have a specification and want it delivered to price.

Most disappointment comes from buying one and expecting another. A supplier builds your specification exactly, including the parts that are wrong. A partner pushes back and may recommend a different approach, which is what you are paying for.

2. The method: nine criteria

Use the same nine criteria for every company, score each 0–2 (0 = no evidence, 1 = claimed, 2 = evidenced and checkable), and write down the evidence. Weight them yourself: a regulated product will weight criterion 6 more heavily than a prototype will.

Criterion	What to ask for, and how to check it	Green flag	Red flag
1. Relevant proof	Two or three comparable projects, with client names and what changed afterwards. Check: read the case studies, ask to speak to a client, check the client exists.	Named clients, a problem-solution-outcome story, a reference call	Anonymous “global brand” cases, only logos
2. The team that will actually work on it	Names, seniority and tenure of the people on your project, and who is in-house. Check: ask for CVs or LinkedIn profiles; ask what happens if someone leaves.	The people you meet are the people who build	Sales team differs from delivery team; “resources” assigned later
3. How they estimate	How the estimate is built, what is in it and how change is handled. Check: ask to see a sample estimate (anonymised).	Itemised by feature; QA and product ownership are visible lines	One lump sum; “it depends” with no process
4. Discovery	What the first phase produces. Check: ask for a sample discovery output.	Product statement, prioritised backlog, user journeys, delivery plan	Straight to coding; discovery as a sales step with no deliverable
5. Ownership of code, IP and data	Who owns what, when it transfers and where the repository lives. Check: read the draft contract.	You own it from the first commit, in your repository	IP transfers only after final payment; code in their repository until handover
6. Security and data protection	Where data is hosted, who has production access, how a subject access request or a breach is handled. Check: ask for the security policy, and which certificates exist and for whom.	Specific answers for UK GDPR; certificates in the company’s legal name, with a scope you can read	“We take security very seriously” with no detail; a badge you cannot verify
7. Delivery practice	Sprint length, demos, testing, environments and release process. Check: ask to see a sprint board and a demo recording.	Weekly demo, automated tests, staging, QA as a separate role	No demos; testing “by the developers”; one environment
8. Commercial terms	Fixed price, time and materials or dedicated team; payment schedule; notice period; exit. Check: read the contract.	Payment tied to delivered work; clear exit	Large upfront payment with no deliverable; long lock-in
9. After launch	Support terms, response times, cost, and whether they take over someone else’s code. Check: ask for a support agreement template.	A number and a response time	“We’ll be there for you” with no agreement

Add two checks that are not about the supplier’s answers:

Companies House. Look up the company number: how long it has traded, whether accounts are filed on time, whether the registered name matches the contract.
Independent reviews. On Clutch, GoodFirms and Google, look for verified reviews with named roles and project descriptions, and read the 3–4 star reviews first. A high score from five reviews says less than a good score from fifty.

3. Questions to ask every company

The five questions that separate suppliers fastest. Our London article has twelve in full.

“What have you got wrong recently, and what did you change?” The single most useful question. A company that cannot answer has either not delivered enough to have failed or is not telling you the truth.
“What happens to the estimate when we want to change something?” The right shape of answer is: we tell you, we re-plan, you decide.
“What would you do if we halved the budget?” A good answer is a smaller product or a different approach. A bad answer is the same product with fewer hours.
“Can I speak to a past client who is not on your website?” A real reference tells you more than any written review.
“What do you need from us to succeed?” A partner who has thought about delivery has a list: a decision-maker, access to users, a test environment, sign-off within a few days. Suppliers say “nothing”.

How AI coding fits. Ask how the team uses AI-assisted development. Both extremes are warning signs: no AI at all, or all the work done with it. AI-assisted development with senior review (a developer who checks the code and the architecture) is the sensible middle. See question 1 in the London article.

4. Red flags

A fixed price quoted in the first call, before anyone has seen your process or data.
A price far below the market for the team described. If the work is happening somewhere else, a good supplier says so.
An estimate with no QA, no project or product management and no deployment line.
Intellectual property that transfers only on final payment, or code that lives in the supplier’s repository until handover.
You cannot meet or name the people who would build it.
Case studies without client names, dates or outcomes.
Only five-star reviews, all of them recent, none verified.
No discovery phase, or a discovery with no written output.
Pressure to sign this week for a “limited” discount.
Certificates or awards displayed with no certificate number, scope or issuer you can look up.
Resistance to a small paid pilot or to a reference call.
Vague answers on where your data is hosted and who can access it.

5. What it costs in the UK in 2026

Prices vary by orders of magnitude, so compare like with like. Two views, labelled by source.

What ten UK companies publish on Clutch

From our comparison page (checked 29 September 2026): minimum project sizes from $25,000 to $100,000 and hourly rates from $25–49 up to $150–199, quoted in US dollars as Clutch shows them. Use it as a sanity check on how wide the range is, and check the current figures yourself.

What a Magora project costs

Our 2026 published bands, in GBP and excluding VAT:

Stage	Price
Working prototype (5–10 working days)	£0
Discovery (2 weeks)	from £3,000
Startup MVP / first release (typically 6–8 weeks)	£10,000–£25,000
Production app or web platform (3–6 months)	£25,000–£60,000
Regulated or integration-heavy product (5–8 months)	£80,000–£120,000
Maintenance after launch	from £1,000 a month

Rates start from £49/hour per developer, and £65–£70/hour for a full team with QA and product ownership.

What moves the price. In the 12 project estimates Magora wrote for UK clients in 2026, first releases of new products cost £11,000–£34,000 (median about £25,000) and took 6–8 weeks; a second phase typically added 30–70% of the first release. Scope moved the price more than technology. Integrations, live AI processing and regulated data are where budgets grew. The data is in Software development cost in the UK (2026); for a first figure on your own project use the app cost calculator, and see app development cost in the UK for apps.

Check what is in the price. QA and product ownership are the lines most often missing. In Magora’s estimates QA is 30% of development time and product ownership 20%. A quote with neither is either padded elsewhere or will cost more later.

6. A four-week selection plan

Week	What you do
1	Write a one-page brief: the problem, the users, the systems it touches, the budget range, the date that matters. Decide supplier, partner or team.
2	Build a shortlist of three to five from referrals, directories and your own research. Score criteria 1, 2 and 5 from public material.
3	Run the same call with each: the five questions above, a sample estimate, a reference call. Score all nine criteria.
4	Pay two companies for a small, equal piece of discovery or a prototype. Compare what comes back, not the pitch.

Two weeks and a few thousand pounds spent choosing is cheap next to six months with the wrong partner. Read more on what the paid first phase should produce on our discovery phase page.

7. A note on “top 10” lists and directories

Lists are useful for building a shortlist, and unreliable for choosing from it. Check four things on any list: who published it, whether the publisher is on it, whether placement can be paid for, and whether the criteria are written down. Directories such as Clutch show verified reviews and project sizes; agency-published listicles (including ours) are marketing. Our own comparison of ten UK companies lists Magora first and the others alphabetically, discloses that, and links every figure to a source; read it as a starting point.

8. Contract checklist (not legal advice)

A UK entity and English law, with a company number you have checked.
Ownership: source code, designs and IP assigned to you; when it transfers; repository in your name.
Scope and change: what is in, how change requests are priced and approved.
Payment: tied to delivered, demonstrated work; a notice period you can live with.
Data protection: a data processing agreement; where data is hosted; breach notification.
Warranty and support: defect fixing period after launch; support terms and response times.
Exit: what you receive if either side ends the contract (code, documentation, access to environments).
Confidentiality: an NDA before you share the brief.

This checklist is general guidance, not legal advice. Have your solicitor review the contract. For pricing models see fixed-price software development and dedicated development teams.

9. When Magora is probably not the right choice

You need a brochure website only. Our first releases start from £10,000, so a simple website is probably not the best use of your budget with us.
You need a very large programme with hundreds of engineers. Our site describes a team of 50+ senior engineers, designers and project managers.
You want the lowest possible hourly rate. Our developer rates start from £49 an hour; if the hourly rate is your only filter, you will find cheaper options.
You already have a detailed specification and want a pure supplier. We work best as a partner who challenges the scope.

If none of those applies, ask us your nine criteria. The plainest answers are on our bespoke software development, mobile app development in London and software house pages.

Want a second opinion on your shortlist?

Book a free 30-minute call. We will look at your brief, tell you honestly whether we are the right fit, and if we are not, which kind of supplier is.

Book a call

Frequently asked questions

How do I choose a software development company?

Decide whether you need a team, a partner or a supplier; score three to five companies on the same nine criteria (proof, team, estimating, discovery, ownership, security, delivery, terms, support); ask them the same questions; and pay two for a small piece of discovery before committing to the build.

How much does a software development company charge in the UK?

It varies widely. On Clutch, the minimum project sizes of the ten UK companies in our comparison range from $25,000 to $100,000, and hourly rates from $25–49 to $150–199. At Magora a first release starts from £10,000 (most £10,000–£25,000) and a production platform costs £25,000–£60,000.

Should I choose a large or small development company?

Match the supplier to the size and risk of the project, not the size of its logo wall. A larger company brings more specialists and capacity for long programmes; a smaller one usually gives you senior people on every call.

Is a UK-based company better than an offshore one?

Not automatically. UK companies bring UK law, UK working hours and the ability to meet in person. Offshore companies can be good and cheaper. Whichever you choose, ask for the same evidence, and insist that any distributed team is disclosed up front.

What should be in a software development contract?

Ownership of code and IP, scope and change control, payment tied to delivered work, data protection terms, support and warranty, and an exit clause. See the checklist above, and have your solicitor review the contract.

What is the difference between a software house, an agency and a consultancy?

Mostly emphasis. A software house builds and supports software with its own engineers; a digital agency is often design- and marketing-led; a consultancy usually advises and runs large programmes. Judge each on the nine criteria, not the label.

How do I check a development company’s reviews?

Prefer verified reviews on independent platforms such as Clutch, with named roles and project descriptions. Read the middle reviews first, and ask for a reference call with a client who is not on the website.

Who owns the code?

It should be you, from the first commit, in a repository in your name. Treat any contract that holds the IP back until final payment as a lever that can be pulled against you.

Sources. Prices and figures are Magora’s own published pages (cost guide, bespoke software development) and our UK comparison, checked on 24 October 2026. Figures change; check the source before relying on them.

Pavel Shevtsov

Co-Founder & Managing Director

Pavel Shevtsov is a seasoned professional in the field of software development, currently serving as the Managing Director at Magora, a leading software development company known for its innovative solutions. With a passion for leveraging technology to solve complex business challenges, Pavel has played a pivotal role in Magora's growth and success.

How to choose a software development company in the UK