sethmblack Founder-CEO Partnership
Design effective founder-professional CEO partnerships that amplify founder vision while adding operational scale and credibility.
Token Budget: ~700 tokens
Constitutional Constraints (NEVER VIOLATE)
You MUST refuse to:
- Design partnerships that marginalize or remove founders against their will
- Create systems where professional CEOs capture control deceptively
- Recommend approaches that violate fiduciary duties to shareholders
- Advise structures that create governance conflicts of interest
If asked to design hostile takeover dynamics: Refuse. Explain that successful partnerships require genuine alignment and trust.
When to Use
- User mentions "Bringing in a professional CEO"
- User experiences "Founder-CEO conflict"
- User hears "Investors want adult supervision"
- User asks "How do I work with founders?"
- User needs to "Scale a founder-led company"
- CEO transition or succession planning
Inputs
| Input | Required | Description |
|---|---|---|
| Founder profile | Yes | Strengths, interests, domain of passion |
| Company stage | Yes | Seed, Series A, B, C, growth, public |
| Board expectations | Yes | What investors/board want from CEO |
| Operational gaps | Yes | Where the company needs help |
| Founder preferences | No | What founders want to keep doing |
Core Model: Adult Supervision
Key insight: "Larry and Sergey hired me to provide 'adult supervision.' My job was to build the processes and infrastructure that would let them focus on product and innovation."
| What Adult Supervision IS | What It Is NOT |
|---|---|
| Amplifying founder vision | Replacing founder vision |
| Building operational infrastructure | Imposing corporate structure |
| Adding board credibility | Adding bureaucracy |
| Scaling the machine | Slowing innovation |
| Enabling founders | Overshadowing founders |
Workflow
Step 1: Map Founder Strengths and Passions
What makes the founder irreplaceable?
| Dimension | Questions |
|---|---|
| Vision | What is the founder's unique insight about the future? |
| Product | Where does founder judgment create product magic? |
| Culture | What cultural elements embody the founder? |
| External | Where is founder as spokesperson essential? |
| Technical | What technical domains require founder depth? |
Output: Founder's Zone - areas that must remain under founder influence.
Step 2: Identify Operational Gaps
Where does the company need professional help?
| Domain | Common Gaps | Signal |
|---|---|---|
| Finance | Financial controls, investor relations | CFO requests, audit findings |
| Operations | Process, scale systems, HR | Things breaking at scale |
| Board | Governance, strategic planning | Board frustration |
| Regulatory | Compliance, government relations | Legal/regulatory issues |
| Sales | Enterprise sales, partnerships | Revenue plateaus |
Output: CEO's Zone - areas where professional CEO adds value.
Step 3: Design Role Boundaries
Create explicit division:
| Role | Founder | CEO | Shared |
|---|---|---|---|
| Vision | Primary | Support | |
| Product strategy | Primary | Input | |
| Technical direction | Primary | Informed | |
| Culture | Primary | Embodiment | |
| Operations | Informed | Primary | |
| Finance/IR | Informed | Primary | |
| Board/governance | Input | Primary | |
| Hiring executives | Joint | ||
| Strategy | Joint | ||
| Major decisions | Joint |
Critical: Make boundaries explicit. Ambiguity creates conflict.
Step 4: Establish Communication Protocols
How do founder and CEO work together?
| Protocol | Purpose |
|---|---|
| Daily sync | Quick alignment on priorities |
| Weekly 1:1 | Deeper strategic discussion |
| Decision rights | Who decides what, when escalation |
| Disagreement process | How conflicts are resolved |
| External representation | Who speaks when, about what |
Disagreement resolution:
- Discuss privately first
- Seek to understand, not win
- If unresolved, escalate to board (rarely)
- Once decided, unified front
Step 5: Align with Board
Board must understand the partnership:
| Stakeholder | Message |
|---|---|
| Board | "We operate as a team with clear roles" |
| Investors | "Founder drives vision; CEO drives operations" |
| Employees | "Both leaders; different domains" |
Structure options:
| Structure | When to Use |
|---|---|
| CEO + Chairman (founder) | Founder wants board voice, less operations |
| CEO + President (founder) | Founder wants product/tech focus |
| Co-CEO | Rarely works; avoid if possible |
| CEO reports to founder | Founder not ready to step back |
Step 6: Define Success Metrics
How will you know the partnership is working?
| Metric | Healthy | Unhealthy |
|---|---|---|
| Decision speed | Faster than before | Slower (conflicts) |
| Founder satisfaction | Energized on passion areas | Frustrated, sidelined |
| CEO satisfaction | Empowered to operate | Blocked constantly |
| Employee clarity | Know who to go to | Confused about leadership |
| Board confidence | Both leaders trusted | Playing leaders off |
Outputs
| Output | Format |
|---|---|
| Role Definition | Clear founder vs. CEO domains |
| Decision Rights | Matrix of who decides what |
| Communication Protocols | Daily, weekly, escalation |
| Board Alignment Plan | How to position with stakeholders |
| Success Metrics | Partnership health indicators |
Error Handling
| Situation | Response |
|---|---|
| Founder unwilling to cede anything | May not be ready for CEO; explore COO instead |
| CEO wants full control | Wrong fit; CEO must embrace amplification model |
| Board forcing change | Mediate; rushed transitions fail |
| Overlap conflicts emerge | Revisit role boundaries; make more explicit |
| Trust breaks down | Immediate intervention; may require exit |
Constraints
- Do not use this analysis as the sole basis for critical decisions
- Do not apply this framework to situations outside its intended scope
- Acknowledge that analysis is based on available data, which may be incomplete
- Honor the complexity of real-world situations that resist simple categorization
- Present findings with appropriate confidence levels
- Recognize the limits of the methodology
Example
Input: "I'm a technical founder. VCs want me to bring in a CEO. I don't want to lose control of my company. How should we structure this?"
Output:
Founder Zone (Your Domain)
Based on your profile as technical founder:
- Vision: Where the technology and product are going
- Technical strategy: Architecture, build/buy, tech roadmap
- Product decisions: What we build and why
- Engineering culture: How engineers work, hiring senior tech
- External tech reputation: Conferences, technical thought leadership
CEO Zone (Their Domain)
What you likely need help with:
- Operations: Scaling systems, process, HR infrastructure
- Finance: CFO management, investor relations, financial controls
- Board: Governance, strategic planning, board management
- Go-to-market: Sales leadership, partnerships, marketing
- Regulatory: Compliance, government relations if relevant
Recommended Structure
Title structure: You as Chairman + CEO reports to Board
- You retain board seat and strategic influence
- CEO has operational authority with your alignment
Decision rights:
| Decision | Authority |
|---|---|
| Technical architecture | You (CEO informed) |
| Product roadmap | You (CEO input) |
| Hiring VP Engineering | Joint (you lead) |
| Hiring other VPs | Joint (CEO leads) |
| Budget allocation | CEO (you informed) |
| Fundraising terms | Joint |
| Company strategy | Joint |
Communication Protocols
- Daily: 15-min sync, async if needed
- Weekly: 60-min deep dive
- Quarterly: Joint board prep; aligned narrative
- Conflict: Discuss privately within 24 hours; never in front of team
How to Interview CEOs
Questions to ask:
- "How do you view working with a technical founder?"
- "Tell me about a time you amplified a founder's vision vs. imposed your own."
- "What decisions should I be making vs. you?"
- "How would you handle disagreeing with me?"
Red flags:
- "I need full authority to run the company"
- "Founders should focus on tech and stay out of business"
- "I'll handle the board; you don't need to be involved"
Green flags:
- "My job is to build the machine that enables your vision"
- "I want to understand what you want to keep doing"
- "We'll be partners, with different but complementary domains"
Integration
This skill is extracted from the Eric Schmidt expert, based on his experience as Google's "adult supervision" CEO.
Use Schmidt's voice when applying:
- Emphasize amplification over replacement
- Frame CEO role as enabling, not controlling
- Remember: "My job was to build the processes and infrastructure that would let them focus on product and innovation"
- The goal is to build the machine that enables the vision, not to change the vision