Insights / LinkedIn: A Distribution Strategy That Doesn't Require Becom…
LinkedIn: A Distribution Strategy That Doesn't Require Becoming a Thought Leader
Alice B
You write the post on a Tuesday afternoon. You draft it in Notion first because writing straight into LinkedIn feels dangerous. You remove the second exclamation mark. You consider removing the first one. You hit post. You refresh. Three views. Refresh. Seven. By the end of the afternoon there are twelve, and two of them are your mother. The worst part is that the product is fine.
"I tried LinkedIn for a month. Posted every day. Shared my founder journey. Got some likes from other founders. Zero new customers. Concluded it doesn't work for B2B SaaS." - r/SaaS, approximately once per week.
That’s the expertise vs performance split.
LinkedIn doesn't work as a vanity metric machine. It does work as a narrow, specific distribution channel for founders willing to write about the specific problem their product solves, for the specific person who has it, with enough detail that the post is actually useful. The performance version - vulnerability posts, hot take carousels, personal brand building - is optional. The expertise version isn't. Both approaches are real. The performance version builds a larger audience faster. The expertise version builds a smaller audience that's more likely to become customers. For a technical founder who finds the performance version alienating, the expertise version is worth understanding.
Why the standard LinkedIn advice doesn't work for technical founders
The 'post your journey' advice was designed for consumer-facing founders and coaches, not for technical founders selling B2B SaaS to professional buyers. The LinkedIn playbook - post daily, share failures and wins, be vulnerable, build your personal brand - is optimized for reach on a general audience.
For a technical founder selling a $500/month tool to VP of Sales at Series B companies, for example, general reach is not the goal. Reaching the specific 500 people at that job level who have that problem is. The performance version builds reach. The expertise version builds relevance. For B2B SaaS with a narrow ICP, relevance compounds faster than reach.
The founders who feel alienated by the standard LinkedIn advice usually feel that way because it asks them to perform in a register they don't naturally inhabit. If that's not how you communicate in the rest of your life, doing it on LinkedIn creates content that reads as constructed - and buyers, who are already skeptical, can usually tell.
Not sure which distribution channel to prioritize?
Run the free self-assessmentThe Tincture LinkedIn Distribution Stack
Three types of content, one connection practice, and a posting cadence that's sustainable without a content team.
Each content type is designed for a different interaction with your ICP - recognition, bookmarking, and credibility-building - and all three are accessible to a technical founder who communicates naturally about the domain they work in.
Write the specific problem post
Write about one specific problem your ICP has. Not 'why [category] matters for SaaS' - that's too broad. 'Why your pipeline forecast is probably off by 30% and what to look for in your CRM to find out' is specific enough that the VP of Revenue Operations it's written for either immediately recognizes the problem or immediately knows it doesn't apply to them. Both are the right outcome. The test: could this post have been written by any content marketer with access to Wikipedia, or does it require genuine experience with the problem? If it requires genuine experience, it does the work of establishing your credential without requiring you to explicitly claim it.
Publish a framework or checklist
A short, actionable framework from your domain. Not a listicle masquerading as insight - an actual structured approach to a problem your ICP has. Five questions to ask before changing your pricing. The three CRM fields that predict whether a deal closes. Frameworks work on LinkedIn because they're inherently shareable and saveable. A buyer who saves your framework post is bookmarking you as a source of competence - a different relationship than a buyer who liked a post because it resonated emotionally.
Share a data point or observation
Something specific you've noticed working with companies at your customers' stage. Not invented - observed. 'Across the last six pipeline audits we've done, the single most common source of inflated pipeline is...' reads as expertise. 'Here are five things I've learned about pipeline management' reads as content. Buyers trust reports more than constructions, and they can usually tell the difference.
One weekly connection practice builds the right network without feeling like networking: connect with a named list of target accounts, then send a short, specific message that references something real about their company. Not a pitch - a connection. 'I saw you're building out your RevOps function - happy to share what we've seen work for teams at your stage if useful.' Response rates on specific messages are meaningfully higher than generic connection notes.
What cadence actually works (consistency over frequency)
Two to three posts per week is the minimum for consistent visibility. One post per week is enough for presence but not growth. Consistency matters more than frequency. The sustainable cadence for founders who aren't building a media operation: two thoughtful posts per week, plus occasional comments on posts from your ICP's network. Comments that add a specific, relevant data point or a genuine counter-perspective perform better than 'great point' responses. This doesn't require a content team or a media strategy - it requires knowing your ICP's problems well enough to write something useful to them twice per week. If you can run a discovery call, you can write a LinkedIn post.
What not to do
Broad audience appeal: writing for 'anyone in SaaS' produces content that nobody finds specific enough to act on. Competitor criticism: even indirect criticism reads as insecurity to sophisticated buyers in your target ICP. Engagement bait: 'Comment YES if you agree' and poll posts generate algorithmic engagement and almost no pipeline. Posting without a path: every post should have a natural next action for the reader who recognizes themselves in it - 'if this is your situation, here's what to do' gives readers a direction. A post without a path creates recognition without resolution.
Frequently asked questions
How should a technical founder use LinkedIn for B2B SaaS distribution?
Focus on specific, expertise-driven content about the problem your product solves - written for the exact job title and company stage of your ICP. Post 2-3 times per week. Connect with targeted buyers using specific, non-generic messages. The goal is recognition from the right 500 people, not reach across 50,000 people who won't buy from you.
Does LinkedIn work for B2B SaaS lead generation?
Yes, but only if the content is specific enough to the buyer. Generic thought leadership builds follower count, not pipeline. Content that addresses a specific pain point your ICP has, written with enough specificity to prove genuine expertise, attracts buyers who are already looking for a solution.
How often should a SaaS founder post on LinkedIn?
Two to three times per week is the minimum for algorithmic visibility. Consistency matters more than frequency: two specific, useful posts per week outperform five generic posts.
What should a technical founder post on LinkedIn to attract customers?
Specific problem posts written for your ICP, short frameworks or checklists from your domain, and observations from your work with companies at your customers' stage. Avoid broad audience appeal, generic founder journey content, and engagement-bait formats.
Is building a personal brand on LinkedIn necessary for SaaS founders?
No - not in the performance version most LinkedIn advice promotes. The expertise version of a LinkedIn presence produces pipeline without the personal brand performance. For a technical founder who finds the performance version inauthentic, the quality and consistency of the expertise version usually outperforms it.
