Change orders, RFIs, and the email avalanche: what small construction firms automate first

A general contractor running about $50M in revenue loses 333 project-management hours a year to manual RFI and submittal handling. That’s eight working weeks. Add change orders, supplier emails, daily reports, and the inspector paperwork nobody went into this business to write, and the project managers in your office now spend 3 to 3.5 hours per day on email alone. None of that time swings a hammer.

If you run a small construction firm in Europe — five to thirty staff, somewhere between a residential GC and a regional specialty contractor — you’ve felt this. The volume of admin per project has roughly tripled over the last decade while your office headcount hasn’t.

I want to walk through what’s worth automating right now, what isn’t, and where the new generation of construction-AI tools actually fits a firm that doesn’t have a CTO.

The numbers nobody wants to look at

Two studies anchor every honest conversation about RFI and change-order admin.

The Navigant Construction Forum analyzed 1,362 construction projects and found the average project generated 796 RFIs. Median response time was 9.7 days. Around 22% of RFIs got no response at all. The average review-and-response cost per RFI was $1,080, roughly eight combined hours of admin and technical work. About 13% of RFIs were “not justifiable” — the answer was already in the contract documents — which alone wasted six figures on a typical large project.

That study is from 2013. The problem hasn’t gone away. Procore’s 2024 benchmark data, pulled from live customer projects, shows a 7.3-day average RFI response time and a 10-day submittal turnaround. Better than 2013, sure, but still long enough that a question raised on Tuesday doesn’t get a clear answer until the following Wednesday — by which point the trade is either guessing or sitting on its hands.

Then there’s rework. The FMI / PlanGrid “Construction Disconnected” study found 48% of all construction rework comes from poor communication and bad project data. The follow-up FMI/Autodesk numbers put rework at 5–9% of total project cost, with about $7.1M in avoidable rework per $1B of revenue for a typical contractor. Scale that down to a €5M Lithuanian GC and you’re still looking at real money disappearing into emails that didn’t get sent or got sent to the wrong person.

If you’ve been told the answer is “more software,” look at your existing software bills. That’s part of the problem, not the solution.

Why this particular moment matters

A few things changed in the last year that are worth naming.

Construction labor in the EU is getting worse, not stabilizing. FIEC’s November 2025 position paper on labor shortages projects the bloc needs roughly 2 million additional construction workers by 2030. The European Commission’s Q2 2025 indicators show 28.7% of EU construction managers report labor shortage as a binding constraint on production. Lithuania filled its 2024 third-country worker quota early and left construction firms here especially short-handed. The OECD’s 2025 Economic Survey of Lithuania flags demographic decline as a structural drag on the sector.

You can’t hire your way out of this. Even when you can find people, they don’t want to spend their day on RFI emails — they want to be on the site.

The AI tooling stopped being theoretical at the same time. On April 2, 2026, Trimble announced it’s acquiring Document Crunch — an AI contract-review tool already used on 10,000+ projects by names like Balfour Beatty, Barton Malow, and DPR. Procore’s Groundbreak 2025 launched Helix, Assist, and Agents as native AI inside the platform, with Polish among the first localized languages. Trunk Tools closed a $40M Series B in July 2025 led by Insight Partners. Its pitch: “ChatGPT for the jobsite.” Turner Construction, the largest US GC by revenue, announced a wall-to-wall ChatGPT Enterprise rollout at its Nashville Innovation Summit last October.

A small contractor in Vilnius doesn’t need to copy Turner’s playbook. The point is that the question stopped being “does this work yet” and became “where do I start.”

What I automate first for a small construction firm

I usually open the conversation with one number: how many emails did your project manager handle yesterday? Most owners don’t know — but if you put a counter on the inbox, the median for a working PM is 38 to 50 emails per day, most of them RFIs, submittal questions, supplier confirmations, and inspector follow-ups.

Five workflows tend to come off that pile first.

RFI triage and drafting. Every RFI lands in the inbox alongside everything else. A construction-specific AI agent reads the incoming message, classifies it, checks the contract documents and the drawing set the question references, then either drafts a response (when the answer’s in the docs) or routes it to the right architect or engineer with the relevant context already attached. The 13% Navigant figure — RFIs that should never have been raised — gets answered automatically. The rest reaches a human with the homework done.

