Is my app quote reasonable? How to compare software development quotes

Is my app quote reasonable? A quick test

A quote is reasonable if it falls inside the market range for its type of build and the vendor can show you the hours behind it. Start with the band. If your quote sits well outside it, find out which assumptions differ before you decide anyone is wrong.

Type of build	Published Australian range (AUD, ex GST)	What a quote in this band should normally cover
Simple app or MVP	$20,000 to $50,000	One core workflow, standard design components, a basic backend
Standard business app	$50,000 to $120,000	iOS and Android, login and roles, admin tools, one or two integrations
Feature rich platform	$120,000 to $250,000	Several user types, payments, several integrations, reporting
Simple internal software tool	$15,000 to $40,000	One team, one workflow, low sensitivity data
Mid complexity business system	$40,000 to $150,000	Customer portal, job management, quoting and invoicing

The app bands come from AppGurus’ 2026 guide and the software bands from Expeed’s 2026 guide. Wave Digital puts most production ready MVPs at $125,000 to $250,000 or more, which shows how much the definition of “MVP” moves the number. These are market ranges, not quotes, and our app development cost guide and custom software cost guide explain what pushes a project from one band to the next.

Then apply three checks:

1. Is the scope written down? If the quote is a single number with a paragraph of description, it isn’t comparable with anything.
2. Can you see the hours? Effort by feature or by phase lets you see where the money goes.
3. Is GST stated? Business quotes are usually ex GST. Add 10% to compare like with like, and ask your accountant whether you can claim it back.

Why do quotes for the same app differ so much?

Because each vendor is pricing a different app in their head. Rates in Australia sit in a fairly narrow band; the number of hours each vendor assumes does not. Conduct reports small and medium Australian agencies at about $123 to $330 an hour, while AppGurus puts typical local rates at $120 to $200. A tenfold gap in totals almost always means a large gap in assumed scope.

The usual sources of the gap:

• Backend and admin. A cheap quote may cover the screens a customer sees and nothing behind them. Someone still has to build the database, the API and the tools staff use to manage users, content and orders.
• Design depth. Template components cost far less than a custom design system with user testing.
• Integrations. “Connects to Xero” can mean pushing one invoice or a full sync with error handling.
• Testing. Conduct’s budget split puts quality assurance at 15 to 20% of a project. A quote with no testing line has moved that cost to you.
• Who does the work. Onshore, offshore or a mix, and how senior the people are. Our onshore vs offshore guide covers that trade off.
• Risk. A vendor quoting a fixed price on a vague brief adds contingency. A vendor quoting low on a vague brief may plan to recover it through variations.
• After launch. Warranty, hosting setup, app store submission and handover are included by some vendors and excluded by others.

What should a complete software quote include?

A complete quote lets you answer three questions without asking: what you get, what it costs in total, and what happens when something changes. Use this checklist on every quote you receive.

Item	What good looks like	Why it matters
Written scope	User types, main journeys, screens or features, integrations	Without it, the price has no anchor
Exclusions	A written list of what is not included	This is where most surprise costs hide
Assumptions	Who supplies content, data, API access, test devices	A broken assumption becomes a variation
Effort breakdown	Hours, days or cost by feature or phase	Lets you compare vendors and cut scope sensibly
Testing	Automated tests, manual testing, who tests on which devices	Untested code costs more after launch
Deployment	Environments, hosting setup, app store submission	Often missing from cheap quotes
Timeline and milestones	Dates or durations for each stage you can review	Gives you checkpoints before the next payment
Payment schedule	Payments tied to milestones	Keeps payment and progress in step
Change process	How new requests are priced and approved, in writing	Stops scope creep becoming bill creep
Warranty	A defined period of defect fixes after launch	Shows what is fixed without a new invoice
Ownership	When the IP is assigned and when the code and accounts are handed over	Decides whether you can move to another team later
Ongoing costs	Hosting, licences, store fees, support options	The build price is not the total cost

If a vendor can’t fill in a row, that isn’t always a deal breaker. It is a question to ask before you sign. Our contract checklist goes deeper on the ownership, warranty and liability rows.

What are the red flags in a software quote?

The biggest red flags are missing scope, payment that runs ahead of progress, and silence on ownership. Any one of these deserves a direct question. Three or more together usually means the quote isn’t comparable with the others.

