Ten weeks before a Series C close, a CTO walked the reviewer through the people slide. Three senior engineers, all critical to the platform, all named as the team's strongest performers. The reviewer asked one quiet question: when did each of them join? The dates came back within four months of each other. All three had been brought in together when their previous company was acquired three years and eight months ago.
The reviewer pulled up the cap table. All three were on a standard four-year stock vesting schedule. All three would be fully vested within four months of close. There was no refresh history. The CEO had been planning to "have the conversation" once the round closed.
The deal still happened, but with a retention pool carved out of founder equity, a key-person clause naming all three, and a quarterly attrition check-in for the first eighteen months post-close.
A team's retention story is told by the calendar of its vesting schedule, not by the founder's confidence in it.
The lens
Investors don't buy a roster. They buy predictable execution through founder transition, the next eighty hires, the integration period, the first regulated customer that demands a named CISO. The team in the room during diligence is not the team that will deliver the next two years of the plan. The diligence question is whether the company can absorb turnover without losing momentum, and whether the founder has built the system, at the executive layer and beneath it, to make that true.
What to look for, and what each answer signals
Investors ask for the critical-role map. Eight to twelve roles by business impact, primary and deputy named for each, with a date showing the last real knowledge-transfer activity. A clean map with active deputies is a strong signal. Empty deputy cells are mediocre but honest. Critical roles missing from the map entirely is worse than empty cells: the gap nobody named is the one most likely to surface during integration. The worst signal of all is a map full of named deputies who have never done anything deputy-shaped. A deputy who has never shadowed an incident, paired on-call, or authored a runbook is not a deputy.
Investors pull the vesting roll-up. Top twenty employees, count how many are within twelve months of full vesting, and review refresh-grant history for the last twenty-four months. Vest completions clustered near the transaction date are a planning failure. Refresh-grants that appear only in the months before close are worse: they read as a panic, not a practice. The cleanest pattern is steady, performance-linked refreshes that started long before any deal was on the table.
Investors test the onboarding metrics. Time to first merged PR. Time to first on-call shift. Time to leading a feature end-to-end. The numbers themselves matter less than whether they are tracked at all. A team that can produce them has built knowledge transfer as a system. A team that cannot is running on heroics.
Investors read how the CEO uses the executive team. Look at the last ten cross-functional decisions of meaningful size: pricing changes, senior hires, vendor choices, roadmap shifts. Who actually made them? If the CEO's name appears on most of the list, the C-level is performing roles, not occupying them. A useful follow-up is to ask each C-level executive what they decide without involving the CEO for a check. The pause before the answer is the signal. This matters because a CEO who doesn't fully trust the executive team has no executive bench to fall back on when scale, attrition, or a regulated customer demands one. The org chart says one thing. The decision log says another. The decision log is what matters.
How it shows up in the deal
At Seed and Series A, awareness is enough: a founder who can name the two hardest-to-lose people and what they would do about it. By Series B and growth, succession is expected to be a managed function with quarterly reviews, named active deputies, and onboarding metrics that get reported. In control buyouts, buyers sample the artifacts. They interview the named deputy without the primary in the room, run the vesting roll-up themselves, and price the synergy case against what the team can deliver after close, not against the org chart on the day of signing.
Toolkit investors deploy
Investors have a small set of mechanics for pricing people risk into the deal rather than passing on it. A retention pool, sized to bridge the period when existing equity loses its retention pressure and funded out of founder equity, keeps named individuals in place through a transition. A key-person clause identifies the individuals whose departure within a defined window post-close triggers protections: escrow release, earn-out adjustment, or deployment of the retention pool. Double-trigger acceleration keeps key employees at their desks through the integration window, since their unvested equity accelerates only if a change of control is followed by termination without cause. The acquirer's incentive is to keep them, because firing them triggers the payout. The seller gets the retention they wanted without paying for it directly, and the employee gets downside protection against being discarded the day after close.
These mechanics work best when the underlying succession practice is sound and the instruments are bridging a real transition. They work badly as substitutes for a bus factor of one. How the founder engages with the conversation is itself diagnostic. Founders who have thought about retention in advance arrive with structures that fit. Those hearing about double-trigger acceleration for the first time across the negotiating table are telling you, indirectly, what their internal retention practice has looked like.
Red flags
- Critical-role definitions that exist only in the founder's head, or a role map with most deputy cells empty.
- Deputies named on paper who have never shadowed an incident, paired on-call, or authored a runbook for the system they are supposed to back up.
- Multiple senior employees fully vested in the same window, with no refresh history predating the deal conversation.
- C-level executives who describe themselves as "helping the CEO think through" their domain rather than owning it. In reference calls, the pattern is hard to hide.
- Senior employees who have raised compensation concerns in the last six months without resolution.
Two or more of these usually produce a price adjustment or a remediation condition. Three or more, and the question becomes whether the team will hold together long enough to deliver the plan.
Mini-glossary
- Deputy: A named successor for a critical role who has actively practiced the role's responsibilities. A deputy who has never shadowed an incident or authored a runbook is a deputy in name only.
- Vesting cliff: The initial waiting period before any equity vests. If an employee leaves before the cliff date, they receive nothing.
- Full vesting: The point at which all granted equity has vested and no further equity is contingent on the employee staying. The retention pressure created by unvested equity ends at this date.
- Key-person clause: A contractual provision that triggers protections (escrow release, earn-out adjustment, retention pool deployment) if a named individual leaves within a defined window post-close.
- Double-trigger acceleration: A vesting clause where unvested equity accelerates only if two events occur, typically a change of control followed by termination without cause within a defined window.
Your turn
What people surprise hit you hardest in a deal? A full-vesting cluster nobody noticed until the cap table was on screen, a deputy who turned out to be a deputy in name only, a C-level who turned out to be running the founder's errands, a key engineer who handed in notice the week integration planning started? Share the scar. It helps the next team.
Next in the Playbook
Edition 27 explores the Post-Close 100-Day Tech-Value Plan: how diligence findings convert into a shared roadmap that founders, CTOs, and investors actually execute against. Stay tuned!
Originally published on the Tech Due Diligence Playbook newsletter on LinkedIn.