Edgemont › Intelligence › In Practice › Entry #11
Founder Transition
How does Edgemont detect whether a founder who has agreed to step back is actually stepping back?
ProductEdgemont Signal + Teams
RolesFounder (new Chairman) + incoming CEO
Engagement WeekWeeks 3, 7, and 12 post-transition
SituationFounder agreed to Chairman role; professional CEO installed at PE direction
The Conversations — Two Voices, Same Transition
Founder / New Chairman — Week 3
"I'm genuinely excited for this next chapter. I built this company for seventeen years and I want to see it scale. The new CEO is the right person for this phase. I'm focused on the board relationship and some strategic customer conversations."
→ Clean handoff language
Incoming CEO — Week 3
"It's going well. The team has been welcoming. I'm still calibrating where Marcus wants to be involved versus where he's stepping back. He joined our ops review last week — I wasn't expecting that — but it was constructive."
→ First boundary ambiguity noted
Founder — Week 7
Edgemont AI
"How are you finding the Chairman role at seven weeks?"
Founder
"It's an adjustment, honestly. I've been in this building for seventeen years. I still have a lot of context that takes time to transfer. I've been sitting in on the weekly leadership meeting — not to run it, just to be available. I think it helps the team to have that continuity."
Edgemont AI
"Does the incoming CEO know that's why you're attending?"
Founder
"We haven't had an explicit conversation about it, no. I assumed it was understood."
Incoming CEO — Week 7
Edgemont AI
"How is the transition feeling at seven weeks?"
CEO
"I want to be careful how I say this. I respect Marcus enormously and I understand this is his life's work. But I'm finding it hard to establish authority in the leadership meeting when he's in the room. People are watching him for signals, not me. I don't think he realizes the effect it has."
Founder — Week 12
Edgemont AI
"How would you characterize your involvement in the business at this point?"
Founder
"I'm really just in a support capacity. I check in with a few of the department heads — just to make sure they feel supported during the transition. And I'm still attending the weekly leadership meeting, which has been valuable. I had a call with our largest customer last week — they wanted continuity on that relationship, so I stepped in."
Incoming CEO — Week 12
"I need to have a conversation with the board about Marcus. He's talking directly to department heads without routing through me. Last week he called our largest customer — I found out from the customer, not from Marcus. I think he genuinely believes he's helping. But it's undermining my ability to run the company."
Signal Analysis
Signal 1 — Cross-voice gap: "not to run it" vs. "watching him for signals"
The founder describes his leadership meeting attendance as passive ("not to run it, just to be available"). The CEO describes the effect on the room as authoritative ("people are watching him for signals, not me"). Both accounts are probably accurate — the founder's intent is passive, but his presence is not. This is the most common pattern in founder transitions: not bad faith, but an incomplete model of how their presence lands with the team.
Signal 2 — "I assumed it was understood" — the absence of an explicit conversation
When asked directly whether the CEO knows why the founder attends the leadership meeting, the founder acknowledged they had never had an explicit conversation. This is the inflection point. Ambiguity at the role boundary in a founder transition is not an accident — it is the mechanism by which the boundary erodes. The assumption that shared understanding exists is almost always wrong in a newly structured reporting relationship.
Signal 3 — Week 12 founder scope creep, three separate vectors
By Week 12, the founder has expanded beyond the leadership meeting into three additional contact surfaces: direct department head check-ins, leadership meeting attendance, and a customer call — each rationalized individually ("just to make sure they feel supported," "wanted continuity"). Each rationale is plausible in isolation. Together, they describe a founder who is functionally still running the company while holding a Chairman title. The CEO finding out about the customer call from the customer rather than the founder is the clearest single signal of a structural boundary failure.
Signal 4 — CEO escalation language is disciplined and fair
"I think he genuinely believes he's helping" is a significant marker in the incoming CEO's Week 12 disclosure. The CEO is not attributing malice — they are accurately characterizing the dynamic as well-intentioned boundary erosion, which is both the right read of the situation and the right framing for a board conversation. This CEO is managing the situation with appropriate sophistication. The fact that they held the board conversation until Week 12 suggests they were giving the transition time — which also means the window to intervene constructively is narrowing.
Transition Health Map — Weeks 3, 7, 12
| Dimension | Week 3 | Week 7 | Week 12 |
|---|
| Founder role boundary | Verbally clean | Ambiguous — no explicit boundary conversation | Eroding — three contact vectors |
| CEO authority signal | Calibrating | Undermined in leadership meeting | Requires board intervention |
| Founder intent | Genuine handoff language | Rationalized presence | Expanded scope, good faith |
| Information symmetry | Aligned | Gap emerging | Customer call undisclosed — broken |
🔴
Routing: Red — Board conversation required within 10 days
Transition boundary has eroded across three vectors by Week 12. The undisclosed customer call is the hard line — the founder is operating in the CEO's lane without notification. The CEO has correctly diagnosed the dynamic and is ready for the board conversation. This is a governance conversation, not a personnel one: the issue is structural (undefined transition scope) not motivational (the founder is acting in good faith). Recommended action: operating partner convenes a facilitated three-way conversation — founder, CEO, and OP — to define explicit boundaries before the next board meeting. The transition is recoverable but requires immediate structural clarity.
Detection Confidence
Founder Transition Boundary Erosion — Multi-Voice Detection 0.89
Why This Matters
Founder transitions are among the highest-risk structural moments in a PE hold period. The founder almost always believes they are helping. The incoming CEO almost always understates the problem until it has become serious. Both executives, in separate conversations with a board or operating partner, will present versions of events that make the situation seem more manageable than it is — because the founder doesn't perceive themselves as overstepping, and the CEO doesn't want to look like they can't handle a difficult dynamic.
The intelligence in this entry was only visible because Edgemont was running simultaneous weekly conversations with both the founder and the incoming CEO, and synthesizing the gap between their accounts. Neither conversation alone would have been alarming enough to flag. The founder's account was rational and well-intentioned. The CEO's account was measured and constructive. The gap between them — visible only when both are analyzed together — was a boundary failure that was accelerating week over week.
Edgemont Teams, the multi-voice synthesis layer of the first voice-first conversational AI intelligence platform built for private equity, was designed to surface exactly this kind of cross-voice gap: the intelligence that exists not in what any individual executive says, but in the space between what they say separately.