Build in public, they say. Tweet your progress. Share your MRR. Document everything. The formula is pretty well-established at this point — and most of it doesn't apply when you're 17 with no audience, no revenue, and a product that's still half-finished.
I tried doing it the standard way. Here's what I learned.
The problem with most build-in-public content
Most build-in-public posts are written for an audience that already exists. The founder already has 5k followers. They're sharing metrics that are already interesting. They're leveraging credibility they already built somewhere else.
If you're starting from zero, you don't have that. Sharing your week-one metrics is just sharing noise. Nobody cares that you have 3 users — and they're right not to. The interesting part isn't the number. It's the thinking behind the decision that got you there.
Don't share the metric. Share the thinking that produced it. One of these ages well. The other is noise.
I stopped posting vanity updates and started writing about the actual decisions I was making: why I built feature A before feature B, what the tradeoff was, what I was wrong about the week before. That stuff has a longer shelf life. And it's more useful to the people reading it.
Being young is a weird asset online
Here's something I didn't expect: being 17 and building something real makes people pay attention in a way that's hard to manufacture. Not because of pity — because it's genuinely unusual and people are curious about the specifics.
The instinct is to hide your age or downplay it. I think that's wrong. The age isn't the story — but it is context that makes the story more specific. A 17-year-old building ACT prep because he's living the problem right now is a more concrete narrative than "founder solves education problem." Concrete is memorable. Vague isn't.
I've gotten more useful conversations from one specific post about a product decision than from three weeks of "shipped X" updates. Specificity filters for the right audience — people who are genuinely interested in how you think, not just what you built.
That said: don't make being young the whole personality. It's context, not content. The product still has to be real. The thinking still has to be there. People will see through it fast if the substance isn't underneath.
What actually works
Write about the moment you changed your mind. Those posts perform well because everyone has had that experience — realizing the thing they thought was true isn't. Write about a mistake you made and what it cost you. Write about a decision that looked wrong from the outside and why you made it anyway.
Do not write about your roadmap. Roadmaps are for investors. For building in public, the only thing that's interesting is what you've already decided and done. The future is cheap. The past is evidence.
The other thing: be useful. Every post should give the reader something — an idea, a framework, a question to ask themselves. If you're just narrating your week, you're a diary. That's fine, but it's not building in public. Building in public is when the reader gets something out of watching you build.
Be useful. If you're just narrating your week, you're a diary. That's fine, but it's not building in public.
I'm still figuring this out. I have a small audience and most of my users don't come from Twitter. But the writing practice is valuable regardless — it forces me to actually think through why I made the decisions I made, which makes me better at making the next ones.
That's probably the most honest thing I can say about building in public: do it because it sharpens you, not because it grows you. The growth follows eventually, if the thinking is real.