Our flagship · Our own product
The report
nobody wants
to write.
An assistant for the person running the jobsite. Voice-first, integrated with Procore, built because the same thing was broken everywhere we looked.
Why we built it
A superintendent runs a jobsite all day. At seven at night, in his truck, he writes down what happened. From memory. So the daily log gets done badly, late, or not at all — and we heard the same complaint at company after company. The person who loses is the owner. That log is the record that settles a dispute over who was on site, prices a change order, backs up a delay claim and defends an insurance case.
What we decided to do
Stop building forms. Build the assistant for the guy in the field.
The reason to try it now is that the models finally got good enough to hold a real conversation about a jobsite — to know what a complete record looks like and ask for the part you left out. So the system does the asking. He talks, it writes, it talks back. For the owner that means structure without training: nobody teaches a superintendent how to fill out the form, because the system is walking him through it. Everything since has been the same idea pointed somewhere new.
Your own private copy for an hour. Opens in its own tab.
By the numbers
Measured from the codebase
- Written in
- TypeScript, monorepo
- Runs on
- Cloudflare Workers
+ Durable Objects - Database
- Supabase / Postgres
- Voice in / out
- Deepgram Nova-3
+ Aura-2 - Reasoning
- Claude Haiku
- Procore sections
- 17 mapped · 16 pushed
- Agent can call
- 35 tools
- Weekly checks
- 10 detectors
- Offline
- Local-first, phone wins
on reconnect - Demo accounts
- Real, per visitor,
destroyed after an hour - Lines of code
- about 138,000
Procore is optional by design. The demo you are about to open is a real account with a real jobsite in it, created the moment you click, and gone an hour later.
- 6surfaces on one idea
- 1 hryour own private copy
- 0sign-up forms — it just opens
What's inside
Six surfaces. Three are working and in the demo, one is working and only partly shown, two are previews of where this goes. The pill on each one tells you which.
- 01The daily logWorking, in the demo
- 02JSA safety sign-offWorking, in the demo
- 03OAC meetingsWorking, in the demo
- 04The weekly reportWorking, partly shown
- 05Field PulseConcept preview
- 06Phone callsConcept preview
One idea underneath all six: a system that knows what complete looks like.
01
The daily log
Working · in the demo
Talk through the day the way you'd tell a foreman; it writes the daily log as structured entries and asks for whatever is missing.
02
JSA safety sign-off
Working · in the demo
It drafts the morning safety talk from the day's scope, and the crew signs by scanning a QR code — a talk designed around the contractor's and insurer's rules.
03
OAC meetings
Working · in the demo
Preps the weekly owner–architect–contractor meeting pack by conversation, and carries every open item into the next meeting on its own.
04
The weekly report
Working · partly shown
It rolls the week up and audits it with ten checks — real in the product, not shown in this demo.
05
Field Pulse
Concept preview
The idea: load the project schedule once and match each day's log against it, so "are we behind?" gets an answer.
06
Phone calls
Concept preview
The idea: calls get captured and turned into log entries the super approves — shown on a sample call, with no live phone line.
What to look for
It opens mid-week, not empty. Five days are filed. Today is half done.
Start with the log. Talk to it. Then open today's JSA and look at the QR code. Then OAC meeting 12.
The strip at the top counts down your hour and brings you back here.
Opens in its own tab — the session security that protects a real customer keeps it out of a frame. A sample jobsite, yours for an hour. Field-tested and in active development.
NextSMART Action Hub