04 Founder Visibility
What Founders Should
Actually Post
Good founder content helps people understand how you think.
The founder content system
Thinking
What the founder actually understands about the problem space
Clarity
That thinking expressed specifically and accessibly
Usefulness
Content that helps the reader think or act differently
Trust
Credibility earned through repeated, useful specificity
The question is not what content will perform. It is what content will help the right people understand how you think — and whether to trust you.
Why this matters
Most founder content is optimised for the wrong outcome and achieves the wrong result.
The pressure to produce content has led to a specific failure mode: founders publishing content that looks like thought leadership but does not demonstrate any. Inspirational quotes reformatted, generic advice about entrepreneurship, company announcements framed as insights, lessons from yesterday's team meeting that would be unremarkable in any context.
This content is visible but not trust-building. It signals presence without demonstrating expertise. And for founders in technical markets — AI, deep-tech, enterprise software, cybersecurity — the people they most need to reach are the ones most likely to dismiss generic content immediately.
What actually works is simpler and less performative. It is content that helps a specific, well-defined reader understand something better — about the problem, about the market, about how to think about a decision they face. That specificity is both harder to produce and far more valuable to the right audience.
Founder reality
Clarify what content is actually worth creating:
What do I know about this problem that most people in our market don't — and how would I explain it to a smart colleague?
What are the three most common misunderstandings that prospects have when they first engage with us?
What have we learned in the last six months that, if published, would help our ideal customers think better about their problems?
What questions do I most enjoy explaining — because I have a genuine, specific answer that I haven't seen articulated elsewhere?
If I could write one thing that would change how the right 50 people in my market think about our problem space, what would it be?
The answers to these questions are the content. They do not require frameworks, polish, or editorial production. They require honesty and specificity.
The framework
Six content types that build founder trust — ranked by trust yield
Not all content builds trust equally. These types build the most, in order.
01
Counterintuitive observations — things you believe that most people in your field don't
The highest trust-building content. When a founder articulates something that is genuinely counterintuitive, specific to their domain, and backed by real experience, it signals expertise immediately. It also tends to attract exactly the right people — the ones who are advanced enough to evaluate the claim.
02
Honest lessons from failures — what went wrong, why, and what you learned
Failure content is often high-trust because it is hard to fake. Specific, honest descriptions of what went wrong and why — without the 'but everything worked out' redemption arc — demonstrate both self-awareness and genuine experience. They also create disproportionate engagement from people who have faced similar problems.
03
Problem explanations — articulating the problem your company solves better than anyone else
Founders who can explain their problem space more clearly than the market typically expects are immediately more credible. Long-form problem explanations — why the problem exists, why it is hard, what makes it more complex than it appears — build the deepest pre-existing trust with technical buyers.
04
Market observations — specific, credible takes on what is changing and why
Well-grounded market observations demonstrate that the founder is reading the environment accurately. These work best when they are specific (a named dynamic), honest (including what is uncertain), and connected to real experience rather than industry report summaries.
05
Framework shares — structured ways of thinking about common problems
When a founder has developed a specific way of thinking about a problem that their audience faces, sharing that framework creates enormous trust. Frameworks that get adopted by readers create lasting credibility — they are referenced, shared, and associated with the founder's name.
06
Work-in-progress thinking — honest uncertainty about problems you are working on
Publishing genuine questions — not rhetorical ones, but things the team is actually uncertain about — creates a different kind of trust. It signals intellectual honesty and invites dialogue with exactly the kinds of people most valuable to the company.
Common mistakes
01
Generic lessons learned
Lessons framed as universal truths ('you need to listen to your customers', 'failure is part of the journey') teach nothing and signal nothing. Lessons from a specific situation, with specific context, specific outcome — those create trust.
02
Announcement content dressed as insight
Announcing a partnership, a product update, or a hiring decision is fine — it does not build thought leadership. Combining an announcement with genuine insight about what the decision reflects or what problem it solves works much better.
03
Writing for the wrong reader
Content optimised for engagement from a broad audience rarely creates trust with a specific technical buyer, candidate, or partner. Define the reader precisely. Write for them specifically. Accept that the reach will be smaller and the resonance much higher.
04
Publishing without a point of view
Content that describes a situation without taking a position rarely creates trust. A clear, defensible point of view — even a contrarian one — is what makes content memorable and what makes a founder seem credible rather than cautious.
Example scenario
A founder of a developer tooling company. Strong technical background. Tried content for three months: mix of company updates, industry news commentary, and generic tech takes. No business impact.
The content audit
Review of 24 posts: 12 company announcements, 8 industry news reactions, 4 generic software development observations.
None of the posts demonstrated specific expertise about the problem the company solves.
None would have been useful to the specific developers and engineering leaders the company sells to.
The content shift
Published a 1,200-word piece on a specific failure in developer tooling adoption they had studied in depth.
Followed with a short framework for evaluating developer experience that engineering leaders could apply immediately.
Published an honest, uncertain take on a direction in the tooling space they were watching but unsure about.
The outcome
Three pieces. Forty times the engagement from the right people. Two inbound conversations from senior engineering leaders. One became a customer six weeks later. The founder had been producing content for three months without this result — because the content was visible but not useful to the right people.
Takeaway
Write what you actually know. For the people who actually need it.
The most trusted founders are not the most prolific — they are the most specific. Write what you genuinely understand, for the specific reader who needs to trust you, with the specificity that signals real knowledge. Everything else is just content.
Related thinking
Continue reading
Thought Leadership Without Pretending