How would you use this?
Where would it live in your day, your shop, your product? The use we didn't imagine is usually the one that matters.
The seven-day build · running now
Build 01.
The day-one contract — what "done" means
We missed a visit we wanted.
This one started with a screwup. We'd just opened our calendar to the public, and people actually came — including a visit from 43North. Nobody heard them at the door. The building is a former house and still reads like one, so a visitor does what anyone does at a house that might not be expecting them: stands on the step, hesitates, and leaves.
The obvious fix hasn't really changed in a hundred years. A doorbell tells the inside that somebody's outside; the modern version adds a camera, which helps the owner and does nothing for the visitor. The person at the door still learns nothing — whether they're expected, whether anyone's in, whether to wait, knock harder, or come back at two.
Meanwhile, every website has a bot now. Ask a question at midnight and something answers. A visitor at the door has invested far more than a click — they drove over, parked, walked up — and gets less back than a web page gives a stranger. That became the actual starting point: if a click deserves an instant answer, a visit deserves a better one. A bot for the front door.
So we walked the neighborhood and looked at doors. More paper signs than we expected: hours crossed out and rewritten, "deliveries after 12:30 — use the back door," and a surprising number of QR codes already taped to the glass — check our menu, check appointment availability. Every one of those signs is a small business trying to put a message at the door, with paper, because paper is what there is. The front of a building is already a display. It's just a bad one.
Build 01 is the fix we owed ourselves: a plate at the door that says the right thing at the right time, lets a visitor say why they're here, and rings whoever's working — wherever in the building they actually are.
Seven days, posted as they happen.
No cleanup, no retelling — each day goes up the day it happens, dead ends included. If you're following along and something looks wrong, it probably was; the next day's entry says what we did about it.
Borrow from this build.
A build like this throws off parts that outlive it — circuits, firmware patterns, enclosure tricks, supplier finds. These are the pieces worth lifting for your own project. Stop in and we'll walk you through any of them.
Customer discovery · you're it
Tell us where this should go.
The build answers "can we make it work." You answer the harder question — whether anyone wants it, and in what form. Three things we genuinely want to hear:
What are we missing?
The dealbreaker we can't see from inside the workshop — the feature, the price, the constraint that would make you pass. Say it plainly; day six exists for exactly this.
Want to run with it?
If this belongs in your business or your build, come talk to us. Everything posted here is on the table — partner on it, license it, or take the idea further than we would.
The comment board · 0 on file
Or say it here, in writing.
Every comment is read by a human before it appears — same as the Tailwinds field reports. Sharp objections are worth more to us than encouragement.