May 6, 2026 • 18 min read
Dean Loader
Presenting a construction quote in 2026 isn't just about what you write — it's about whether the client trusts the number when you walk them through it. Builders who present quotes well win at higher rates than those still emailing PDFs. Here's how to do it properly for Australian residential work, written by someone who's done it for 25 years.
Most builders think presenting a quote means typing it up, exporting a PDF, and emailing it across with a "let me know if you have any questions". That's not presenting. That's sending.
Presenting a quote is the moment you sit with the client — in their kitchen, on a video call, or with a screen between you on a tablet — and walk them through what they're paying for and why. It's where you handle the questions they'd never type into a reply email. It's where the deal is actually made or lost.
The mistake plenty of builders make is treating the quote document as the conversation. The document is the artefact. The presentation is the conversation. The two are different jobs, and they need different thinking.
In 2026, the gap has widened. Tools have changed. Clients expect more. The builder who hand-delivers a printed quote on letterhead can still win a job if the work and the conversation are right — but they're going to find that more clients than ever are quietly comparing them to the builder down the road who sent an interactive proposal the same afternoon and is already in their inbox following up.
A construction client looking at a quote is doing two things at once: they're checking the number, and they're checking the builder.
The number tells them about the job. The presentation tells them about you.
If your quote is a thrown-together PDF with the wrong margin on the cover page, vague line items, no validity date, and an "all prices include GST" note jammed at the bottom — they're not just questioning the quote. They're questioning whether you'll run their build the same way. The presentation is a sample of how you work. Clients know that, even if they don't say it.
A quote that's clearly laid out, easy to navigate, with explicit GST handling and dated allowances tells the client they're dealing with a builder who treats their money with the same care they'd treat the work. That's a trust signal. It costs nothing to do well.
The flip side is also true. A quote that looks expensive to produce — polished web format, embedded images of similar past work, structured pricing the client can actually navigate — signals professionalism before they've read a single line item. They aren't paying for the quote. They're paying for the impression that the build will be run the same way.
business.gov.au's guidance on quoting puts it simply: a good quote is "clear, specific and complete." Australian residential clients have specific expectations around quotes, and there are some compliance baselines that apply whether you like them or not. Get these right and the client takes you seriously before you've talked price.
The non-negotiables for an AU residential quote: your ABN and registered business name (not just a trading name); the client's full name and project address; a date issued and a valid-until date — typically 14–30 days for residential work, beyond that you're carrying material price risk; a clear scope summary so the client doesn't have to reverse-engineer it from the line items; GST handling that's explicit, not buried — show line items ex-GST, total ex-GST, GST as its own line, and total inc-GST (don't hide GST in fine print and hope nobody asks); and a quote number for your records and theirs.
Lump sums hide assumptions. Line items expose them. For a kitchen renovation, line items are usually the right call — each trade or category becomes a row, the client sees what they're paying for, and you have a clean reference if there are variations later. For a small job under $20k, a clear lump-sum with a one-paragraph scope can be cleaner. The choice depends on the job, but err toward line items when the project value or complexity is meaningful.
These are where quotes go wrong if you're not careful. An allowance is "I've put aside X dollars for the bathroom tiles, and we'll true it up when you choose them." A prime cost item is similar. A provisional sum covers work where the scope isn't fully nailed down. Whatever you call them, flag them clearly. The client should know which numbers are firm and which are placeholders. Burying these in fine print is a quick way to lose trust at the variation stage.
Static PDFs have been the default for residential quotes for twenty years. They're familiar. They're easy to attach. They print cleanly. They've also been the bottleneck of the construction sales process for at least the last five.
Here's what a static PDF actually does for you: it freezes the quote at a point in time; it's easy for the client to forward, save, or print; it doesn't require anything from the client — they can just open and read.
And here's what it can't do: tell you when the client opened it (or whether they have at all); update if scope changes — you have to email a new version and hope they open the right one; embed images, walkthroughs, or links to similar past work; let the client browse at their own pace, expanding sections that interest them and skimming over sections they don't care about; capture a signature or acceptance directly.
An interactive web-based proposal does all of those. The client opens a link instead of a PDF. They see your branding, the scope laid out properly, optionally images of similar past work, and structured pricing they can navigate. You get notified when they open it and what links they click, then can follow up with context.
The gap shows up most clearly on jobs over $50k. The clients who are spending real money want to feel like they're working with a builder who runs a real business. A static PDF doesn't deliver that signal anymore. An interactive web proposal does.
The catch — and this matters — is that web proposals are only better if the underlying work is better. A polished proposal hiding a sloppy quote is worse than a plain PDF with a careful quote. The format amplifies whatever you've built. If your scope is tight and your pricing is honest, a web proposal compounds that. If it isn't, a web proposal exposes it faster.
This is where 25 years of building has actually mattered to me. The structure of a quote walkthrough is more important than what's in the quote itself, because the conversation is where doubt either compounds or gets resolved.
A few rules I've learned the hard way.
Letting the client read it cold gives them time to think. If you walk in and hand them the quote for the first time, they're processing the price while you're trying to talk through the scope, and they hear neither.
"Before we get to the number, let me walk you through what's in this." Spend ten minutes on what you're going to do, the order you're going to do it in, and the assumptions you've made. By the time you get to the price, they've understood what they're paying for. The number lands differently.
"This doesn't include the council fees because those go directly to council." "This allowance for tiles assumes a midrange supplier — if you go premium that'll come back as a variation." Naming the boundaries proactively prevents the boundary-question anxiety later.
It's a fair question. The honest answer is usually some version of: "Yes, here's the trade-off — if we drop X, the saving is Y, but you'll feel it in Z." Don't discount blindly. Show the trade-off. Most clients respect the honesty more than they respect the discount.
If a client wants to remove the structural engineer from a renovation, that's not a discount — that's a different (worse) job. Saying "no, I don't build that way" is sometimes the most professional thing you can do. Builders who flex on safety to win jobs eventually lose worse jobs anyway.
"I'll check in on Friday. If you've got questions before then, ring me." Don't make them feel chased. But don't disappear, either.
The five days after a quote goes out are the highest-leverage period in the whole sales cycle. Most builders waste them.
For more on why fixed-price quotes carry their own risks in 2026 and what to do about it, see why fixed-price quotes are riskier in 2026.
Modern proposal platforms tell you when the client opens the email, when they click through to the proposal, and which links they follow. That turns blind chase-ups into informed conversations — "saw you opened the quote yesterday — any questions you'd like to walk through?" lands very differently from "just touching base on the quote". The whole follow-up timeline below assumes you've got that visibility. If you don't, get it — send tracking is what Core Estimator's proposals are built around for exactly this reason.
Confirm the client has it. A short text or email — "sent the quote through, let me know if anything's not coming through clearly". Especially important if you've sent a web proposal and the client isn't sure how to open it.
Check-in. "Just touching base — did the quote come through alright? Happy to walk through anything if helpful." If you're using a web proposal that tells you when it's been opened, this gets sharper: "Looks like you opened the quote on Tuesday — any questions you'd like to chat through?" Following up with context is dramatically more effective than following up blind.
If you haven't heard back, one more soft check. "Just wanted to touch base — no pressure, but if there's anything I can clarify on the quote let me know."
If still no response, leave it. The client has either gone with someone else or paused the project. Chasing past two weeks rarely works and starts to look desperate. The job will come back if it's meant to.
When the valid-until date hits, don't just let it lapse silently. A quick note — "the quote I sent expires next week, happy to extend it or update if you've got more clarity on timing" — keeps the relationship warm. Some jobs come back six months later because of a polite expiry note that the cheaper builder never bothered with.
An interactive web-based proposal that the client can open and browse at their own pace works better than a PDF. PDFs feel formal but flat; web proposals let clients see scope, images, and answers to common questions without having to ring you. If you're still emailing PDFs in 2026, you're underselling yourself before the conversation even starts.
Yes — Australian consumer law expects quotes to be clear about GST treatment. The cleanest way: show line items ex-GST, total ex-GST, GST as its own line, then total inc-GST. Avoid blanket "all prices include GST" buried in fine print — clients should be able to see exactly how the GST is calculated.
A quote is generally treated as a fixed-price offer in Australia — once the client accepts it, the builder is bound to that price unless the quote includes specific provisions for variations. An estimate, by contrast, is usually a ballpark and not binding. Be careful which one you send and how it's worded.
14-30 days is standard for residential work. Material prices can move quickly enough that anything beyond 30 days carries real risk for the builder. Always include a "valid until" date — not just for legal protection, but because a quote with no expiry feels unprofessional.
For anything over $50k, walk them through it — in person, on a video call, or by sharing your screen on a web proposal. Emailing a quote without context loses the moment when you can answer objections and reinforce scope. A quote presented well converts noticeably better than one that lands cold in the inbox.
A polite check-in 3-5 days after sending. Web proposals make this easier — many tools tell you when the client has opened the quote, so you can follow up with context ("looked like you opened the quote — any questions?") rather than blindly. Don't wait two weeks; the client's enthusiasm is highest in the first week.
Builder ABN, business name, client name and project address, quote number, date issued, valid-until date, and a clear total inc-GST. Optionally a short scope summary so the client doesn't have to dig. The cover page is the first impression — it should look like the rest of the way you'd run their job.
With a static PDF, you have to email a new version and hope the client opens the right one. With a web proposal, it depends on where you are in the process. While the proposal is in draft, you can update it and the client always sees the current version. Once you publish and lock it, the client's copy is frozen — which is actually what you want after they've accepted. Communicate any pricing change clearly before you lock it: don't change pricing silently. Trust takes years to build, seconds to lose.
See what a Core Estimator proposal looks like to a client.
The honest answer from a developer actively building AI features into a construction estimating platform: no, AI won't replace construction estimators. But what's actually changing is more nuanced than the vendor blogs make out.
Excel works for construction estimating to a point. Here's where it breaks, and what to actually look for when you outgrow it — written by someone who's built the kind of sheets construction companies depend on.
Written by Dean Loader
Dean Loader spent 25 years as a residential builder specialising in architectural and bespoke work before co-founding Core Estimator. He's been where his customers are — sitting across from clients with a quote that needs to hold, managing variations, and knowing what it costs when a number is wrong.
Receive expert estimating advice, takeoff strategies, and bidding guides every week.
