Building in public means sharing selected decisions, experiments, results, and lessons as you build a company. For a B2B founder, share enough to demonstrate judgment while keeping pipeline, employee matters, sensitive commercial terms, and trade secrets private.
What building in public means
Building in public makes your work visible to people with power over your company's future. Every post can become diligence material for an investor or competitive intelligence for someone chasing the same customers. Treat the feed like a public record you're glad to be held to, and decide your disclosure boundaries before you draft.
What it looks like when it works
Copy.ai provides a concrete example of public updates creating discovery. In his March 2021 coverage of Copy.ai, TechCrunch reporter Alex Wilhelm said he first heard of the company through its monthly updates on Twitter. The updates gave him company information he could use in his reporting.
I was Copy.ai's first CMO. The useful point here is narrower than saying public updates caused the company's growth: a reporter could follow its progress before speaking with the team. A founder can share outcomes and lessons without publishing the machinery behind them.
What to share
Public posts can demonstrate judgment through lessons, process, defensible results, and positions.
Lessons that cost you something. The launch that flopped, the channel that went nowhere, the hire you got wrong in the abstract (never the person). Share these the way you'd tell a founder friend over dinner: what you tried, what it cost, what you'd do differently. Remove identifying details, and hold the story if the people involved would still be recognizable.
Process. How you run discovery, how you structured pricing, how you decide what to build next. Process posts can demonstrate competence, as long as you share the shape of the system rather than the playbook line by line.
Numbers you'd defend. A number belongs in public only when it's accurate, you're permitted to disclose it, and you've considered how others could use it. Check confidentiality obligations and get any required approval. Being comfortable repeating it to your board is a useful test of accuracy, but it doesn't establish permission to publish.
Positions. What you believe about your market that others in your seat won't say out loud. A customer who has read your thinking has something concrete to discuss on a call.
If you want to check whether your feed makes those positions clear to the right people, take Megaphone's free feed diagnostic. Use the result to decide what your public writing needs to communicate before adding more posts.
What to hold back
Pipeline. Deal names, prospect names, close dates, win rates on live deals. A prospect may recognize themselves even if you remove their name, and a competitor can use the details to identify whom to approach.
People. Confidential information about an employee's performance, exit, or compensation belongs outside a founder's feed. A lesson about your own management decision still needs to protect the person involved.
Leverage. Margins, discount history, churn details, contract terms. Consider whether a customer could use the disclosure in a renewal negotiation before you publish it.
Clone fuel. Architecture, vendor lists, and the exact mechanics of your best channel can expose a competitive advantage. In his guide to sharing without revealing too much, Arvid Kahl distinguishes a business insight from a trade secret. The relevant question is whether the post teaches a useful lesson or hands someone instructions for competing with you.
The part the solo-maker advice skips
Audience fit matters when a B2B founder shares company work. Attention from fellow founders can be enjoyable without bringing you closer to the customers you need. Treat that as a reason to inspect who responds, not as proof that public writing can't work.
A sustainable publishing process needs a schedule and a subject you can keep returning to:
- Publish on a schedule you can hold through a difficult stretch. At Megaphone, posting stays off while we build the system, then starts on the full weekly plan. Keep sensitive developments private, even when they explain why you have less to say.
- Stay in a subject you know. I use my own marketing account as the example: when I wander into unrelated topics, I see reach drop. Maybe I'm just uninteresting outside that lane. I can't assume every account will respond the same way.
Kahl's video explains how to separate business insights from information you should keep private.
The decision, made calmly
A disclosure filter gives each draft post a concrete review:
- Name the person the post helps and the lesson they can use.
- Remove confidential information and details that identify someone who hasn't agreed to be included.
- Check each factual claim and obtain any required disclosure approval.
- Read it as a customer, employee, investor, and competitor. Hold or rewrite anything that gives away more than the lesson requires.
If your writing needs a clearer connection to the people you want to reach, use the free diagnostic to identify what to fix in your feed. Megaphone's diagnostic is a starting point for that publishing decision, not a confidentiality review.