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. Consistent, boring, expensive.
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. When it is thin, the company has nothing to point at.
And the daily log was only the first thing. The safety talk has no helper. The owner's meeting gets its agenda retyped by hand every week. The week's report is buried in five days of notes. The phone rings all day and nothing said on it gets written down.
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.
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.
On a form, that is the interview. In a meeting, it is what carries forward. On a call, it is catching the question nobody asked.
01
The daily log
Working · in the demo
Why
Procore's daily log is nineteen sections. Its "voice" option is the phone's dictation typing into one box at a time. Neither knows whether you are done.
What it does
You talk to it the way you would tell a foreman what happened. "Six guys on site, crane ran all day, rebar delivery at ten" lands as a manpower entry, an equipment entry and a delivery — as structured rows, while you are still talking. The weather is pulled for the jobsite's real coordinates without you asking.
It knows what a finished log looks like, so it asks for what is missing. It talks back out loud, which is what makes it a conversation and not dictation. Interrupt it mid-sentence and it stops and listens.
Name two subcontractors in one breath and they become two separate entries; say "they" three turns later and it knows which one. Decline to answer something and it records that you declined instead of leaving a hole — except the crew's comments, which it will not let you skip, because that is the field a dispute turns on.
Lose signal on site and the log lives on the phone. When the signal comes back, the phone's version wins.
When it is done, it pushes to Procore — 17 section types mapped, 16 pushed — or it never touches Procore at all, for a company that does not use it.
Look for: today's log is half done — morning in, afternoon open. Say the line above and watch the rows appear.
02
JSA safety sign-off
Working · in the demo
Why
Every morning, before work starts, someone has to give the safety talk and prove the crew heard it. In practice: a super in a parking lot with a clipboard, a crew waiting on him, and a sign-in sheet that ends up in a truck door. That sheet is a legal document.
What it does
The assistant drafts the talk from the day's scope — what is being done, what can go wrong, what to do about it — through the same kind of conversation as the log. It can read the talk aloud, section by section, with a timer and a progress bar, so the super is facilitating rather than performing.
Sign-off is a QR code. Every crew member scans it with their own phone — no account, no app — and taps their name. The "4 of 7 signed" counter on the super's screen moves within about five seconds. Duplicate names are caught. The code is bound to that one session and cannot be reused.
The recorded question-and-answer clip is transcribed by AI into a structured form. The walkthrough video is kept as evidence and is never analysed.
The AI-led talk was designed around the rules that actually govern it — the general contractor's subcontract and the insurer's manual — with a qualified person present and every acknowledgment captured.
Look for: yesterday's talk is signed 6 of 6. Today's is at 4 of 7. Open it and look at the code.
03
OAC meetings
Working · in the demo
Why
The owner–architect–contractor meeting is where the money gets decided, and its minutes are the accountability record — a delay argued there can cost thousands a day. The pain is smaller and constant: the same open items get retyped into every week's agenda by hand, and nobody remembers which meeting a thing started in.
What it does
It mirrors the shape of Procore's own Meetings tool on purpose, so nothing has to be relearned: categories, numbered items, owner, due date, status. Then it adds two things Procore does not have.
First, the pack preps itself through a conversation — one or two questions at a time, skipping categories with nothing in them, confirming in batches.
Second, carryover. Anything left Open or On Hold rolls into the next meeting on its own, tagged with the meeting it was born in. Closed stops it. Meetings number themselves. The whole thing exports as a branded PDF pack ready to send.
Look for: open meeting 12. An item raised in meeting 10 is still there, unchanged, still tagged 10.
Agendas and packs today. Recording the meeting and producing minutes from it is designed and not built.
04
The weekly report
Working · partly shown
Why
The owner's question on Friday is "what happened this week?" The answer is spread across five daily logs and a lot of weather.
What it does
It rolls the week up — man-hours, weather, deliveries, delays — and writes an executive summary a superintendent would put his name on.
Then it audits the week. Ten checks run over the logs looking for the things that get a company in trouble later: a log entered late, a day marked complete with nothing in it, crew logged with no work, work logged with no crew, suspicious zeros, a subcontractor who vanished mid-week with no delay recorded, entries copied forward from yesterday, weather that contradicts the work, and entries too vague to defend.
What the demo shows: the report, on a sample screen. The ten checks are real in the product and are not visible here — the live version needs a connected Procore account, which the demo does not have.
05
Field Pulse
Concept preview
Why
A super should not have to read a schedule to know whether he is behind. He is already telling the log what happened every day. The schedule is sitting in another program.
The idea
Load the project schedule once. From then on, what gets said into the daily log is matched to the schedule's activities automatically — so "are we behind?" has an answer, with the evidence attached. A command centre for the project: progress curve, the schedule, photos on a map, the weather, and a chat that answers questions with citations.
It would be opt-in for a project that has a schedule. The daily log keeps working exactly as it does for one that does not.
In the demo: a working picture of it. Ask it "are we behind schedule?" — the answer, the curve and every number in it are scripted.
06
Phone calls
Concept preview
Why
A superintendent's day is interruptions. The phone rings, a question gets answered, a delivery gets moved — and none of it makes the log, because the log is not where the conversation happened. A missed call is worse: the question never gets asked at all.
The idea
Calls are captured and turned into log entries you approve. Each one moves through captured → transcribing → extracting → ready and lands in a review inbox as a pre-filled entry. Longer term, when he misses a call the system answers it, takes the question, and works out what the caller needed.
In the demo: the whole flow, on a sample call. There is no live phone line behind it.
Under the hood
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
- 0signup — it just opens
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 meeting 12.
The strip at the top is your clock and your way back.
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