Why we built Archiboost
A note from the founders on scattered project information, the limits of manual review, and the kind of AI assistance architects actually need.
Every architect knows the moment: a set is close to going out, the team has already reviewed it, and someone finds a conflict that was visible all along. The answer was somewhere in the drawings or specs. Finding it required the time and attention that a busy project rarely gives away.
We are Georgios Kontominas and Vasu Jogani, the co-founders of Archiboost. We started the company because we believe that part of the work can be better supported. Project information is spread across drawings, schedules, specifications, codes, and past decisions, while the person checking the work needs all of it in one place.
Review should begin with context
On a complex project, a reviewer is asked to catch relationships between documents, not just errors on a single sheet. Does the schedule match the plan? Does the specified assembly match the detail? Is the relevant code requirement reflected consistently across the set?
Archiboost Drawing QA/QC helps teams look for those connections across drawings and specifications. It surfaces possible coordination, code, and constructibility issues with source references, giving reviewers a starting point they can verify. The team decides which findings matter and what to do next.
That is the role we want AI to play: bringing the evidence into view, while architects retain judgment and responsibility for the design.
The same problem continues beyond QA/QC
Getting a reliable answer can mean searching a project folder, a code book, a firm's standards, and previous work. Project Copilot helps teams ask questions across those sources and trace answers back to citations. Detail Library lets firms search and reuse their own details instead of rediscovering them project by project.
These tools are connected by one idea: valuable knowledge already exists inside the work. Making it accessible at the right moment can make a review more thorough and a decision easier to check.
What comes next
We are opening the Archiboost site to the public so more teams can see how the platform works and tell us where their review process gets stuck. We will share what we learn here: product changes, examples of useful checks, and the questions we are still trying to answer.
If you lead QA/QC, manage a project team, or are simply tired of finding a preventable conflict after issue, book a conversation with us. Tell us how your team reviews a set today. We would like to show you what Archiboost can add to that process.
