“The answer and the place are the same interaction, so nobody goes hunting.”
Not after it
Measured, not recalled
Flying the camera to the element in question
Answers building questions against the live model.
ReadsElement types, quantities, rooms, scope and budget
Best forStand-ups and stakeholder walkthroughs
What is blocking the pool, how far apart are those columns, which rooms are behind. Answering in text leaves the hardest part undone, because you still have to go and find the thing.
Flying the camera to the answer removes that step. You are looking at the element being discussed while it is being discussed.
Geometry and quantities:
Spans, distances, areas and counts taken off the model itself.
Rooms and storeys:
Which room, which floor, and what sits behind the wall you are looking at.
Scope and budget:
The scope lines and costs already attached to the element you asked about.
In a room full of people, an answer that arrives tomorrow is not an answer. Meetings end with actions to go and check things.
The question gets asked and answered in front of everyone, off the model rather than from memory.
Built for GMs and facilities managers
Spans and distances come off the model geometry, which is why they can be checked against a code clause instead of taken on trust.
It also puts you in place: the elements behind the answer are highlighted and the camera flies to them, so pricing that selection or raising a ticket against it is the next click, in the model, rather than an action item for later.
One live model:
Every trade works the same twin in the browser studio, with nothing to install.
Ask in the model:
The copilot flies to the room you asked about.
Nothing gets lost:
Notes and tickets stay pinned to the element itself.
Bring the files you already have. We will show you the twin you keep for the life of the building.