AI automation for construction firms and contractors

The paperwork of a job, from first enquiry to last retention payment

AI automation for construction takes on the paperwork of a job, from the first enquiry to the last retention payment: enquiry capture, quantity takeoffs and quotations, supplier prices, subcontractor coordination, material orders, site progress reporting, variations, payment applications and the document trail a dispute is decided on. It does not sign off structure and it does not touch safety certification.

Contractors are usually sold software for the wrong problem. The bottleneck is rarely the drawing package. It is the four days between a site visit and a price going out, the verbal variation nobody wrote down, and the application submitted a week after the valuation date.

Most of what follows is ordinary automation rather than anything clever. A reminder that fires when a valuation date approaches will earn more than any model, and it will still be running in three years.

• Winning work: enquiries, site visits, takeoffs, supplier prices, quotes and the chasing that follows
• Running work: programme dates, subcontractor confirmations, material orders, deliveries and daily reports
• Getting paid: valuations, payment applications, invoices, variations and retention release dates
• Staying compliant: insurances, certificates and qualifications collected before anyone reaches the gate
• Knowing where you stand: cost against budget per job, applied against certified, outstanding against overdue

The week you actually have

No solutions in this section. Count the ones you recognise.

• A quote is promised on Friday and goes out the following Wednesday, by which time somebody else has quoted
• The takeoff is done twice because the drawing was revised and nobody flagged which revision the price was built on
• Material prices moved between quoting and ordering, and the difference comes out of your margin
• A subcontractor confirms a start date on the phone and nobody writes it anywhere
• Two trades turn up on the same day for the same space
• Site progress is reported as photographs in a group chat with no dates attached to them
• A variation is agreed verbally on site and argued about at the end of the job
• The payment application goes in after the valuation date, so the money lands a month later than it should
• Retention on a job finished last year is still outstanding and nobody is chasing it
• A delivery arrives when nobody is on site to receive it
• The client asks for an update and somebody has to ring three people to answer
• A dispute starts and the evidence is spread across a group chat, an inbox and one foreman's phone
• Plant and tool hire is still running on a job that finished
• Insurances and qualifications for a subcontractor are chased on the morning they start

The arithmetic on your own jobs

There is no industry average here worth borrowing. Three sums on your own numbers, and the first one is usually the shock.

• Sum one: your average job value, multiplied by the number of enquiries last quarter you never got round to quoting at all.
• Sum two: the hours your estimator, site manager and office spend each week on takeoffs, applications, chasing and reports, multiplied by what an hour costs you, multiplied by fifty two.
• Sum three: for every payment application submitted late last year, the amount multiplied by the weeks it was late, priced at whatever your overdraft or finance actually costs.

If you cannot answer the first sum because unquoted enquiries were never recorded anywhere, that is the finding. The first thing to build is the record, not the automation.

What gets built, and where a contractor starts

The first build is whichever sum was largest. For most contractors it is the quote path, because turnaround decides win rate and because the same work produces the pricing library everything later depends on.

• One place every enquiry lands, from calls, email, WhatsApp and the website, with a first reply going out the same hour
• Quotation support: your own priced items reused, drawing revisions tracked, the quote produced in your format
• Supplier price requests sent, gathered and compared into one sheet instead of a folder of replies
• Quote follow up, so a price that went out is chased without anyone remembering to chase it
• Subcontractor coordination: dates confirmed in writing, reminders before a start, a record of who agreed what
• Compliance packs collected before a start date: insurances, certificates and qualifications requested and chased
• Site reporting assembled from the foreman's photographs and voice notes, dated and filed against the job
• Variations captured on site as a record with a photograph and a signature rather than as a memory
• Payment applications and invoices prepared on the contract's own schedule, with reminders before each date
• Retention release dates diarised at the moment a job completes, and chased when they arrive
• Material ordering and delivery slots booked against the programme rather than against optimism
• A job dashboard: spent against budget, applied against certified, outstanding against overdue

What stays human on a live site

Nothing that touches safety certification or structural sign off is automated. Not a design check, not temporary works, not an inspection sign off, not the approval of a method statement. Those are professional judgements with names attached and legal weight behind them.

A system can assemble the evidence, hold the record and remind you a notice is due. It must not be the thing that decides the answer.

• Any decision about whether work is safe to proceed, and any instruction that changes how something is built
• Structural, design and temporary works sign off, and every inspection that carries a signature
• Contractual notices and correspondence, which are prepared but sent by a person who has read them
• Priced quotations above whatever threshold you set, approved before they leave the office
• Anything heading into a dispute or an adjudication
• The conversation with a client whose job has slipped, which nobody should receive as an automated update

What changes with the contract and the country

Building is similar everywhere. Getting paid for building is not.

