Sign in Get the app

Build in public

Build in public from your commits

Building in public means sharing the work as you do it; paste a week of commit messages below and get 3 posts drafted, free.

Free. No signup. Runs in your browser, nothing is sent.

A cadence that fits around real work is three posts a week: a ship note written from your commits, one number you are happy to share, and one lesson. Below: that cadence, 12 founders who do this, a Product Hunt launch week plan, and what to keep private.

Checked November 19, 202621 sources

Sample data

What building in public means

It covers a wide range. At one end, companies publish their books. Buffer's open metrics page showed an MRR of $2.4M, an ARR of $28.7M and a CEO salary of $340,200 when we checked on November 19, 2026. At the other end, a solo developer posts once a week about what they shipped and never shares a dollar figure.

Both count. What they have in common is that the posts come from real work, in close to real time. That gives people a reason to follow you before they need your product. It also leaves a public record of every decision.

It is not a daily status report. The useful version is narrow: one thing you did, why, and what happened.

A weekly cadence: ship notes, numbers, lessons

Three posts a week is enough to stay visible and few enough to keep up for a year. Each one has a different source, so you never stare at a blank box.

A build in public week
DayPostWhere it comes fromTime
TuesdayShip note: one change people can useMerged PRs, commits, your changelog10 min
ThursdayA number, with what it meansYour analytics or billing dashboard5 min
FridayA lesson: a mistake, a surprise, a decisionNotes you kept during the week10 min
Any dayReplies on other builders' postsYour feed10 min

The ship note is the easiest, because the work already happened. Pick the change a user would notice first, say what they can do now, and stop. If you keep a changelog, the note is already half written; our release notes template shows a format that makes the lift easy. The number post is the one people skip. It does not have to be revenue: signups, a conversion step, a build time or a support queue all work, as long as you say why the number matters. The lesson post is the one people remember. Write it as a single decision and its result.

XDraft in Gin's format (a ship note for Zest, our own product)

New in Zest: standups now include blocked PRs.

If your coding agent opened a PR that is stuck, it shows up in the standup instead of waiting for someone to notice.

LinkedInA template for the number post. Fill in the brackets; we never invent numbers.

Numbers from week [N] of building Zest:

[number] teams ran a first standup.
The step where most people stopped: [step].

This week we are changing [what] to fix it. I will post the result next Thursday.

Pick the days once and keep them. Followers notice a rhythm more than they notice any single post.

Short on time? Our marketing for developers plan fits a smaller version of this week into 30 minutes.

From a week of commits to three posts

A week of commit messages is the raw material, but most of it is not news. Pull the list with one command:

Last 7 days of commit subjects
git log --since="7 days ago" --no-merges --pretty=format:%s

Then sort every line into one of two piles:

  • Users can see it: a new feature, a fix for a bug people reported, something faster that people will feel. These become posts.
  • Users cannot see it: dependency bumps, refactors, CI changes, tests, renames. These stay in the commit log. Nobody follows you for your lockfile.

Rewrite what is left from the user's side. A commit subject is a note to the next developer; a post tells a user what they can do now. Group small fixes into one post rather than three thin ones.

An example week of commits (illustrative)

feat: show blocked PRs in standup
fix: standup sent at wrong hour for non-UTC projects
chore(deps): bump hono
refactor: split standup builder
ci: cache bun install

XDraft in Gin's format

This week in Zest:

- Standups now include blocked PRs
- Standups arrive at the right hour in your project's time zone

Two small changes for anyone running coding agents across time zones.

Three of the five commits are invisible to users and get dropped. The two that remain are rewritten as what a user now gets, and the time zone fix becomes a reason to care instead of a confession.

The tool under the answer does this sort for you: paste the output of the command above and it drafts 3 posts from the changes worth posting.

12 founders and companies who build in public

