How to use AI for construction quoting and estimating

AI can safely take most of the paperwork out of a construction quote today. It can read the plans and specs, pull out the scope, inclusions and exclusions, draft the quote letter from your past quotes, check the finished quote against the customer's brief, and draft the follow-up on quotes nobody has signed. What it should not touch is the pricing: your rates, your margin, your read on site risk, your compliance details and the final sign-off stay with a person.

The way to start is small. Put your last 10 to 20 sent quotes, your standard inclusions and exclusions, and your terms into a Claude Project. Tell it to use only those documents and to mark anything it cannot find. Then run four prompts per job: scope, gaps, letter, check. The prices come from your estimating or job system, entered by your estimator.

Last, connect it to the rest of the business. The quote's value, status and expiry date go into your CRM so someone follows it up, and the accepted quote goes into your job system so nobody types it twice. Done this way, your estimators spend their hours on the numbers and the risk, which is the part your customers are actually paying for.

What can AI do in a quote, and what must a person keep?

Here is the split we work from for a 50 to 250 person builder, trade or building services business:

The line sits there for a legal reason. Business Queensland's guide to preparing a quote says that a quote, once accepted by the customer, becomes a legally binding contract. A wrong exclusion is work you have agreed to do for free, and a missing expiry date can leave you honouring a price after your materials have gone up. A machine can draft the words. A person has to own the offer.

This video from our YouTube channel looks at where AI needs a human and where it does not.

Before you upload anything: two checks

Your own setup. Use a business Claude plan, keep the Project shared only with the estimating team, and know where the data goes. Anthropic says that by default it does not use inputs or outputs from its commercial products, such as Claude for Work and the API, to train its models.

The customer's documents. Tender conditions and head contracts sometimes mark drawings and specs as confidential or limit where they can be stored. Read those conditions first, the same way our guide to answering a tender in an afternoon with Claude sets out.

One practical limit on drawings: Claude reads the images and charts inside PDFs of 100 pages or fewer. From 101 to 1,000 pages it reads the text only, and a file in a Project can be up to 30MB. So split a big drawing set and upload the sheets that matter to your trade, plus the spec sections that name it.

Step 1: build the quoting Project

A Claude Project holds documents and a standing set of instructions, and on Team and Enterprise plans you can share it with the people who need it. Put in:

• Your last 10 to 20 sent quotes, won and lost, so it learns how you write and what you normally exclude.
• Your standard inclusions and exclusions lists, by job type if you have them.
• Your terms and conditions, exactly as your lawyer last approved them.
• Your licence, insurance and company details, as they must appear on a quote.

Then set the Project instructions:

You help our estimating team prepare quotes.
Only use facts that appear in the project documents or the job documents I paste in.
Never invent a price, rate, quantity, licence number or date.
If something you need is missing, write [CHECK: what is missing] instead of guessing.
Copy our terms and conditions word for word. Never reword them.
Write in plain Australian English.

Step 2: read the plans and pull the scope

Upload the job's drawings and spec, then run this:

Read the attached drawings and specification for [job name].
List everything that falls within our trade: [your trade].
For each item give the drawing or spec reference.
Separately list:
- anything marked "by others", "allow for", "provisional" or "TBC"
- anything that conflicts between the drawings and the spec
- anything our standard exclusions list would normally exclude
Do not estimate quantities.

The second list is the useful one. Conflicts between drawings and spec, and the "allow for" lines nobody priced, are where a quote turns into a dispute. Your estimator now starts the takeoff knowing what to ask the builder or the client before pricing.

Keep quantities with your estimator and whatever takeoff tool they already trust. Claude can read a finishes schedule well. Measuring off a scanned A1 sheet is a different job, and a wrong area flows straight into the price.

Step 3: draft the letter, then check it against the brief

Once the estimator has priced the job, paste the priced line items in from your estimating or job system and run:

Draft the quote letter for [job name] using the priced items below.
Follow the structure and tone of our past quotes for similar jobs.
Include our standard inclusions and exclusions that apply, plus any job-specific
exclusions from the scope list.
Show each price excluding GST, the GST amount, and the total including GST.
Include an expiry date of [date] and our terms exactly as written.
Mark anything you are unsure of with [CHECK].

Then the check, which is the prompt that pays for the whole exercise:

Here is the customer's brief or request for quote, and our draft quote.
Build a table with one row per requirement in the brief:
- the requirement, quoted exactly
- whether our quote covers it, excludes it, or does not mention it
- where in the quote it is covered
List anything in our quote that the brief did not ask for.

"Does not mention it" is the column to read twice. That is the missed item the customer assumes is included. We wrote up this check in more detail in check your proposal against the brief before you send it.

