Building Quietly

There’s a version of building something that looks like this: announcement posts, waitlists with 10,000 signups, a podcast appearance before you’ve shipped a single thing. The founder as protagonist. The build as content.

I’ve tried that version. I understand the logic. Attention is leverage. Distribution is moat. Document the journey.

But somewhere in the last few months, I started doing something different. I started building quietly.

Not in secret. Not with false modesty. Just… without the noise. Without narrating every decision as it happened. Without making the thing into a story before the thing even existed.

And I want to try to explain why — because I think there’s something real here, even if it’s hard to articulate without sounding like I’m romanticising stubbornness.

I’ve spent years in the cycling world, racing, photographing it, writing about it, working in it commercially. I know what it looks like when something is built for the announcement versus built for the person it’s supposed to serve.

You can feel the difference. The brand that launches with a film and then quietly disappears. The app that has a beautiful landing page and a product that doesn’t quite hold together. The founder who has a thousand followers watching the journey and somehow no customers at the end of it.

I’m not immune to this. I’ve made versions of this mistake. The seduction of the narrative is real.

But something shifted when I started working on what I’m working on now.

I found myself not wanting to talk about it. Not because I wasn’t excited, hell I was, I am, more than I’ve been about anything in a while but because talking about it felt like it would cost something. Like the energy would leak out. Like the clarity I had when it was just me and a blank document and a problem I actually understood would get muddied by other people’s opinions before I’d figured out my own.

So I kept it quiet. I built. I asked a small number of people questions and listened hard. I made decisions slowly and then committed to them.

And what I noticed was this: the building got better. Not because secrecy is some magic, but because silence created the conditions for honesty. I wasn’t performing the build. I was just doing it.

There’s a particular kind of pressure that comes with building in public. It’s subtle and it’s not always bad, accountability has real value. But there’s also a gravitational pull toward the shareable moment, the quotable insight, the arc that makes sense in retrospect.

Real building doesn’t always look like that. Real building looks like a Tuesday afternoon where you’ve changed your mind about something for the third time and you’re not sure if that’s wisdom or weakness. It looks like a conversation where someone tells you something you didn’t want to hear and you spend three days figuring out if they’re right. It looks like less than you thought, taking longer than you planned, costing more than you budgeted and still being the right thing to do.

None of that makes good content. All of it makes a better product.

I’m not saying don’t share what you’re building. I’m not even saying I won’t eventually. There’s a time for that.

But I think there’s something worth protecting in the early phase of making something a kind of private seriousness that lets you ask the uncomfortable questions before the world has opinions. Who is this really for? Does this actually solve something? Am I building this because it needs to exist, or because I need to feel like I’m building?

Those questions are easier to answer when no one’s watching.

There’s something I’m building. I’ll tell you more about it when it’s ready. When it’s earned the telling.

For now: if you’re making something quietly, in the background, without the announcement post, keep going. The quiet is doing something.