You've decided to commission software, asked three teams for a proposal, and received three figures that look nothing alike. The highest may be several times the lowest, even though all three are for “the same app”. That rarely means one team is expensive and another cheap; it means they read the same sentence and understood different jobs. In this post we explain which items make up a proposal and how to compare proposals fairly.
Why the same app gets different prices
Take the sentence “We want a mobile app for booking appointments.” One team reads it as a single type of user, five or six screens and a simple calendar. Another adds staff accounts, online payment, reminders, cancellation and refund rules, and a panel where the business manages everything. Neither is wrong; they have simply priced different products.
Scope isn't the only source of the gap. One proposal includes design, testing and post-launch support, while another never mentions them. So before looking at the figures, ask first: what exactly is inside this price?
The items that drive the price
The cost of software depends largely on effort: how many people work for how many weeks. Each of the items below raises or lowers that effort.
- Scope: the number of flows matters more than the number of screens. A flow is the series of steps by which a user completes one task from start to finish, such as signing up, placing an order or requesting a refund. Every new flow means design, development and testing.
- Design: using a ready-made design template takes far less effort than drawing screens specific to your brand. The proposal should say who does the design and how many rounds of revisions you get.
- Integrations: every point where the software has to talk to another system. Examples are a payment provider, accounting software, a courier or your existing legacy system.
- Admin panel: the back-office screens where you manage products, users and orders. Customers never see it, so it is often forgotten, yet on most projects it is a considerable share of the work.
- Platforms: web only, or iOS and Android as well? On most projects both mobile platforms can be built from one shared set of code; even so, each platform needs its own testing and its own store submission.
- Testing: trials on different devices with scenarios close to real use. If it isn't in the proposal, either it won't be done or its time will be squeezed out of another item.
- Infrastructure and hosting: the servers the software runs on, plus backups and monitoring.
- Post-launch support: a bug-fix period, updates and small improvements.
A distinction often missed
The development fee is paid once; costs such as servers, the domain, store developer accounts and the payment provider's commission continue for as long as the product lives. If the proposal has no separate estimate of these recurring costs, be sure to ask.
Fixed price or a monthly team?
Proposals usually come in one of two models. With a fixed price, the scope is written down at the start and a single fee is agreed for that scope. With a monthly team model, a set team's effort is reserved for you month by month, and what gets built is decided together at the start of each period.
For clearly scoped projects we work at a fixed price and cost each phase separately in the proposal. If you know what you want and need to see your budget in advance, this model fits. For products that need ongoing development and whose direction shifts with user feedback, we use the monthly team model, because nobody can write down today what you will need in three months. A fixed price given while the scope is unclear wears both sides out: the team adds the risk of that uncertainty to the price, and you renegotiate with every change.
What a good proposal contains
A good proposal doesn't have to be long, but it should cover these headings:
- Written scope: the screens and flows to be built, item by item. It should also state plainly what is out of scope, for example content entry, translation or a second language.
- Phases, with a price for each: discovery, design, development, testing and launch on separate lines. That way you see where the money goes and can postpone a phase if you need to.
- Timeline: a week-by-week plan and what is expected from you.
- Ownership of what is delivered: who keeps the source code (the files the software is made of), the design files, the domain and the server accounts. This shouldn't be left to assumption; it should be written into the agreement.
- Change requests: how new wishes that come up mid-project will be priced and how they affect the timeline.
- Maintenance terms: how long is the bug-fix period after launch, and on what terms does support continue afterwards?
A proposal that doesn't say what won't be built hasn't fully said what will be built either.
Signs worth a closer look
Some proposals look attractive at first glance but leave the real cost for later. When you see one of the signs below, don't rule the proposal out straight away; ask a question first.
- A single total with no breakdown. If you can't see what each piece of work costs, you can't know what you are negotiating.
- No mention of testing or maintenance. This work doesn't disappear; either it isn't done, or it turns up later as a separate invoice.
- Vague scope. Phrases such as “a modern online store” or “all necessary features” let each side understand whatever it wishes.
None of these is, on its own, a sign of bad faith; some teams simply prefer a short proposal. What matters is that the missing detail is put in writing before you sign.
Comparing proposals fairly
Putting prices for different scopes side by side will mislead you. We suggest comparing in this order:
- 1
Write your own scope on one page: who will use it, what they will be able to do, which systems it connects to. Send that page, unchanged, to every team.
- 2
Put the proposals you receive into a table. Use the items from this post as rows and the teams as columns, and mark each cell “yes”, “no” or “unclear”.
- 3
For every unclear cell, ask the team concerned in writing and have the answer added to the proposal.
- 4
Look at the totals only once the missing items have been filled in. Part of the gap usually explains itself at this stage.
- 5
Discuss the remaining difference with the teams: look at similar work they have done, and ask how they work and how they will show you progress.
The last step looks less concrete than the figures, but it matters at least as much. We show progress not with a slide deck but with a working version, delivered at regular intervals, that you can try yourself; at the proposal stage, we suggest asking every team how they do this.
Lowering the cost sensibly
If your budget falls short of the proposal, the first instinct is to ask for a discount. But if the price drops while the scope stays the same, something has to give, and that is usually testing, care in the design or the time set aside for the work. You pay for it after launch, in bug fixes.
The healthier route is to shrink the scope, not the price. Limit the first release to the few flows that do the product's real job and move the rest to a second phase. Postponing the mobile app in favour of a responsive web version, or replacing advanced reports with a simple export button, are routes we take often. When each phase is priced separately these decisions become easier: you see directly how much you save by postponing a given item.
A question to ask the team
Ask: “What would be the most sensible first release on this budget?” The most useful answer is not a discount but a narrower scope, with an explanation of what has been postponed and why.
A short checklist before you sign
- Is the scope written item by item, and is what falls outside it stated?
- Are the price and delivery date of each phase shown separately?
- Do design, testing and launch appear in the proposal?
- Is there an estimate for recurring costs such as servers and third-party services?
- Is ownership of the source code and the accounts written into the agreement?
- Is it clear how change requests will be priced?
- Are the post-launch bug-fix period and the maintenance terms in writing?
- Does it say how often, and in what form, you will see progress?
The proposal that lets you answer “yes” to all of these may not be the cheapest, but it is the one where you know what you are paying for. We prepare our own proposals in the same order: first we pin down the scope together, then we price each phase separately.