Every fact below is what the founder's or company's own page showed when we checked on November 19, 2026. Figures are theirs, mostly self-reported, and will have moved by the time you read this.

  1. Buffer publishes open metrics: 356,874 monthly active users, $2.4M MRR, $27.37 average revenue per user, and salaries (CEO $340,200, average $166,535). It also posts monthly shareholder updates; the latest listed was December 2025.
  2. Ghost runs a live feed on its about page: "Yes, this is a live feed of our real data." It showed $11,135,698 in annual run rate and 30,215 active customers, and says "All of our company metrics are public."
  3. Cal.com calls itself "the most public private company". Its open page says: "Our salaries, cap table and core metrics are public, and so is our handbook." The charts redraw from live data every hour.
  4. Plausible states its numbers in prose on its about page: more than 22,000 paying subscribers, $1 million in annual recurring revenue crossed in 2022, a team of 11, and no outside investors.
  5. Baremetrics started the Open Startups movement in a post by Josh Pigford dated April 22, 2015. The early list included Buffer, ConvertKit, Ghost and Hubstaff, each with a public revenue dashboard.
  6. Marc Lou puts his whole portfolio on his homepage: "I was fired everywhere, so I built 43 startups," a revenue chart labeled "$1,234,942 in 12 months", and each product's last 30 days of revenue.
  7. TrustMRR, which Marc Lou built, lists startups with revenue it marks as verified. Its stats page showed: "Daily snapshot of $1,990,847,799 verified revenue across 70M transactions."
  8. Pieter Levels runs Nomads.com, Remote OK, Hoodmaps, Photo AI and Interior AI, "all bootstrapped without funding" per levels.io. His stats page indexes 958 posts about building them.
  9. Tony Dinh writes a monthly newsletter about "my indie hacking journey, what I have built and learned". His June 10, 2026 issue was titled "I'm on Product Hunt! + Updates Jun 2026".
  10. Arvid Kahl built Podscan in public. Audiohook bought it, in a deal that closed on August 24, 2026. Months earlier, in an April 3, 2026 essay, he argued the revenue level below which sharing felt safe "has effectively collapsed to zero".
  11. Mautic, the open source marketing tool, adopted the Open Startup model on May 2, 2023, with monthly reports on revenue, community growth, contributors and website traffic.
  12. Bannerbear shows that you can dial it back. Its open page now reads: "Bannerbear was an open startup with public metrics, we now only share selected metrics".

Two patterns stand out. The companies that share the most (Buffer, Ghost, Cal.com) automate it: a live page beats a monthly chore. And the solo founders who last years post about the work itself, with numbers as a bonus rather than the point.

A Product Hunt launch week plan

A Product Hunt launch is where months of posts pay off, because people who watched you build are the ones who show up on the day. The rules below come from Product Hunt's own launch guide, checked November 19, 2026.

  • Every launch goes live at 12:01 AM Pacific Time on the day you pick, and you can schedule it from tomorrow up to 30 days ahead.
  • You do not need a hunter. Product Hunt's FAQ says "You can, and should, hunt your own product." Launches must come from personal accounts, not company accounts.
  • "Never ask for upvotes." Ask for feedback and trials instead. No paid upvotes, no extra accounts, no mass DMs to strangers. Upvotes from established members count far more than new accounts.
  • The product page takes a 60-character tagline, a 500-character description and at least one gallery image. Launching again within two months needs a relaunch request.
Launch week, day by day
WhenWhat to do
3 to 4 weeks outPick a day you can be online for all of it, schedule it, and set one or two measurable goals.
The week beforeBuild the product page and gallery, draft the maker comment, and tell your followers the date.
Launch dayPost the maker comment, share the link where your audience already is, and reply to every comment you can.
The week afterShip one fix from launch feedback and post about it. Write down results against your goals.

Checked 2026-11-19.

Product Hunt's own launch day advice comes down to: "The most important thing you can do is be there." The build in public habit makes that easier, because you already know how to talk about the product in short posts.

What not to share

