A.I. that removes your failure costs.

That's exactly why it works. In construction the lost time isn't on site, it's around the site. The report typed up at the office in the evening. The quote request forwarded three times. The five phone calls it takes to move one planning slot.

An example. At Renoffice a coordinator used to write his site report at the office, hours after the site visit. Now he dictates it on a tablet, on site, with photos attached. The report is finished before he's back in the van. The business case counted on more than 80 hours saved a year.

Honest answer: only if it's less work than what they do today. Otherwise they won't.

That's why we build in as little typing as possible for site work. Dictating instead of typing. Taking a photo and drawing on it instead of describing it. One button instead of a menu.

And we deliberately keep email alive. At Renozen, workers and subcontractors still get an email when a new task comes in, because not everyone works fully digitally. The difference is that everything now leaves from one system instead of four.

We get that question at almost every construction firm. WhatsApp works, until you have twenty sites and nobody remembers which group holds which agreement.

What we do in practice: the subcontractor sees only their own sites, with the latest version of the drawings and their tasks. Nothing to search for, nothing to install. If they report a problem, it lands straight with the site manager instead of in a group of thirty people.

At Renoffice that runs through a chat: the subcontractor says who they are, and gets their planning for the day back.

No, but the approach is different. At a large firm it pays to build your own platform. With a crew of five or ten, the gain usually sits first in your mailbox, your reports and your quote preparation.

That's also cheaper to start with. We'd rather tell you that you don't need custom software yet than build something your volume won't pay back.

We start with a session where we map the opportunities together. Then we take one idea and work the numbers through completely: how much time that process really costs today, what's left over, what the build and the yearly running cost come to. So you know what it returns before the first line of code.

At Renoffice the maths was simple: four coordinators, forty working weeks, half an hour less work per site visit. That's more than 80 hours a year.

We only take on projects we believe will pay for themselves. If the numbers don't add up, we'd rather say so now than after three months. We don't price on the basis of what you can save. You pay for the build, not for your own gain.

Usually yes, and if not we say so up front. We work inside what you already have. Microsoft 365 and SharePoint, Teamleader, your ERP or accounting package, your planning tool, your folder structure on the server.

Where it sometimes gets stuck: packages running on your own server, or vendors who don't open an API. It happens. Then we look for a way around it, or we tell you the idea isn't feasible today.

Send us the names of your packages and you'll have an honest answer within the day.

No, and that's good news, because otherwise you'd never start. What does help: one place where a site's documents live, SharePoint for instance. Not perfectly ordered, but in one place.

A.I. can actually do part of the cleaning up itself. At TSG Belgium, a technical service provider for fuel and payment systems, we made more than 1,000 technical documents searchable. A technician enters an error code and gets the right answer straight away, with the document name and page number alongside it. At an estate agency we pulled phone numbers out of free-text notes to make the files usable again.

Yes, and today that's one of the most requested applications in construction.

How it works: your coordinator picks the site, marks who was present, takes photos per item and dictates their remarks. A.I. turns speech into text and rewrites it into a clean formulation. On the photo they can mark what it's about. The report comes out as a PDF, ready to send.

The gain isn't only time. Reports now look the same everywhere, and what was said on site actually ends up in the report.

Partly, and here we're deliberately careful.

What works well today: the preparation. Pulling a quote request out of your mailbox, finding the attachments, checking what's missing, creating the project folder and setting up a first version in your own template. At Renozen the checking folder and the contractor quote fill automatically as soon as a quote is marked accepted. Nobody retypes quote lines any more.

What isn't reliable enough today: extracting a complete bill of quantities from a drawing and trusting it blindly. Too much money hangs on a single mistake. So your estimator stays at the wheel. A.I. delivers the preparatory work, it doesn't set the price.

A first version, yes. Final responsibility, no.

At engineering consultancies we see the same question come back every time: can A.I. gather the data from addresses, drawings, measurements and the Flemish databases, and turn that into a first report. It can, and it saves a lot of research.

But a report with a technical conclusion needs experience and interpretation. Anyone who can't judge the source can't sign the report. So we build towards a system you can check: for every piece of information you see where it came from. The control sits where the risk sits.

Yes, and this is often the fastest first step.

Dryguard is a damp-proofing contractor. The owners got the same questions in every day about prices, rising damp, planning and guarantees. We analysed seven years of sent mail to capture their own writing style, and put their expertise into a knowledge base they manage themselves. Three times a day there are now drafts waiting in the inbox.

On recurring questions we estimate the time saved at 30 to 50 percent per reply. The agent never sends by itself. The owner reads, adjusts and sends.

At Bouwunie, the umbrella organisation for construction firms in Belgium, we did something similar with the general inbox: every email is matched to the right expert and routed automatically.

No. And our clients don't want that either.

