Drawings, contracts, permits, certificates and RFIs in one repository with version control and approval paths. Who changed what and when is in the history, not in someone's inbox.
The designer emailed the new revision to the site manager. The site manager was on holiday. The wall stands in the wrong place and someone has to pay for it.
The foreman asks about a detail, the designer answers on the site manager's phone. A year later, in a dispute with the client, nobody can prove who agreed what.
Declarations of performance and technical data sheets sit in supplier emails, on USB sticks and in a box in the site office. Before final handover, someone spends a week calling for the missing ones.
A structure built around your projects and your numbering. Design studios stay in their own software, the system organizes what comes out of it.
Three years ago features like these needed a data science team. Today language models read emails, documents and photos, and we build them into the system we make for you. Below is what makes sense in this solution. A person approves, AI prepares.
AI reads the uploaded PDF, recognizes the type (drawing, contract, certificate, decision), number, revision and discipline, and proposes a place in the structure. The document controller clicks "approve".
Example file "K-12_revC_slab.pdf" from an email → structural drawing K-12, revision C, stage "slab over 1st floor", revision B marked superseded
Beyond overlaying the drawings, AI describes what changed: moved openings, a different section, new reinforcement. The site manager gets a list of changes instead of only coloured patches.
Example revision B → C of an architectural drawing → "door D3 moved 40 cm, lintel added on grid 5, partition wall thickness changed"
From the drawings, specifications and earlier RFIs on the project, AI drafts a response. The designer corrects and signs instead of writing from scratch.
Example RFI "what concrete class in the ground-floor columns?" → a draft response quoting the specification and drawing number, for the structural engineer to approve
AI compares the BoQ and deliveries with the list of uploaded certificates and declarations. Whatever is missing goes on a list with the supplier's name and a draft email asking for it.
Example BoQ: mineral wool for the facade → no declaration of performance from the supplier, a ready email requesting the document
We do not force design studios to change tools. Revisions come in from Revit, Archicad and AutoCAD as PDF, DWG or IFC, and contracts from the mailboxes and drives where they sit today.
The first version solves the most frequent problem: which revision is current. Contracts, certificates and approval paths follow once the site is already using the repository.
You have the diagnosis, we build the solution. Web applications, B2B portals and automations for companies without a large IT department. Today a system can read emails and documents, suggest decisions and answer customers on its own, so we build that in from the first version, not as an add-on a year later.
We agree scope, price and dates upfront, show progress every week, and the code and data stay yours.
You describe how a revision travels from the studio to the site today and where the contracts live, we tell you where to start and how long it takes.
Write to us