AI automation for contracting, MEP and fit-out firms in the UAE
Every tender goes out complete and on time, and the price stays with the people who set it.
The drawings, the specification, the BOQ and the client’s own forms are read as they arrive, and the pack is assembled against what this client and this project actually ask for. The quotes still outstanding are chased on a schedule, the pricing stays where it is decided, and what cannot be resolved stops at a person with the reason attached.
Four jobs a contractor repeats.
The tender
Assembled while there is still time to price it properly.
An invitation arrives as drawings, a specification, a BOQ and the client’s own forms, and someone has to turn all of it into a submission that answers every line. The documents are read as they arrive, the pack is built against what this client asks for every time, and your estimator opens it ready to price.
The submittal
Approved the first time, not returned marked up.
The material submittal, the shop drawing and the method statement have to answer the specification clause by clause, and what comes back marked is usually one reference or one attachment nobody caught. Each pack is checked against the specification and against what this consultant has asked for before, and what does not line up is named while there is still time to fix it.
The variation order
Submitted with the evidence attached, not reconstructed later.
An instruction changes the work, and the claim for it has to carry the drawing revision, the site record, the dates and the rates it prices against. The file is built as the evidence appears rather than assembled at the end, and it reaches the person who signs it with the gaps already named.
The subcontractor quote
Compared on one basis, in one place.
Quotes come back in different formats, against different scopes, with the exclusions buried in different places. They are read as they arrive and laid out line against line with the gaps and the exclusions named, and the award stays a call your team makes.
Construction software ends at the login.
It holds the programme and the cost codes, and the assembly still happens in someone’s head. Runbook arrives knowing your business, because writing down how you actually build a bid is where we start.
You own it. No seat bill.
It runs in your cloud account. If you stop paying us, it keeps running. What stops is us watching it, fixing it and extending it.
How the work runs.
The audit
We sit with the people who make the calls and read everything they read, including the exceptions that are not written down anywhere. You get the work mapped, the jobs ranked worth programming and not, and the value case in your own numbers.
The build
The data layer first, then the agents on top of it. It ends in production, inside the systems your team already opens, not in a pilot.
The run
We watch it and extend it as the work changes. Failures reach us before they reach you.
You leave the first meeting with a one-page sketch of the job you brought.
Questions contractors and MEP firms ask.
Does this price our work?
No. The rates, the margin and the commercial call stay with the people who make them, and nothing goes out that a person has not approved. What the system does is build the pack around that decision: gather the documents, lay the quotes out on one basis, carry forward what was submitted last time for reference, and chase what is still outstanding.
Every tender is different. How can it be programmed?
The same work sits behind every bid: a specification to read against the BOQ, the client’s own forms to answer in the format that client insists on, qualifications to write, subcontractor prices still outstanding. Runbook builds that pack in whatever format the documents arrive. What changes from bid to bid is the number and the risk your firm agrees to carry, and neither of those is ours to set.
Where does the system stop and where do we decide?
It stops at any line it will not cross alone, and that line is drawn with you before anything is built. A submittal that does not match the specification, a quote with a scope gap, a variation with evidence missing: each one stops and goes to the named person with the reason attached, rather than being resolved quietly.
Our drawings and quotes arrive by email, live in a drive, and the rates sit in a spreadsheet. Does that matter?
No. That is where most of this work already sits, and attachments arrive in whatever format the sender used. We build the data layer that reads those sources as they are, including the spreadsheets that hold the rates and the exclusions, and the agents run on top of it.
How long does it take?
The scope, the fee and the finish date are agreed with you in writing before anything starts. We do not publish a length, because it follows the size of the operation, how many systems the work touches and what condition the data is in.
Who owns it when you leave?
You do. The code, the credentials and the documentation sit in your accounts and under your name from the day we start. It runs in your cloud account, and if you stop paying us it keeps running.
What does the first meeting cost?
Nothing. It is forty five minutes, and you leave with a one-page sketch of the job you brought: the steps as they run today, where the line would sit, and what we would measure.
We are an MEP subcontractor, not a main contractor. Does this still apply?
Yes, and the same holds for a fit-out firm pricing to a developer. The shape does not change with who you price to: an enquiry arrives, a pack has to be assembled around it, quotes have to be compared on one basis, and what is outstanding has to be chased. We start from the way your firm actually runs it, not from a template of the sector.