On this page21
- What build in public actually is (and isn't)
- What to share: metrics, decisions, failures
- Cadence and platforms
- Pick one primary platform
- A realistic weekly rhythm
- What to share by startup type
- Turn short posts into long-form assets
- The risks, and how to manage them
- Templates for 10 build-in-public post types
- 1. The weekly shipped log
- 2. The metric update
- 3. The decision post
- 4. The mistake post
- 5. The customer lesson
- 6. The behind-the-scenes process
- 7. The milestone with context
- 8. The opinion post
- 9. The hiring post
- 10. The monthly recap
- How to start this week if you hate posting
- Measuring whether it's working
Build in Public: A Playbook for Founders Who Hate Self-Promotion
Building in public means sharing the real work behind your startup (numbers, decisions, mistakes and lessons) on a regular schedule, so an audience gets to know you before you ever ask them for anything. It works for founders who dislike self-promotion because you're not promoting anything. You're documenting. Pick one primary platform, post two to three times a week, use a small set of repeatable post types, and decide upfront which numbers stay private. Done that way, build in public turns into a steady source of trust, hiring interest, investor attention and early customers.
Most founders who say they hate self-promotion actually hate performing. That's fine. Build in public is closer to keeping a lab notebook where other people can read along.
What build in public actually is (and isn't)
It is a habit of showing your work: what you shipped, what you learned, what you got wrong, what you're deciding next.
It isn't a highlight reel, a growth-hacking trick or a daily "we're so back" post. Audiences can tell the difference fast. The posts that travel are specific and slightly uncomfortable to publish.
Three outcomes justify the time:
- Trust before the sale. Buyers who've watched you work for months need less convincing.
- Talent and investors. Strong candidates and seed investors read founder feeds closely. A visible thinking trail does part of the diligence for them.
- Feedback loops. Posting a decision before you make it gets you objections you'd otherwise hear six months later from churned customers.
What to share: metrics, decisions, failures
The most useful split is between things that are safe to share, things that need judgement, and things you keep private.
| Category | Usually safe | Share with care | Keep private |
|---|---|---|---|
| Metrics | Growth rates, user counts, waitlist size, shipping velocity | Revenue, churn, conversion rates | Runway, burn, bank balance |
| Product | What shipped, what you cut, roadmap themes | Pricing experiments, unreleased features | Security architecture, unpatched issues |
| Customers | Anonymous patterns, lessons from calls | Named logos (with permission) | Contract terms, anything under NDA |
| Team | Hiring lessons, how you work | Departures (framed carefully) | Performance issues, compensation of individuals |
| Fundraising | Lessons from the process after it closes | Round size once announced | Live term sheets, investor names before closing |
| Failures | Bad bets and what you changed | Outages and incidents (after resolution) | Legal disputes in progress |
A useful filter before you post anything: would you be comfortable if your biggest competitor, your lead investor and your next hire all read it on the same morning? If yes, post. If it only works for one of those three, rewrite it.
Cadence and platforms
Consistency matters more than volume. Two good posts a week for six months beats a daily streak that dies in week three.
Pick one primary platform
- X: fast feedback, strong for devtools, AI and indie founders. Short posts and threads.
- LinkedIn: strongest for B2B buyers, enterprise, and anyone over 30 holding a budget. Longer text posts do well.
- Newsletter or blog: slower to grow but you own the list, and long posts get indexed by search and AI assistants.
- YouTube or short video: high effort, high trust. Best if you're comfortable on camera.
Start with one. Repurpose to a second only after the first habit sticks.
A realistic weekly rhythm
| Day | Post type | Time needed |
|---|---|---|
| Monday | Weekly goal or decision you're weighing | 15 minutes |
| Wednesday | Lesson, mistake or behind-the-scenes from the week | 30 minutes |
| Friday | Shipped log or metric update | 15 minutes |
| Monthly | Long-form recap (newsletter or blog) | 2 hours |
That's around an hour a week plus a monthly recap. If you want a done-for-you schedule, the 30-day founder content calendar lays out a month of prompts mapped to these post types, and the post on the 30-day founder content calendar explains how to adapt it.
What to share by startup type
The best build-in-public content depends on who's watching. What earns trust with developers bores an enterprise buyer, and the reverse.
| Startup type | Audience you're building | Posts that work | Posts to avoid |
|---|---|---|---|
| AI devtools and APIs | Developers, technical founders | Benchmarks, changelogs, architecture choices, latency and cost numbers | Vague vision posts, revenue brags |
| B2B AI SaaS | Ops leaders, buyers, champions | Customer lesson posts, workflow breakdowns, pricing decisions | Raw usage metrics with no context |
| Vertical AI (legal, health, finance) | Practitioners in the industry | Accuracy lessons, compliance learnings, domain-expert collaboration | Anything that hints at customer data |
| Consumer AI | Users, creators, press | User stories, growth milestones, quirky product moments | Long technical threads |
| Web3 protocols | Community, developers, token holders | Shipping logs, governance decisions, ecosystem updates | Anything that reads like price talk |
If you're unsure, write for the person who would sign the contract, then check that a future hire would also find it interesting. That combination rarely goes wrong.
Turn short posts into long-form assets
Every month, pick the three posts that got the most real replies and expand them into one longer piece: a blog post, a newsletter issue or a LinkedIn article. Long-form posts get indexed by search engines and pulled into AI assistant answers in a way short social posts mostly don't. Over a year, that gives you twelve searchable essays built from material you already wrote, and a public record that a journalist, investor or candidate can read in one sitting.
Keep a running "swipe file" of every post with its replies. Patterns show up quickly: the questions people keep asking are your next FAQ page, your next blog post and often your next product decision.
The risks, and how to manage them
Build in public has real downsides. Name them before you start.
- Competitors copy you. They might. Execution is rarely the thing a post gives away. Keep unreleased product detail and specific customer names private.
- Investor optics. A flat month posted publicly can follow you into a fundraise. Share growth rates or ranges instead of raw revenue when numbers are volatile.
- Customer discomfort. Never describe a customer in a way they could recognise without asking first.
- Team pressure. Public metrics can feel like public grades for your team. Agree with them what you'll share.
- Audience mismatch. Followers from viral posts may not be buyers. Judge posts by who replies, not how many.
- Burnout and performative posting. If posting starts to feel like a job, drop to once a week. The audience prefers fewer honest posts.
- Security and compliance. In security, fintech, health and anything regulated, run posts past whoever owns compliance. For cybersecurity companies especially, a casual infrastructure screenshot can be a real disclosure.
Templates for 10 build-in-public post types
Copy these, fill the brackets, cut anything that sounds like marketing.
1. The weekly shipped log
Shipped this week:
- [Feature or fix] because [user problem]
- [Feature or fix] because [user problem]
Didn't ship: [thing] because [honest reason]
Next week: [one priority]2. The metric update
[Month] numbers for [product]:
[Metric 1]: [value] ([change] vs last month)
[Metric 2]: [value]
What moved it: [one specific cause]
What didn't work: [one experiment that flopped]3. The decision post
We're deciding between [option A] and [option B].
A gets us [benefit] but costs [cost].
B gets us [benefit] but costs [cost].
Leaning toward [choice] because [reason].
If you've made this call before, what did you learn?4. The mistake post
I got [thing] wrong.
What I believed: [assumption]
What happened: [specific result, with a number if possible]
What we changed: [action]
What I'd tell a founder six months behind me: [one line]5. The customer lesson
On [number] customer calls this month, one pattern kept coming up: [pattern].
We assumed [old belief]. Customers actually [new insight].
So we're [change].6. The behind-the-scenes process
How we [do a specific thing] at [company]:
1. [Step]
2. [Step]
3. [Step]
Tool we use: [tool]. Time it takes: [time].
Steal it.7. The milestone with context
We just hit [milestone].
It took [time]. The first [half] was [what was hard].
What changed: [specific turning point].
Thanks to [people or community, by role if not by name].8. The opinion post
Unpopular take in [your space]: [opinion].
Why I think so: [evidence from your own work]
Where I could be wrong: [honest caveat]9. The hiring post
We're hiring a [role]. What the job actually is:
- [Real task]
- [Real task]
Who will hate it: [honest description]
Who will love it: [honest description]
[Link]10. The monthly recap
[Month] at [company], in five lines:
Best thing: [win]
Worst thing: [setback]
Biggest lesson: [lesson]
Number I'm watching: [metric]
Next month's bet: [priority]How to start this week if you hate posting
- Choose one platform and one weekly slot you'll protect
- Write your private "never share" list (runway, customer names, security details)
- Draft three posts from the templates above before publishing the first
- Publish the shipped log on Friday, even if it feels small
- Reply to every comment for the first month
- Review after 30 days and note which post type got real replies or DMs
- Double down on that type and drop the one that felt forced
Measuring whether it's working
Don't judge build in public by likes. Track the things that matter to a startup: inbound messages from potential customers, candidates who mention your posts, investors who reach out, and replies that changed a decision. A simple monthly tally in a spreadsheet is enough.
After three to six months, consistent founders usually find their feed has become their most effective warm-intro machine. That's also the point where a press story lands better, because journalists and podcast hosts check your feed before they book you. If you want help turning that body of work into bylines and interviews, that's what founder profiling covers, and thought leadership for AI founders goes deeper on the strategy.
You don't need to love self-promotion. You need to keep a notebook and leave it open.
Want a starter set of prompts mapped to your first month? Grab the 30-day founder content calendar.