The AI AdoptionFree AI pre-audit

10 best AI use cases for construction.

Job programmeOne renovation job, from the first enquiry to the last progress claim

  1. Winning workOutlookGmail
    Quote draftedTender checklist
  2. ApprovalsOutlookGoogle Sheets
    Approvals chased
  3. On siteWhatsAppProcore
    Extras to signDelays caught
  4. ClientsOutlookGoogle Drive
    Friday update
  5. MoneyXeroQuickBooks
    Invoices checkedBooks checked
  6. Running the businessn8nLooker Studio
    One viewAutomations watched
Where the ten use cases sit on a building job, from the first enquiry to the month-end checks. Each marker links to its use case below.

Ten jobs in a building business that AI can take on, from the first enquiry to the month-end checks. Each one shows the workflow step by step, the apps it connects, a prompt to try in Claude with your own files, and the step that stays with you.

By The AI Adoption · Published on

  1. Winning work

    How to automate your quotes?

    A late quote often loses the job. With this, the draft is ready the same day. You just check the price and send.

    • Gmail
    • Outlook
    • Claude
    • HubSpot
    • Pipedrive
    • Slack
    • Google Sheets
    • Excel

    How it runs

    An enquiry arrives by email or from your website form. Claude sets spam aside, and the lead is saved in your CRM, or joined to the open lead when the customer is already there. The request is read against your rate card: when a detail or a rate is missing, the customer is asked and the quote waits. Once the scope is complete, the quote is drafted in your template, with any special detail noted at the top.

    First test

    Run a past enquiry with your rate card and template, and compare the draft with the quote you sent. Remove one detail and run it again: you should get a question for the customer.

    You keep

    Every quote while auto-send is off. With it on, only a quote with a special detail waits for you to check and send; the others go out and the person in charge is told.

    Each step shows the app that runs it; the app beside it can do the same job.

    Try this prompt in Claude

    Read this enquiry against my rate card. List the scope and quantities, and flag any special detail. If a detail or a rate is missing, write the question for the customer and stop. Otherwise, draft the quote in my template, priced only from my rates, with the special details noted at the top.

  2. Winning work

    Bid on more jobs, without the paperwork

    One missed requirement buried in a tender pack can cost you the job. Now every pack becomes a checklist with pages and dates. You only decide whether to bid, then submit.

    • Gmail
    • Outlook
    • Google Drive
    • SharePoint
    • Claude
    • Google Sheets
    • Excel
    • Slack

    How it runs

    The tender pack lands in your tender folder with its attachment list, and any missing or unreadable file is asked for first. Claude then builds a checklist of every requirement, document and deadline, each with the page it comes from, and marks the clauses on payment, insurance and damages for your review. If you decide to bid, each line goes to someone in your team with its date and is chased until it is ticked.

    First test

    Use a past tender you already submitted. Open the cited pages for a few lines, and compare the checklist with what your team had to supply.

    You keep

    The decision to bid, once you have read the flagged clauses, and the final check of the pack before you send it. A decline is drafted for you.

    Each step shows the app that runs it; the app beside it can do the same job.

    Try this prompt in Claude

    Read this tender pack. Check that every file on the attachment list is present and readable, and list any that are not. Build a checklist with one line per requirement: what is asked, the document, its page and the deadline. Flag clauses on payment, insurance and damages. Do not infer requirements the pack does not state.

  3. Approvals

    Stop chasing approvals by hand

    Your jobs wait on the council, the surveyor or the client to sign off. With this, every request is followed until the yes is in. You just check the reminders and send.

    • Gmail
    • Outlook
    • Claude
    • Google Forms
    • Google Sheets
    • Excel
    • Slack
    • Teams

    How it runs

    On a live job, you email the council, the surveyor or the client and tag the request. Each one gets a row in the approvals tracker: what is waiting, who must answer and by when. Every day the replies are read. A clear yes in writing closes the row and the person who asked is told; a question, a change or a no goes back to them. Past the due date, a short chase is drafted for you to check and send, up to the limit you set.

    First test

    Use a copy of your tracker with one row of each kind: approved, questioned, not yet due, overdue, and chased to your limit. Check which route each takes.

    You keep

    Each chase, checked and sent from your inbox. Past your limit, the emails stop and the person who asked picks up the phone.

    Each step shows the app that runs it; the app beside it can do the same job.

    Try this prompt in Claude

    Today is [date]. For each row of this approvals tracker, read the replies. Mark Approved only on a clear yes in writing. Flag a question, a change or a no for the person who asked. If nothing came back, the due date has passed and the row has fewer than [limit] chases, draft a short, polite chase: job, item, date asked.

    Fill in the words in blue first.

  4. On site

    Track your extras on site instantly, without friction

    Extras agreed on site get lost on the way to the office. Now each day’s notes become the site report, and every extra becomes a variation to sign. You only set the price.

    • WhatsApp
    • Claude
    • Google Drive
    • Procore
    • Slack
    • DocuSign
    • PandaDoc
    • Xero

    How it runs

    Photos and voice notes come in from the crew during the day. At the end of it, Claude writes each job’s site report in your template and checks every request made on site against the agreed scope. Work the scope does not cover becomes a variation notice, with the notes and photos it comes from. Your project manager sets the price, an unsigned variation is chased by your approvals flow, and once signed it goes on the next progress claim.

    First test

    Pick a past day when an extra was agreed on site. Give Claude that day’s messages and photos with the scope, and compare its variation with the one you raised.

    You keep

    The price and time on each variation, set by you or your project manager. Nothing goes out for signature until they are set.

    Each step shows the app that runs it; the app beside it can do the same job.

    Try this prompt in Claude

    Write today’s site report for [job] from these notes and photos, in my template: work done, issues and photos. Check each request made on site against the attached scope. For any work the contract does not cover, draft a variation: what was asked, by whom, citing the notes and photos. Leave price and time blank.

    Fill in the words in blue first.

  5. On site

    How to automate project delay tracking?

    A schedule fed by hopeful updates rarely shows where a job is running late. Here, only site updates that prove a milestone move the schedule. Your project manager confirms the rest.

    • WhatsApp
    • Gmail
    • Claude
    • Google Sheets
    • Smartsheet
    • Slack
    • Looker Studio
    • Power BI

    How it runs

    Every morning, before site starts, the updates sent from site since yesterday are read against the proof each milestone needs. Only a proven milestone moves the schedule, with its actual date next to the planned one; a hopeful sentence never counts as progress. Tasks behind plan, or silent for too long, go to the project manager in one morning message, and they set the new date and the reason. When a new date moves handover, a client milestone or a payment claim, you are told straight away.

    First test

    Use a week of a past job where something slipped. Check the late tasks it lists against what actually happened, and that a vague update is not counted as progress.

    You keep

    Every new date and its reason, set by the project manager. When a key date moves, you decide what the client hears.

    Each step shows the app that runs it; the app beside it can do the same job.

    Try this prompt in Claude

    Here are yesterday’s updates from site and our programme, with the proof each milestone needs. For each update, say which task it belongs to and whether it proves the milestone. List the tasks past their planned date without proof, and those with no update for [days]. Do not mark anything done on a hopeful sentence.

    Fill in the words in blue first.

  6. Clients

    Update every client weekly, without writing a word

    The Friday update gets written from memory, late, one job at a time. Now it comes from the week’s site reports and photos. You only check the ones that mention a delay or money.

    • Google Drive
    • Procore
    • Claude
    • Slack
    • WhatsApp
    • Gmail
    • Outlook
    • n8n

    How it runs

    Every Friday, for each live job, the week’s site reports, programme and photos are taken from the project folder. Anything missing, unclear or contradicting between them goes to the manager first. Claude then writes the update in your tone: progress, next steps and the decisions the client owes. An update with no delay and no new cost goes to the client with you in copy; one that mentions either waits in drafts until you have read what it promises.

    First test

    Use one past week of a job and the update you sent. Check each progress line against a site report, and that any delay or extra cost is flagged.

    You keep

    Any update with a new date or an unexpected cost. It waits in drafts until you read what it promises and send it.

    Each step shows the app that runs it; the app beside it can do the same job.

    Try this prompt in Claude

    Write this week’s client update for [job] from these site reports, programme and photos, in the tone of my past update. Cover progress, next steps and decisions needed. First list any missing day, or report that disagrees with the programme. Flag every new date or cost the client did not expect.

    Fill in the words in blue first.

  7. Money

    Never handle an invoice. Ever. With complete peace of mind.

    Every supplier invoice is read, checked against its order and docket, and lined up for payment. Anything wrong is caught and queried before it reaches you. You only approve the payment run.

    • Gmail
    • Outlook
    • Claude
    • Slack
    • Google Drive
    • Teams
    • SharePoint
    • Xero

    How it runs

    Each supplier invoice is picked up with its order and delivery docket. Claude compares it line by line, quantities and unit prices, and checks it against past invoices for duplicates. A complete, matching invoice joins the list waiting for approval in Xero or QuickBooks. A missing docket goes to the site, and a difference against you is queried with the supplier before the invoice comes back for another check.

    First test

    Use an invoice from a known supplier that someone has already checked, and compare the results. Run it again with the docket removed: it should stop and name what is missing.

    You keep

    The payment run. Checked invoices wait in Xero or QuickBooks for your approval; refuse one and your reason goes to the supplier or to the team.

    Each step shows the app that runs it; the app beside it can do the same job.

    Try this prompt in Claude

    Compare this invoice with its purchase order and signed docket, line by line, showing quantity and unit price from each. Mark each line matching, in our favour, or against us beyond [tolerance]. Check supplier, number and amount against this list of paid invoices. If a document is missing, say which and stop. Draft a supplier query for any line against us.

    Fill in the words in blue first.

  8. Money

    How to automate your accounting checks?

    Accounting errors often surface at month-end, when there is least time to fix them. With this, possible issues are caught through the month, each with a suggested fix. Your finance manager decides every change.

    • NetSuite
    • Xero
    • Claude
    • Google Sheets
    • Excel
    • Slack
    • WhatsApp

    How it runs

    Every week, well before month-end, each business’s bills, sales invoices and bank lines are pulled from NetSuite or Xero. Claude matches the lines by invoice number, supplier or customer, amount and business. A possible duplicate, a missing document, a gap or a line in the wrong business gets a suggested fix beside its source, and your finance manager accepts, changes or dismisses it. Anything still open as month-end nears reaches you before the books close.

    First test

    Use a month you have already closed for one business and compare with your team’s corrections. Then add a copy of one bill: it should show as a possible duplicate.

    You keep

    Every change in the books, decided by your finance manager. Anything still open as month-end nears reaches you before the books close.

    Each step shows the app that runs it; the app beside it can do the same job.

    Try this prompt in Claude

    Here are this month’s bills, sales invoices and bank lines for [business]. Match each line by invoice number, supplier or customer, amount, currency and business. List any possible duplicate, missing document, unmatched bank line or line from another business, with its source and a suggested fix. Change nothing.

    Fill in the words in blue first.

  9. Running the business

    How to bring information scattered across different software into one place

    Automatically pull information from the tools your businesses use into one clear view. Spend less time switching between systems and piecing together what’s happening.

    • NetSuite
    • Procore
    • n8n
    • Make
    • Google Sheets
    • SharePoint
    • Looker Studio
    • Power BI

    How it runs

    On the schedule you set, each business’s figures are pulled straight from its software, NetSuite, Xero or Procore, with no export by hand. Every line gets its business and project, keeps its source date and is counted once in a shared table. The group view shows a page per business and a summary, each figure linked to its source. When a source does not come through, that business is marked out of date and the person who owns the connection is told.

    First test

    Use last month’s exports and compare the totals per business with your accounts. Leave one business’s file out: it should be listed as missing.

    You keep

    The decisions you take from the view. A connection that stays broken comes to you or your AI specialist, and its figures are never shown as current.

    Each step shows the app that runs it; the app beside it can do the same job.

    Try this prompt in Claude

    Here are this month’s figures exported from [software] for each of our businesses, with our list of business and project names. Put every line in one table: business, project, amount and source date, each line counted once. List any line you cannot place, and any business whose figures are missing or older than the others.

    Fill in the words in blue first.

  10. Running the business

    How to spot broken automations before they hold up your business

    Automatically check that each automation delivers its expected result. The person responsible is alerted when something is missing, and you’re notified if it stays unresolved. Alerts close once it’s working again.

    • Google Sheets
    • Excel
    • n8n
    • Make
    • Slack
    • WhatsApp

    How it runs

    The day an automation goes live, it joins a watch list: when it should run, what it should leave and who owns it. A separate check, on its own schedule, reads each automation’s run history. When one has not run, or left nothing, the person responsible is told what to check, fixes it and runs it again. If it is still broken at the next check, you or your AI specialist take it over, and the alert closes once it works.

    First test

    Use a week when an automation failed or never started. Check that it is caught, that a quiet run with nothing to do is not, and that the alert names the right person.

    You keep

    The fix itself, by the person responsible. If an automation is still broken after the alert, you or your AI specialist take it over.

    Each step shows the app that runs it; the app beside it can do the same job.

    Try this prompt in Claude

    Here is our list of automations, with when each should run, what it should leave and who owns it, and this week’s run history. For each one, say whether it ran on time and left its output. A run with nothing to process counts as done. For each failure, write a short alert for its owner: which automation, its last success and what to check.

Where to start.

Pick the one that costs your team the most time this month and run its first test on a past job, with files you are allowed to use. Keep the step that stays with you where the workflow puts it. Running it every day, connected to your own accounts with the right access and checks, is the part we set up with you.

To find which of these fits your business first, book a free AI pre-audit: forty-five minutes on your own work, with a clear next step, with or without us.

Bring your questions.

Free AI pre-audit