Nobody sends the quote: turnaround time is the easiest edge in Australian trades

Because the quote is built twice. Once on site, in a notepad or a phone, and once again at night in a spreadsheet or a template. The second build is the one that gets skipped when the day runs long. Trade forums show the same two workarounds over and over. Spreadsheets and a notepad on the job, or the phone. As one solo operator put it on r/Plumbing: "Been on my own for about a year now. Currently I type up quotes in the Notes app on my phone and text them to customers, which I know looks unprofessional but it's fast." That is the choice as that operator framed it. Look amateur and be quick, or look sharp and be slow. Neither is a system. Both are the same missing piece: nothing captures the pricing decision at the moment it is made. This is a recurring complaint rather than a measured statistic. Nobody has surveyed how many Australian quotes die between the site visit and the send button. But the demand side gives a strong hint.

Low enough that showing up counts as a strategy. On r/AusRenovation, a homeowner described the experience from the buying side. A landscaper came out to look at their garden and said the quote would take about a week or so. Then: "I didn’t hear anything after two weeks, so I gave him a gentle nudge. He said he’d try to send it through that weekend, and I even said I was happy to wait until during the week. But still nothing." That customer was ready to buy, patient, and prompting. They still did not get a document. Read that as a market signal rather than a complaint. When buyers are chasing suppliers, turnaround is the differentiator. A quote that arrives the same evening, with photos of what was inspected and a line-item breakdown, is a visible contrast with a competitor who sends nothing at all. The counter-argument is fair and worth stating. Some trades are slow to quote because they are already flat out, which is exactly what that same thread describes about trades in Victoria. If your problem is too much work, faster quoting will not help you and may hurt margin. This piece is for the operator who wants the work and is losing it to their own admin queue. Marketplace data gives a sense of the gap, without measuring quoting speed directly. hipages reported 1.3 million jobs posted by Australian homeowners in FY24, with 86% of jobs connected to at least one tradie in the second half of the year, which implies roughly one in seven job requests received no tradie connection at all (hipages Group FY24 results). That is a marketplace with a commercial interest in the number, and connection is not the same as a quote arriving. Beyond that, be sceptical of anyone quoting Australian quoting statistics at you. There is no published survey with a stated methodology and sample covering how long Australian trade quotes take, what share are never sent, or whether faster quoting wins more work. The ABS does not collect it, and neither Master Builders nor the trade associations publish operational quoting benchmarks. Measure your own turnaround for a fortnight and you will know more than any figure you can look up.

The mistake is trying to automate the pricing. The pricing is the part you are actually good at. Automate the transcription instead. Three components do most of the work. Pre-built line items hold your own labour rates, materials and mark-ups, entered once, and must never pull prices from a shared or market database. Photo capture on site attaches photos to the specific line they justify, and does not replace your written note on site conditions. Saved assemblies per job type let one tap load the ten lines a standard job always needs, and must never lock you out of deleting or adding lines. An assembly is just a saved bundle. A hot water unit changeover, a switchboard upgrade, a standard bathroom rough-in. You build the bundle once, then on site you load it, delete what does not apply, add what is unusual, and adjust the quantities. The judgement stays with you. The typing does not. The target is a quote finished in ten minutes, not zero. Not an instant quote. A quote finished before you leave the driveway.

Because turning structured data into a decent-looking document with a variable number of rows is genuinely hard, and a home-built quoting setup can come apart at exactly that step. This is not a trades-specific problem. On r/zapier, someone building exactly this asked for help and described the wall: "The standard “create document from template” approach doesn’t handle a variable number of rows or dynamically inserted category headings in a table very well (at least not how I’ve managed to set it up)." A separate attempt, pushing the data through Google Sheets and exporting as a PDF, they described as messy and fragile, and said it felt more like a hack than a stable solution. They had not landed on an answer at all; they were still asking whether anyone had done it successfully. That is the last mile. Everything upstream is easy. Capturing lines on a phone, storing them, calculating a total. Rendering fifty or sixty line items across three levels of category headings into a branded PDF that does not overflow the page is the bit that breaks at 9pm on a Thursday. Two honest options. Use an established trade job-management platform that already solved it, such as ServiceM8, Tradify or simPRO, and accept its template constraints. Or build the document layer properly, with a real templating engine rather than a document-merge action bolted onto a workflow tool. The middle path, a merge template held together by workarounds, is the one that produces quotes with broken tables in front of a customer. Pick the option you can maintain. A fragile PDF generator that only one person understands is worse than a plain template you can fix yourself.

