Build in Public, Fail in Public: The Under-20 Playbook

Because they keep shipping, and they keep doing it in front of everyone.

This week TechCrunch profiled what it's like to be a founder under 20 in 2026, and the piece hit a nerve. The poster child is Arlan Rakhmetzhanov, a 19-year-old from Kazakhstan who started coding at 15 and now runs Nozomio, a YC-backed company building an API index for AI agents. He's raised more than $6 million, and he talks about the job with a bluntness most older founders have trained out of themselves: "I either win or lose."

That quote is the whole story. A generation of founders grew up streaming their lives, so narrating a startup feels normal to them. They post revenue screenshots, botched launches, rejection emails, all of it. And the market is paying attention, because in a year when AI tools flattened the technical barrier to building, the scarce skill turned out to be showing up in public every single day.

You don't have to be 19 to use this. You just have to understand why it works.

The short answer: sharing the real numbers and real decisions of your company as they happen, not after you've won.

It used to mean a monthly blog post about revenue. Now it's faster and rawer. Founders post the metric dashboard on Monday, the failed feature on Wednesday, and the lesson on Friday. The under-20 crowd treats an audience the way older founders treat a board: a group they report to, which forces clear thinking.

There's a spectrum here. On one end, full transparency, revenue and all. On the other, sharing process without numbers: what you tried, what broke, what you learned. Both count. The common thread is that you publish before you know how the story ends.

And that's the uncomfortable part. Building in public means failing in public too. The TechCrunch piece is blunt about this: young founders who flame out do it with an audience watching. They've decided the trade is worth it. The attention that comes from honesty compounds faster than the embarrassment of a miss.

Three things, mostly.

First, speed without ceremony. A 19-year-old doesn't schedule a meeting to discuss the plan for the meeting. They ship the thing, post the result, and adjust. AI tools reward this loop, since the cost of trying something dropped to nearly zero.

Second, they have no reputation to protect. That sounds like a weakness. It's the opposite. A founder with a 15-year corporate career hesitates to post a failed launch because colleagues might see it. A teenager posts it before lunch. No sunk reputation means no fear, and no fear means faster learning in the open.

Third, public accountability. When you announce on Monday what you'll ship by Friday, an invisible contract forms. Rakhmetzhanov's "I either win or lose" framing isn't bravado, it's a commitment device. The audience becomes the deadline.

None of these require youth. They require deciding that momentum matters more than image. Plenty of 40-year-old founders have made that trade and seen the same compounding attention. The teenagers just made it look normal.

Let's be real: there are costs, and pretending otherwise is how people get burned.

The obvious one is that the internet keeps receipts. A failed startup with a public paper trail follows you into your next fundraise. Investors will read your old posts. Most will respect the honesty; a few will hold it against you. You don't get to choose which kind you pitch.

The subtler cost is emotional. Publishing a bad month invites strangers to comment on your bad month. The under-20 founders TechCrunch interviewed describe growing thick skin fast, and not all of them enjoyed the process. If a rough comment section would knock you off course for a week, that's data about how much to share.

There's also a competitive cost, though it's smaller than people fear. Yes, competitors can see your roadmap. In practice, execution gaps matter far more than information gaps. Nobody ever lost a market because a rival read their changelog.

The mistake isn't sharing too much or too little. It's sharing without deciding in advance what the boundaries are.

Pick a lane and stay consistent. Credibility dies from whiplash, not from failure.

The founders who make this work follow a few unwritten rules. They share outcomes with context, not raw drama. "We lost our biggest customer, here's the postmortem" builds trust. "Everything is falling apart" builds nothing. They publish on a rhythm, weekly or twice weekly, so the audience knows the silence after a launch isn't hiding. And they never fake it. One inflated metric, discovered later, erases two years of honest posts.

A useful test before hitting publish: would you say this to a smart investor over coffee? If yes, post it. If you'd spin it in that meeting, don't post the spun version either. People can smell it.

