Take-offs that refresh
The take-off was right on the day it was done. The model has moved since.
Counts are read straight from the model, and every item is linked to its spec and package. When a revision lands, the take-off is run again, not redone.
Every answer cites its source. People decide.
How it works
Ask. Inspect. Verify. Publish.
Ask
A plain-language question.
Inspect
The full blast radius, on the model.
Verify
Checked against the governing drawings and specs.
Publish
A dashboard, report or register, citations attached.
One job, start to finish.
Values come from a structured reference campus, not from a client project.
- 01
Reference campus: 96 electrical cabinets across 6 halls, 16 in Hall 2.
- 02
One shared product, one package, one long-lead order.
- 03
1,440 racks on campus, 240 per hall.
- 04
Every count links to the elements behind it, so anyone can check it.
Platform capabilities used
The same capabilities serve every segment. Each one links to its section.
Stop waiting. Start building.
Book a call with the founders. Thirty minutes, your questions, and what Criad looks like on a data centre build.