Table of Contents
- London Developer and Agency Rate Benchmarks for 2025
- What a Legitimate London Discovery Phase Costs and Includes
- How to Spot the “London Front, Offshore Build” Model
- Q1 – What Development Methodology Do You Use and How Will I See Progress?
- Q2 – How Do You Handle Scope Changes During a Project?
- Q3 – Who Specifically Will Build My Product, and Where Are They Based?
- Q4 – What Does Your Discovery Phase Include and What Do I Receive at the End?
- Q5 – Have You Built Something Similar Before? Can I Speak to That Client?
- Q6 – Who Owns the Code When the Project Ends?
- Q7 – What IP Assignment Clause Does Your Contract Include?
- Q8 – What Are Your Payment Terms and What Happens If Milestones Slip?
- Q9 – What Warranty or Defect Liability Do You Offer After Delivery?
- Q10 – What Does Your NDA Cover and Does It Protect Both Sides?
- Q11 – What Post-Launch Support Is Included and What Does It Cost After That?
- Q12 – How Do You Handle Data Protection and GDPR in the Build?
- Q13 – What Tech Stack Will You Use and Can I Switch Providers Later?
- Q14 – How Do You Approach Security Testing and Vulnerability Checks?
- Q15 – What Does Failure Look Like, and What Is Your Process If It Happens?
- How to Verify a London App Developer Using Companies House
- What UK Copyright Law Says About Software Ownership
- How to Use Clutch UK and The Manifest to Cross-Check Reviews
- Contract Red Flags Under UK Law
- Sales Process Signals That Predict Delivery Problems
- Why Agile Methodologies Are Sometimes Used to Obscure Poor Planning
- Frequently Asked Questions
- Conclusion
You are days away from signing a contract with a London app developer. The agency has given you a polished proposal, the sales call went well, and the timeline looks reasonable. This is exactly the moment most business owners stop asking questions and start trusting instinct. That instinct will cost them. The right London app developer questions, asked before the ink dries, are not just a due diligence formality. They are negotiating leverage. They signal that you know this market, that you understand UK contract law, and that you will not be an easy client to over-promise and under-deliver to. The 15 questions in this guide are drawn from the specific realities of the London market in 2025, not from generic advice that could apply anywhere in the world.
Before You Ask a Single Question – What London App Development Actually Costs
London Developer and Agency Rate Benchmarks for 2025
Understanding rate benchmarks before you walk into a negotiation is the difference between knowing you are getting a fair deal and hoping you are. In London, freelance app developers currently charge between £80 and £150 per hour depending on seniority and specialism. Boutique London agencies with in-house teams typically bill between £120 and £200 per hour. Any agency quoting significantly below £80 per hour for London-based work should be asked directly where the team is located, because those rates are not sustainable for a genuinely local team.
For project-based pricing, a minimum viable product for a mobile app in London typically runs between £25,000 and £80,000. Anything quoted at £10,000 flat for a full-featured app is either missing scope, hiding costs in future change requests, or being built offshore with a London sales contact at the front. A mid-complexity app with integrations, a CMS, and a custom backend will sit between £50,000 and £150,000 at a reputable London agency. These are not aspirational numbers. They reflect the actual cost of hiring skilled engineers in one of Europe’s most expensive tech labour markets.
What a Legitimate London Discovery Phase Costs and Includes
A discovery phase is the structured period of work that happens before a development contract is signed. It produces the artefacts a developer needs to price and plan your project accurately, and it produces the documents you need to get competitive quotes from multiple agencies. In London, a credible discovery phase costs between £2,000 and £10,000 depending on the complexity of your product. What you should receive at the end of it includes a detailed functional specification, user journey maps, technical architecture documentation, an honest risk register, and a properly scoped project estimate broken down by feature.
Any agency that refuses to sell discovery separately from development, or that offers you a free “discovery” that lasts half a day and results only in a fixed-price quote, is conflating sales with discovery. A genuine discovery phase is billable work. If the agency is not willing to sell it standalone, that tells you something about how they intend to manage the rest of the engagement.
How to Spot the “London Front, Offshore Build” Model
One of the most common models operating in London’s app development market is the agency that presents a London office, London-based account managers, and London pricing, while routing the actual build work to teams in Eastern Europe, South Asia, or Southeast Asia. This is not inherently dishonest. Hybrid models can deliver good results. The problem arises when the offshore arrangement is not disclosed, when the London premium is charged without the London quality, or when the time zone and communication gaps cause problems that the client was never warned about.
Signals to look for: the agency is reluctant to tell you exactly who will be building your product; the contract refers to “partners” or “resource providers” without naming them; video calls feature the same two account managers but no engineers; and the quote is suspiciously competitive for a business with London overheads. Ask Q3 from this list directly and watch how the answer is framed.
Questions 1 to 5 – About Their Process and Methodology
Q1 – What Development Methodology Do You Use and How Will I See Progress?
Most London agencies will answer this question with the word “agile.” That answer tells you almost nothing. What you need to understand is how agile is operationalised in their specific process. Ask how long their sprints are, how sprint reviews are structured, and what you as the client are expected to do between reviews. Ask what project management tool they use and whether you will have direct access to it. Ask whether standups are daily and whether you are invited.
The distinction matters because understanding why agile alone is failing UK businesses requires looking at how agencies deploy the methodology. Agile, used well, gives you visibility and control. Agile used poorly gives the agency flexibility to move scope without accountability. A developer who cannot explain their agile process in concrete operational terms is waving a methodology flag without running the process.
Q2 – How Do You Handle Scope Changes During a Project?
Scope change is where most London app projects go wrong and where most budget overruns originate. Every agency will tell you they manage change requests professionally. The question is what “professionally” means in their contract. Ask specifically whether change requests require a written estimate before work begins, whether they are priced at the same day rate as the original contract, and how disputes about whether something is a change or part of the original scope are resolved.
A developer who cannot give you a concrete answer to the dispute resolution question is likely operating without a formal change control process. That means scope disputes will be resolved by whoever argues more forcefully, and that is rarely the client.
Q3 – Who Specifically Will Build My Product, and Where Are They Based?
This question is the most important one in the first five. Ask for the names or roles of the specific people who will be building your product. Ask where they are physically located. Ask whether they are employees of the agency or contractors engaged for your project. Ask whether the same team will be working on your project from start to finish or whether resources are shared across multiple clients simultaneously.
A good agency will answer this question directly. They may not share full names before a contract is signed, but they will tell you the team structure, the seniority levels, the locations, and the employment model. Evasiveness here is a direct signal about how transparent they will be once you are a paying client.
Q4 – What Does Your Discovery Phase Include and What Do I Receive at the End?
Cross-reference this answer against the benchmarks above. A credible discovery deliverable for a London project includes a functional specification document, wireframes or user journey maps, a technical architecture proposal, a risk register, and a properly itemised cost estimate. If the agency describes discovery as “a few calls to align on requirements” followed by a quote, what they are describing is a sales process, not a discovery phase.
Ask specifically whether the discovery deliverables are yours to take to other agencies for competitive quotes. A confident, reputable developer will say yes. The answer to this question reveals whether the agency views discovery as a genuine service or as a lock-in mechanism.
Q5 – Have You Built Something Similar Before? Can I Speak to That Client?
Portfolio review is standard due diligence, but the reference call is where real information surfaces. Most London agencies will provide polished case studies. Fewer will connect you with the actual client who commissioned the work. Ask for three references, not one. Ask to speak specifically to the person who managed the project on the client side, not the CEO who approved the budget. Ask those references what went wrong, not just what went right. Every project has problems. A reference that describes a perfect experience is either rare or rehearsed.
You can also check whether the companies referenced in a portfolio actually exist and match the described projects by searching the Companies House register. If a case study names a client company, verify that the company is registered, active, and operates in the sector described.
Questions 6 to 10 – About the Contract and Legal Protections
Q6 – Who Owns the Code When the Project Ends?
In the United Kingdom, copyright in software created under a contract does not automatically transfer to the commissioning party. This is a fundamental difference from US work-for-hire doctrine, and it catches many UK business owners by surprise. Unless your contract contains an explicit IP assignment clause, the developer may retain copyright in the code they have written for you, even after you have paid in full. That means they could theoretically prevent you from modifying the software, reselling it, or moving it to another developer.
Ask directly: who owns the intellectual property in the code at the point of final payment? Ask to see the specific contract clause that addresses this. If the answer is that you receive a licence rather than outright ownership, understand precisely what that licence permits and prohibits.
Q7 – What IP Assignment Clause Does Your Contract Include?
The clause you want to see should read, in substance, that upon receipt of final payment, all intellectual property rights including copyright in all code, documentation, and deliverables created for the project are assigned to the client. Watch for qualifications: clauses that exclude pre-existing IP, third-party components, or “background IP” can significantly limit what you actually own. Ask for an explanation of any carve-outs and get confirmation that any excluded components are either open source with a permissive licence or licensed to you directly.
Any agency presenting a contract that explicitly retains IP rights or grants only a limited licence should be challenged on this point. If they will not negotiate a full assignment clause, that is a red flag significant enough to walk away from.
Q8 – What Are Your Payment Terms and What Happens If Milestones Slip?
Payment structures in London app development contracts vary widely. Fixed-price contracts often use milestone-based payment tied to deliverable sign-off. Time and materials contracts bill monthly or fortnightly based on time logged. Ask what the payment schedule looks like, what triggers each payment, and what your recourse is if a milestone is delivered late or not to the agreed specification.
Under the Late Payment of Commercial Debts (Interest) Act 1998, UK businesses have statutory rights when invoices are paid late. But the more important protection is a contract that defines what a completed milestone looks like and what happens when it is not delivered on time. A vague milestone definition is a mechanism for extracting payment regardless of delivery quality.
Q9 – What Warranty or Defect Liability Do You Offer After Delivery?
Most London app development contracts include a defect liability period, typically 30 to 90 days after delivery, during which the developer must fix bugs at no additional cost. Ask how that period is defined, what counts as a defect versus a new feature request, and what happens if a critical bug is discovered after that period ends. Ask whether emergency support is available and at what rate.
A developer who offers no warranty period is asking you to accept all technical risk from the moment of delivery. That is not a standard the London market accepts for serious projects. Any agency that resists a reasonable defect liability clause should be asked why.
Q10 – What Does Your NDA Cover and Does It Protect Both Sides?
An NDA in an app development context should protect your business idea, your user data architecture, your commercial plans, and any proprietary processes you share during the project. Ask whether the NDA is mutual, covering information shared in both directions, or one-sided. Ask how long it lasts and whether it covers the agency’s subcontractors and offshore partners explicitly.
A developer who objects to a mutual NDA with subcontractor coverage is signalling either that they use third parties they do not fully control, or that they do not take confidentiality obligations seriously. Either signal deserves follow-up.
Questions 11 to 15 – About Post-Launch, Support, and Long-Term Risk
Q11 – What Post-Launch Support Is Included and What Does It Cost After That?
The moment your app goes live is not the end of the engagement. It is the beginning of the operational phase, and the support structure you have in place determines how quickly you can respond to bugs, performance issues, and security vulnerabilities. Ask what support is included in the contract after launch, what the response time SLAs are, and what a retainer for ongoing maintenance would cost.
London agencies typically charge between £1,500 and £5,000 per month for a maintenance retainer covering monitoring, updates, and minor enhancements. If an agency is unclear about post-launch costs or presents them as something to discuss later, that vagueness will translate into expensive conversations when you actually need support.
Q12 – How Do You Handle Data Protection and GDPR in the Build?
If your app collects any personal data from users, GDPR compliance is not optional and it is not something that can be bolted on after launch. Ask the developer how data protection is factored into their technical architecture decisions from the beginning of the project. Ask whether they conduct a Data Protection Impact Assessment for projects involving sensitive or high-volume personal data. Ask who holds the ICO registration, what their approach to data minimisation is, and how they handle third-party integrations that involve data transfer.
The ICO data protection guidance sets out the obligations clearly. A developer who cannot speak to privacy-by-design principles or who treats GDPR as a legal checkbox rather than a technical discipline is creating liability that will land with you as the data controller, not them.
Q13 – What Tech Stack Will You Use and Can I Switch Providers Later?
Vendor lock-in is a long-term risk that many clients do not consider when signing their first app development contract. Ask what framework, language, and infrastructure platform the developer proposes and why. Ask whether those choices are industry standard or proprietary. Ask what it would take for another developer to pick up the codebase if you decided to switch providers in two years.
Red flags include: a developer who insists on a proprietary CMS or deployment environment that only they support; code written in an obscure framework without a clear justification; infrastructure locked to a specific cloud account they control. Standard tech stacks, clean documentation, and infrastructure you own are not just best practice. They are negotiating points you should insist on before signing.
Q14 – How Do You Approach Security Testing and Vulnerability Checks?
Security testing should be part of the build process, not an afterthought. Ask whether the agency conducts automated security scanning during CI/CD, whether they perform manual penetration testing before launch, and how vulnerabilities discovered post-launch are handled. Ask specifically about their approach to authentication, data encryption in transit and at rest, and protection against common attack vectors such as SQL injection and cross-site scripting.
A developer who treats security as a separate engagement to be scoped and quoted later is operating a development process that does not have security baked in. For any app handling payments, personal data, or business-critical operations, that is an unacceptable approach.
Q15 – What Does Failure Look Like, and What Is Your Process If It Happens?
This is the question most clients never ask, and it is the one that reveals the most about an agency’s culture and maturity. Ask the developer to describe a project that did not go well. Ask what went wrong, what they did about it, and what the outcome was for the client. Ask what their escalation process looks like if a project falls behind schedule or the client is not satisfied with delivery quality.
An agency that cannot describe a project failure, or that attributes every past problem to client scope creep, has not done the internal reflection that produces reliable delivery. The agencies that handle problems well are not the ones that never have problems. They are the ones that have built honest processes for catching and resolving them.
UK-Specific Due Diligence – What No Generic Checklist Covers
How to Verify a London App Developer Using Companies House
Before signing any contract, search the agency’s registered company name on the Companies House register. Confirm the company is active, that the registered address is not a virtual office servicing dozens of companies, that the directors match the people you have been speaking to, and that the filing history shows accounts have been submitted on time. Late accounts or dormant company filings for an agency presenting itself as a thriving London business are worth questioning directly.
Also check the company age. An agency with two years of trading history presenting a portfolio of five-year-old projects may have rebranded or restructured. Ask about trading history and any predecessor companies. This takes ten minutes and eliminates a significant category of risk.
What UK Copyright Law Says About Software Ownership (and Why It Differs from the US)
Under the Copyright, Designs and Patents Act 1988, the author of a work is generally the first owner of copyright. For software written by an employee in the course of their employment, the employer owns the copyright. But for software written by a contractor or an agency commissioned by a client, the contractor or agency is the default copyright owner, not the client, unless there is a written assignment in the contract. This is the opposite of the US work-for-hire doctrine, which is why US-focused advice on IP ownership does not transfer cleanly to UK contracts.
The practical implication: if your contract does not contain a clear IP assignment clause transferring ownership to you on final payment, you are paying for software you do not legally own. This matters most if you ever want to sell your business, raise investment, licence the software to third parties, or move development to another provider.
How to Use Clutch UK and The Manifest to Cross-Check Reviews
Clutch and The Manifest are the most credible third-party review platforms for software development agencies in the UK. Unlike Google reviews, Clutch reviews require verification of the reviewer’s identity and involve a structured interview process conducted by Clutch analysts. This makes them significantly harder to game than unverified review platforms.
When reviewing an agency on Clutch UK developer listings, look beyond the overall score. Read the qualitative comments, pay attention to the scores for quality of delivery versus cost, and note whether reviews mention specific problems and how they were handled. An agency with 4.8 stars and thirty reviews that never mention a single problem is either unusually fortunate or has been selective about which clients they direct to the platform.
Red Flags to Watch for Before You Sign
Contract Red Flags Under UK Law
When you review the contract, these are the specific clauses that should give you pause. An IP clause that grants a licence rather than an assignment of copyright. A variation clause that allows the developer to change the price or timeline without client consent. An exclusion of liability clause that removes all developer responsibility for defective work. A governing law clause that specifies a jurisdiction other than England and Wales. A payment structure that requires more than 30 percent upfront before any work has begun. Any of these in isolation may be negotiable. Multiple in the same contract is a pattern.
Also watch for contracts that reference terms and conditions by URL rather than including them in the document itself. Those terms can be changed at any time, and you may not be notified. Insist that all terms are included in the signed document.
Sales Process Signals That Predict Delivery Problems
The sales process is the first piece of work an agency does for you. How they conduct it predicts how they will conduct the rest of the engagement. Specific signals to watch for: a quote delivered within 24 hours of an initial call without a discovery process, which indicates the scope has not been properly analysed. A quote that does not itemise features or assumptions, making it impossible to compare with other agencies on a like-for-like basis. Pressure to sign before a deadline that is tied to a commercial incentive rather than a project constraint. An unwillingness to introduce you to the technical team before signing.
Knowing how to spot an unreliable software agency in London means paying as much attention to the sales process as to the portfolio. The best tech partner for your business in London will run their sales process with the same rigour they bring to delivery. If the sales experience feels disorganised, rushed, or evasive, that is not a coincidence.
Why Agile Methodologies Are Sometimes Used to Obscure Poor Planning
The discussion about why agile alone is failing UK businesses is not a criticism of agile as a methodology. It is a criticism of how the label is misused. Agile is a framework for managing complexity and change in software development. It requires discipline, documentation, and continuous communication to work. When an agency uses the word “agile” to justify the absence of a fixed specification, the absence of a detailed project plan, or the absence of clear milestones, they are using agile terminology to obscure the absence of a process.
The signal is when “agile” is offered as an answer to why you cannot have a detailed functional specification, a realistic timeline, or a meaningful fixed price. Good agile practice produces better specifications, not fewer. It produces more transparency about timeline, not less. If agile is being used to keep you in the dark rather than bring you into the process, that is a planning problem being rebranded as a methodology.
Frequently Asked Questions
What Questions Should I Ask a London App Developer Before Signing?
The most important areas to cover are: who specifically will build your product and where they are located; who owns the code after final payment and what the IP assignment clause says; what the discovery phase includes and what you will receive; how scope changes are managed and priced; and what post-launch support costs. This guide covers all fifteen questions in detail.
How Much Does It Cost to Hire a London App Developer in 2025?
London-based freelance developers charge between £80 and £150 per hour. London agencies typically charge between £120 and £200 per hour. An MVP mobile app in London costs between £25,000 and £80,000. A mid-complexity app with integrations and a custom backend will typically cost between £50,000 and £150,000. Discovery phases cost between £2,000 and £10,000 separately.
How Do I Protect My IP When Hiring an App Developer in London?
Under UK copyright law, code created by a contractor or agency does not automatically belong to you. You need an explicit IP assignment clause in your contract that transfers all intellectual property rights to you on receipt of final payment. Review the clause for carve-outs covering pre-existing IP, background IP, and third-party components, and confirm that any excluded elements are licensed to you with no restrictions on use.
What Should a Discovery Phase Include Before App Development Begins?
A credible discovery phase should deliver a functional specification document, user journey maps or wireframes, a technical architecture proposal, a project risk register, and a detailed cost estimate itemised by feature. You should receive these as documents you own, which you can use to obtain competitive quotes from other agencies. Any discovery process that does not produce these deliverables is not a discovery phase.
How Do I Check If a London App Developer Is Legitimate?
Search the company name on Companies House and verify the registration is active, the directors match who you have been dealing with, and accounts have been filed on time. Check the agency on Clutch UK and read the qualitative review comments. Ask for three client references and request conversations with the project managers, not just the executives. Verify that portfolio case study companies are real and active businesses.
Conclusion – The Signing Moment Is Your Leverage Moment
The moment before you sign a contract with a London app developer is the moment of maximum leverage in the entire engagement. Once you have signed, your negotiating position changes. Problems that surface later are harder and more expensive to resolve than questions you ask before the contract is in place. These fifteen questions are not obstacles to a good working relationship. They are the foundation of one.
An agency that responds well to rigorous pre-contract questions is demonstrating exactly the kind of transparency and confidence you need in a long-term development partner. An agency that becomes evasive, defensive, or dismissive when asked about IP ownership, team structure, or their process for handling failure is showing you, before you have committed a pound, exactly how they will behave when the project is under pressure.
London’s app development market has agencies of every quality level operating under similar-looking websites and proposals. The questions in this guide are the filter that separates the ones who will deliver from the ones who will cost you far more than their original quote. Use them, and use the signing moment well.
