---
title: "Construction Site Automation in 14 Days | JustAutomate"
description: "Site reports from a phone, change orders with a number and an approval, stage cost against the estimate as it moves. Workshop EUR 3,500 net a week."
url: "https://justautomate.ai/en/industries/construction-companies/"
lang: en
---

Construction and contracting

# Automation for construction companies from a site photo to the job file

The work happens on site and the paperwork happens in the office. Photos stay on phones, measurements come back on a scrap of paper, a change agreed at the gate leaves no trace anywhere. We move the record to where the work is: one photo from a phone and the job file starts filling itself.

 Book a free consultation [See what the workshop looks like](https://justautomate.ai/en/services/process-workshop/)

- 14 daysto the first working automation, counted from the end of the workshop
- EUR 3,500net per week of workshop, a published price we do not negotiate
- 5 to 10 secondsfor the AI agent to answer a question from your contracts and site records

The problem

## Why does the build move on while the paperwork stays behind?

The foreman photographs the finished work on his phone and the photo stays on his phone. The note from a talk with the inspector goes into a chat thread. The measurement travels back to the office on paper and someone copies it into a spreadsheet, usually in the evening, usually from memory. **The place where the work happens and the place where the record happens are two different places**, a dozen kilometres and several hours apart.

The most expensive item on that list is the change order. Agreed on site, built the same week, written down nowhere. At handover there is nothing to prove it with, so either the contractor swallows the cost or a dispute starts in which both sides quote a conversation. The estimate then lives a life of its own: subcontractor invoices arrive with no stage attached, and the overrun shows up after the month closes, when there is nobody left to negotiate with.

Some deadlines in construction do not forgive. The window for notifying a subcontractor to the client, and the period you stay liable for defects after handover, come from the law of the country you are building in and from the contract you signed. Both run in years, both start on a date somebody has to remember, and both differ from job to job. A project manager holding three contracts at once cannot keep those dates in their head, and should not have to.

- The photo that proves the work stays on the foreman's phone and never reaches the job file
- A change agreed on site leaves no trace, so at handover there is nothing to prove it with
- A subcontractor invoice lands with no stage attached, so you learn the stage cost a month late
- An inspection or a notification deadline reminds you of itself once it has passed

Why now

## What changed, so this works without a new system on site?

One device works on a building site: the phone in a pocket. What changed is that a site report no longer needs an app anybody has to learn. A form opened from a QR code at the gate is enough: photo, one sentence, pick the stage. Date, time and location attach themselves, because the phone knows them anyway.

The second change is on the office side. More of the paperwork is already digital: site diaries, tender portals, subcontractor invoices arriving as files instead of paper. None of those systems talks to your estimate or to your invoice approval flow, so a person in the office still retypes numbers between them. Wiring them together is no longer a project: the connection runs through [n8n](https://docs.n8n.io/) or Make and is counted in days of work.

The third thing is the AI agent. A rule will file a photo into the right folder, but it will not answer a project manager asking whether the contract with this subcontractor has a penalty for walking off site. A language model reads contracts, handover protocols and project documentation at once, answers in a sentence and names the document it took the answer from.

What changes

## What does the project manager get?

- ### A site report in half a minute
The foreman takes a photo and picks the stage. The entry lands in the job file with date, time and location, with nothing retyped in the office that evening.
One action on a phone instead of five in the office
- ### Change orders with a number and an approval
A request raised from the form gets the next number, goes for approval and waits for the decision in one place. At handover there is something to show for what was agreed and when.
A number and an approval date instead of a conversation nobody remembers the same way
- ### Stage cost against the estimate as it moves
Subcontractor and supplier invoices arrive with a stage attached on the day they land. The overrun shows up in the week it grows.
The overrun in the week, not after the month closes
- ### Deadlines watched by a calendar, not by memory
Defect liability, subcontractor warranties, building inspections and document validity sit in one place and speak up before the date, not after it.
One calendar for handover dates, warranties and inspections, with a reminder before each
- ### An answer from the contract instead of a call to the office
The project manager asks about a clause, about the scope in a protocol or about the material budget on one site. The AI agent answers from the project documents.
An answer in 5 to 10 seconds, naming the source document

Proof

## Do you use this yourselves?

Yes. It is the only rollout we can put numbers on without asking a client for permission to publish their data: an AI agent running in production inside our founders' own company, launched in March 2026 and built by the method described above. Below is six months of measurement, together with what these numbers do NOT prove.

Built for ourselves. These are not client deployments but implementations inside the founders' own companies. We say so plainly, because proof you cannot verify is not proof.

- ![JustIdea Agency](https://justautomate.ai/klienci/justidea.png)![JustBot](https://justautomate.ai/agenci/justbot-80.webp)JustBottheir agent
JustIdea Agency, a performance marketing agency of around 30 people
23
people from the company work with the agent
38
systems wired in permanently
112
processes run without a human
475
thousand lines of the agent’s code
An agent wired into Google Ads, Meta, the CRM, the task system, the SEO tool, Analytics, Search Console and the data warehouse. First commit 1 March 2026, today 23 people use it.
8 of 38 systems it works in

  - Google Ads
  - Meta Ads
  - HubSpot
  - ActiveCollab
  - Ahrefs
  - GA4
  - Search Console
  - BigQuery
Before
In the twelve months before launch the agency ran at a margin of minus 4.42 percent. Across a twenty-month window there was not a single run of three profitable months.
After
May, June and July 2026 are three profitable months in a row, the first such run in the whole window. Revenue barely moved, so the change sits on the cost of delivery, not on sales.
Margin up 5.55 percentage points year on year, with revenue up 1.5 percent

How much the team actually uses it

Operations run by the agency agent in successive months of 2026, from the first commit in March. From 83 operations in March to almost 63 thousand in August, with users growing from 4 to 23\. This curve is here because a rollout nobody uses looks identical in a report to a successful one.

Measurement: Agent call log in the data warehouse, March to August 2026, counted at the level of a single tool invocation.

How much of it runs without a human

Of 64,903 operations run in the last thirty days, 29,854 went through without a human: client site monitoring, warehouse loading, ad account reviews, catching form submissions. The rest is work someone requested and reviewed. We give both numbers, because autonomy without oversight is not a feature but a risk.

Measurement: Agent audit log, the 30 days before 2 September 2026, split by whether a call had an associated human session.

And on your sites

## What if this will not fly on our sites?

Four sentences we hear in contracting firms more often than any others. We answer them the way we would on a call.

- Nobody on our sites is going to click through a system.
Which is why the way in is a phone and a photo, not a system. One action instead of five: picture, pick the stage, one line of description. If even that will not fly, we automate the office side and we do not pretend we will change the habits of a crew. We say that at the workshop, rather than hoping people get used to it.
- We estimate in our own software and we are not changing it.
No need to. We take the list of items and stages in whatever form your software exports, and we set it against actual cost. Estimating stays where it is, because that is the estimator's workbench and not the place where the money leaks.
- Our accounting sits on a server in the office, not in the cloud.
On-premise packages run on an SQL database and have no cloud webhooks, so nothing can look into them from outside. We put a connector inside your network that reads the database and exposes an agreed scope of data. We do this routinely, it is not an exception or a workaround. The scope is written down in the workshop and nothing outside it leaves.
- Every site is different, you cannot standardise this.
We do not standardise the site, we standardise the file: what a site entry looks like, who approves a change request, where the handover protocol lands and which stage an invoice falls under. A road contract and a building contract differ in scope of works, not in whether a photo carries a date.

Site reporting

mobile forms on a phone, a QR code at the site gate, photos with date and location

Teamwork

Microsoft 365, Google Workspace, Slack, shared drives

Estimating and measurement

cost spreadsheets, bills of quantities, exports from estimating software

Accounting and invoices

Sage, Xero, QuickBooks, on-premise accounting on an SQL database, subcontractor invoice approval

Running contracts

ClickUp, Asana, Jira, Notion, programmes kept in a spreadsheet

Automation layer

Make, n8n, custom API integrations

## What exactly we automate for a contractor

The usual split of paperwork in a construction company before the rollout and after it.

| Area                               | Today                                                | After the rollout                                      |
| ---------------------------------- | ---------------------------------------------------- | ------------------------------------------------------ |
| Site report                        | photos on the foreman's phone, description in a chat | a form entry in the job file, with date and location   |
| Handover protocol                  | written out by hand, scanned or not                  | generated from a form, with a number and an approval   |
| Change order                       | agreed on site, no trace of it                       | a numbered request with a decision and a date          |
| Measurement                        | copied from paper into a spreadsheet at night        | entered once, on site, straight into the schedule      |
| Stage cost                         | known after the month closes                         | invoice attached to a stage on the day it lands        |
| Warranty and inspection dates      | a spreadsheet and the manager's memory               | a reminder before the date, with the list of buildings |
| A question about a contract clause | a call to the office and a hunt through the inbox    | an AI agent answers and names the document             |

The scope of the first rollout is agreed in the workshop. We take the three items with the highest return and add the rest only once the first three work.

How we work

## Four steps from paper on site to a job file that fills itself

Each step ends with something you can judge before you decide on the next one.

1. ### Workshop on site and in the office
One week. We walk the site and we sit in the office. We follow the route from the contract, through the works and the change requests, to the handover protocol and the subcontractor settlement. We come out with a map and a list of the places where a record goes missing or gets made twice.
2. ### Picking three automations
From the map we take the three with the highest return and we measure them before we start: how many entries a day, how many hours of retyping, how many disputed changes a quarter. Without that number, after a month nobody can say whether it worked.
3. ### Building the first one
Fourteen days to a working solution. In construction we usually start with the site report, because it is the only entry a person makes in the field, and it decides whether the rest has anything to feed on.
4. ### Measurement, then the next one
After thirty and ninety days we check the indicators agreed in the workshop, including how many people actually use it. Only then do we decide on the next area.

Before and after

## How a project manager's week changes

### Before

- An evening in the office retyping measurements and notes from site
- Photos from three sites scattered across phones and chat groups
- A change order to be proven from memory, and only at handover
- The overrun against the estimate visible after the month closes

### After

- The entry is made on site, at the moment of the work, so the evening stays free
- The job file collects photos and descriptions by itself, sorted by stage
- A change request carries a number, a date and the name of whoever accepted it
- Stage cost against the estimate is visible in the week it grows

What changes is where the record is made: the site instead of the office. The number of things to record stays the same.

For the owner and the project manager

## What the person signing this off gets

The first thing shows up after a month: you stop learning about an overrun once there is nobody left to talk to about it. The drift from the estimate appears in the week it grows, so a conversation with a supplier, a subcontractor or the client still has a point.

The second is quieter and it counts in a dispute. A file of dated photos, numbered change requests and signed protocols is the material that defends your version in front of the client and in front of a court. Today that version is held in two people's memory, and those people sometimes leave.

- The drift from the estimate visible in the week, not after the month closes
- Stage documentation ready to show the client or the bank without collecting it from people
- Defect liability, warranties and inspections in one calendar, on the periods your contracts and local law set
- Knowledge of how the build actually went stays in the company when a manager changes job

What it costs

## The workshop price is published, the rollout is quoted after it

The workshop costs **EUR 3,500 net per week** and we give that price before the first call, because a company has a right to know what it is agreeing to. One contract usually takes a week; a firm running several sites at once sometimes takes two. We quote the rollout after the workshop, once we know how many systems we are connecting and what state they are in.

Tool cost goes to the vendor directly, or you pay nothing at all when the solution runs on your own infrastructure. No margin from us. The AI model cost is a vendor cost as well, in the range of EUR 0.005 to 0.07 per query depending on the model and the length of the answer.

- ### Process workshop
EUR 3,500 net
per week, usually one to two
A closed piece of work. It ends with a map of how site documents move and a 30-day plan you can run without us.

  - A week of work on site and in the office
  - A map of the route from contract through site to subcontractor settlement
  - Three automations with the highest return, costed before the start
  - The indicators to measure after 30 and 90 days
 Start with the workshop
- Most popular
### Workshop and first rollout
Quoted after the workshop
scope follows from the number of sites and systems
The variant most firms pick. A working site report fourteen days after the workshop, on your site and with your people.

  - Everything in the workshop
  - The first automation live 14 days after the workshop
  - A site form, the job file and numbering for change requests
  - Training for the person who runs it on your side
  - Measurement after 30 and 90 days
 Talk about a rollout
- ### AI agent for contractors
Quoted after the workshop
for firms running several contracts at once
For a firm where questions about scope, contract and stage budget come in a dozen times a day and end in a call to the office.

  - Everything in the first rollout
  - An agent answering from contracts, protocols and project documentation
  - Stage cost against the estimate, on request
  - Alerts on defect liability, warranty and inspection dates
  - Access for project managers, the office and the board
 Ask about the agent

If the workshop shows that your problem is not paperwork but the programme or the crewing, we say so and we do not propose a rollout. The workshop still ends with a document you can defend in front of your board without us.

## Frequently asked questions

What does automation mean in a construction company?

It means moving the record to where the work happens. The site report is made with a photo from a phone, the handover protocol and the change request come out of a form with a number and an approval, and the subcontractor invoice arrives with a stage attached. The data already exists in your company, it just sits on phones, on paper and in inboxes. Automation collects it into one job file. It does not replace your estimating software.

Our foremen will not tap on a phone, what then?

We start with the simplest possible way in: a QR code at the site gate, a photo, pick the stage, one sentence. One action instead of five. If even that will not fly, we automate the office side, meaning invoice flow, protocols and deadlines, and we do not pretend we will change the habits of a crew. We say that at the workshop, before we put a rollout quote on the table.

Do we have to bring in a new system to run the build?

No. We work with what you have: the shared drive, the spreadsheets, the estimating software and the accounting. We add a layer that ties those places together and makes sure a record is made once. Rolling out a new construction management system is a project measured in quarters, and the first working automation is meant to exist in fourteen days.

Will you connect to accounting software sitting on a server in our office?

Yes. On-premise packages run on an SQL database and have no cloud webhooks, so nothing can look into them from outside. We put a connector inside your network that reads the database and exposes only the agreed scope of data outward. That scope is written down in the workshop and nothing beyond it leaves.

How do you keep track of warranty and defect liability dates?

The handover date, subcontractor warranty periods and inspection dates land in one calendar the moment the building is signed off. How long you stay liable for defects, and how long the client has to object to a notified subcontractor, comes from the law where you are building and from the contract, so the periods differ between jobs and between countries. We enter your periods as rules, the system counts from the handover date, and it speaks up before the date showing which building and which subcontractor it concerns.

Will this improve the margin on a contract?

We do not promise that and we could not. Contract margin depends on the estimate, on material prices and on decisions a person makes. Automation looks after the paperwork and shows the drift earlier, so those decisions get made while they still change something. We do not promise a shorter build either.

How long from signing to the first result?

One week of workshop and fourteen days to the first rollout, counted from the end of it. We measure the effect after thirty and ninety days, on indicators agreed before the start, together with the number of people who actually use it.

What does the rollout cost after the workshop?

It depends on how many sites you run at once, on the systems we connect to and on the state of your documentation. We quote after the workshop, because that is when we know the answer. The workshop itself costs EUR 3,500 net per week and you know that price before the first call.

## Let us start with one site

The free consultation takes 30 minutes. We walk one of your processes, usually the route from a site photo to an entry in the job file, and we tell you what can be closed in fourteen days and what needs the documents tidied up first. You do not have to give us access to any system at this stage.

We run at most two rollouts at a time, so that somebody is actually sitting on each one.

[Book a free consultation](https://justautomate.ai/en/contact/)

**PS.** If someone in your firm looked for a photo proving the scope this week and did not find it, that is exactly the problem. An entry made on site closes it. An entry retyped in the office that evening does not.

## Related

- [Document automation](https://justautomate.ai/en/services/document-automation/)
- [Reporting automation](https://justautomate.ai/en/services/reporting-automation/)
- [Notification automation](https://justautomate.ai/en/services/notification-automation/)
- [BOND: business AI agent](https://justautomate.ai/en/services/bond-business-ai-agent/)
- [Manufacturing automation](https://justautomate.ai/en/industries/manufacturing-companies/)
- [All industries](https://justautomate.ai/en/industries/)

---

**JustAutomate** · contact: contact@justautomate.ai · form: https://justautomate.ai/en/contact/