Founder Thought Leadership

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

1. 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.
2. 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.
3. 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

1. Create the IP library — document the founder's original frameworks, mental models, and coined terms. These become the building blocks for all content.
2. Write a 2-week content calendar — draft actual posts with platform-specific formatting.
3. 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 brand
• content-strategy — for broader content planning across blog, SEO, and channels
• landing-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.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: shawnpang
• Source: shawnpang/startup-founder-skills
• License: MIT

Install and usage instructions live in the source repository linked above.