How it works
The house is not the hard part. Keeping every photo, date, and yes in one head is. This page is why it exists, a day on site, and who should not use it.
No account to look around. Works with no signal.
What actually goes wrong
A builder does not lose a custom home over framing. A builder loses it over a leak nobody logged, a plumber booked on two lots, and a tile nobody can prove the homeowner approved.
“Four hundred photos. I could not tell you which house they belong to.”
“Any update?” — every afternoon, from a client who just wants to see the house.
“On Whitaker Tuesday. Also on Calderwood Tuesday.”
Who sees what
Not a permissions screen you set up later. It is the design.
Every house. Photos, the calendar, selections, money.
The houses, the dates, the finishes. Not the money.
Progress, selections, and the decisions the builder needs.
Trade, dates, and spec. One link. It stays current.
A day on site
If it is slower than the walk back to the truck, the builder will not use it. So it is not.
7:40am
The builder taps the camera on the home screen, picks the house, and files a Field Note labeled Leak. Needs You shows it to the builder right away.
10:15am
The builder reviews the packet, then texts the link. The crew confirms the dates. If the builder adds a photo after sending, the crew sees it on the same link.
4:00pm
The leak photo and the hood decision are already on the homeowner’s phone. The “any update?” text is never written.
6:30pm, at the kitchen table
Budget, committed, spent. Overspend shows. Invoices on one sheet. The owner sends paid costs to QuickBooks when ready.
Built for a basement with no bars
Everything saves to the phone first and syncs when there’s signal. Log twenty items in a poured basement — it catches up on its own.
During development a live sync incident wiped a site’s records. Every device still held its own copy. The whole job came back on reconnect. Nothing was lost.
That was not a feature demo. It was a bad afternoon the design happened to survive.
Why it exists
I watched a very good builder run my build — and saw how much one person is expected to hold in one head.
A custom build is a logistics problem in a hard hat. Memory, a phone, and a truck cab. The craft was never the hard part. The information is.
SitePlumb was written during that build. The homeowner side is not a module bolted on. It is where this started. The builder side grew around what a builder actually juggles.
That is why Field Notes is three taps. Anything slower does not survive a real jobsite.
Read this before you get excited
The home page already says no estimating and no timesheets. This is the rest.
The packet is narrow and useful. Some crews will ignore it and answer the phone instead. That is the trade, not the software.
Support is me. I answer. Fast fixes. No 24-hour call center.
No bulk import. Put the next house in. Keep the old system open until you stop checking it.
Early access
Free while we work together. Two to twenty custom homes and an opinion. That is the whole requirement.