Section 1
Concentration risk, stated plainly
If a meaningful share of your pipeline arrives because people follow you personally, then your attention is a channel, and channels have to be resourced. That has three consequences most founders meet late. It does not transfer. Demand attached to a person stays with the person, so an acquirer discounts it and a successor cannot inherit it. It does not pause. Stop publishing for a quarter and the channel decays, which means the commitment is ongoing rather than a campaign. And it constrains the company, because a public position taken in year one becomes awkward when the business needs to change direction in year three, and the audience will notice the reversal before your customers do. None of this argues against doing it. It argues for doing it deliberately, with a plan for building company-level channels alongside, so the personal one is an accelerant rather than the whole engine.
Section 2
Publish what operating taught you
The only durable material is the part you learned by doing the work: the pricing change and what it did to close rates, the hire that did not work and what you now screen for, the process you built after an outage. Nobody else has that, and it cannot be produced by summarising other people's writing. Commentary on the news of the field is the alternative, and it is a treadmill. It performs adequately, requires constant input, and builds an audience for the commentary rather than for you. The test is simple enough to apply before publishing: could someone who has never run a company have written this. If yes, it is not your material, and someone with more time will produce a better version of it next week.
Section 3
Choosing the surface
Use the model that follows to decide what is in scope. Column one lists the subjects where you have direct operating experience, column two what publishing on each would attract, and column three the audience you would then be obliged to serve. The third column is the one founders skip and later regret.
Section 4
How much to disclose
Difficulty is the most persuasive material available and the easiest to overspend. The version that works is retrospective and specific: what went wrong, what you did, what changed structurally as a result. The version that damages you is live and unresolved, published to an audience that includes people deciding whether to depend on your company. The test is direction of benefit. If the reader gains a decision rule they can use, publish it. If the writing mainly relieves you, that is a conversation for a peer group rather than a feed. Timing matters too: a difficulty disclosed after it is resolved reads as command of the situation, and the same difficulty disclosed while it is live reads as instability to a customer with a renewal pending. [The Power of Founders Sharing Personal Struggles](/blog/the-power-of-founders-sharing-personal-struggles) works through where that line falls.
Section 5
Cost, and when to stop
Account for the time honestly. A serious publishing habit consumes several hours a week for years, and those hours come out of the product, the team or your rest. It is a reasonable trade if the channel is producing pipeline you can trace. It is a poor one if it is producing approval, and the two are easy to confuse because they feel identical in the moment. Review it annually against one question: what did this bring that another use of the same hours would not. Track conversations that became revenue, hires that arrived because of it, partners who reached out. If the honest answer is a larger following and nothing measurable, reduce the surface and reinvest in the company channel. Building that operating capacity is a separate discipline, and [AI Automation for Non-Technical Founders: Where to Start](/blog/ai-automation-for-non-technical-founders-where-to-start) is a sensible entry point. For the narrower case of speaking to capital, see [Telling Your Story to Investors: What Works, What Doesn't](/blog/telling-your-story-to-investors-what-works-what-doesn-t).