Build in public

Why Building in Public Works

Building in public taps into the 'IKEA effect' and the principle of reciprocity. When people see the effort, the challenges, and the behind-the-scenes work, they feel more connected to the product and the founder. They've seen it being built, so they value it more. By sharing your journey, you are giving value first -- in the form of lessons, entertainment, or inspiration -- which makes your audience want to give back, either through feedback, sharing, or eventually, purchasing.

This strategy also short-circuits the trust deficit new products face. Every post, every metric shared, every challenge overcome is a small deposit in the bank of trust. It serves as continuous social proof. When a potential customer sees a founder openly sharing their revenue, their user feedback, and their product roadmap, it signals confidence and transparency, reducing the perceived risk of trying or buying a new, unknown product.

Three real examples

Your first 100 followers are the hardest to get, but they will be your most valuable source of early feedback and support.

The step-by-step playbook

1. 1

   Step 1: Choose Your 'Public' Square

   Decide where you'll share your journey. Twitter/X and LinkedIn are the most common for founders. Pick one platform to start and be consistent. Don't try to be everywhere at once. Go where your target audience is.

2. 2

   Step 2: Define Your Content Pillars

   Decide what you'll share. Good pillars are: 1) Metrics (MRR, users, traffic), 2) Wins (features shipped, new hires), 3) Losses & Lessons (bugs, failed experiments), and 4) Behind-the-Scenes (your process, your 'why').

3. 3

   Step 3: Set a Realistic Cadence

   Consistency is more important than frequency. A weekly update thread is a great start. Daily posts can work if they are small and authentic. Whatever you choose, put it in your calendar and stick to it for at least 30 days.

4. 4

   Step 4: Post Your Origin Story

   Start by introducing yourself and your project. Why are you building this? What problem are you solving? This first post sets the stage and gives context for everything that follows. Pin it to your profile if you can.

5. 5

   Step 5: Document, Don't 'Create'

   Don't overthink it. The easiest way to build in public is to document what you're already doing. Fixed a bug? Share how. Designed a new feature? Post a screenshot. The content is your daily work.

6. 6

   Step 6: Share Numbers, Not Just Stories

   Numbers are the language of building in public. Share your monthly recurring revenue (MRR), number of users, conversion rates, or even just website traffic. This transparency is what makes the process compelling and builds credibility.

7. 7

   Step 7: Engage With Everyone

   Building in public is a dialogue, not a monologue. Reply to every comment and question. Thank people for their feedback. This engagement is how you build a community, not just an audience.

The 'Weekly Update & Feedback' Template

Here's a simple template for a weekly update on Twitter/X or LinkedIn. It's designed to share progress and actively solicit feedback.

Another week building {My Product}! Here's a quick update:

- 🔥 Shipped: {A feature or fix you launched}
- 📈 Metric: {e.g., Weekly Active Users} is now at {Number}
- 🤔 Learning: {A lesson you learned this week}

I'm currently working on {Next feature/problem}. Here's a sneak peek (see screenshot/video).

What do you think of {Specific question about the new feature}? Feedback is a gift!

Key Questions for Your 'Build in Public' Strategy

• What is the unique story behind why I'm building this?
• Which platform do my ideal customers spend the most time on?
• What are the 3-5 key metrics that truly define my product's progress?
• What is my 'red line' -- what information is too sensitive to share publicly?
• How can I turn my updates into a conversation rather than a broadcast?

The most important questions are about your 'why' and your audience. If you know why you're sharing and who you're sharing it for, the 'what' and 'how' become much easier.

Recommended tools

Prices are indicative and change - check the vendor before buying.

Do it faster with AI Prompts

Mistakes that kill this play

• ×Only sharing the wins. People connect with struggles. Sharing your challenges makes you more relatable and trustworthy.
• ×Being inconsistent. Building in public is a flywheel; it needs consistent pushes to get going. Sporadic updates won't build momentum.
• ×Broadcasting, not engaging. Don't just post and ghost. The real value is in the conversations and relationships you build in the replies.
• ×Forgetting the 'build' part. You must make progress on your product. If you're only tweeting and not shipping, your audience will lose interest.
• ×Sharing sensitive information. Know where to draw the line. Don't share customer data, critical security info, or personal details that could put you at risk.
• ×Chasing vanity metrics. Focusing on follower counts instead of genuine engagement and feedback leads to hollow results.

Your First 7 Days of Building in Public

• Day 1: Choose your primary platform (e.g., Twitter/X). Write and post your origin story: who you are, what you're building, and why. Pin it to your profile.
• Day 2: Share a screenshot or a short video of the current state of your product. Talk about what you're working on right now.
• Day 3: Share a 'learning'. What's something you figured out this week? It could be a technical discovery, a user insight, or a marketing lesson.
• Day 4: Post one key metric. It doesn't have to be revenue. It could be '0 signups' or '100 landing page visits'. Be honest.
• Day 5: Ask a direct question to your audience. For example, 'What's the one feature you wish our product had?' Spend 30 minutes engaging with every reply.
• Day 6: Share a small win. Did you fix a bug, design a new logo, or get a nice comment? Celebrate it publicly.
• Day 7: Summarize your week in a short thread. What went well? What didn't? What are you focused on next week? Link to your posts from the week.

More Level 1 hacks