Change-order drafting and impact calculations. A scope change comes in by email. The agent pulls the original contract, the schedule, your historical labor and material rates, and drafts the change order with cost and timeline impact filled in. You review and send. Industry analysis suggests projects that standardize their change-order process cut admin delays by more than half. Standardization is the part AI does well, because it does the same thing every time.

Submittal tracking. This is the quiet killer. A typical mid-size project has hundreds of submittals in flight at any given time, and the standard failure mode is that one gets stuck on someone’s desk for three weeks while the trade twiddles its thumbs. An agent that watches the submittal log, sends nudges on the right cadence, and escalates when something’s been sitting longer than your defined SLA buys back days per project.

Daily reports. A foreman snaps photos and records a voice memo at the end of the day. The agent generates the daily report — manpower, weather, work completed, materials used, safety observations — formatted for whatever standard your jurisdiction expects. The PM reviews and signs. What used to be the two hours of paperwork the foreman does after he leaves the site becomes about twenty minutes of editing.

Supplier and subcontractor email. Most of it is routine: order confirmations and delivery scheduling, plus the late-payment chasers nobody enjoys writing. An agent drafts the responses, the office reviews in batches, and your PM stops moonlighting as a part-time AP clerk. The pattern is the same one a small marketing agency I worked with used to claw back 15 hours a week from email — different industry, identical mechanic.

If you’re already on Procore, Buildertrend, CMiC, or Autodesk Construction Cloud, most of these workflows can plug into the platform’s API rather than living separately. If you don’t yet — most small EU contractors I work with run on a mix of email, WhatsApp, and Excel — the agent runs as a layer over those tools without forcing you to migrate.

The privacy question

A construction firm’s bid file is one of its most sensitive business documents. Your historical project costs and markup patterns are exactly what competitors would pay to see. So the question of where the AI runs matters more here than in some other industries.

I work with three privacy tiers and I let the client choose based on what they’re actually moving through the system.

A Mac Mini or Mac Studio in your office running an open-weight model handles the most sensitive workflows: bid pricing and anything you’d consider confidential. Nothing leaves your network. April 2026 isn’t 2024 — open-weight models like Gemma 4, Qwen 3.6, and DeepSeek V4 have caught up to closed models on the kind of structured-text tasks construction admin actually needs. Cloud APIs from Anthropic or OpenAI work fine for less sensitive workflows like supplier email and public RFIs. A dedicated GPU server hosted in Frankfurt or Vilnius sits in the middle for firms with serious data-volume needs.

Most small contractors don’t need fully on-prem AI. They need to know that the choice exists, and that the consultant they hire will explain the trade-offs in plain language rather than push them toward whichever option pays the highest commission.

What this doesn’t replace

A few honest limits worth naming.

AI doesn’t make estimating decisions. It helps you assemble a draft estimate fast — pulling history, applying your rates, flagging the gaps — but the bid number is still yours. Same for change-order pricing: the agent calculates the impact based on your inputs; you decide whether to push, swallow, or split it with the owner.

It doesn’t read between the lines on a hostile email. If a difficult client is heading toward a dispute, the agent’s draft response will be technically correct and emotionally tone-deaf. That’s a moment where you take over.

And it doesn’t fix process problems. If your RFIs are slow because your architect of record won’t return calls, an agent doesn’t make the architect call back. It does make it harder for him to ignore you, because the follow-ups now go out automatically on a defined cadence with the deadline written into every message.

If you’ve been held hostage by a high-performing PM — the one person in the office who knows where everything is and how everything works — the right time to start is before they leave, not after.

What it costs

For a five-to-thirty-person construction firm, setup runs €4,000 to €9,000 depending on how many workflows you start with and how messy the existing data is. Monthly runtime and maintenance lands in the €350 to €700 range. Most contractors I work with start with one workflow — usually RFI triage or daily reports — prove it pays back, then add the next.

That’s well below what you’d pay for an additional admin hire, and the agent doesn’t take parental leave or get poached by the competition.

I built lobsterpack.com because most European small contractors are getting either oversold by enterprise platforms or undersold on what’s now possible with a quiet local setup. If you want to talk through what would actually move things for your specific firm, look at the construction industry overview or book a discovery call. I’ll give you an honest read — including, sometimes, “you don’t need this yet.” That answer is also fine.