AI-native chat interface

Ask the project one question and get an answer you can hand to someone else. Stoa goes through everything the project holds at once: drawings, specifications, contracts, minutes, the schedule, the inspections logged in your quality app, and the email that holds the actual decision. It reads the drawings themselves, not only the text around them. Every sentence comes back with the document and page behind it, so you can check it rather than take it on trust. Ask in whatever language you work in, whatever language the documents are written in, at a desk or out on site from your phone.

2–8 h

a week back per person on complex sites, design partners report. Most of it is time that used to go into finding where something was written down.

Interview conducted with design partner (7/2026).

Linked documents

Open a floor plan and everything marked on it is live. Click a wall type and every place it appears comes back: the detail that defines it, the schedule that lists it, the clause of the specification that governs it — each one the sheet itself, at the right place, not a search result you still have to find your way into. The same for a room number, a door tag, an RFI the drawing answers. You stop leaving the drawing to find out what the drawing says.

Change feed

Every change in the project lands in one feed, found rather than announced: a drawing reissued, a specification revised, a date that moved. The feed is filtered to the scope you are answerable for, so what you open already concerns you. Open one and it says what it is — which document, which revision it supersedes, what is standing on it, and where it now contradicts another discipline. Put the two revisions side by side and what the designer actually moved (a dimension, a wall type, a whole region of a sheet) is read off the drawing itself instead of trusted to a revision note.

Project dashboard

Where the project actually stands, on one page, at the altitude the reader works at. A site manager, a project engineer and the client's representative open the same project and see different things, because what counts as a blocker depends on what you are answerable for. Blockers are found rather than reported — the drawing an activity is waiting on, the approval that never came back, the revision that moved a date underneath it — and every task in the schedule has its readiness written up before anybody asks: what it needs, what is in place, and the one thing that is not. This is the part that can only exist once everything above it is connected: the schedule knows which documents it stands on, and those documents know what changed this week.

Automation features

A problem arrives: an RFI, an inspection that failed, a delivery that slipped. Everything attached to it arrives with it, the drawings, the clause, the activity it blocks, the people who have to know. From there you act. Take it out as a report in Word, Excel or PDF, or hand the whole pattern to an agent you built yourself, so the next one is handled before anybody opens it.

AI-native project document bank & schedule

Two products, not a by-product of the sync. A project bank where the team keeps its documents and a schedule where it keeps its dates. Either one is enough to run a project on, whether or not anyone ever asks Stoa a question. They stand side by side because they hold the same material: every activity in the schedule stands on documents in the bank, and the bank always knows which sheet is the one in force. They read from the systems you already run, and they work the same if you never connect one.

Everything the project already knows, feeding one place.

Built for the way construction information behaves

Source-exact citations

Always the current revision

Multilingual

Roles, scopes, audit

What the layer gives you