They centralise prices, and price is local. A scaffolding owner on r/ausbusiness put the objection better than any consultant would: "Not trying to be an ass but the reason estimation tools have always struggled in construction is because they typically centralise prices. I own a scaffolding company and there's simply way too many factors that affect prices, let alone a 6 in 1 estimating tool. Basically, without knowing the companies overheads, site conditions and the market they're positioned (industry/region/sectors), it's going to cause a tonne of problems." That is the correct test for any quoting tool you are shown. Ask where the numbers come from. If the answer is a shared database, an industry average, or a model that infers pricing, it does not know your overheads, your travel, your subcontractors or the access constraints on that specific site. The useful role for AI in quoting is narrower and more boring. Transcribe a voice note from the site walk into draft line items. Read a supplier invoice PDF and pull the current material cost into your own rate card. Draft the follow-up email three days after sending. Flag quotes that have gone quiet. None of that touches the price. All of it removes typing. That distinction is the difference between a quoting tool you keep and one you abandon after a month.

Someone in the business, not an outside agency on a retainer. Quoting logic changes constantly. Material costs move, you add a service, a supplier changes their pack sizes, you decide to load travel differently for outer-suburb jobs. If every change requires an email to a contractor, the system slowly drifts away from how you actually price, and eventually someone quietly goes back to the spreadsheet. That is the failure worth designing against. Not a technical fault, but nobody owning the thing. The skill that makes it stick is not building the workflow. It is mapping the process honestly, deciding what stays a human judgement, and being able to diagnose the thing when it breaks. Someone in the office who understands both the pricing and the tooling will outperform any external build, because they are there when the pricing changes.

How fast should a trade quote go out? Same day where possible, next business day at the latest. One Australian homeowner on a renovation forum described chasing a landscaper for weeks and never receiving the quote. Against that baseline, a next-day quote is a strong competitive position, even if the document is plain rather than polished. Is a quote typed in the phone Notes app really that bad? It works better than no quote, which is the honest alternative for many solo operators. The problem is not the format, it is that nothing is recorded, tracked or reusable. A basic itemised template that saves your line items solves both speed and record-keeping at once. Should I use ServiceM8, Tradify or simPRO, or build something? Start with an established platform rather than a custom build. Check how each one handles the PDF, the follow-up and the mobile capture before you commit, and note that ServiceM8 and simPRO are Australian while Tradify is a New Zealand company. Build custom only when a specific step in your process, usually an unusual assembly or an integration, genuinely does not fit the platform. Can AI write my quotes for me? It can draft line items from a voice note, extract material costs from supplier PDFs and write follow-ups. It cannot price your job. Pricing depends on your overheads, site access and local market, none of which a generic model knows. Keep the price under your control. Why do quoting systems get abandoned after a few months? Because pricing logic changes and nobody inside the business can update the system. When every change needs an external contractor, the tool drifts from reality and staff revert to spreadsheets. Internal ownership is what keeps a quoting system alive past the first rate rise. What is the single highest-value change to make first? Build one saved assembly for your most common job type. One bundle of standard line items you can load, edit and send from site. It removes the second build at night, which is the step where most quotes are lost.

Quotes are reproduced verbatim and attributed to the subreddit they appeared in, not to individuals: r/Plumbing, r/AusRenovation, r/zapier, r/ausbusiness. No statistics are cited in this article. Observations described as recurring patterns are drawn from public forum discussions and are not survey data.