The Logbook

There's a moment in every founder's journey where the abstract becomes concrete. Where the renders stop being renders. Where the conversations stop being conversations. Where the dream stops being a dream and becomes something you can hold in your hands — or in this case, something you can wire money for. That moment happened on May 7, 2026.

The morning of December 17, 1903 was cold and unforgiving. Wind cut across the dunes of Kitty Hawk, North Carolina at nearly 27 miles per hour. The temperature hovered just above freezing. Five witnesses stood in the sand — a handful of local men who had no idea they were about to watch the world change forever.

The morning of December 17, 1903 was cold and unforgiving. Wind cut across the dunes of Kitty Hawk, North Carolina at nearly 27 miles per hour. The temperature hovered just above freezing. Five witnesses stood in the sand — a handful of local men who had no idea they were about to watch the world change forever.

Drawings are useful. Renders are useful. They help develop an idea, stress-test proportions, catch problems before they become expensive. Up to a point, they're the right tool. But there are things a screen simply cannot tell you. How a case feels when you pick it up. Whether the weight is right for the size. How the watch sits against a wrist — not a rendered wrist, a real one. Those answers only exist in one place.

There wasn't a moment where everything clicked. It was more gradual than that — a point where the adjustments slowed, then stopped, not because perfection had arrived but because the resistance had gone. The watch. The site. The language. Each one had been through its own process of removal and refinement. And somewhere along the way they stopped pulling against each other and started saying the same thing.

After the watch, the website felt like it should be the straightforward part. Pick a theme. Arrange the content. Done. It wasn't. Themes that looked clean in previews felt cluttered with real content inside them. Layouts that seemed right for an hour revealed something slightly off by the next morning — a spacing issue, a hierarchy problem, a tone that didn't match what the watch was trying to say. Small things. But small things compound.

There's a graveyard of good ideas behind this watch. Elements that made sense on their own, looked considered in isolation, and solved a real problem — right up until they met everything else. Extra text. Additional markers. Layout variations. Each one added something to the dial — and quietly took something else away. A little clarity here. A bit of balance there. Nothing dramatic enough to reject outright, but enough to make the whole feel slightly less than it should.

"Designed to be right" is easy to say. Most things are, in one way or another. At some point it needed a definition — something with edges, something that actually cuts. The limit of one hundred came from a simple question: at what number does every decision still matter? Where is the point before volume starts absorbing mistakes, averaging out quality, making it easy to move on without resolving things properly?

There was a version of this watch that worked, technically. The specs were sound. Individual elements looked right on their own. By most measures, it was close. But close isn't the same as right. The whole thing felt like a negotiation — different ideas sitting in the same space, each pulling in a slightly different direction. Nothing was wrong exactly. Nothing was settled, either.

With the design far enough along, I started reaching out to manufacturers. It felt like a natural next step. Send some messages, get some quotes, figure out what's possible. The first few replies taught me something quickly: nobody can help you if you don't know what you're asking for.

On screen, it looked like a watch should look. Balanced. Considered. Every element placed with intention. I looked at it for a while, feeling like something was finished. Then I strapped on a printed test piece and glanced at my wrist. It took a moment to read. Not long — a second, maybe less. But a second is too long. That hesitation was the whole problem, right there on my wrist.

I had ideas before I had knowledge. That gap needed closing before anything else. So I started at the beginning. Cases. Dials. Movements. Tolerances. Assembly. Not as concepts—as physical realities. The kind you only understand when you're holding the parts, asking why something doesn't fit, and realising the answer lives in a decision made three steps earlier.