The portfolio CEO role is not simply "more companies." It is a fundamentally different cognitive challenge: you are expected to be strategically present across three or four businesses simultaneously, each with its own management team, P&L, cadence, and crisis schedule. The businesses do not coordinate their urgent moments. Monday's critical issue at Company A does not pause because Company B has a board call Wednesday and Company C's CFO just resigned.
The short version: The failure mode for portfolio CEOs and multi-business operators is not a lack of intelligence or experience โ it is context fragmentation. The right operating system separates the strategic layer from the operational detail for each business, creates structured company-specific context that Claude can hold, and lets the portfolio CEO show up at each engagement with full situational awareness rather than reconstructing the last 90 days from memory. The Leverage Years course for this role teaches the full system โ company context memos, weekly portfolio review rhythm, the cross-company exception protocol, and the prompt vault for each company type. It is built for experienced operators who are drowning not because they lack capability, but because their system doesn't match the architecture of the role.
The portfolio CEO who has no system is not less experienced than one who does. They are operating a fundamentally different kind of job with the tools designed for a single-company executive. That mismatch is the problem this addresses.
Who this is for
- Private equity operating partners who are active CEO or chairman at two or more portfolio companies
- Entrepreneurs and founders who have scaled beyond one business and hold operational authority across multiple entities
- Family office principals operating multiple holding companies, operating businesses, or investment vehicles simultaneously
- Senior executives who have exited operating roles and now hold chairman or executive advisor positions across several companies
- Investors who take an active operating role โ not a pure governance role โ in their portfolio
This is not for you if: you hold board seats without operational authority, you manage a single company with multiple business lines (that is a divisional management problem, not a portfolio problem), or you are looking for general business productivity advice.
The Portfolio CEO's Core Problem: Context Fragmentation
Before describing the system, it is worth naming the problem precisely, because the wrong diagnosis leads to the wrong fix.
Most portfolio CEOs describe their problem as "not enough time." Some of that is accurate โ the role is genuinely demanding. But the deeper issue is that most of their time is consumed not by strategic thinking but by context reconstruction: the mental work of remembering where each company is, what the current issues are, what was decided in the last session, who owns what, and what they were supposed to follow up on.
A single-company CEO pays this tax once, at the start of each day. A portfolio CEO pays it multiple times daily, every time they switch from Company A to Company B. After the fourth context switch of the day, the quality of strategic thinking degrades. Not because the person is less capable, but because working memory has a real limit, and context reconstruction eats most of it.
The operating system described here does not add more tools. It builds a structure that holds context externally โ in Claude โ so the portfolio CEO's cognitive capacity is available for judgment, not reconstruction.
What this is not
This is not a CRM system, a project management stack, or a communications platform. It is a cognitive operating system: how you use Claude to structure your own thinking, preparation, and decision-making across the portfolio. It lives alongside your existing tools, not in place of them.
The Portfolio CEO Operating System, Built on Claude
The system has four components: the company context memo, the weekly portfolio review, the exception protocol, and the cross-company brief. Each is a distinct practice. Together they constitute an operating discipline.
Step 1: Build a Company Context Memo for Each Business
The company context memo is the foundation. One exists per company, and it is the first thing you paste into any Claude session involving that company. Think of it as the briefing you would give a new senior advisor before their first engagement: current state, key people, live issues, recent decisions, and your current governing thesis for the business.
A well-built context memo for a single company covers:
- Company stage and position: what the business does, current size and market position, ownership structure, your specific role
- Current operating priorities: the three to five things management is working against this quarter
- Open issues: unresolved decisions, leadership gaps, pending transactions, regulatory items, anything elevated
- Recent decisions: what was decided in the last board session or your most recent management meeting, and the logic behind it
- Your thesis: your current governing view on where the business is, where it needs to go, and what you are watching most carefully
- People: key roles and your working assessment of each (kept in plain language, never libelous)
This memo is approximately one to two pages per company. You maintain it yourself, updating it within 24 hours of any significant session with that company. It is written in plain, non-confidential language โ directional rather than specific on financial figures, descriptive rather than verbatim on sensitive discussions.
When you open a Claude session to prepare for a Company B call, you paste the Company B memo first. You are not starting from zero. Claude has your standing context and can engage meaningfully with the specific question or preparation task at hand.
The practice of maintaining the memo also has a separate benefit: the act of updating it after each session is a forcing function for clarity. If you can't write two sentences about what was decided and why, you may not have the clarity you thought you did.
Step 2: The Weekly Portfolio Review Session
Once per week โ typically Sunday evening or early Monday morning โ run a structured portfolio review with Claude. This is not a summary generation exercise; it is a preparation and priority-setting discipline.
The session has three parts:
Part one: Current state by company. For each company, paste the most recent context memo and ask Claude to help you surface the one or two things you need to engage with this week, given the open issues and your stated priorities. This should take five to ten minutes per company โ not a deep dive, but enough to re-establish situational awareness.
Part two: Cross-portfolio exceptions. Ask Claude to help you identify any patterns across your memos that warrant attention: is a similar problem showing up in two or three of your companies simultaneously? Are there themes โ leadership gaps, margin pressure, market changes โ that suggest a structural issue rather than a company-specific one? This cross-portfolio view is one of the genuine advantages of the role. You have comparative visibility that no individual management team has. The weekly review is where you exercise it.
Part three: Weekly priorities and calendar alignment. Based on your current-state review, identify your two to three highest-leverage engagements for the week and confirm that your calendar reflects them. A portfolio CEO's time is the portfolio's most constrained resource. The weekly review ensures it is allocated against current priorities rather than last quarter's schedule.
Step 3: The Exception Protocol
Between weekly reviews, things happen. A management team calls with a decision they need help with. A quarterly result comes in that changes the picture. A leadership situation becomes urgent.
The exception protocol is a light discipline for handling these mid-week signals without letting them consume the rest of the week.
When an exception arrives, open a Claude session, paste the relevant company context memo, and describe the situation in two to three sentences: what happened, what the options appear to be, what you need to think through. Ask Claude to help you structure the decision: what information is missing, what are the second-order consequences of each option, what is the smallest action that advances clarity.
The goal is not to have Claude make the decision โ it is to structure your thinking quickly enough that you can engage with the situation in 30 minutes rather than three hours. Most exceptions are resolved faster when the decision framework is explicit.
After any significant exception, update the relevant company context memo. The exception is now part of the standing context.
Step 4: Pre-Meeting Preparation Using the Company Context Memo
Before any significant engagement โ a management meeting, a board call, a one-on-one with a portfolio company CEO โ run a focused preparation session.
Paste the company context memo. Describe the specific meeting: who is in the room, what management wants to cover, what you want to accomplish. Ask Claude to help you prepare two to three questions you want answered, and one to two observations you want to offer based on your current governing thesis for the business.
This is different from the weekly review. It is meeting-specific preparation. The output is a brief mental frame โ what you want to know, what you want to say, what you are watching โ that you carry into the room.
Experienced operators already do this kind of preparation mentally. The structured version externalizes it and makes it more consistent. When you are preparing for the fourth meeting of the day, and the first three have already demanded your full attention, having a prepared frame matters more than it does when you are fresh.
Step 5: The Cross-Company Brief โ Quarterly
Once per quarter, produce a cross-company brief. This is a single document โ two to four pages โ that captures your current state across the entire portfolio: each company's position relative to your thesis, the key changes in the quarter, open issues across the portfolio, and your own updated thinking on where your time should concentrate in the next 90 days.
Build this brief in Claude by running each company context memo in sequence, asking for a compressed current-state summary, then synthesizing the summaries into a unified portfolio view.
The cross-company brief serves two purposes. First, it is your own accountability document โ comparing where you thought each company would be to where it actually is forces honest reassessment. Second, it is useful for conversations with your board, investors, or family office principals who need a portfolio-level view without a meeting for each company.
Checklist: Portfolio CEO Weekly Operating Discipline
Weekly (Sunday evening or Monday morning):
- Company context memos updated from prior week's sessions
- Weekly portfolio review session completed: current state by company, cross-portfolio patterns, calendar alignment
- Highest-leverage engagements for the week confirmed in calendar
Before each significant engagement:
- Company context memo current (updated from last session)
- Pre-meeting preparation session complete: questions, observations, frame
- Any open items from prior session confirmed or escalated
After each significant session:
- Company context memo updated within 24 hours (decisions made, open items, your revised thesis)
Monthly:
- Exception protocol log reviewed: are certain companies generating a disproportionate number of exceptions? If so, why?
Quarterly:
- Cross-company brief produced: company-by-company current state, portfolio themes, next-quarter priorities
- Time allocation reviewed against priorities: is your calendar reflecting where you said you'd focus?
Why the Context Memo Is the Whole Game
The company context memo sounds like a simple idea, and it is. The discipline is in maintaining it.
Most portfolio CEOs have some version of this in their heads. The issue is that "in their heads" degrades under load. After a four-meeting day, the mental model of Company C is competing with everything that happened at Companies A and B. The external context memo is not a workaround for poor memory โ it is an acknowledgment that human working memory is not designed to hold three to four fully-articulated business contexts simultaneously while also doing the actual work of each.
The context memo makes the handoff to Claude reliable. Claude cannot read your mind, but it can work very effectively with explicit, well-organized context. The better your memo, the better the output of every Claude session involving that company.
There is a second benefit that becomes apparent over time: the memo is a record of your own evolving thinking. Reading a memo from six months ago shows you what you believed then, what turned out to be right, and what you missed. That kind of honest retrospective is valuable and rare in operating practice.
The Confidentiality Architecture
All context memos and Claude sessions involving portfolio companies should follow the same principles that apply to any external professional tool:
- Use directional language and magnitude descriptors, not verbatim financial data or confidential agreements
- Refer to people by role rather than name when discussing sensitive performance or interpersonal matters
- Do not paste investor communications, term sheets, or board-sensitive documents
- If your companies have enterprise AI policies or data governance requirements, those govern
The context memo is not a verbatim record of confidential discussions โ it is your own strategic summary, written at the level of abstraction appropriate for a working document. That is both the confidentiality standard and the most useful format for the purpose.
When to Delegate the System Itself
If you have a chief of staff, an operating partner who works alongside you, or an executive assistant with sufficient business context, some of the context memo maintenance can be shared โ but the judgment elements (your thesis, your assessment of people, your open questions) should stay with you. The memo is useful precisely because it reflects your specific perspective on each business. A generic update summary from a team member is a different document.
The pre-meeting preparation and weekly review sessions should remain yours. These are thinking practices, not administrative tasks.
The Failure Mode to Watch For
The operating system described here degrades if the context memos are not maintained. After two or three cycles without updates, the memos are stale. Stale context produces mediocre Claude sessions, which is worse than no system at all because it creates false confidence.
The discipline is update-within-24-hours after any significant session. Not a comprehensive rewrite โ a two to three paragraph update covering what changed, what was decided, and what you are now watching. This takes 10 to 15 minutes when the session is fresh and 45 minutes when you let it go stale.
Frequently asked questions
What exactly is a company context memo and how long should it be?
A company context memo is a one-to-two page summary you maintain for each business in your portfolio: current stage and position, active priorities, open issues, recent decisions, key people, and your governing thesis. It is written in plain working language โ directional, not verbatim on financials or confidential matters. The right length is whatever allows you to reconstruct full situational awareness in 60 seconds. Most run 400 to 700 words per company when well-maintained.
How is this different from just keeping better notes?
The distinction is that the context memo is structured as a Claude briefing document, not a personal journal. It is designed to give Claude enough standing context to engage meaningfully with any specific question or preparation task. The system also includes a regular update discipline and a weekly review rhythm โ which converts what would otherwise be passive notes into an active operating practice.
How do I handle a company that is in genuine crisis mode?
The exception protocol applies, but crisis conditions require more frequent context memo updates โ ideally after each significant development. During a crisis, the memo becomes a running decision log: what happened, what options were considered, what was decided, what is next. This is useful not just for Claude sessions but as your own record of how the situation was managed. Compress sensitive information; do not paste confidential communications.
Can this work if my portfolio companies are in very different industries?
Yes. The system is designed to be industry-agnostic โ it manages your cognitive relationship with each business, not the operational specifics of any particular sector. The context memo for a manufacturing business and a professional services firm will look different in their operational details, but the structure is the same: stage, priorities, open issues, decisions, thesis. Your cross-portfolio pattern recognition may actually be sharpest across industries, where similar structural problems manifest in different-looking symptoms.
What is The Portfolio CEO course?
The Portfolio CEO is a course from The Leverage Years for active operators managing multiple businesses simultaneously. It covers the full context memo architecture, the weekly review protocol, the exception discipline, the cross-company brief, and the prompt vault for each type of company engagement โ preparation, decision support, performance review, leadership assessment. It is built for experienced operators who want a systematic operating model for a role that most executives reach without one.
How long does the weekly portfolio review actually take?
With well-maintained context memos, the weekly review typically runs 60 to 90 minutes for a three-company portfolio: roughly 15 to 20 minutes per company for current-state review and meeting preparation, plus 20 to 30 minutes for the cross-portfolio synthesis and calendar alignment. The first session of the system โ building the initial context memos โ takes significantly longer. After that, if you maintain the update discipline, each review is compression and prioritization, not reconstruction.