A fixed-price software quote gives you one number for a defined piece of work. That is reassuring, but the number is only as good as the words around it. If the scope is vague, so is the price: you find out what was left out when you ask for it, and the extra cost arrives as a change request.
This post sets out what a good quote should contain, the questions worth asking before you sign and how to compare quotes from different suppliers fairly. It applies whether you are commissioning a mobile app, a web platform or an AI agent.
What does a fixed price actually fix?
A fixed price fixes the cost of an agreed scope. It does not fix the scope itself. If you want something the quote does not describe, the supplier can reasonably price it separately, so your real protection is a clear description of what will be built and a clear process for changes.
Fixed price suits work you can describe well in advance: a first version of an app, a defined integration, or a single agent doing one job. Where the requirements are still uncertain, ask for the first version to be scoped tightly and the rest left for a later quote, rather than a large fixed price built on guesses.
What should a fixed-price software quote include?
Use this checklist when a quote arrives.
| Item | What good looks like | Why it matters |
|---|---|---|
| Scope and deliverables | A written description of the features, screens, integrations and outputs | It is the thing the price buys |
| Exclusions and assumptions | What is not included, and what the supplier assumes you will provide | Many disputes start here |
| Price and payment stages | The total, what is paid when, and whether VAT is included | No surprises at each milestone |
| Timetable | Milestones and what each one depends on, including your own tasks | Delays on either side are easier to discuss |
| Testing and acceptance | How the work is tested, by whom, and what counts as done | Both sides share a clear finish line |
| Change process | How new requests are described, priced and approved before work starts | It keeps the fixed price fixed |
| Running costs | Hosting, licences, store fees, third-party services and AI usage | Some costs continue after the build |
| Ownership | Who owns the code, designs and data, plus any third-party components | Ownership is not automatic |
| Hosting and data | Where it runs, where data is stored and who can reach it | It matters for UK GDPR and for leaving later |
| Handover and support | Source code, documentation, admin access and what support covers after launch | You can change supplier if you need to |
Who owns the code when you pay for it?
Do not assume that paying for software means you own it. The Intellectual Property Office's guidance on ownership of copyright works says that when you commission a work, the first owner of the copyright is the person or organisation that created it, not you as the commissioner, unless you agree otherwise in writing. Someone working under a contract for services will usually keep the copyright in what they produce.
So the quote, or the contract that follows it, should say plainly whether copyright passes to you, whether you receive a licence instead, and what happens to reusable components the supplier brings to the job. Either arrangement can be fine. You just need to know which one you are getting. This is general information, not legal advice.
What if the supplier handles personal data?
If the software will store or process personal data on your behalf, such as customer records in a hosted app, the supplier is likely to be acting as your processor under UK GDPR. The ICO explains what a controller and processor contract must include. That means the subject matter, duration, nature and purpose of the processing, and the types of personal data and whose data it is. It also means terms on following your documented instructions, confidentiality, security, sub-processors, helping with people's rights, deleting or returning data at the end, and audits.
A quote will not contain all of that, but it should say where data will be hosted and confirm that a proper data processing agreement will be in place before any live data moves.
Questions to ask before you sign
- What exactly is out of scope, and what are you assuming we will provide?
- How will the work be tested, and what has to be true for us to accept it?
- How are changes priced, and does any change work start before we approve it in writing?
- What will this cost to run each month after launch, and who pays which bills?
- Who owns the code and designs once the work is paid for, and will we get the source code?
- Where will it be hosted, and where will our data be stored?
- What support is included after launch, and what does it cost after that?
- Which parts rely on third-party services, and what happens if their prices or terms change?
- Who will work on the project, and who is our main contact?
How do you compare quotes fairly?
Quotes for the same idea can look very different, and the lowest figure is not always the cheapest outcome. Put them side by side against the checklist above. A lower price with a short scope and a long list of exclusions may cost more by the time the software is finished. Count running costs over the period you expect to use the software, not just the build.
The simplest way to get comparable quotes is to give every supplier the same brief: who the users are, the main jobs the software must do, the systems it connects to, any dates that matter and how you will judge success. One or two pages is enough. For an AI project, our post on starting a first AI project explains what to put in that description, and the AI Project Planner kit helps you turn the idea into a one-page specification that suppliers can price.
How APPS 365 quotes
Every project starts with a free call, and work starts only after a written fixed quote. You get the price, the scope and the timetable in writing, with code ownership, hosting and data residency agreed in writing in the quote. For custom app development, each app is priced after a free call, and we talk through the running costs to expect before you commit. For AI work, custom builds are from £999, with a fixed quote after a call and monthly running costs on top. When your brief is ready, request a free quote with no obligation.
Talk it through first
If you would like help shaping your brief before you ask anyone for a price, book a free 30-minute call. There is no obligation, and you will come away knowing what to put in front of suppliers.
