Build in Public
How to Build a Founder Brand While Building Your SaaS in Public
Build a recognizable founder brand from real SaaS work using problems, point of view, proof, and a clear connection to the product.
By Uriel Bitton · 4 min read
The short answer
SaaS founders can build a founder brand by repeatedly connecting themselves with a specific customer problem, a clear point of view, evidence from real startup work, and the product they are building. Building in public supplies the raw material naturally. The goal is recognition and credibility around useful work, not becoming a full-time creator or optimizing company decisions for content.
A strong founder brand is not created by posting about entrepreneurship every day. It forms when people repeatedly associate you with a specific problem, a useful point of view, and evidence that you are actually working on it. Building your SaaS in public gives you that evidence naturally. The goal is to turn real product work into a recognizable public record without letting content become a second company.
Start with the problem you want to be known for
Do not begin with: “What should my personal brand be?” Begin with: “What problem do I want someone to associate with me six months from now?”
If you are building software that helps SaaS teams understand onboarding drop-off, your founder brand should probably orbit activation, onboarding decisions, user behavior, and the mistakes you discover while solving those problems. This gives your public work coherence.
You can still share launches, failures, experiments, and milestones. They simply connect back to a recognizable area of expertise instead of becoming unrelated founder diary entries.
Add a point of view, not just information
A founder brand becomes memorable when the audience understands how you think.
Buffer founder Joel Gascoigne has written about the importance of a company having a clear point of view, describing how Buffer’s values eventually became something its community discussed and spread as well.
You do not need a controversial opinion every week. You need defensible positions produced by your work.
For example: “We stopped optimizing onboarding for completion rate. We care more about whether a user reaches one meaningful outcome.” That tells the reader something about the product and the founder’s reasoning. Over time, those positions become recognizable.
Use the Problem–Point of View–Proof–Product Bridge
Before publishing an important build-in-public update, check four elements.
Problem
What customer problem or operating question does this relate to?
Point of view
What do you currently believe about that problem? State uncertainty when the evidence is incomplete.
Proof
What happened in the actual work? Proof might be a product decision, customer-safe observation, experiment, failure, screenshot, workflow change, or result.
Buildside’s guide to what SaaS founders should share recommends including enough context and evidence for another person to understand or challenge the decision.
Product bridge
Why does this lesson connect to what you are building? This does not require a sales pitch. A simple line such as, “This is the reason we changed the activation report in our product this week,” is enough. Without the product bridge, you can build an audience that remembers your advice but forgets your SaaS.
Let operating work create the content
Founders often burn out on personal branding because they maintain two separate systems: build the company and invent things to post about. Combine them.
One decision you made.
One assumption that changed.
One customer problem that became clearer.
One experiment that failed.
One result worth explaining.
Buffer formalized a similar idea in 2025 with its Team of Creators initiative. The company described public creation as a way for team members to build their voices while experiencing the same challenges as Buffer’s customers, improving both connection and product understanding.
For a small SaaS founder, the mechanism can be much simpler: do the work first, then extract the useful lesson.
Build recognition through repetition
You do not need every post to say the same thing. You need multiple posts to reinforce the same territory.
If your territory is SaaS onboarding, one month could include why you rejected a feature request, an onboarding mistake you found, a customer-safe workflow observation, an experiment that changed your opinion, and a product improvement resulting from that lesson. Different stories. Same expertise.
Edelman and LinkedIn’s 2025 B2B Thought Leadership Impact Report, based on nearly 2,000 professionals, found that strong thought leadership can help less familiar vendors gain consideration and influence buyers beyond the people directly interacting with sales.
That does not mean posting guarantees pipeline. It means useful expertise can matter before a buyer speaks with you.
Do not optimize your startup for content
There is a failure mode. A founder discovers that certain posts perform well and starts making company decisions partly because they will create good content. Reverse that. The startup should create the content. The content should not create the startup.
Buildside’s practical guide to building a SaaS in public recommends treating public building as a by-product of operating the company and narrowing the cadence if publishing begins consuming time reserved for customer or product work.
For your next five public updates, use the same test: What problem does this connect me with? What do I believe? What evidence do I have? How does it connect back to the product? If those four pieces stay consistent, you are no longer merely posting startup updates. You are building a founder brand around the work itself.
Sources
Frequently asked questions
What should a SaaS founder be known for?
Choose a problem territory closely connected to the customers and product you are building. Your public decisions, experiments, lessons, and opinions should repeatedly reinforce that association.
Do founders need to post every day to build a personal brand?
No. Frequency should follow the supply of useful evidence from your work and the cadence you can sustain without reducing product or customer time. Consistent relevance matters more than manufacturing daily updates.
Should a founder brand be separate from the startup brand?
They can have distinct identities, but an early-stage founder brand should usually create a clear bridge back to the startup. Otherwise the founder may accumulate attention that does little to help the product.
What should founders post when building their brand in public?
Use real decisions, customer-safe observations, experiments, product changes, failures, and lessons. Explain the problem, your current point of view, the evidence, and how it connects to what you are building.
A note from Uriel Bitton
A founder brand should grow out of the startup rather than compete with it for time. Repeatedly connect the same customer problem with your point of view, real evidence from the work, and the product you are building. Over time, those public decisions become a recognizable body of work.
Keep building with us
Get practical founder lessons and product updates in your inbox.