When it comes to the contract structure you sign for an Australian app build, one thing determines everything else: who absorbs the cost when the project does not go according to plan. With fixed-price, the risk sits with the agency. With time-and-materials, it sits with you.
That is how it’s presented, and it would seem that fixed-price is a clear winner. It isn’t, not always. Time-and-materials is the only option that can truly offer you flexibility in a project when requirements are still in an early stage, and will continue to evolve over time – particularly in the MVP phase.
We’re not that neutral for most of our Sydney and Melbourne assignments; we are fixed price, so we’re not that unbiased. But we’ve experienced the same thing when the fixed-price was the wrong approach or in projects where it was the right approach, but the scope of the job had shifted from what they initially requested.
This guide tells you the truth about both models: when each is the right one, what each one is really worth in the Australian market, how the hybrid model that’s now the industry standard is the best of both worlds, and a table of pros and cons of each model based on project and situation.
Fixed-Price vs Time-and-Materials: The Core Difference in One Paragraph
Fixed-price: the scope of work, the price and the time are agreed in advance of the development process. Price will not change until scope changes. The agency takes the hit for over-estimating the job, you take the hit of changing the scope. The risk lies with the agency.
Time and materials (T&M): charges are based on the hours of work at a predetermined rate. Requirements are evolving, scope can change, features are being added and priorities change all without formal change orders. When you sign, you have no idea of what the final cost is going to be. Risk sits with you.
The third model is hybrid: a fixed-price for the initial defined build (your MVP or version one) and then a T&M retainer for post-launch iteration. This has become the industry standard for app projects in Australia of less than $300,000 (Bolder Apps, June 2026).
The rest of this guide goes through when each model is suitable, how much each model costs in Australia and how one actually selects the model.
Fixed-Price App Development in Australia: The Honest Case For and Against
The case for fixed-price:
Budget certainty. Ceiling is known before development begins. For small businesses, startups who are on a funding runaway or enterprises having a locked budget, that certainty has a great commercial worth.
The agency is responsible for the risk. If they don’t realize how complicated it is to integrate, or how many design iterations it takes, or how much time is spent in the QA process, that’s on them. When it comes to T&M, all of those underestimated turns into an invoice for you.
It encourages correct scoping. If you’re in a studio that has a fixed price, they have a real monetary incentive to scope your project before they begin. A studio that skips discovery under a fixed-price contract bears the consequences — which is exactly the incentive structure that produces better upfront requirements and ultimately better software. which in turn generally results in better front-end requirements and ultimately better software.
The criteria for accepting are established. You don’t have to pay for hours if nothing that is paid for actually gets delivered, because the acceptance criteria are defined at each milestone with a fixed-price contract.
Better IP and time accountability. Of course, there is a downside to the Fixed-price option: these are the milestone-based payment structure, time-bound deliveries, and more definite IP transfer points. If your goods are not delivered in accordance with the contract, you have stronger statutory guarantees to make if it is a fixed price contract with defined acceptance criteria, under the Australian Consumer Law. For Sydney-specific rate context across fixed-price engagements, our Sydney app developer guide covers what discovery costs, what blended agency rates look like, and how fixed-price is structured from our Barangaroo studio.
The case against fixed-price:
Contingency adds to the quote. As Website Builder Australia stated earlier this May 2026, fixed price quotes tend to incorporate contingency components, as the builder has to safeguard themselves against uncertainty. The buffer (usually 10-20% over the estimate) is a risk premium that you are paying now, regardless of whether the risk eventuates or not. For a breakdown of what Sydney agency rates actually include and why the contingency buffer exists, our Sydney app developer rate guide covers the billing formula from our own studio data.
The cost of scope changes is high and it takes time to make changes. If something you don’t agree on the scope of work, it should be a change order, documented, repriced, signed off on by you before it happens. If the requirements are truly expected to change, an early MVP helps, a new idea is great, an integration with third parties that is complex and unpredictable is a liability, and the friction really hurts the product.
It is not a good fit when the scope of the project is truly ambiguous. Has a fixed price requirement for a scope that is truly measurable. As long as you can’t tell me enough about what you are creating to give me a fair price, a fixed-price quotation is just a piece of fiction. Or you have to pay for the conservative estimate, or you have to pay for the variations from the aggressive estimate.
Can misalign incentives on complex projects. For a large and complex build, a studio that is bound to a fixed price may be more focused on delivering to the scope than delivering what the project really needs. The desire to complete what was set is able to overpower the urge to identify gaps during the project.
Time-and-Materials App Development in Australia: The Honest Case For and Against
The case for time-and-materials:
It’s right for genuinely uncertain scope. Early-stage MVPs where user research will shape the feature set, AI and ML projects where integration complexity genuinely isn’t knowable until you hit it, complex enterprise integrations with third-party systems whose behaviour can’t be fully specified upfront, T&M is the honest contract for work that can’t honestly be fixed-priced.
Saigon Technology’s 2026 analysis put it well: fixed-price works best when requirements are stable, and T&M suits situations where change during development is expected. For agile projects where the product vision will genuinely evolve alongside user feedback, T&M gives you room to pivot without the friction of formal change orders.
There is no hidden contingency in the rate. The rate is an hour rate – end of story. No hidden risk premium getting added on before the job starts. If your project goes quicker than you thought it would, you are going to pay less.
Very suitable for after-launch tasks. Once launched, the work is truly open-ended and priorities regarding features change according to user behavior, competitor actions, and market cues. T&M retainers work well during this stage and this is the way most studios have their continuous post launch work anyway.
Clear reporting of the use of team time. With T&M you can view exactly what hours went where. There are even clients, especially technical, who prefer visibility over the black box of a fixed-price engagement.
The case against time-and-materials:
Final price is not guaranteed. Australian T&M invoices end up 30-80% higher than the initial estimate (Bolder Apps, June 2026). That original figure was not a promise, it was a forecast and a forecast is unreliable. The structural reasons why both T&M and fixed-price projects exceed initial estimates — and the full 3-year cost of ownership model — are covered in our hidden costs guide.
It’s up to you to scope the discipline. With T&M, scope control is yours. All billed hours are considered to be authorised hours. Without an active involvement in scope, the engagement will become “off track”, and that means a level of involvement and project management that a lot of non-technical founders just don’t have.
It is possible for completion incentives to misalign. T&M means the studio is paid for the hours, whether they are good or bad. Even if the studio has a good client-service culture, it will still be efficient. One that doesn’t have that culture doesn’t have to worry much about inefficiency financially. The structural risk that is inside T&M is that misalignment.
Australian Consumer Law makes it more difficult to enforce. A T&M engagement is significantly more difficult to dispute under Australian Consumer Law if the output quality is poor. if the quality of the work produced isn’t good, since there aren’t any specific acceptance standards, or an exact deliverable. If the result is not what you’d hoped for, it’ll be much more difficult to determine whether it’s a breach of the Australian Consumer Law if you’ve paid for hours of work as opposed to a fixed-price deliverable and acceptance criteria.
Fixed-Price vs Time-and-Materials: Full Comparison for Australian App Development Projects
FULL COMPARISON:
| Factor | Fixed-Price | Time-and-Materials |
|---|---|---|
| Budget certainty | High, total spend known before signing | Low, final cost unknown at signing |
| Who absorbs scope risk | Agency | Client |
| Scope flexibility | Low, changes need formal change orders | High, changes absorbed naturally |
| Right for stable requirements | Yes | No, overpriced for stable work |
| Right for uncertain/evolving requirements | No, contingency inflates cost | Yes, honest for unknown scope |
| Incentive for accurate scoping | High, agency bears underestimation cost | Low, hours are billable regardless |
| Contingency buffer in price | Yes, 10–20% typical | No |
| T&M final cost vs estimate (AU 2026) | n/a | 30–80% above estimate average |
| Fixed-price final cost vs quote (AU 2026) | 10–25% above at signing, then fixed | n/a |
| Right for agile/MVP with unknown scope | No | Yes |
| Right for defined-scope build | Yes | No, no ceiling, no incentive to complete |
| Post-launch ongoing work | Usually T&M retainer | Natural fit |
| Australian Consumer Law protection | Stronger, defined acceptance criteria | Weaker, hours-based delivery |
| IP assignment clarity | High, milestone-based handover | Medium, ongoing delivery |
| Privacy Act 2026 compliance scoping | Should be explicit in discovery | Must be raised as a change if not scoped |
| Recommended for non-technical founders | Yes, removes scope management burden | No, requires active scope discipline |
| Recommended for technical CTOs | Yes, for defined builds | Yes, for exploratory builds |
| 2026 industry default for MVP builds | Fixed-price discovery + fixed MVP build | T&M retainer for post-launch iteration |
The Hybrid Model: Why Fixed-Price Discovery + Fixed MVP Build + T&M Retainer Has Become the 2026 Default in Australia
The argument over fixed price versus T&M is becoming somewhat of an either/or proposition. Projects that are less than $300,000, especially in Australia, often have a hybrid model that is being adopted as the industry standard.
Phase 1, fixed-price discovery ($5,000–$15,000, 1–2 weeks). All projects begin here. Documented requirements, tech selection, integration mapping, UX research, and an accurate cost assessment of the actual build. Fixed price due to clear, concise, and well-defined deliverable; fixed timeline due to two well-focused weeks of discovery being estimable. What is produced: scope document, technology recommendation, week-by-week delivery schedule, and a solid price for the phase two. This is exactly what our product planning service delivers — scope document, technology recommendation, Privacy Act compliance assessment, and a fixed-price commitment for Phase 2, before any development begins.
Phase 2, fixed-price MVP build ($30,000–$200,000, 8–22 weeks). Discovery’s already identified integrations, edge cases and complexity drivers and now there’s a precise spec for the scope. The fixed price here is the truth, not an estimate. You absorb the risk of underestimation, you absorb the cost of scope changes, and if there is a scope change, it is dealt with via a formal change order process for which the price is agreed prior to the change.
Phase 3, T&M retainer ($9,000–$20,000/month, ongoing). But once launched, the work is truly open-ended. The priorities of the features change in response to user behavior, analytics, and competitive factors. The main reason for using T&M in that situation is that scope was not originally unclear, but because it is actually changing according to the actual signal.
The two phases of a custom app project have fundamentally different scope properties — and the hybrid model addresses this directly (Bolder Apps, June 2026). The MVP launch is scopeable. Post-launch iteration is not. Applying the same contract structure to both mismatches the contract to the work.
A real Australian example:
Let’s say for instance you’re building a platform for matching patients with practitioners, like our HealthMate project with Melbourne healthtech.
Phase 1, Discovery, $10,000 (2 weeks): delivers a Scope Document, Privacy Act compliance map, FHIR integration spec and a fixed price for Phase 2.
Phase 2: $95,000 (16 weeks) Fixed-Price MVP Build – iOS, Android, Backend API, three integrations and a Privacy Act compliant Privacy Policy Architecture. The price was determined after Phase 1.
Phase 3: T&M retainer, $12,000/month: Post launch feature work as per Practitioner feedback, Analytics and Marketplace expansion. The scope is dynamic and changes month by month according to its usage.
Total for Phases 1 and 2: $105,000 – fixed and predictable. Phase 3 is of course vary by usage and growth decision, flexible and appropriate. HealthMate was built from our Collins Street studio. For a full picture of Melbourne rates, discovery costs, and the R&D Tax Incentive that can reduce effective Melbourne build costs by up to 43.5%, our Melbourne app developer guide covers both in detail.
What Fixed-Price and T&M Mean Under Australian Contract Law
The distinction between these two structures is not just a legal or mere theoretical issue as far as Australian law is concerned.
The Australian Consumer Law (ACL) and Fixed-price. Services should be provided with reasonable skill, care and time, and be suitable for the purpose. A fixed price contract with clear acceptance terms and a specified number of milestones provides clear contractual basis for challenging delivery that falls below spec and clarity of statutory guarantees as per ACL Part 3-2 (as compared to T&M contracts).
Legally assigning IP rights in Australia. On payment under Australian law, IP does not automatically pass to you: it must be assigned to you. (This was covered in part 1 of this series). A naturally occurring sign-off point, and final payment, in the context of a fixed-price contract are the points in time at which IP is handed over. In T&M contracts, it is more important to draft the IP explicitly because there are no milestones for delivery.
The validity of the change order process and change order. It is not a legally binding variation under Australian law to approve a scope change verbally as opposed to on paper and before implementation, in Fixed Price. Obtain a written sign-off from the change management process in your studio before further work begins.
The December 2026 Privacy Act angle. If your app uses automated decision-making, APP 1.7–1.9 compliance must be scoped as a discovery deliverable — not discovered mid-project as a T&M variation. Ask your studio directly: ‘Is the December 2026 Privacy Act compliance scope included in your discovery deliverables?’ For the full budget and timeline impact of the December 2026 changes by industry, see our Privacy Act 2026 app development guide.
Which Contract Structure Is Right for Your Project? The Decision Matrix
Here’s the matrix we actually use when advising Australian clients on contract structure, covering the most common project types and buyer profiles.
DECISION MATRIX BY PROJECT TYPE:
| Project type | Recommended structure | Reason |
|---|---|---|
| MVP with well-defined features | Fixed-price (Phase 2) after fixed-price discovery (Phase 1) | Scope is knowable after discovery |
| MVP with uncertain/evolving requirements | T&M with weekly or fortnightly billing | Scope will change, fixed-price contingency wastes budget |
| Mid-complexity consumer app | Hybrid, fixed-price build + T&M retainer | Build is scopeable; post-launch is not |
| Enterprise platform with complex integrations | Hybrid with phased fixed-price milestones | Breaks large undefined scope into scopeable phases |
| AI-integrated app with custom ML | T&M for the AI/ML phase; fixed-price for the app shell | ML complexity is genuinely unknown until encountered |
| Fintech / healthcare (compliance-heavy) | Fixed-price with explicit compliance scope in discovery | Compliance scope must be known before price commitment |
| Post-launch feature development | T&M retainer | Scope evolves based on user behaviour, T&M is correct here |
| App redesign or UX refresh | Fixed-price after design discovery | Design scope is definable; fixed-price is honest |
| Legacy app migration | T&M, or phased fixed-price if an audit’s been done first | Hidden complexity in legacy systems makes fixed-price risky |
| Non-technical founder, first app | Fixed-price after discovery | Removes scope management burden; provides accountability |
| Technical CTO, defined backlog | Either, CTO can manage T&M scope effectively | Both work; fixed-price preferred for budget predictability |
The pattern here’s pretty consistent: fixed-price fits when scope is genuinely knowable, T&M fits when it genuinely isn’t. The most common mistake is applying fixed-price to unknowable scope (which inflates contingency or triggers mid-project variations), or applying T&M to knowable scope (which produces open-ended billing with no real incentive to finish). When in doubt, the hybrid model, fixed-price discovery to make scope knowable, then a fixed-price build, turns genuinely uncertain scope into scopeable scope before any price gets locked in. For Melbourne-specific cost context across both fixed-price and T&M structures, our Melbourne rate guide covers blended agency rates, project cost by type, and the R&D Tax Incentive calculation from our Collins Street studio.
What Every Australian App Development Contract Should Include — Regardless of Fixed-Price or T&M
Regardless of what model you choose, fixed-price, T&M, or hybrid, be sure to include the following in your contract.
Fixed-price contracts: A clearly written scope document (which is incorporated by reference), milestone-based payments with each milestone having acceptance criteria attached, a written change order process (verbal is not sufficient), a fixed delivery time with milestone dates, a written post delivery defect liability period (typically 30 to 90 days) and a scope that complies with Privacy Act APP 1.7-1.9, if applicable.
For T&M contracts: agreed hourly rate or fortnightly/monthly rate per role, itemised (PM, developer seniority, designer, QA), agreed on a billing cycle (weekly/fortnightly, too long to properly oversee scope, monthly’s too much), clear notice period to end engagement, defined process to introduce scope changes and prioritise them, etc.
Both: Australian jurisdictional dispute resolution (NSW or VIC, depending on studio location), a clear superannuation and tax obligations process (which is assigned to the studio), a defined team composition and named roles (not our experienced team), and clear access to source code and source code handover process.
Knowing what should be in the contract is half the work. The other half is knowing how to evaluate whether the studio in front of you will actually honour it. Our guide to finding a trustworthy Australian app developer covers the verbatim interview scripts, proxy evaluation framework, and Australian legal checklist for non-technical founders.
Fixed-Price or T&M? The Honest Recommendation for 2026
When it comes to app development for Australian projects in 2026, the combination of fixed price and T&M is the correct choice – not just one or the other.
Fixed-price discovery leads to scope knowability. Fixed price build provides certainty of cost for the most costly and riskiest part of the project. The T&M retainer provides you with true flexibility in the stage where you don’t have a definite end.
When deciding whether to go with a studio that has a set price or a studio that is all T&M, here’s the truthful way to make the decision:
When to go fixed price: Your scope of work is clearly understood, it is stable, you are a non-technical founder who can’t actively manage the scope of the T&M, your budget has a hard cap, or you’re in an industry where you must be compliant and have defined acceptance criteria that you can’t actively manage yourself.
Use Go T&M when: your requirements are truly not known and will change as users provide feedback; you have the technical capability to actively manage scope yourself; your project has an AI or ML element with unknown complexity; you are in a post-launch iteration phase.
The warning sign either way: a 30 minute brief that was turned into a quote in 24 hours is not a fixed price quote, it is just a guess that has a max price. A T&M engagement with no monthly spend cap and no sprint review cadence is not a flexibility tool — it is open-ended billing with no accountability structure.
To explore how our app development team structures fixed-price engagements for Sydney and Melbourne projects — including what a discovery phase produces and what fixed-price means in practice — book a free consultation from either studio.
Fixed-Price vs Time-and-Materials App Development — FAQ
Q1: What is the difference between fixed-price and time-and-materials app development in Australia?
With Fixed-Price, scope, cost, and timeline are agreed prior to development, the price doesn’t fluctuate unless there is a scope change, and the agency takes the risk of under estimating. Time-and-materials: hours worked are paid at an agreed hourly rate, scope may change as desired, pricing is not known at the time of the contract, and it is the contractor’s responsibility to absorb the budget risks. The big distinction is actually whose neck it falls on if the scope of work goes out of hand – agency or the client.
Q2: Is fixed-price or time-and-materials better for app development in Australia?
Neither’s universally better. Fixed-price is for those who have defined requirements and stability, typically following a suitable discovery process. T&M is suitable where requirements are inherently ambiguous, as is common with an MVP in early stages or feature development after launch, and should be flexible to user feedback. Australian projects that involve a fixed-price project for the defined build followed by a T&M retainer for the post-launch iteration are the norm for projects under $300,000 for 2026 (Bolder Apps June 2026, Software Co project data 2026).
Q3: What is the average percentage of overrun for T&M projects in Australia?
The average T&M final invoice is 30-80% higher than the initial estimate (Bolder Apps, June 2026). That was never a promise, that was just an estimate. Fixed-price quotes are usually quoted 10-25% higher at signing to cover contingency but guarantees an end result of the price. Fixed price, in general, proves to be the total-cost-cheaper option for projects that are relatively simple in scope over the entire project life cycle.
Q4: What is Hybrid App Development?
It is a fixed-price for the defined-scope build with a T&M retainer for the iterations after the build. The structure involves fixed pricing for discovery (1-2 weeks at $5k to $15k) to make scope known, and then a fixed pricing for the MVP build (8-22 weeks), once scope is known, then a T&M retainer ($9k to $20k/month) for any post-launch work. It’s now the default for Australian projects below $300,000, as it reflects the true difference between each of the project’s phases.
Q5: Does “fixed price” make sense for an MVP?
It’s right for an MVP if the scope has been properly defined through a structured discovery phase first. If there’s no discovery, it’s basically a wild guess, but the studio adds a buffer on the unknowables so that they can charge 10–20% more. Once discovered correctly, the scope can be known and honest is really honest. If the requirements of MVPs are truly unpredictable and are going to change as users provide feedback, then T&M may be a more straightforward contract to adhere to, you are paying for flexibility instead of a contingency for flexibility that you will need anyway.
Q6: What should a fixed-price app development contract include in Australia?
It should include: A well defined scope of work that is incorporated by reference, Milestone based payment with acceptance criteria against each milestone, A written change order process (oral is not acceptable in Australian Law), A fixed delivery schedule with Milestone dates, Explicit IP assignment on delivery, Post delivery defect liability period (usually 30-90 days), Screen for compliance with the Privacy Act APP 1.7-1.9 if it’s an app that carries out automated decision making. Unlike T&M contracts, fixed-price contracts with defined acceptance criteria result in the activation of statutory guarantees under the Australian Consumer Law with greater certainty.
Q7: Under what circumstances would T&M be a good option for an Australian App project?
Where there is real uncertainty about requirements and they will change as you receive feedback from users (e.g., early MVPs, features based on AI/ML, where you’re not sure how it will be integrated into the project), when you have the technical ability to monitor scope and ensure that there is no drift in your billing streams, when the project is in the post-launch phase and priorities shift due to user behaviour, or when you are dealing with a legacy app migration where there is a hidden amount of complexity and you do not know how to estimate it accurately at the outset. For defined scope builds, where a completion incentive is not guaranteed and there is no bill limit, t & m on scopeable work will lead to unnecessary cost overruns.
Q8: Does the new Privacy Act in December 2026 impact the way contracts are drafted?
Yes. If, for example, your app requires automated decision-making (credit scoring, health triage, personalised recommendations, dynamic pricing), then your fixed priced discovery deliverables should explicitly include the Privacy Act APP 1.7 – 1.9 compliance scope or it will surface as a T&M variation mid-way through your project. When the discovery is being done under a fixed-price contract, inquire directly if the scope of compliance for December 2026 is part of the discovery deliverables. If it’s a T&M contract, make it a defined sprint in the early stages of the engagement, before general development.