Capture the site, index it to the model and the date, and rank what looks wrong — then route each observation to a named owner on a clock, because one nobody closes is evidence.
Capture from 360 walkthroughs, fixed cameras and scheduled flights, each flown by a named certificated pilot.
02
Blur faces and mask off-site areas at ingest, before a frame reaches a screen — no face or gait template is made.
Reason
03
Register each capture to the model and the date, and index it to the level, the zone and the capture position.
04
Compute geometric deltas between captures and against the baseline revision the project has named as current.
05
Compute progress per element as an estimate, carrying its method and confidence — never as a certified figure.
Decide
06
Rank candidate observations against the rule set configured for this site, not against a national default.
07
Route each ranked observation to the named person with authority to abate it, with an escalation clock running.
Out
08
Retain the frame, the rule cited, the routing, the owner and the closure decision against the observation.
09
Execute write actions only inside the approval boundaries agreed during implementation.
→Product statement
The agent raises candidates; the site safety manager decides what is a breach — and once raised, an observation cannot be unrecorded, only closed, late and on the record.
Example workflow
One capture run, frame to owner
AgentHuman
1Capture run receivedA 360 walkthrough, a fixed-camera series or a flight with a named remote pilot
2Frames de-identifiedFaces blurred and off-site areas masked at ingest, before any person sees the frame
3Candidates rankedDetected conditions, progress deltas, the frame and confidence
A good baseline says nothing about the night shift
Start from the baseline: daylight structure work from surveyed positions misses least, and the aggregate inherits that. Nestack reports the missed-hazard rate by slice, alongside the false-positive rate that produces it.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
Night, low light and heavy occlusion
9.9%
2.9×
Review
Fitout and wet trades
7.5%
2.2×
Review
Structure phase, daylight capture
5.1%
1.5×
Watch
Repeat typologies, BIM baseline
1.7%
0.5×
Normal
Bar: missed-hazard-rate lift vs. an all-frame baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 of 4 slices over threshold
Evidence-linked improvement
A closed cycle looks like a new test
An explanation closes nothing. The cycle ends with a case the next release has to clear.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Missed-hazard rate rises in a capture slice.
02Diagnose
The frames, the rule set and the routing log are read side by side until the cause is one of them.
03Improve
The change is stamped to a version, with the frames that produced it attached.
04Verify
Re-run the affected cases; a fail holds the release.
05Learn
A standing test, plus a rule change in the detection set.
Learn → DetectThe return edge. Each turn hands the next one a longer suite to beat.
Typical build scope
Twelve workstreams across six weeks
The build scope read against the delivery timeline. Week structure follows the six-week plan — discovery, capture, detection workflow, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Capture workflow discovery and boundary definition.
02Capture-source and site-system assessment.
03Jurisdiction, notice and recognition-gate mapping.
04Capture ingestion and de-identification.
05Detection logic and baseline-model binding.
06Confidence scoring and observation routing.
07Safety review workflow.
08Site-system and observation-log integration.
09Paired-frame regression cases.
10Guardrails and publication controls.
11Observation-trail instrumentation.
12Deployment, documentation and Agent Care handover.
12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallelFinal scope and sequence confirmed in discovery
Engagement tiers
What each tier includes
Rows are the capabilities named in each tier's scope. Higher tiers include everything below them.
Capability✓ in scope · — not at this tierPilotOne site, one capture cadenceProductionProduction site systemsAdvancedMultiple sites / capture modes
Introduced at Pilot
Ranking to your site rule set✓✓✓
Safety review and escalation✓✓✓
Detection baseline✓✓✓
Introduced at Production
Reporting by capture zone—✓✓
Escalation clock in your systems—✓✓
Approved write-back—✓✓
Dashboard and BI integration—✓✓
Introduced at Advanced
Multi-jurisdiction capture rules——✓
Multi-stage site review——✓
High capture volume——✓
Enterprise capture controls——✓
Build priceFrom $5,000From $8,000Custom quote
Final build priceConfirmed after discovery based on integrations, workflow complexity, transaction volume, approval controls and deployment requirements.
Separate from buildBuild pricing is separate from recurring Agent Care, which covers managed monitoring, evaluations, incidents and verified improvements after launch.
What we need from you
What you bring, and what we build with it
Each input maps to a piece of build scope and a week in the delivery timeline.
You bringWe build with it
01Your site rule set and capture cadence→Capture ingestion and zone mappingWeek 1
02Representative captures from live levels→Detection baseline, zone mapping and baseline-model bindingWeek 2
03Your surveillance notices and consent records→Jurisdiction, notice and recognition-gate mappingWeek 1
04Access to relevant APIs, feeds or exports→Capture-source and site-system assessment, then integration setupWeek 2
05Captures where the hazard was there and unflagged→Detection cases, paired frames and the evaluation suiteWeek 4
06What an observation must reach before it is closed→Confidence scoring, routing, guardrails and escalation controlsWeek 3
07Named owners with authority to abate→Safety review workflow, then pilot and production validationWeeks 5–6
Nothing else is requiredDeployment, documentation and Agent Care handover are ours.
Delivery timeline
Four phases across six weeks
Phases are drawn over the weeks they occupy. Week 5 carries evaluation and pilot capture together.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Capture workflow discovery, jurisdiction mapping and the boundaryW2Capture-source integration and the detection baselineW3Detection workflow, confidence logic and routing controlsW4Evaluation suite, guardrails and failure-mode testingW5Site-system integration, pilot capture runs and targeted correctionsW6A month of capture reviewed by the site team, then handover
Reading the bandBars stop where the named work stops. The week 5 overlap is scheduled, not padding.
At the end of W6Hand-over happens against a verified capture run, not a demo.
DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Construction AI agent
Build a site-vision agent around who closes the observation.
Show us how you capture, who owns an observation and where the imagery goes. If your queue already outlives its clock, we fix the closure loop before we add a single detector.