1. No scope document. A price without a written scope is a guess you have agreed to pay.
2. The whole price upfront. Paying everything before work starts leaves you with nothing to hold back if delivery slips.
3. No IP or ownership clause. Under Australian copyright law the author owns the code by default, so silence favours the vendor. See who owns the source code.
4. No testing line. Either testing is hidden in other lines or it isn’t happening.
5. Vague items. “Integration”, “backend” or “admin panel” as a single line with a single price, and no detail.
6. Hourly billing with no estimate or cap. That is time and materials with none of the controls that should go with it.
7. No warranty. If defects found after launch are billed as new work, the vendor has no reason to test well.
8. A price that drops sharply when you push back, with no change in scope. It suggests the first number wasn’t built from the work.
9. The vendor keeps the accounts. Domains, hosting, app store listings and databases should be registered to you.
10. One sided terms. Since 9 November 2023, the ACCC says unfair terms in standard form contracts are banned for small businesses with fewer than 100 employees or under $10 million in annual turnover. Its examples include terms that let only one party end the contract or limit its responsibilities.

None of this proves a vendor is acting in bad faith. Some good small teams simply write thin quotes. The fix is the same either way: ask for the missing pieces in writing.

Which questions expose missing scope?

Ask questions that force the vendor to describe the work, not the price. Their answers tell you what they assumed and how well they understood your business.

• Walk me through what a customer does from opening the app to finishing the main task. What did you assume at each step?
• Who manages users, content and orders, and through what screens?
• What exactly does the integration with our existing system do, in which direction, and what happens when it fails?
• How many hours have you allowed for testing, and on which devices?
• What will we need to pay for each month after launch?
• What is excluded from this price?
• What happens if we ask for a change halfway through?
• Who will write the code, and can we meet them?
• When does the code become ours, and when do we receive the repository and every login?

A vendor who answers quickly and specifically has usually built something similar before. A vendor who says “we’ll work that out later” is telling you the price will change later too.

How do you compare quotes like for like?

Write one scope, send it to every vendor, then score the responses with weights you set before you open them. Setting the weights first stops the lowest total from deciding the outcome by default.

Copy this matrix. Score each quote from 1 to 5 on each row, multiply by the weight, and add up the totals.

Criterion	Weight	What a 5 looks like
Scope coverage	25%	Every feature in your scope is priced, with exclusions listed
Total cost over two years	20%	Build plus hosting, licences and support, all stated
Delivery risk	15%	Milestones you can test, payments tied to them, a realistic timeline
Ownership and exit	15%	IP assigned as paid for, clear handover of code and accounts
Team and evidence	15%	You’ve met the people doing the work and seen comparable work
Quality practices	10%	Testing, code review, security checks and a warranty described

A worked example (hypothetical vendors and figures). A business sends one scope for a booking app to three vendors.

	Vendor A	Vendor B	Vendor C
Quoted build price (ex GST)	$38,000	$96,000	$165,000
What the quote covers	Customer screens only; admin and integration excluded	Customer app, admin portal, payment and calendar integration, testing, 30 day warranty	Same as B, plus a custom design system, discovery workshops and six months of support
Weighted score out of 5	2.3	4.2	3.9

Vendor A looks cheapest, but adding the excluded admin portal and integration through a second vendor would likely push the total past Vendor B. Vendor C is the most complete, and if the business needs the six months of support anyway, its real gap to B is smaller than the headline. Vendor B wins on these weights; a business with a bigger brand budget might reasonably weight design higher and pick C.

The point of the matrix isn’t precision. It makes the trade offs visible, so you choose deliberately.

When is the cheaper quote the right one?

The cheaper quote is the right one when it covers your actual scope and the vendor can show how they’ll deliver it. Low price isn’t a red flag on its own.

It is often the right call when:

• The job is small and clearly defined, such as one internal tool for one team.
• You’re testing an idea and plan to rebuild once it proves demand. Our MVP cost guide covers how to cut scope sensibly.
• The vendor has built the same kind of thing before and can reuse proven parts.
• A freelancer or small team suits the work and you have someone on your side to manage it. The freelancer vs agency guide sets out when that works.
• An existing SaaS product or low code tool covers most of the need. Sometimes the cheapest quote is a subscription, not a build.

It is usually the wrong call when the low price comes from excluding work you need, from fixed pricing on a vague brief, or from terms that leave the vendor owning your code.

How AWLabs quotes

We don’t quote a fixed price from a brief alone. The first step is a Development Consult, a 15 minute phone call or a Zoom with Andy, to understand what you need. If it makes sense to go further, a paid Discovery Audit maps the workflows, integrations, data and risks; its fee is credited in full against the build. From that we write a Schedule of Work with three fixed price options, The Minimum, The Recommended and The Complete, each listing scope, exclusions, assumptions, milestones and the payment schedule, so you can see exactly what changes between them. Senior engineers lead every build, you get updates every Tuesday and Friday (Sydney time), and the code is assigned to you as each part is paid for, with the repository and accounts handed over after final payment. A 30 day warranty applies after launch, then an optional Care Plan.

If you already hold quotes from other vendors, the matrix above works for ours too. See how we work or our custom software development service.