One more thing. Share decisions, not just results. "We chose usage pricing over seats, here's why" teaches your audience something and shows how you think. Results attract spectators. Reasoning attracts believers, and believers become customers, hires, and investors.

A simple rule covers most cases: share the journey, protect the engine.

Fair game, and the stuff audiences love: revenue milestones (exact or ranged), failed experiments and what they cost, pricing changes and reasoning, hiring lessons, tool choices, weekly goals and whether you hit them.

Keep private: customer names without permission, anything covered by a contract, security details, unlaunched features competitors could front-run cheaply, cap table specifics, and co-founder disagreements while they're still live. Air the lesson after it resolves, not the fight during.

It helps to write this down before you start, because you will be tempted to overshare on a great day and undershare on a terrible one. Some founders keep the boundary list right inside the same doc as their business plan. Wherever your plan lives, a spreadsheet, Notion, or a structured planning tool like Foundra, add a page that says "public" and "private" and sort your metrics into the two columns once. Then posting becomes a habit instead of a nervous judgment call each time.

The founders who fail at this rarely fail from one big leak. They fail from drift.

This is the part that makes the whole trade worth it: the audience is the go-to-market.

The under-20 boom isn't happening because teenagers are better engineers. TechBuzz's read on the trend is that they're building without Big Tech's help, and their public feeds are doing the work a marketing budget used to do. Every post is a tiny ad that doesn't feel like an ad. Followers watch a product get built, feel invested, and convert at rates cold traffic never will.

The numbers back the logic. An early-stage company posting consistent build updates can reach thousands of qualified people per week for free. Compare that to what the same reach costs in paid channels right now, and public building starts to look less like a personality quirk and more like an arbitrage.

It also compounds in hiring and fundraising. Investors who watched you ship for six months need a shorter pitch. Candidates arrive pre-sold. The July Hacker News mood, all about evidence over hype, cuts the same direction: buyers and backers trust what they can verify, and a public track record is verification you built by accident.

Start smaller than you think, and start before you feel ready. That's the actual playbook.

Concretely, this week: pick one channel where your customers already hang out. Post one honest update about what you're building and what's hard about it. No polish, no announcement voice. Then commit to a rhythm you can keep for 90 days, because the first month of building in public feels like shouting into a void, and the compounding only shows up after that.

Set one public goal with a date. "Shipping X by Friday" does more for your focus than any productivity system. Miss it? Post why. That post will outperform the win.

And borrow the mindset, not just the tactics. The teenagers aren't fearless because they're young. They're fearless because they've done the math: the downside of looking foolish is small and temporary, and the upside of being known is large and permanent. That math doesn't change at 25, 35, or 50.

You either win or you learn in public. Both beat losing quietly.

Do I have to share revenue to build in public? No. Plenty of founders share process, decisions, and lessons without a single dollar figure. Numbers accelerate trust, but consistency matters more than transparency depth. Pick a level you can sustain for a year.

Won't competitors steal my ideas? They can see your ideas either way once you launch. In practice, execution and distribution decide markets, not secrecy. The main exception: specific unlaunched features that are cheap for a bigger player to copy. Keep those quiet until they ship.

Which platform should I build in public on? Wherever your customers already are. B2B founders usually get the most from X and LinkedIn; consumer founders often do better on TikTok or YouTube. One channel done consistently beats four done occasionally.

What if my startup fails while everyone is watching? Write the postmortem yourself, in plain words, and post it. Founders who document a failure well often find their next thing faster, because the audience trusts them more, not less. The record of how you handled it becomes an asset.

Is building in public worth it for boring B2B products? Often more so. Niche audiences are underserved, so an honest feed about building, say, logistics software can become the best-known voice in that niche within months. Small audience, high buying intent.

1. Build in public, fail in public: what it’s like to be a founder under 20 right now (TechCrunch)
2. The Under-20 Founder Boom: Building Startups Without Big Tech (TechBuzz)
3. 19-year-old founder vows to build a company bigger than Google as Nozomio raises $6M (Mezha)
4. Hacker News Trends, July 2026 (Mean CEO)