Rouandi: an AI estimating workflow deployed inside a civil engineering firm
Rouandi is a civil engineering and construction firm. Mirage deployed one Construction Intelligence workflow directly inside its estimating process: real projects, real documents, the team reviewing every output. That review became the feedback loop that made the workflow reliable, and the basis for expanding it. This page sets out what was deployed, how, and what the team kept in its own hands; it publishes no figure Rouandi has not.
Updated .
About Rouandi
Rouandi is a civil engineering and construction firm, the kind of operation Mirage's Construction Intelligence products are built for: estimating and engineering teams working from technical drawings and documents on live projects.
Rouandi had already adopted the Mirage Intelligence platform. The next step was deploying it inside a real workflow, not running it as a standalone tool on the side of the team's actual process.
Defined scope
Rather than roll the platform out broadly, Mirage and Rouandi picked one real workflow already running inside the team's estimating process and deployed Construction Intelligence directly into it. Narrow scope, real documents, a live project: the deployment had to hold up under actual use before it earned the right to expand.
What the workflow reads, what it returns, who reviews
The shape of an estimating workflow as Mirage deploys it in a civil engineering firm. The documents are Rouandi's own; the rows describe the mechanism, not Rouandi's figures, which this page does not publish.
| Reads | Returns | Reviewed by |
|---|---|---|
| Technical drawings and documents of a live project, as issued | Structured output for the estimate, each item tied to the document it came from | Rouandi's estimating team, before any use |
| The team's corrections on the previous output | An adjusted system before the next document: a correction becomes a rule | Mirage's engineers, with the team |
| The edge cases that only show up on a live project | Handled case by case during the deployment, not in a slide deck | Both, on the document that raised them |
| New document types, as they are brought into the loop | The same review cycle, extended | The team, as part of the expansion |
No output reached the estimate without a person on Rouandi's side accepting it. That rule is the one every Mirage construction deployment keeps: estimators validate instead of measuring.
Deployed with the team
Mirage's engineers did not hand Rouandi a platform and a manual. They worked directly alongside the team on their real documents, the workflow's actual edge cases, and the situations that only show up once you are running on a live project, adjusting the system as those cases came up instead of covering them in a slide deck. Training happened along the way, as a by-product of the work, not as the point of the engagement.
The five steps, as they applied here
Every Mirage deployment follows the same five steps, in this order. At Rouandi they looked like this.
| Step | What it means | At Rouandi |
|---|---|---|
| Observe | Engineers spend time with the operational team before writing anything | Time with the estimating team on the workflow it already ran |
| Map | Workflows, exceptions, data sources, manual checks and escalation points mapped with the team | One workflow chosen, its documents and its checks written down |
| Build | The system is built around the constraints observed on site | Construction Intelligence deployed into that workflow, on live documents |
| Run | In production with human supervision and feedback loops from day one | Every output reviewed; every correction fed back before the next document |
| Expand | Once a workflow is trusted, the same team moves to the next one | More workflows, new document types and more of the team, as set out below |
The clocks are the same for every client: a reply within two business hours, a proof of concept on the client's own documents one week after the first meeting, and the first workflow in production in 4 to 6 weeks. Workflows spanning several systems can take longer and are scoped at the first meeting.
Human in the loop
Every output the system produced went through Rouandi's team before it was used: they validated it, corrected what needed correcting, and that correction became the input Mirage used to adjust the system before the next document. Output, review, correction, adjustment, repeated on every real document, is what took the workflow from a working demo to something the team could rely on without re-checking the parts it had already got right.
Adoption
The workflow is now part of how Rouandi's team runs that piece of estimating, not a pilot running alongside the real process.
Where it goes next
- More workflows deployed into other parts of Rouandi's estimating and engineering process
- New document types brought into the same review loop
- More of Rouandi's team working directly with the system day to day
Start with one workflow. Make it reliable with the people doing the work. Then expand.
FAQ
One Construction Intelligence workflow, inside Rouandi's existing estimating process, on real projects and real documents, with every output reviewed by the team before use. Rouandi had already adopted the Mirage Intelligence platform; this deployment put it to work in one real workflow rather than beside the process.
Two: one estimating workflow in production with every output reviewed by the team, and five or more team members trained on the system. No time saving, accuracy or volume figure is published for Rouandi, and this page does not estimate one.
Rouandi's estimating team. Every output went through the team before it was used; their corrections adjusted the system before the next document. Nothing reached an estimate without a person accepting it.
Forward-deployed, in Mirage's five steps: Observe, Map, Build, Run, Expand. Mirage's engineers worked alongside the team on live documents and the edge cases that only appear in production, and training happened as a by-product of that work.
For every Mirage client: a reply within two business hours, a proof of concept on the client's own documents one week after the first meeting, and the first workflow in production in 4 to 6 weeks. Workflows spanning several systems can take longer and are scoped at the first meeting.
OCBM, a general contractor, with three agents in production and every quantity traceable to its source drawing; and John Cockerill, an industrial engineering group, with 80 to 90% less time on piping takeoff and a fabrication bill of materials ten times faster. Both are linked below.
See what Mirage can run in your operations
Show us the workflow that costs you the most time
Leave your work email, then pick a time for a 30-minute call. We look at one of your workflows together, and you leave with a written plan to automate it. No commitment.