• Payment structures differ. Where contracts run on valuations, certified sums and retention, the money system is a calendar of dates. Where work is quoted and invoiced on completion, it is a chasing system. Building the wrong one wastes the whole exercise.
• Contract forms differ, and with them the notices, the deadlines and the evidence you must keep. Reminders are only useful when loaded with your contract dates rather than generic ones.
• Safety and building control regimes differ by country and sometimes by city, and none of that is automated. The system keeps the paperwork current and holds the record of who was certified when.
• Channel differs. Most foremen will not open a portal. Where the site's real communication tool is WhatsApp, the system reads from that channel or it is not used, and business messaging there runs on opt in, on approved templates and on a window that closes after the last reply.
• Seasonality differs. Monsoon, winter shutdowns, holiday periods and Ramadan hours all move the programme, and a scheduler that does not know your non working days produces dates nobody believes.

Where a contractor should not start with software

Three situations where the honest answer is to spend the money elsewhere.

One more that gets missed. If your site team will not use anything except the app they already message on, then either the system is built into that channel or it is not built. A portal nobody opens is a monthly fee for a login screen.

• If your prices are not written down anywhere, no system can produce a quote. The first job is a priced item list, which costs a week of somebody's time and is worth more than any automation bought afterwards.
• If you win a handful of large jobs a year through relationships, quoting speed is not your constraint and this will not become your constraint by buying it.
• If jobs are losing money because they are priced too low, automation makes you lose it faster. Fix the pricing, then automate the sending.

How soon a contractor sees anything, and who signs what

The start of this is deliberately short, because a contractor who has waited three months for software has already stopped believing in it. The audit takes the first week and its output is a written list of every date your contracts already impose: valuation dates, notice periods, retention release. One piece is live inside a fortnight and it is almost always that calendar, because a reminder firing before a valuation date earns money in its first month and needs nothing integrated to do it. The quote path follows across month two, once there is a priced item library worth reusing.

Nothing carrying a signature is automated. A contractual notice is prepared and then sent by a person who has read it. A priced quotation above whatever threshold you set waits for human approval before it leaves the office. A variation is captured on site with a photograph and a signature, which makes it a record rather than a decision. And anything about whether work is safe to proceed hands it to a person with a name and professional liability attached, every time, because a system that assembles evidence is useful and a system that concludes from it is a defendant.

The document trail is what a dispute gets decided on, so ownership is not a preference in this trade. The job records, the dated site reports, the variation evidence and the automations live in accounts in your own company's name, so you own the system and the trail stays yours whether or not a supplier is still involved. A contractor with a capable office manager can run the date calendar in-house indefinitely once it has been set up, and saying so is more useful than pretending otherwise. What is harder to keep internally is the quote path, because a priced library is only worth having while somebody maintains it against supplier prices that keep moving.

Wobble works with RM Gulistan Engineers in Karachi, an engineering and contracting business, on three purpose built ERP systems covering accounts, HR and inventory, led from ideation through to ongoing management. Moiz Khan owns automation architecture and decides what gets built and how it runs; Ibrahim owns build and workflows. The company works from Karachi, bills month to month and is answerable for what it operates, across 25 engagements in six countries. The RMG write up is not finished, so the honest statement is that three systems are live and the detail is still to be published rather than that there is a case study to read.

Common questions

Can it do a quantity takeoff from drawings?

Partly, and honestly is the right answer here. It can hold your priced item library, reuse measurements across similar jobs, track which drawing revision a price was built on and assemble the quote document. The measurement itself still gets checked by whoever puts their name on the price.

Will this work if my site team only uses WhatsApp?

Yes, and it is usually the right design. The foreman keeps sending photographs and voice notes to the same number, and the system turns those into dated site reports filed against the job. Nobody on site is asked to learn a portal, which is why the record actually gets kept.

Can it produce payment applications?

It can assemble them from the job record on the schedule your contract sets, and remind the right person before each valuation date. A person reviews and submits, because an application is a contractual document and the amount claimed is a judgement about progress rather than a calculation.

What about health and safety paperwork?

The chasing is automated, the judgement is not. Insurances, certificates and qualifications can be requested, collected and re-requested before they expire, and a subcontractor without current documents can be flagged before a start date. Nothing certifies competence and nothing signs off a method statement.

We are a small contractor with a few staff. Is this worth it?

It depends entirely on the hours your estimator, site manager and office spend each week on takeoffs, applications, chasing and reports, priced at what an hour costs you. If the office work fits comfortably into the hours available, spend the money on tools or on another pair of hands. The usual trigger is an owner doing quotes at night because the day is spent on site.

Where does the evidence live if we end up in a dispute?

In one place, filed against the job, with dates attached at the moment things happened rather than reconstructed afterwards. Photographs, site reports, variations, instructions and correspondence in one record is the practical benefit, and it is the reason many contractors build the site reporting piece before anything else.