← Back to Hub research

Build in public, without the cringe. A playbook.

Build-in-public works when it compounds, not when it broadcasts. Here is the version of the playbook written for owner-operators with one to fifty people on the team, not unicorn founders chasing a Series B.

Open X on any Tuesday and you will see two versions of build-in-public. The first is the indie-hacker MRR chart, posted at midnight, with a green arrow and a victory-lap caption. The second is the founder thread that reads like a press release written by a board deck. Both are skippable. Neither moves a real business forward.

The version that does work is quieter, slower, and useful. A weekly note that explains a real decision you made. A short post that names a mistake you fixed last month. A case study that shows your customer winning, with their numbers, not yours. Done for 18 months, that pattern compounds. It builds a small audience of people who already trust you before they ever email. For an owner-operator running a 1-to-50-person business, that compounding trust is the entire point. You are not trying to go viral. You are trying to make the next 20 sales calls easier.

What to share, what to keep private

Most owner-operators stall on the first question. What is safe to put on the internet? The lines are not that hard once you split them.

Share decisions, not customers. "We dropped a product line last quarter because the gross margin slipped under 20 points" is a great post. "Acme Corp churned because their CFO is difficult" is a lawsuit. Talk about the call you made, the data behind it, and what you would do differently. Talk about customers only with their explicit yes, by name, in a structured case study you both review before publish.

Share numbers, with the right denominators. Absolute revenue is fine if you choose to share it. What is more useful for your audience is a ratio. Close rate by lead source. Hours saved per week by a new process. Refund rate before and after a packaging change. Ratios are sharable without exposing your bank balance, and they are what other operators actually want to learn from.

Share mistakes after the fix, not during. "We had a data outage last Thursday" while it is happening is panic content. The same story written three weeks later, with what broke, why it broke, what you changed, and how you would catch it earlier next time, is gold. The delay also stops you from publishing the version that gets the on-call engineer fired.

Keep these private always. Customer names without consent. Specific security incidents, vendor or API keys, internal compensation, anything covered by an NDA, anything about a pending deal, anything about a current legal matter. If you would not say it on a call with your insurance broker on the line, do not post it.

Weekly cadence compounds. Daily noise does not.

The trap most owner-operators fall into is thinking build-in-public means posting every day. It does not. Daily posting is a job. Weekly posting is a habit you can hold for 200 weeks. The compounding lives in the consistency, not the volume.

The format that has done the heavy lifting for the last five years is the weekly newsletter. Substack alone has crossed 5 million paid subscriptions and counts more than 17,000 writers getting paid through the platform¹. The growth is not from people posting hot takes seven days a week. It is from operators, journalists, and specialists who ship one solid piece on a predictable day. That predictability is what trains an audience to open.

For an owner-operator, a Tuesday or Saturday newsletter at the same time every week is enough. One main idea, 600 to 1,200 words, written like a long email to a peer. Add a recurring section, what you shipped, what you learned, what you are working on next, and you have a format you can hold for years. Beehiiv, Substack, and ConvertKit all give you the infrastructure for free until you scale, and the actual writing is the unscalable bit.

The platform mix that fits a small team

You do not need to be on every platform. You need a home base and one or two amplifiers.

Newsletter is the home base. You own the subscriber list. Nobody can deplatform your inbox. Open rates around 30 to 45 percent for a niche operator audience are realistic. Every other channel exists to feed this one.

X is for thread-building and operator-to-operator reach. Use it to post the chart, the lesson, or the one-paragraph excerpt from the newsletter, with a link. Threads still get reach when they pay off with a concrete takeaway by the third post. Pure-quote tweets do not.

LinkedIn is for credibility with buyers. If you sell to mid-market or enterprise, LinkedIn is where your prospect's procurement lead will check you before the call. Repost your newsletter intro plus the link, once a week, and keep your profile current with what your business actually does this quarter. That alone clears 80 percent of the bar.

YouTube, TikTok, and podcasts are bonus channels. Pick at most one. Each new channel is an hour a week you stole from product or customers.

Turning audience into pipeline

An audience that does not produce revenue is a hobby. There are four moves that turn followers into customers without making your feed feel like a sales funnel.

Named case studies with customer numbers. Once a quarter, publish a long-form case study with the customer's logo, the problem they had, the work you did, and the result in their words. Get their sign-off in writing. One real case study outperforms 50 generic thought-leadership posts because the buyer reading it can substitute their own logo into the story.

Free tools tied to the work you sell. A spreadsheet that runs a small cash-flow forecast. A Notion template for a weekly sales review. A short SQL query that flags duplicate contacts in HubSpot. People download, use, and remember you when the bigger version of that work shows up on their plate. Jason Lemkin built SaaStr partly on this pattern, giving away the playbook for going from a million to a hundred million in SaaS while running SaaStr Fund alongside it².

A clear "what we sell" page, one click away. The single most common build-in-public failure is a great newsletter with no obvious path to hire the writer. A simple services page with three packages, fixed prices or price bands, and a "book a call" button converts more readers than the next ten posts.

Treat referrals as a first-class output. Ask happy customers to introduce you on LinkedIn or forward your newsletter to one operator they respect. A single warm intro from inside an industry beats 1,000 cold impressions from outside it.

The trap of metrics theater

Followers, impressions, and likes are dashboards optimized for the platform's revenue, not yours. It is easy to spend a year growing a follower count from 2,000 to 12,000 and not move revenue by a dollar. Paul Graham's framing for startups applies here too. Most founders, he wrote, do not know whether their business is default alive or default dead, the trajectory that actually matters³. Build-in-public metrics have the same problem. Many founders cannot tell you which posts produced calls, which produced subscribers, and which produced applause.

The metrics that matter for an owner-operator are short. Newsletter subscribers added per month from non-paid sources. Reply rate on the newsletter (a real reply, not an emoji). Inbound calls booked per quarter that referenced something you wrote. Customers closed who said "I have been reading you for a while." Track those four. Ignore the rest. If you cannot point at a number that ties content to pipeline within two quarters, the playbook is broken, not the channel.

Key takeaways

• Share decisions, ratios, and fixed mistakes. Keep customer names, security details, and pending matters private.
• Weekly is the cadence that compounds. Daily is a job you will quit.
• The newsletter is the home base. X and LinkedIn are amplifiers, not replacements.
• Named case studies, free tools tied to your service, and a one-click "hire us" page do the conversion work.
• Track newsletter subscribers from organic sources, real replies, inbound calls referencing your writing, and closed deals that named you. Ignore vanity metrics.
• If you cannot connect content to pipeline within two quarters, fix the playbook, not the channel.

Sources

1. Backlinko (Iqbal, Mansoor). "Substack User and Revenue Statistics," updated 2025. Substack has crossed 5 million paid subscriptions and counts more than 17,000 writers earning revenue through the platform. backlinko.com/substack-users
2. SaaStr. "Who is Jason M. Lemkin?" SaaStr is a community of 500,000-plus B2B and SaaS founders built around publicly shared playbooks for going from one million to one hundred million ARR, while Lemkin also runs SaaStr Fund alongside it. saastr.com/who-is-jason-m-lemkin
3. Graham, Paul. "Default Alive or Default Dead?" October 2015. Most founders cannot answer whether their business is on track to profitability before running out of cash, the single metric that decides which decisions are sane. paulgraham.com/aord.html