What we automate is the work around the conversation: gathering the data, writing the report, setting up the follow-up. At Renozen the salesperson dictates the client meeting and the client gets a summary afterwards. The conversation at the kitchen table stays human. There's just nobody left who has to type it up in the evening.

Recording is allowed, but not just like that. In Belgium you have to inform the other party, and you need a valid reason to keep and use the recording. That's a GDPR question, not a technical one.

How we handle it in practice: the salesperson asks the client explicitly for permission before recording further. We agree up front what is kept, for how long, and who can access it. And we put that on paper instead of arranging it afterwards.

We're not lawyers. If you're in a situation where the letter of the law really matters, we'll tell you to check it with your legal adviser.

Yes. We're only the party working with it on your instructions. We put that in a data processing agreement at the start of every programme, not afterwards. It sets out who can access your data, where it lives, how long we keep it and what happens if you stop.

Processing stays within Europe and your data is never used to train A.I. models. For client files we don't work with public chat tools.

There's the European A.I. Regulation, the AI Act. For the applications this page is about, site reports and internal automation, you're in the lowest risk category. We take this along in the programme and put it on paper, so you have something to show if anyone asks.

Two things already matter today for a construction firm:

• You have to give your people basic A.I. literacy if they work with it. That obligation has applied since February 2025.
• Image, video or audio created or altered by A.I. has to be recognisable as such. Those transparency rules apply from 2 August 2026. That's mainly relevant for your marketing and your 3D visuals.

We see that often. Someone launches a tool, and a few months later half the team has stopped using it. Usually the tool isn't the problem. Nobody owned it, and too much came at once.

What does work: one internal owner, one process at a time, and a recurring moment where we look together at what's sticking. We've learned ourselves what happens when you skip that. After about three months you fall back on the old way of working.

A fair concern, and you're right to test it first. A programme without buy-in becomes a tool nobody opens.

That's why we start with the people who do the work, not with management alone. In the session where we map the opportunities, site managers, planners and administration sit at the table together. They know where it grinds. And we prefer to pick the first project where someone is most frustrated today.

The question of whether this replaces someone's job comes up almost always. Our answer: no, but it does change which part of your job you still do yourself. That's a conversation you're best having with your own crew, not us.

Often an existing package is the right answer, and then we say so. We're not an extension of a software vendor and we get no commission for pushing you somewhere.

The reason to build your own is usually a combination that doesn't exist in any single package. At Renoffice that was dictating, annotating on the photo and messaging the subcontractor directly, together in one app. At Renozen it was the link between the approved quote, the documents and the site follow-up.

If your package does cover it, our solution doesn't need to sit in between. That's how you avoid double costs.

Less than you think, but not zero.

The start asks the most: sitting down once to map out your process and get your settings right. After that we work in short sprints with a demo every week. At Renozen that was half an hour a week from the owner and a few users.

What we don't do: build for months and then deliver something you haven't seen anything of yet.

We'd rather go live small and adjust on real sites than build for months on something that returns nothing yet. How fast you see results depends on what you choose:

• A mail agent or a notetaker flow: count on one to two months.
• Your own app for site reports or site follow-up: at Renoffice less than eight weeks from idea to working version. At Renozen ten one-week sprints, with a first group of users straight after.

Then you have to be able to stop it before it goes out. That's why there's a human in between as standard with us.

Concretely: the coordinator reads their report before it's sent. The agent prepares a draft, it doesn't send by itself. When there's doubt about which file or which subcontractor, the employee gets a choice instead of a wrong link.

And we test in silent mode first. The flow does its work, but you only see what it would have sent. Only when you say it's right does sending get switched on.

There is one, and it's this: A.I. doesn't free up time out of nowhere. The gain sits in the preparatory work, and that gain only becomes money once you also decide what to do with the time freed up. Taking on more sites with the same crew is a choice, not an automatic consequence.

Two things we've seen underestimated in construction. Integrations with packages running on your own server are tougher than a demo suggests. And if the data in your system is wrong, no A.I. can make anything good out of it. At one client, 35 to 40 percent of the conversations turned out not to be linkable automatically, because the phone numbers sat in the wrong field.

That's why we measure up front how much time a process really costs today, instead of working from assumptions.

We've worked with more than a hundred companies. In construction and renovation with Renoffice, Renozen and Dryguard among others, and with engineering consultancies and sector federations. The projects range from site reports on a tablet and one platform for site follow-up to a mail agent and a searchable knowledge base.

Want to talk to someone from the sector before you decide? Ask in the meeting. We'll put you in touch with a client who went through the same thing.

A half-hour conversation where we ask how you work today. No demo, no slides.

If we see an opportunity worth having, we propose a session where we map every idea with your team and prioritise three to five of them. If we don't see it, we say that too.