Founder Thought Leadership
When to Use
- Founder wants to build a personal brand that drives pipeline, recruiting, or fundraising
- Founder wants to establish IP (intellectual property in ideas, not legal) — original frameworks, contrarian takes, or proprietary insights
- Founder wants to grow a relevant audience on X or LinkedIn
- Founder wants to turn founder journey into content (building in public, lessons learned)
Context Required
- Founder's area of expertise and unique perspective
- Target audience (customers, investors, talent, peers)
- Platform priority (X, LinkedIn, or both)
- Current following size and engagement baseline
- Company stage and what they're optimizing for (pipeline, recruiting, fundraising, awareness)
Workflow
- Define the founder's IP territory — identify 2-3 topics where the founder has genuine, earned insight that others don't. These must pass the "why should anyone listen to YOU on this?" test.
- Audit existing content — review the founder's last 20 posts on each platform. Identify what got traction, what fell flat, and what's missing from their voice.
- Build the content system — create a repeatable framework:
- Pillar posts (1-2/week): original frameworks, data, or contrarian takes that establish IP
- Proof posts (2-3/week): behind-the-scenes, customer wins, lessons from failure, building in public
- Engagement posts (daily): replies, quote tweets, threads on others' content
- Create the IP library — document the founder's original frameworks, mental models, and coined terms. These become the building blocks for all content.
- Write a 2-week content calendar — draft actual posts with platform-specific formatting.
- Set up the feedback loop — define which metrics to track (impressions, profile visits, inbound DMs, pipeline attributed to content).
Output Format
## Founder Thought Leadership Plan
### IP Territory
- Topic 1: [topic] — why you have authority here
- Topic 2: [topic] — why you have authority here
### Original Frameworks
- [Framework name]: [one-line description]
- Origin story: [how you discovered/developed this]
- Post format: [how to present it]
### Platform Strategy
**LinkedIn:** [posting cadence, format preference, audience]
**X/Twitter:** [posting cadence, format preference, audience]
### 2-Week Content Calendar
| Day | Platform | Type | Topic | Hook |
|-----|----------|------|-------|------|
| Mon | LinkedIn | Pillar | ... | ... |
| Tue | X | Proof | ... | ... |
| ... | ... | ... | ... | ... |
### Metrics to Track
- [metric]: [current baseline] → [30-day target]
Frameworks & Best Practices
The IP Test: A post builds IP if people screenshot it, reference your framework by name, or tag you when the topic comes up. If none of that happens, it's content — not IP.
Platform differences:
- LinkedIn: longer-form, professional framing, storytelling, carousels perform well. Algorithm rewards comments over likes. Post early morning (7-8am local).
- X/Twitter: shorter, punchier, thread format for depth. Algorithm rewards replies and quote tweets. Contrarian takes travel further. Consistency matters more than timing.
Building in public works when:
- You share specific numbers (revenue, users, churn), not vague "we're growing"
- You share failures and what you learned, not just wins
- You give away frameworks others can use immediately
Common mistakes:
- Writing for peers instead of customers (founder echo chamber)
- Posting generic startup advice instead of specific, earned insights
- Treating both platforms identically (different audiences, different formats)
- Optimizing for impressions instead of inbound conversations
- Abandoning after 2 weeks because "nothing happened" — compound effects take 90+ days
Related Skills
social-content — for ongoing social media content beyond founder personal brandcontent-strategy — for broader content planning across blog, SEO, and channelslanding-page — to convert audience attention into signups or leads
Examples
Prompt: "I'm a technical founder building a dev tools startup. Help me build thought leadership on X."
Good output includes: Identifying 2-3 IP territories based on the founder's unique technical insights, drafting 10 posts that establish original frameworks (not generic "startups are hard" content), platform-specific formatting for X (thread structure, hook patterns), and a system for turning daily building into content.
Prompt: "I want to grow my LinkedIn to attract enterprise buyers for our security product."
Good output includes: IP territory around security insights the founder has from building the product, pillar posts that demonstrate expertise to CISOs and security engineers, proof posts showing customer outcomes, and a strategy for engaging in security-focused LinkedIn discussions.
1---2name: founder-thought-leadership3description: When the user wants to build personal brand, thought leadership, or IP as a founder on Twitter/X or LinkedIn. Also use when the user mentions "founder brand", "personal content", "build audience", or "grow my following".4---5
6# Founder Thought Leadership
7
8## When to Use
9- Founder wants to build a personal brand that drives pipeline, recruiting, or fundraising
10- Founder wants to establish IP (intellectual property in ideas, not legal) — original frameworks, contrarian takes, or proprietary insights
11- Founder wants to grow a relevant audience on X or LinkedIn
12- Founder wants to turn founder journey into content (building in public, lessons learned)
13
14## Context Required
15- Founder's area of expertise and unique perspective
16- Target audience (customers, investors, talent, peers)
17- Platform priority (X, LinkedIn, or both)
18- Current following size and engagement baseline
19- Company stage and what they're optimizing for (pipeline, recruiting, fundraising, awareness)
20
21## Workflow
22
231. **Define the founder's IP territory** — identify 2-3 topics where the founder has genuine, earned insight that others don't. These must pass the "why should anyone listen to YOU on this?" test.
242. **Audit existing content** — review the founder's last 20 posts on each platform. Identify what got traction, what fell flat, and what's missing from their voice.
253. **Build the content system** — create a repeatable framework:
26 - **Pillar posts** (1-2/week): original frameworks, data, or contrarian takes that establish IP
27 - **Proof posts** (2-3/week): behind-the-scenes, customer wins, lessons from failure, building in public
28 - **Engagement posts** (daily): replies, quote tweets, threads on others' content
294. **Create the IP library** — document the founder's original frameworks, mental models, and coined terms. These become the building blocks for all content.
305. **Write a 2-week content calendar** — draft actual posts with platform-specific formatting.
316. **Set up the feedback loop** — define which metrics to track (impressions, profile visits, inbound DMs, pipeline attributed to content).
32
33## Output Format
34
35```markdown
36## Founder Thought Leadership Plan
37
38### IP Territory
39- Topic 1: [topic] — why you have authority here
40- Topic 2: [topic] — why you have authority here
41
42### Original Frameworks
43- [Framework name]: [one-line description]
44 - Origin story: [how you discovered/developed this]
45 - Post format: [how to present it]
46
47### Platform Strategy
48**LinkedIn:** [posting cadence, format preference, audience]
49**X/Twitter:** [posting cadence, format preference, audience]
50
51### 2-Week Content Calendar
52| Day | Platform | Type | Topic | Hook |
53|-----|----------|------|-------|------|
54| Mon | LinkedIn | Pillar | ... | ... |
55| Tue | X | Proof | ... | ... |
56| ... | ... | ... | ... | ... |
57
58### Metrics to Track
59- [metric]: [current baseline] → [30-day target]
60```
61
62## Frameworks & Best Practices
63
64**The IP Test:** A post builds IP if people screenshot it, reference your framework by name, or tag you when the topic comes up. If none of that happens, it's content — not IP.
65
66**Platform differences:**
67- **LinkedIn:** longer-form, professional framing, storytelling, carousels perform well. Algorithm rewards comments over likes. Post early morning (7-8am local).
68- **X/Twitter:** shorter, punchier, thread format for depth. Algorithm rewards replies and quote tweets. Contrarian takes travel further. Consistency matters more than timing.
69
70**Building in public works when:**
71- You share specific numbers (revenue, users, churn), not vague "we're growing"
72- You share failures and what you learned, not just wins
73- You give away frameworks others can use immediately
74
75**Common mistakes:**
76- Writing for peers instead of customers (founder echo chamber)
77- Posting generic startup advice instead of specific, earned insights
78- Treating both platforms identically (different audiences, different formats)
79- Optimizing for impressions instead of inbound conversations
80- Abandoning after 2 weeks because "nothing happened" — compound effects take 90+ days
81
82## Related Skills
83- `social-content` — for ongoing social media content beyond founder personal brand
84- `content-strategy` — for broader content planning across blog, SEO, and channels
85- `landing-page` — to convert audience attention into signups or leads
86
87## Examples
88
89**Prompt:** "I'm a technical founder building a dev tools startup. Help me build thought leadership on X."
90
91**Good output includes:** Identifying 2-3 IP territories based on the founder's unique technical insights, drafting 10 posts that establish original frameworks (not generic "startups are hard" content), platform-specific formatting for X (thread structure, hook patterns), and a system for turning daily building into content.
92
93**Prompt:** "I want to grow my LinkedIn to attract enterprise buyers for our security product."
94
95**Good output includes:** IP territory around security insights the founder has from building the product, pillar posts that demonstrate expertise to CISOs and security engineers, proof posts showing customer outcomes, and a strategy for engaging in security-focused LinkedIn discussions.
yanacuti1121