Founders accumulate a great deal of hard-won knowledge, and much of it would genuinely help other people building companies. The instinct to share it is sound. Writing about what you have learned builds professional standing, attracts the right peers and clients, and forces a clarity of thought that is hard to reach any other way. The hesitation is equally reasonable, because commercial figures are sensitive, contracts contain confidentiality clauses, and a careless post can harm a customer relationship or hand a competitor an advantage.
The tension is not a reason to stay silent. Sharing lessons and protecting numbers are separate activities, and the skill lies in telling them apart. A founder can describe the shape of a problem, the reasoning behind a decision and the lesson that followed, without quoting a revenue figure or a private client detail. Working at that level of abstraction is what makes public writing safe and durable.
Why founders hesitate to share
Most founders who avoid writing publicly do so for a small number of reasons. They worry about breaching a non-disclosure agreement, handing competitors useful information, or being held to a public claim later. Some worry about the opposite problem: that anything safe enough to publish will be too generic to be interesting.
These worries are legitimate, but they are also solvable. The first step is to understand which information is genuinely sensitive and which only feels that way.
Deciding what counts as sensitive
Sensitive information tends to fall into predictable categories. Precise financial figures, including revenue, margins, runway and valuation, are the most obvious. Customer identities and the terms of commercial agreements are usually protected by contract. Proprietary technical methods, unpublished plans and anything that could affect a share price or an investor negotiation are also best left out.
Beyond those, much of what founders assume to be secret is not. The fact that a particular market turned out to be harder than expected, or that a hiring approach did not work, or that a pricing model was revised, is ordinary operating experience. It is confidential only if a specific agreement says so, and it becomes safe to discuss once names and numbers are removed.
A useful test is to ask what a competitor could actually do with the information. General lessons about process and judgement are rarely exploitable, while specific, current and quantified details sometimes are.
Turning experience into transferable lessons
The most durable public writing does not tell the reader what happened to you. It tells them how to think about a situation they are likely to face themselves. This shift, from report to lesson, is what allows a founder to be useful without being indiscreet.
A useful structure is to describe the problem before the answer. Set out the situation in general terms, explain the competing considerations a founder weighed, describe the decision that was made and why, and finish with what would be done differently. None of these steps requires a single number. The value for the reader lies in the reasoning rather than in the outcome.
It also helps to write about categories rather than instances. Instead of describing one negotiation, describe the pattern that several negotiations revealed. Instead of naming a customer, describe the type of buyer and the friction they tend to create.
Describing direction without decimals
When a founder does want to convey scale, direction is often enough. Saying that a metric grew, stalled, or fell after a change communicates the lesson without exposing the underlying figures. Readers learn from the movement and the cause, and the confidential baseline stays private. Where a figure is already public, or where a contract clearly permits disclosure, it can be used, but the default should be to describe the direction of travel rather than the exact value.
Methods for describing outcomes without figures
There are several reliable ways to convey a result without quoting it. Qualitative comparison works well: better than expected, slower than planned, broadly in line with the forecast. Relative description works too: enough to fund the next stage, not enough to justify the hire. Structural description is often the strongest, explaining what changed in the business rather than how much.
Founders can also separate the mechanism from the magnitude. The mechanism, such as shifting from outbound sales to partnerships, is usually shareable. The magnitude, such as the number of deals it produced, often is not. Explaining the mechanism teaches the reader; withholding the magnitude protects the company.
Time also helps. Lessons that have aged, where the specific facts no longer matter, can often be told in more detail than recent ones.
Handling confidentiality and contracts
Before publishing anything, a founder should check the obligations that actually apply. Employment contracts, customer agreements and investor documents may all contain confidentiality clauses that survive the end of a relationship. Where the position is unclear, it is worth taking legal advice rather than guessing.
Confidentiality is usually about specific facts rather than general knowledge. A founder can almost always discuss the type of work, the nature of the challenge and the personal lesson, provided the identifying details are removed. If in doubt, describe the situation at a level where it could apply to many companies, not only your own.
It is also wise to avoid writing about a live situation. Commentary on an unresolved negotiation, a pending contract or an unannounced plan invites trouble. Wait until the outcome is settled, and write about it as history.
Keeping claims honest and verifiable
Public writing creates a record, and that record should be one a founder would be comfortable defending. Avoid suggesting results that cannot be supported, and avoid implying that a single decision caused an outcome when many factors were at play. Honest, modest accounts age far better than triumphant ones, and they are far harder to undermine.
It also helps to be consistent across platforms. If the same lesson is told on a blog, on LinkedIn and in a talk, the facts should match, because inconsistency invites exactly the scrutiny a careful founder is trying to avoid.
Practical checklist
- [ ] Identify which figures are contractually confidential before writing anything.
- [ ] Remove all customer names, exact financials and proprietary methods.
- [ ] Write about the pattern rather than the single instance.
- [ ] Lead with the problem and the reasoning, not the outcome.
- [ ] Describe direction and mechanism rather than precise magnitudes.
- [ ] Avoid commenting on live negotiations or unannounced plans.
- [ ] Keep accounts modest and consistent across every platform.
- [ ] Take legal advice where a confidentiality obligation is unclear.
Contributing to BGTC Voice
Sharing lessons is one of the most useful things a founder can do for the wider ecosystem, and it does not require surrendering anything confidential. If you have written about building a company in a way that respects client and investor agreements, we would welcome your perspective in BGTC Voice. Send practical, evidence-based accounts that help others learn without exposing what should stay private.