Some things should never appear in a post, and some are a judgment call.

  • Never: customer names or data without permission, screenshots with emails, API keys or tokens in view, and security bugs before the fix has shipped.
  • Ask first: anything about a teammate, a partner deal, or another company's numbers.
  • Think twice: the details that make you easy to copy.

That last one has changed. In his April 2026 essay, Arvid Kahl argues that an AI agent can now read a founder's public posts and site and build a competing product in days. He suggests holding back revenue, customer counts, architecture, and the specific vendors you use. What he would still share: surprising findings, broad industry lessons, and stories about a customer conversation or a bug, without the business context. His filter is short: "Interesting to participate in. Not easy to clone."

You can also change your mind later, as Bannerbear did. A ship note never needs a revenue number to be useful.

Where Gin fits

The hard part of building in public is not the shipping; it is writing about it every week while you keep shipping. Gin takes the ship note off your plate. Sign in with Google, then paste one message into your coding agent:

Paste into Claude Code, Codex or Cursor
Set up Gin for this project. Read and follow https://trygin.ai/setup.md My one-time code: GIN-XXXX-XXXX

From then on, each merged PR or coding session arrives as a message. One model call picks which channels it deserves; a dependency bump gets none, much like the sorting above. You swipe right to post or left to pass, and after three right swipes in a row on a channel, Gin offers autopilot for it. Its default slots line up with the week above: LinkedIn on Tuesday and Thursday at 9:00, X on weekdays at 12:00.

Gin writes from what you ship, so the number and lesson posts stay yours. The Free plan covers up to 3 products and 20 published posts a month; swiping and remixing cost nothing. Autopilot comes with the paid plans (pricing). The Claude Code marketing guide shows exactly what that pasted message sets up.

Questions

What does building in public mean?

It means sharing your work as you do it: what you shipped, what your numbers did, and what you learned. Some companies publish revenue and salaries, like Buffer and Ghost. Many solo founders share only ship notes and lessons. Both count.

What should I post when building in public?

Three kinds of post cover most weeks: a ship note about one change users can see, one number with what it means, and one lesson from a decision or mistake. Skip internal changes like refactors and dependency bumps.

Do I have to share revenue to build in public?

No. Many founders never share dollar figures, and Arvid Kahl now suggests holding revenue back. Signups, a conversion step, build times or support volume all make good number posts.

When does a Product Hunt launch start, and do I need a hunter?

Launches go live at 12:01 AM Pacific Time on the scheduled day, and you can schedule up to 30 days ahead. You do not need a hunter; Product Hunt says to hunt your own product from a personal account.

Is building in public risky?

It can be. Arvid Kahl argued in April 2026 that AI agents make products built from public details easier to clone, and suggested holding back revenue, customer counts, architecture and vendors. Never share customer data, secrets or unfixed security issues.

Related guides

Sources

Checked November 19, 2026. Prices and limits change; each link goes to the page we read.

  1. Buffer: open metrics
  2. Ghost: about (live metrics)
  3. Cal.com: Open Startup
  4. Plausible: about
  5. Baremetrics: Open Startups (Apr 22, 2015)
  6. Marc Lou: homepage
  7. TrustMRR: startup statistics
  8. Pieter Levels: levels.io
  9. Pieter Levels: stats (post index)
  10. Tony Dinh's newsletter archive
  11. Arvid Kahl: The Increasing Risk of Building in Public (Apr 3, 2026)
  12. Podnews: Audiohook acquires Podscan (Sep 30, 2026)
  13. Mautic adopts Open Startup model (May 2, 2023)
  14. Bannerbear: Open Startup Metrics
  15. Product Hunt: How Product Hunt works
  16. Product Hunt: Set your goals and pick your launch date
  17. Product Hunt: Build your product page
  18. Product Hunt: How to promote your launch (and what to avoid)
  19. Product Hunt: What to do during and after your launch
  20. Product Hunt: Relaunch your product
  21. Product Hunt: Launch FAQ and myths

You ship. Gin posts.

Get the app, paste one message into your coding agent, and swipe through your first cards tonight.