Skip to main content
  1. Blog/

Why I build in public

··1 min
Artem Daniliants
Author
Artem Daniliants
I build startups, grow companies, and teach what I learn along the way.

There’s a growing movement of founders and builders who share their journey openly - revenue numbers, user metrics, failures, and pivots. I’ve been doing this for years, and here’s why I think it matters.

The fear of transparency
#

Most business owners guard their numbers jealously. Revenue is a secret. Failures are hidden. The public persona is always “crushing it.”

But here’s the thing: nobody believes that anymore. Audiences are sophisticated enough to spot performative success, and they’re drawn to authenticity instead.

What I share (and what I don’t)
#

I share project status honestly - including failures and shutdowns. I share the reasoning behind decisions, the lessons from mistakes, and occasionally specific metrics that illustrate a point.

What I don’t share: client data, team members’ personal information, or anything that could harm someone else.

The unexpected benefits
#

  1. Trust compounds - People who see your failures trust your successes
  2. Accountability - Public commitments are harder to abandon
  3. Community - Other builders connect when they see real stories
  4. Content - Your journey is the content

Getting started
#

You don’t need to share revenue dashboards on day one. Start small: share what you’re working on, what challenges you’re facing, and what you’re learning. The rest follows naturally.

Related

5 lessons from a failed startup

··2 mins
In 2017, I shut down an e-commerce venture after 18 months. It was painful, expensive, and one of the best things that happened to my career. Here’s what I learned. 1. Validate before you build # We spent three months building before talking to a single potential customer. By the time we launched, we’d built features nobody asked for and missed features everyone needed.