Move Fast. Think Clearly. Sunday Edition. | Begin in Privacy, Launch in Public. | Why the best founders know that stealth isn’t a strategy. It’s a season.
A few years ago I noticed something about myself that I couldn’t quite explain.
Whenever I got excited about a new idea, my first instinct was to tell people about it. Friends. Colleagues. Anyone who would listen over coffee. The conversations were always enjoyable. People asked thoughtful questions. Someone would suggest a feature. Someone else would point out a competitor. Another person would immediately ask how I’d make money.
On the surface, it felt productive. I walked away feeling energized because people were engaging with the idea.
But something strange kept happening.
A few days later, the excitement would quietly fade. Not because the feedback was negative. Most of it was genuinely thoughtful. The idea simply stopped feeling alive. It was as if I had invited the world into a conversation before I had finished having it with myself.
For a long time, I assumed I wasn’t very good at handling feedback.
Now I think the timing was wrong.
The Stealth vs Public Debate
The startup world has spent years debating whether founders should build in public or stay in stealth.
It’s an interesting debate, but I suspect it’s answering the wrong question.
The real question isn’t whether ideas should be public or private. It’s whether they’re ready.
Ideas, much like people, seem to have seasons. Some need conversation. Others need protection. The difficult part isn’t choosing one philosophy over another. It’s recognizing which season your idea is currently living through.
Before You Launch Your Idea
Today we remember Dyson – the company, the engineering, the iconic products. What often gets forgotten is the long stretch before any of that existed. Dyson built 5,127 prototypes before arriving at the design (bagless vacuum cleaner) that eventually worked.
I’ve often wondered what would have happened if every one of those prototypes had been announced to the world.
The story would have become about explaining why version 137 didn’t work, or defending version 842, instead of quietly learning from them.
He wasn’t protecting a secret. He was protecting a learning process.
Those are very different things.
The same pattern appears in places you wouldn’t immediately expect.
The Case for Private Validation
When Linear (PM tool, founded 2019, launched 2020) launched, many people described it as an overnight success. It certainly looked that way from the outside. A beautifully designed product that seemed to appear fully formed.
The reality was far less glamorous and much more interesting.
Its founders, including Karri Saarinen, had spent years experiencing the frustrations of enterprise software while working at companies like Airbnb. They weren’t trying to build “another Jira.” They were obsessed with a feeling. Software shouldn’t feel heavy. It shouldn’t interrupt your thinking. It shouldn’t make you wait.
Karri Saarinen once remarked that “every millisecond matters.”
That’s an extraordinary sentence if you stop to think about it.
Most people don’t notice a few milliseconds. But builders who care deeply about experience do. They understand that products aren’t remembered because of one spectacular feature. They’re remembered because hundreds of tiny decisions quietly add up to something that feels effortless.
By the time Linear became public, the team wasn’t looking for opinions about whether speed mattered.
They already knew it did. Now they wanted to know whether enough other people cared too.
Pieter Levels – The Build in Public Guru
People often describe Pieter Levels as someone who builds in public, and that’s true.
But it’s only half the story. What we see publicly is usually the first version that survived reality, not the first version that entered his mind.
Behind every weekend launch are abandoned experiments, discarded interfaces, rough notes, tiny scripts and questions that never deserved an audience because they hadn’t yet earned one.
Building in public doesn’t eliminate private thinking. It makes private thinking more intentional.
Steve Jobs – Private or Public?
Even Steve Jobs seemed to understand this instinctively.
The original Macintosh team worked in relative isolation inside Apple. Jobs wasn’t creating secrecy for the sake of mystique. He believed breakthrough products needed an environment where ideas could mature before they were negotiated into compromise.
That idea feels surprisingly relevant today.
In a world where every thought can become a post within seconds, patience has become a competitive advantage.
Of course, there’s another trap waiting on the other side.
Some founders protect ideas for so long that protection quietly turns into avoidance. Months become years. Research replaces conversations with customers. Another prototype gets polished. Another framework gets refined. Another notebook fills up.
At some point the greenhouse becomes more comfortable than the outside world.
That’s usually the moment the greenhouse has stopped serving its purpose.
Stealth, Public… You’re Probably Asking the Wrong Question
I’ve come to think of it as a progression rather than a philosophy.
Most worthwhile ideas begin in private because they’re still discovering what they are. Then they find a handful of trusted people who can challenge them without overwhelming them. After that comes reality in the form of customers, experiments and small bets. Only later, once the idea has found its own shape, does building in public become a force multiplier instead of a distraction.
Gardeners understand this instinctively.
Seeds begin in protected conditions, not because sunlight is dangerous, but because timing matters. Eventually the same greenhouse that protected the young plant becomes the thing that limits its growth.
Long-Term Attention is The Moat
Ideas aren’t very different from seeds. This debate also made me hear one of Paul Graham‘s best-known ideas differently.
“Do things that don’t scale.”
For years I interpreted that as operational advice. Now I hear something deeper.
Learn in environments where learning is still possible. Don’t optimize for visibility before you’ve optimized for understanding.
The longer I spend building things, the less I worry about someone stealing an idea. Most interesting ideas already exist in one form or another. What separates one founder from another isn’t the originality of the thought. It’s the attention they give it, the taste they bring to it, and the willingness to stay with it long after the novelty has disappeared.
That’s much harder to copy than an idea. What I worry about now is something else entirely.
I worry about exposing an idea before I’ve discovered what it actually wants to become.
Your Assignment
So I’ll leave you with the question that’s been sitting with me all week. Not whether you’re building in public. Not whether you’re staying in stealth.
Simply this.
What part of your idea is ready for sunlight… and what part still deserves a greenhouse?
The answer might change what you do tomorrow morning.
If you’re sitting with an idea that still feels fragile, or you’re wondering whether it’s time to bring it into the world, I’d love to hear about it.
Write to help@founderhelpdesk.in.
Tell us what you’re quietly exploring. Tell us about the problem that refuses to leave you alone, the observation you can’t shake, or the idea that keeps returning despite your attempts to ignore it. Sometimes all an idea needs is one thoughtful conversation to understand which season it’s in.
Because the hardest part of building isn’t always deciding what to build.
Sometimes it’s knowing when to let the world see it.
Fat Tony, FounderHelpDesk