The four prompts from this post, with the estimator's pricing between the scope and the letter. Prices always come from your estimating or job system.

The Australian details AI should never decide

The offer itself. Business Queensland says an accepted quote becomes a legally binding contract, an estimate is a rough guide that is not binding, and a quote should carry an expiry date, the scope, the exclusions and a signature line for acceptance. Make sure your template has all of them, and that whoever sends the quote knows it is an offer.

GST. business.gov.au says a displayed total price must include all taxes, such as GST, and Business Queensland says to show the GST component on a quote. Put both in your template so the AI copies them every time.

Payment terms and Security of Payment. Security of payment is state law, so the rules differ from state to state. In Queensland, the QBCC says a payment claim must be in writing and meet set content rules, and that "pay when paid" provisions are void under the BIF Act. Your payment terms come from your contract template and your lawyer. The AI copies them and never writes its own.

Step 4: follow up the quotes nobody signed

A quote that goes out and is never chased is the most expensive document in the business. This is where the CRM and the job system come in.

• Record every sent quote in the CRM. In HubSpot that is usually a deal at a "Quote sent" stage, with the value, the expiry date and the estimator as owner.
• Automate the reminders. A workflow creates a call task a few days after sending and again before expiry. HubSpot workflows need a Professional or Enterprise subscription.
• Let AI draft the follow-up. With the quote and the brief in front of it, Claude can write a short email that answers the likely question, such as an exclusion the customer may query. The estimator edits and sends it.
• Send the accepted quote to the job system. Once a quote is accepted, the job is created from it so nobody keys the scope in twice.

If your quotes are built in a job system or ERP and sales loses sight of them once they go out, start with how to know which quotes you lost when they live in the ERP.

For what this looks like in a trade business, see our On Top Roofing case study. The office works in HubSpot and the project managers work in Simpro, with a middleware layer bringing more than 15 Simpro data points across, and a 12 stage quote lifecycle in HubSpot. The case study reports quote to approval going from 5.2 days to 1.8 days. That project was CRM structure and integration work, and it is the base any AI drafting needs, because the AI can only chase quotes the CRM knows about.

Before the build5.2 days

After HubSpot and Simpro1.8 days

Days from quote to approval, as reported in the On Top Roofing case study. That was CRM structure and integration work, with no AI drafting.

What does it take to set up?

Steps 1 to 3 need a business Claude plan, a Project and an estimator who will spend a few hours loading past quotes and testing the prompts on jobs you have already priced. Run the check prompt on three old quotes before you trust it on a live one.

Step 4 is a build: the CRM stages, the workflows and the connection to your job system. That is scoped work, and the cost depends on your systems. Our guide to what a custom AI build costs an Australian business covers how that pricing works.

Frequently asked questions

Can AI do construction estimating? AI can read plans and specs, list scope items, and flag conflicts and "by others" items, which speeds up the start of an estimate. Quantities, rates, margin and the final price should stay with your estimator.

Is a construction quote legally binding in Australia? Business Queensland says a quote, once accepted by the customer, becomes a legally binding contract, while an estimate is a rough guide that is not binding. That is why a person should check and sign off every quote an AI helps draft.

Can Claude read construction drawings? Claude reads the text and the visual elements in PDFs of 100 pages or fewer, and only the text in PDFs from 101 to 1,000 pages. Split large drawing sets and upload the sheets relevant to your trade.

Should AI-drafted quotes show GST? Yes. business.gov.au says a displayed total price must include taxes such as GST, and Business Queensland says to show the GST component on a quote. Put both in your template so every draft includes them.

How do I stop AI making up prices in a quote? Tell it in the Project instructions never to invent a price, rate or quantity, and paste the priced line items in from your estimating or job system yourself. Have it mark anything missing with [CHECK], and have a person read every line.

Sources

• Preparing a business quote, Business Queensland, for quotes becoming binding contracts, estimates, expiry dates, GST and what to include.
• Displaying prices, business.gov.au, for total prices including GST.
• Request payment, Queensland Building and Construction Commission, for payment claims and "pay when paid" under the BIF Act.
• What are projects?, Claude Help Center, for Project knowledge, instructions and sharing.
• What kinds of documents can I upload to Claude?, Claude Help Center, for PDF page limits and file sizes.
• Is my data used for model training?, Anthropic Privacy Center, for commercial products and training.
• Create workflows, HubSpot Knowledge Base, for workflow subscription requirements.
• On Top Roofing Solutions, Neighbourhood, for the HubSpot and Simpro build and its reported results.

---

Want your quotes, your CRM and your job system working together before you add AI on top? See our AI engineering work and AI consulting, or talk to us.