The number an agency quotes you is not a price. It’s a forecast, dressed up as a price. Understanding that distinction before you sign anything will save you tens of thousands of dollars and a significant amount of grief.
We quote projects every week. We also lose projects to competitors who quote lower – and occasionally we watch those same founders come back six months later, out of runway, with half a product and a sour relationship with a dev team. This post is about why that happens and what to do differently.
How Agencies Actually Build a Quote
Every agency starts with a feature list, breaks it into tasks, estimates hours per task, adds a buffer, and multiplies by a day rate. That part is consistent across the industry. What varies wildly is how honest each step is.
Day rates for Australian software teams run from roughly $1,200 to $2,200 per day depending on seniority and specialisation. AI and data engineers sit at the top of that range. A junior-heavy offshore-augmented team might quote $800, but that’s a different conversation – one we’ve written about separately.
The buffer is where things get interesting. A reputable agency adds 20-30% to account for integration surprises, scope creep in discovery, and the inevitable “can we just add one thing” conversations. An agency that’s hungry for the work might add 10% or quietly skip it entirely. That missing buffer doesn’t vanish – it reappears as a variation order halfway through the build, or as rushed work that creates technical debt you’ll pay to fix later.
When we scope a project at Amora, our estimates include discovery time as a billable line item, not a freebie. If an agency is offering you a detailed estimate for free after a 45-minute call, ask yourself what it’s actually worth.
Fixed Price vs Time and Materials: The Real Question Behind the Question
Founders usually ask “which is better?” The honest answer is: it depends on how well-defined your scope is, and how much risk each party is willing to carry.
Fixed price transfers scope risk to the agency. That sounds great until you realise the agency prices in that risk – often adding 25-40% on top of their T&M estimate to cover unknowns. So you’re paying for certainty. If your scope is genuinely tight and you’ve done discovery properly, that premium might be worth it for budget predictability. If your scope has gaps – and most do – you’ll hit change requests anyway, and the certainty you paid for evaporates.
Time and materials gives you flexibility but requires discipline. You need to set a budget ceiling, check velocity weekly, and be willing to have hard conversations about prioritisation. Founders who treat T&M like a blank cheque end up exactly where you’d expect.
For most of the projects we ship – particularly MVPs – we prefer a hybrid: a fixed price for a defined discovery and scoping phase (usually $8,000-$15,000 AUD), followed by T&M with a capped budget for the build. Discovery almost always changes the scope anyway. Locking price before it is finished is optimistic at best.
The Line Items That Should Scare You
When you receive a quote, these are the things worth interrogating:
- “Design” as a single line item. Does that mean wireframes, a design system, responsive breakpoints, and component specs for the developers? Or does it mean a few pretty Figma screens that the dev team will interpret however they like? These are not the same thing, and the difference in build quality is significant.
- QA and testing bundled into development. Dedicated QA is a separate effort. If it’s not a separate line, either it’s not happening or it’s being absorbed into developer time – which means less of both.
- “Deployment” as a half-day task. Standing up a production environment properly – environment variables, secrets management, CI/CD pipeline, monitoring, alerting – takes time. A half-day estimate is a red flag that corners will be cut.
- No line for third-party integration testing. Every Stripe, Xero, HubSpot, or AWS service you connect to adds integration surface. That surface breaks. Budget for it explicitly.
- Ongoing costs missing entirely. Hosting, database, CDN, email delivery, LLM API calls if you’re building AI features – these compound quickly. A fintech we scoped last year was projecting $400/month in infrastructure; the real number, once we mapped their data volumes and API call patterns, was closer to $1,800/month at modest scale.
What Discovery Actually Buys You
Paid discovery is not agencies extracting money before the real work starts. Done properly, it is the single highest-ROI phase of any software project.
In a proper discovery engagement you should get: a finalised feature set with acceptance criteria, a data model and system architecture diagram, an API map showing every integration and its authentication pattern, a UI prototype or wireframe set, a prioritised backlog, and a properly buffered estimate. That package typically costs $8,000-$20,000 AUD depending on complexity.
What it gives you is leverage. You can take those artefacts to two or three agencies and get comparable, apples-to-apples quotes. You own the IP. If the first agency relationship doesn’t work out, you’re not starting from scratch. And you’ll build better – because the team isn’t solving architecture problems while simultaneously writing production code under time pressure.
The mistake we see most often is founders skipping discovery to “save money” and then spending three times as much unpicking decisions made too early. If an agency tells you discovery is unnecessary, they either don’t know your domain well enough to know what they don’t know, or they’re quoting from assumptions they haven’t stress-tested.
How to Compare Quotes When the Numbers Look Nothing Like Each Other
If you’ve sent the same brief to three agencies and received quotes of $45,000, $90,000, and $160,000, the problem is not that one of them is right and the others are wrong. The problem is that all three agencies scoped different projects.
Before comparing numbers, normalise the scope. Ask each agency to tell you explicitly what is and isn’t included. Then build a simple comparison table:
- Feature set – are the same features in scope?
- Design fidelity – wireframes or pixel-perfect UI?
- Testing – unit, integration, end-to-end, manual QA?
- Deployment – who sets up production infrastructure, and what does it include?
- Handover – do you receive a code repo, documentation, runbook?
- Post-launch support – is there a warranty period, and what does it cover?
Nine times out of ten, the cheapest quote is missing two or three of those categories. That doesn’t mean the expensive quote is better – it means you now know what questions to ask.
What “28 Days to MVP” Actually Means in Cost Terms
We ship MVPs live in 28 days. That constraint is real, and it forces a discipline that most teams benefit from – but it does not mean a 28-day project costs less than a three-month one.
What it means is that scope is ruthlessly constrained. We spend real time in scoping deciding what the MVP is not. A 28-day build has a tighter feature set, more opinionated technology choices, and less room for bespoke design. It also requires a founder who is available, decisive, and prepared to make calls quickly when they come up – because they will come up.
For a typical SaaS MVP – authentication, a core workflow, basic admin, Stripe billing, and deployment – you’re looking at $35,000-$65,000 AUD with a team that knows what they’re doing. AI-native products with LLM integration add $15,000-$30,000 on top of that, depending on the complexity of the agent or RAG architecture involved. Anyone quoting you an AI SaaS MVP for $15,000 all-in is either doing very little or handing it to a junior who’s going to figure it out as they go.
If you’re at the point of getting serious about what your build should actually cost and what’s worth prioritising, talk to Amora about your build – we’ll tell you what we’d actually scope, not what sounds good in a sales call.
The founders who get good outcomes from software projects are not necessarily the ones with the biggest budgets. They’re the ones who understand how the estimates are built, ask the right questions before signing, and treat discovery as an investment rather than a delay. That knowledge is genuinely protective – and almost nobody gives it to you for free.
Got something you want built?
Amora Digital is an Australian software and AI agency. We scope it, build it, and ship it – live in 28 days. No offshore teams. No surprises.