To choose a bespoke software development company in the UK, check three things before price: live products you can open and use, a written assignment of the code and intellectual property, and a named senior person who answers for the work. Then settle the UK points in writing: UK GDPR and a data processing agreement, how any overseas data transfer is covered, governing law, scope, milestones and support.
This guide is written for UK buyers. It gives you the exact questions to ask and the red flags that should make you walk away. If you are buying outside the UK, our general 12-point checklist for choosing a software development company covers the same vetting without the UK legal points. If you have not yet settled whether to commission a build at all, read bespoke vs off-the-shelf software first.
Start with the portfolio, not the sales deck
A polished pitch tells you how a company sells. A live product tells you how it builds. Ask for two or three applications you can open in a browser or install on a phone, then use them for ten minutes. Look at how forms handle mistakes, how fast pages load and whether the design holds together on a small screen.
Then ask for references and actually call them. A short conversation with a past client answers questions no case study will: did the team hit its dates, how did they behave when something broke, and would the client hire them again. If a company cannot point to a single reachable reference, treat that as a red flag.
Ask who actually writes your code
Many agencies win the work with senior staff and then hand delivery to juniors you never met. That is not always wrong, because junior developers need to grow, but you should know the mix. Ask who writes the code, who reviews it and how many years the lead engineer has behind them.
Good questions to ask: Who is my day to day contact? Will the people in this meeting be the people building the product? What happens if my lead developer leaves mid project? A serious partner answers plainly and does not hide the team behind an account manager.
Get ownership and contracts right on paper
This is where UK buyers lose the most money. Under the Copyright, Designs and Patents Act 1988, copyright in code belongs first to its author, or to the author's employer, which means your supplier, not you, and an assignment is only effective in writing signed by the assignor (section 90(3)). Paying for the work does not move ownership on its own. Before any code is written, agree in writing that your business owns the source code and the intellectual property on final payment. Ask for the code to live in your own repository from day one, not inside an agency account you cannot reach.
Your contract should name the deliverables, the milestones, the payment schedule and what happens if either side wants to stop. Watch for agreements that keep ownership with the supplier, charge a fee to release your own code, or stay silent on IP entirely. If you commission bespoke software development for a real business need, the code is an asset you must own outright.
UK GDPR and how your data is handled
If your software touches personal data, and most business software does, UK GDPR applies. You are the data controller and your development partner is usually a data processor, so the responsibility does not leave you when you outsource the build.
Ask where data is stored, who can access it, how it is encrypted and how it is deleted when a customer asks. Request a data processing agreement in writing. Confirm you can host in UK or EU regions when a client or regulator needs data to stay local. A partner who cannot answer these questions clearly is a risk to your compliance, not just your project.
UK points to settle with a remote or overseas supplier
Many UK firms commission bespoke software from teams outside the UK. That works, but three questions are specific to UK buyers:
- Overseas access to personal data. If developers outside the UK can see personal data, that is usually a restricted transfer under UK GDPR. Ask how it is covered, for example with the ICO's International Data Transfer Agreement, or avoid it by giving developers anonymised test data and keeping live data in UK hosting.
- Governing law and disputes. Agree which law governs the contract and where disputes are heard. Many UK buyers ask for the law of England and Wales; whatever you choose, write it down.
- Security assurance. Some UK public-sector and enterprise buyers ask suppliers for Cyber Essentials or ISO 27001. Ask which schemes, if any, a supplier holds, and if they hold none, ask for the controls in writing instead: access, encryption, logging and offboarding.
Communication and time zones
Distance matters less than discipline, but it still matters. Decide how much live contact you need. If you want daily face to face calls in your own working hours, an onshore team suits you. If you are comfortable with a written scope, scheduled demos and a few overlapping hours each day, a remote partner works well and costs less.
Ask how often you will see working software, not slides. Weekly demos of real, clickable features are a healthy sign. Monthly updates with nothing to try yourself are not.
Fixed scope versus time and materials
There are two common ways to price a build. Neither is always right for every project.
| Factor | Fixed scope | Time and materials |
|---|
| Best for | Well defined projects with clear requirements | Evolving products where scope will change |
| Budget certainty | High, agreed up front | Lower, tracked as you go |
| Flexibility to change | Limited without a change request | High, reprioritise each sprint |
| Risk sits with | The supplier | Shared, so you must stay involved |
| What you bring | A clear written brief | Time to review and steer every week |
For a first version with known features, fixed scope gives you a firm number. For a longer product that will grow, time and materials keeps you flexible, as long as you stay engaged throughout.
Onshore, nearshore or offshore
Be honest with yourself about the trade-off. Onshore UK teams give you same hour meetings and local contract law, at the highest day rate. Nearshore teams in Europe sit close to your time zone at a middle price. Offshore teams cost the least and can deliver strong work, but they ask more of you in written clarity and structured reviews.
Timeline Digital, a bespoke and custom software development company founded in 2013, is headquartered in Islamabad, Pakistan and serves UK businesses remotely. We do not claim a UK office, and we do not pretend distance disappears. We manage it with a written scope, recorded and live demos, weekly reporting and a single point of contact; our 09:00 to 18:00 Pakistan-time hours overlap UK mornings by about four hours in winter and five in summer. Project source code, designs and documentation transfer to you on full payment, an NDA can be signed before you share sensitive details, and we hold no certifications, so security controls are set out in writing instead. If you want to understand the model in depth, read our guide to software development outsourcing; if you were planning to add engineers to your own team instead, read dedicated team or managed project.
Support after launch
The launch is the start, not the finish. Ask what happens the week after go live. Who fixes an urgent bug, how fast, and at what cost. Is there a warranty period included, and what does ongoing support cost per month.
A good partner offers a clear support arrangement: bug fixes, security updates, hosting and small changes under a monthly agreement, with larger features quoted separately. Avoid anyone who goes quiet once the final invoice is paid.
What it costs and how long it takes
Prices in the UK market vary widely, and any honest quote is built from scope. A focused first version with one core workflow is the smallest and quickest build; an ERP, an advanced multi-module system or a combined web app, mobile app and admin panel is larger and takes longer. Our custom software development cost guide explains the drivers.
The final cost depends on features, integrations, user roles, design and support. With us the pilot is always free. After the approved scope is agreed, we define the project milestones, delivery plan and commercial terms. Any requirement outside the approved scope is reviewed and agreed before additional work begins, so changes to cost or delivery are transparent and agreed in advance. Be wary of any number given before anyone has understood what you actually need.
A short checklist before you sign
Use this list to keep yourself honest.
- You have opened and used at least two of their live products.
- You have spoken to one past client directly.
- The contract transfers source code and IP to you on final payment.
- You know the senior engineer by name.
- Data storage, access and a processing agreement are written down.
- You have agreed fixed scope or time and materials on purpose, not by accident.
- Support, warranty and monthly costs are clear before launch.
This list covers the UK-specific points. For the general vetting steps that apply in any market, see our guide on how to choose a software development company.
Talk to us
If you are comparing a bespoke software development company in the UK and want a straight answer on scope, cost and timeline, we are happy to help. Discuss Your Project with us. We reply with questions first, then a written scope, a free pilot of 2 to 3 of your key modules, and agreed milestones and commercial terms. Before your first vendor call, our list of questions to ask a software development company is worth printing.