# The Acquired-Startup Talent Window: Deal Close to a Tiered, Timed Slate

*Turn one acquisition announcement into a ranked slate where every pre-close employee has a retention tier, a cleared status, and a dated first touch, in two working days.*

- Canonical URL: https://www.refolk.ai/guides/acquired-startup-talent-window
- Pillar: Recruiting and sourcing
- Format: Playbook
- Published: 2026-11-18
- Last reviewed: 2026-11-18
- Reading time: 22 min
- Keywords: how to recruit employees from an acquired startup, when to reach out to candidates after an acquisition, acquisition retention bonus timing recruiting, sourcing talent after a company is acquired, acqui-hire employees leaving first year

## Key takeaways

- In a Census study of 4,000 US startup acquisitions, 33% of acquired employees left within a year, compared with 12% of similar regular hires.
- Top earners at acquired startups reverse the pattern: their extra departures don't show up until two years after the acquisition, so founders and executives belong in a later outreach window than the broad team.
- Only 19% of acquirers extend retention agreements to more than a fifth of salaried staff, so the uncovered middle and broad base are usually the first people available to hire.
- Base every outreach window on the close date, not the announcement, and note that SEC 8-K Item 2.01 only dates deals above 20% significance, so most startup deals have to be dated from Companies House filings or GitHub transfer redirects.
- Anyone likely to be on a single one-year retention package should get a first-touch date of close plus 12 months, the month-thirteen cliff.
- Clear every name in order: your own client contracts first, deal-stage non-solicits second, jurisdiction last, because a non-solicit that is void in California still leaves your client relationships in force.

A startup in your hiring space has just been bought. Its people won't all be reachable at the same time, and some of them you shouldn't approach at all. This playbook is for in-house recruiters, sourcers, talent leaders, and founders who do their own hiring. It turns one announced acquisition into a ranked slate in about two working days. Every name on the slate ends up with a retention tier, a dated first-touch window, and a cleared or suppressed status with the reason logged.

## When do employees of an acquired startup leave?

Employees of an acquired startup leave much faster than comparable hires, and most of them go in the first year. The most senior people are the exception: they tend to stay until year two, so the same deal produces several different windows depending on who you want.

The best evidence is J. Daniel Kim's study of US Census employer-employee data, "Predictable Exodus", published in *Strategy Science* in 2024. It covers 4,000 high-tech startup acquisitions between 1990 and 2011, which moved 350,000 startup employees into new companies.

| Metric | Acquired staff | Matched regular hires | Gap |
|---|---|---|---|
| Left in year 1 | 33% | 12% | 2.75x |
| Stayed past year 1 | 67% | 88% | 21 pts |
| Departure over 3 years | 15% more likely | Baseline | n/a |

The multiple and the gap are my own arithmetic on Kim's figures. The versions of the paper differ slightly: one working version gives one-year retention of 66% against 34%. Every version points the same way, and the gap is roughly the same size.

**33% - Acquired startup employees who left within their first year**

Against 12% of regular hires with similar skills and experience, across 4,000 US startup acquisitions in Kim's Census study.

Three findings shape everything that follows:

- **Departures peak in year one and fall every year after.** In the Census version, the overall exit rate is highest in the first year and declines steadily from there. For the broad team, earlier is better.
- **Top earners reverse the pattern.** Kim finds that the extra departures among top earners don't appear until two years after the acquisition. He links this to the one-year vesting cliff: people forfeit unvested equity if they leave early, so senior people wait it out.
- **Rank predicts exit.** Ng and Stuart (2022) find that turnover among acquired employees rises with job rank, and only 63% of acquired CEOs stay into their second year. Founders and executives are a high-yield tier, but a late one.

The evidence has gaps. Kim's figures are annual, so the quarter in which departures peak isn't publicly established. No published source compares reply or move rates for outreach sent after an announcement with outreach sent after a bonus pays out. Every window in this guide is inferred from departure and bonus data, not from a measured response curve. Log your own reply rates by tier and window so you build that evidence yourself.

## How to date the close, not the announcement

Every window on the slate is counted from the close date, and the close is usually not the day the deal made the news. Retention payouts are typically scheduled after close, so a slate built from the announcement date will be off by however long the regulatory review took.

A deal has two dates. Signing is when the parties agree to the deal. Close, also called consummation, is when ownership actually transfers. For a US public acquirer, each date has its own SEC filing: an 8-K Item 1.01 at signing and an Item 2.01 at close.

| Signal | Statutory lag | Coverage limit |
|---|---|---|
| 8-K Item 2.01 | 4 business days after close | US public acquirer, deal above 20% significance |
| 8-K Item 9.01 financials | 71 more calendar days | Same as Item 2.01 |
| Companies House AP01/TM01 | 14 days | UK entities |
| GitHub repo transfer | Redirect at transfer | Public repos only |

Item 2.01 is only required above 20% significance, meaning the target is large relative to the acquirer. Most startup acqui-hires fall below that line. An acqui-hire is a deal done mainly to get the team rather than the product. For most of your targets, then, no SEC filing will hand you the close date, and you'll date it from registry filings and GitHub instead.

At Companies House, director appointments (form AP01) and terminations (form TM01) must be filed within 14 days. The same deadline applies to changes in persons with significant control (PSC), the register of who controls the company. If a founder resigns as a director of the target's UK entity a week after the press release, that's a strong sign the deal has closed.

#### Dating the close, strongest source first

1. **SEC filing** - Item 2.01 dates the close within 4 business days, but only above 20% significance
2. **Registry filing** - Companies House director and PSC changes land within 14 days for UK entities
3. **GitHub transfer** - The redirect from the old org to the acquirer's org dates the move for public repos
4. **Press and profiles** - Item 8.01, the press release, and employer updates bracket a range, labelled estimated

*Use the strongest dating source available and drop to the next only when it doesn't exist, writing down which one you used.*

Two weaker signals can narrow the range but can't set the date on their own. Practitioners report that LinkedIn employer updates often show up before the formal press release, but the size of that lead isn't verified. Careers-page redirects and email-domain migrations also happen around close, and their timing isn't publicly established either. Use them to bracket a range, never to fix a date.

Done looks like a close date with its source cited, or a date labelled "estimated" with the method beside it, for example "estimated: earliest director change at Companies House, less up to 14 days". Budget one to two hours.

## How to rebuild the pre-close roster

The pre-close roster lists everyone who worked at the target before the deal closed, with role, seniority, and start date for each person. Build it from three sources and deduplicate across them, because no single source sees the whole team.

1. **Profiles that list the target as an employer**, current or past. Include people whose profile now shows the acquirer, since many will simply have relabelled.
2. **GitHub org members and committers from before the transfer.** For engineering-heavy targets, commit history is the most complete record of who actually built the product.
3. **Archived careers pages.** Old job listings show which functions existed and when they were being staffed, which helps you spot gaps in the first two sources.

Record the same fields for every person:

- Name and any GitHub handle
- Role and seniority at the target
- Start date at the target
- Current employer label, and the date it changed
- Location, which you'll need for the non-solicit check

Search on employer history and title, not on headline phrases such as "acquired by". A headline keyword only finds the people who chose to write it, which makes it a poor way to rebuild or count a team.

The GitHub side has two traps. When a repository is transferred, GitHub creates a redirect from the old location, and that redirect dates the org move. GitHub only permanently retires the old owner/repo name if the repo had more than 100 clones or Actions uses in the week before the transfer. For quieter repos, the redirect breaks if anyone creates a new repo at the old location. A broken redirect doesn't prove there was no transfer. Take committers by date range from the repo's own history, using the transfer date as the cut-off.

This is the slowest step: four to six hours by hand, mostly spent matching GitHub handles to profiles and profiles to old job titles. [Refolk](/) cuts most of that matching. You ask in plain English for the contributors to a named target's public repos in the year before the transfer, and you get back people with their GitHub, LinkedIn, and open-web footprints already joined.

> **Tip:** Spot the relabel before you count it
>
> When dozens of profiles switch to the acquirer within the same few days, that's a relabel, not an exit. Compare each person's start date at the acquirer with the close date, and keep anyone whose start date matches the close on the roster as a pre-close employee.

Done looks like one deduplicated list where every row has role, seniority, and start date, and any row with a missing field is flagged, not guessed.

## Which retention tier is each person in?

Put each person in one of four retention tiers based on role and seniority. Retention money and equity lock-in are concentrated at the top, so Tier 1 is the most locked in and the least available early. Much of Tier 3 and Tier 4 has no stay bonus at all.

A retention or stay bonus is cash the acquirer promises to people who are still employed on set dates after close. A tranche is one of those scheduled payments, and its payment date is a cliff: leave the day before and you lose the whole amount.

The four tiers:

- **Tier 1:** founders and C-suite.
- **Tier 2:** VPs and key engineers, meaning anyone the product depends on, whatever their title.
- **Tier 3:** mid-level staff.
- **Tier 4:** the broad base.

The published figures on bonus size and payout timing are grouped by seniority, which maps onto the tiers:

| Group | Median bonus (WTW) | Secondary practitioner range | Typical payout |
|---|---|---|---|
| Senior leadership | Over 50% of base | CEO about 50%, CFO about 43% | 12/24 months, or thirds at 12/24/36 |
| Other salaried | About 30% of base | About 25% for key salaried | Single payment at 6, 12, or 24 months |
| Broad stay bonus | n/a | 5 to 15%, attribution unverified | 6 to 12 months |

The WTW figures come from its Acquirers' Incentive Plan Survey. More than 160 organisations took part, and 84% of them offer a fixed cash bonus. A secondary source adds that most stay bonuses pay out within 3 to 12 months of close, and within 24 to 36 months for key employees critical to the business over the long term. That's why Tier 2 can run longer than Tier 3.

How widely bonuses are spread matters more than their size. According to a secondary citation of WTW's 2024 data, 44% of acquirers offered agreements to at least half their C-suite, but only 19% offered them to more than a fifth of the broader salaried workforce.

**19% - Acquirers that offered retention agreements to more than a fifth of salaried staff**

Compared with 44% that covered at least half their C-suite, which leaves the middle of the org mostly unbonused and free to move.

Two things decide the tier in practice: how much the person has locked in, and how likely it is that the acquirer paid to keep them.

#### Seniority against likely bonus coverage

Horizontal axis runs from Bonus coverage unlikely to Bonus coverage likely. Vertical axis runs from Junior or mid-level to Senior or founder.

| Quadrant | What it means |
| --- | --- |
| Senior, uncovered | Rare. Check whether their role was cut in the remap, then approach early with a low-confidence flag |
| Senior, covered | Tier 1. A light first touch at close + 12, the main window from close + 24 |
| Middle, uncovered | The earliest pool. Approach from close and recheck at months 8 to 9 |
| Key contributor, covered | Likely a single tranche. Approach at the inferred cliff, 6 to 12 months |

*Senior, covered people are the last to become available, and the uncovered middle is available first.*

Give every tier a confidence flag:

- **High:** a clear title such as founder, CTO, or VP, or the author of most commits to the core repo.
- **Medium:** a generic title such as "engineer" with nothing that marks the person as central.
- **Low:** a tier inferred from commit activity alone, or a missing title.

What a tier tells you is whether this kind of role usually gets a package. It misleads when a junior-titled person is quietly critical, such as the sole maintainer of the core service, who may have a key-employee package despite the title. It also misleads when the acquirer ran a broad program that covered everyone. Use the flag to show that uncertainty instead of hiding it.

## What outreach window does each tier get?

Each tier gets a window counted from the close date. The uncovered broad team opens at close, covered mid-level staff open around the 6 and 12 month cliffs, key people on one-year packages open at month 13, and founders and executives open mainly from month 24. Label every window "inferred", because the real bonus terms for a private target aren't public.

| Tier | First touch | Main window | Basis |
|---|---|---|---|
| 1: Founders, C-suite | Close + 12 months | Close + 24 months on | Top-earner exits from year 2 |
| 2: VPs, key engineers | Close + 12 months | Close + 12 to 24 months | One-year package cliff |
| 3: Mid-level | Close, if uncovered | Close + 6 to 12 months | Single tranche at 6 or 12 |
| 4: Broad base | Close | Close to + 9 months | Highest year-1 exits, often no bonus |

The Tier 2 date comes from Haseeb Jawad, who leads corporate development at Commvault: "If you give a one-year retention package and that is the whole strategy, you can guarantee that person leaves on month thirteen." For anyone you believe is on a single one-year package, close plus 12 months is the first-touch date. The same source puts a broader wave of departures around months eight or nine, "when the integration dust settles and the recruiting calls start". That's why the Tier 4 window runs to month 9 and doesn't stop at close.

The published timing advice seems to conflict until you sort it by tier:

- **Customer-prospecting guidance** says to act in the first 30 days. That advice is about selling to the combined company, but the timing fits Tier 4.
- **M&A Science** says months 8 to 9, or month 13 once a one-year package vests. That fits Tiers 3 and 2.
- **Kim** says top earners leave from year two. That fits Tier 1.

> Each source is right about a different tier: the uncovered middle moves first, and the founders move last.

> **Rule:** Every window is inferred and shown as a range
>
> No deal-specific bonus terms are public for private targets, so never show a single date as if it were known. Write "inferred, close + 6 to 12 months" on the slate, and replace it only when a candidate tells you their real timing.

Integration events can pull a window forward. Watch for these:

- **Product sunset.** In acqui-hires, the product is often killed shortly after the acquisition, and a team with no product to work on starts listening.
- **Repo archived or transferred.** The code moving into the acquirer's org signals that integration is under way.
- **Email-domain migration.** It's listed with legal entity name, payroll provider, and holding company among the items that change.
- **Title remaps.** A former startup lead remapped into a narrower role at the acquirer is the classic trigger.

No published study ranks these events by how well they predict exits, and their typical timing isn't publicly established. Treat them as prompts to recheck someone's window, not as dates. When one fires, move the affected tier's next touch forward and log why.

Finding the people whose window is open right now is the hard part. Searching for a shared situation, rather than one company, is often the fastest way in:

I ran this search: `Engineering managers and staff engineers in California whose last startup was acquired in the past 12 to 18 months` - [see the full result list](https://www.refolk.ai/s/4r8zwme5p2).

*Returns Tier 2 people who are past the month-13 cliff, in a state where employee non-solicits are rarely enforceable, with their profiles joined across GitHub, LinkedIn, and the open web.*

## Who must you leave alone?

Suppress anyone you're barred from approaching by your own client relationships or contracts, whatever the law says about the deal's non-solicit. After that, check whether any deal-stage clause reaches you, and only then look at jurisdiction. Run the checks in that order, outermost first, and stop at the first one that blocks the approach.

#### Off-limits checks, outermost first

1. **Your client list** - If the acquirer or the target is your client, the name is suppressed
2. **Your own agreements** - Off-limits terms in your agency or retained-search contracts
3. **Deal-stage non-solicit** - Binds the parties to the deal and anyone approaching on their behalf
4. **Candidate's work state** - California voids most clauses, New York enforces reasonable ones, UK and EU unclear

*A name is cleared only when it passes every layer, and failing an outer layer settles it whatever the inner layers say.*

A deal-stage non-solicit is a clause between the acquirer and the target. A typical version reads: "neither party shall solicit, hire, or engage employees of the other party without prior written consent". Many of these clauses also cover indirect approaches through third parties, so an agency working for either side can be caught. An unrelated outside recruiter isn't a party to the deal. If your company signed anything with either side during the deal process, ask your legal team whether it included a non-solicit before you clear any names.

Jurisdiction comes last:

- **California.** Employee non-solicits are almost never enforceable, under Business and Professions Code §16600 as applied in AMN v. Aya (2018).
- **New York.** Courts enforce reasonable non-solicits. However, hiring many people from one competitor isn't, on its own, enough to enforce one, which matters when you're taking several people from the same team.
- **UK and EU.** The sources behind this guide don't cover them. Treat these names as "hold" until employment counsel has looked at them, rather than clearing them by analogy.

> **Watch out:** Don't clear a name on jurisdiction alone
>
> A non-solicit that's void in California doesn't cancel your client relationship with the acquirer or the off-limits terms in your retained-search agreement. Check your own contracts first. Those are the clauses you've actually signed.

Log one of four statuses for every name: cleared, suppressed (client), suppressed (agreement), or hold (jurisdiction unclear). Suppressed names stay on the roster with their reason so nobody adds them back next quarter.

## The two-day procedure

The procedure runs in seven steps and takes about 10 to 16 hours of focused work, which fits in two working days. Steps 1 to 4 build the slate's timing, step 5 keeps it up to date, step 6 removes the people you can't approach, and step 7 ships it.

#### Deal close to a tiered, dated slate

1. **Date the close, separately from signing** - Check Item 1.01 and Item 2.01 filings, Companies House officer and PSC filings, and the press release. Finish with a close date and its source, or an estimated date with the method written down (1 to 2 hours).
2. **Rebuild the pre-close roster** - Pull profiles listing the target as employer, GitHub members and committers from before the transfer, and archived careers pages, then deduplicate. Every row needs role, seniority, start date, and location (4 to 6 hours).
3. **Assign each name a retention tier** - Place everyone in Tier 1 to 4 by role and seniority, with a high, medium, or low confidence flag (1 to 2 hours).
4. **Put dated windows on every tier** - Work out close + 6, 12, and 24 months, add the year-two window for top earners, and label each window inferred with a range (about 1 hour).
5. **Set integration-event watches** - Watch for product sunset, repos archived or transferred, domain migration, and title remaps, each set to alert the slate owner (1 hour to set up, then ongoing).
6. **Run off-limits and non-solicit checks** - Check your client list, your agreements, any deal-stage clause, and the candidate's work state, in that order, and log a status and reason for every name (1 to 2 hours).
7. **Rank and ship the slate** - Rank cleared names by fit and how soon their window opens, give each a first-touch date, and send it to the hiring manager with flags visible.

When ranking in step 7, sort by window first and fit second within each window. A strong Tier 1 founder whose window opens in 20 months shouldn't push an available Tier 3 engineer off this quarter's list. Put both on the slate with different dates.

## How this goes wrong

Most errors on an acquired-team slate are timing errors that look like data. Each failure below has a cause you can recognise and a check that catches it.

1. **Using the announcement date as the close date.** Every tranche window shifts by the length of the regulatory review, so your month-13 touch lands before the cliff. *Check:* find the Item 2.01 filing or the officer filing, and recount every window from that date.
2. **Treating a missing 8-K as "not closed".** Deals at or below 20% significance don't need an Item 2.01, and most startup deals are below that line. *Check:* look for an Item 8.01, the press release, and registry filings before you decide the deal is still pending.
3. **Reading employer changes on profiles as departures.** Bulk updates to the acquirer's name are relabels, not exits. A slate that counts them as people "already gone" leaves out the very people still inside. *Check:* compare each start date with the close date.
4. **Assuming tranche dates.** No deal-specific bonus terms are public for private targets. A precise date on the slate implies knowledge you don't have. *Check:* every window says "inferred" and shows a range, such as 6 to 12 months.
5. **Treating the tier as certain.** Only 19% of acquirers cover more than a fifth of salaried staff, so many Tier 3 and Tier 4 people have no bonus and can move straight away. Holding them until month 6 because "the tier says so" wastes the best window you'll get. *Check:* default uncovered mid-level and broad-base names to an open window at close.
6. **Clearing a name on jurisdiction alone.** A non-solicit that's void in California doesn't cancel your client relationships or a retained-search agreement. *Check:* run the client and contract layers before the state layer, every time.
7. **Treating a repo archive as a departure.** Some large organisations move repos into a separate archive org purely for tidiness, as Google's open-source management policy describes. The archive flag says nothing about who still works there. *Check:* look at each committer's recent activity, not the repo's archive status.

One more mistake sits outside the data. It's assuming that outreach in the "right" window will get better replies. That's plausible, but nobody has published evidence for it. Treat your windows as hypotheses and log replies by tier and month so you can test them.

## Keeping the slate current after it ships

A shipped slate is a schedule, not a finished list. Most names don't open until months later, so the work is keeping dates accurate, re-checking status when integration events fire, and touching each person when their window opens.

Use one row format for every name so the slate stays sortable and auditable:

**Slate row**

```
Name | GitHub handle | Role at target | Seniority | Start date at target
Tier (1-4) | Confidence (high / medium / low)
Close date | Close source (filing / registry / GitHub / estimated + method)
Window: inferred, close + __ to __ months | First-touch date
Status: cleared / suppressed (client) / suppressed (agreement) / hold (jurisdiction)
Status reason | Work state or country
Integration triggers seen (date + event) | Last touch date | Reply (Y/N)
```

*One row per person. Keep suppressed names in the file with their reason so they aren't re-added.*

The first message should be about the work, not the deal. Never mention or guess at someone's retention package in writing. You don't know it, and guessing reads as surveillance.

**First-touch message, acquired-team candidate**

```
Subject: Your work on {product or repo}

Hi {first name},

I followed {target}'s work on {specific product, feature, or repo} before it joined {acquirer}. I'm hiring a {role} at {company} to {one-line scope}, and the problem looks a lot like the one you solved there.

I know timing after a deal is rarely simple. If now isn't right, tell me roughly when would be, and I'll write then instead.

{your name}
```

*Name the specific product or repo they worked on. Leave the timing question open so they can tell you their real window.*

Re-run the roster query at each tier's window date. People change titles, move, or leave between the build and the touch, and a list from close is stale by month 12. In Refolk, the same plain-English request you used to build the roster runs again as-is, so refreshing a tier is a re-run, not another four-hour rebuild.

#### Before the slate goes to the hiring manager

- [ ] The close date has a cited source, or is labelled estimated with its method written down.
- [ ] Every person on the roster has role, seniority, start date, and location, or a visible flag where a field is missing.
- [ ] No profile relabelled to the acquirer at close is counted as a departure.
- [ ] Every name has a tier from 1 to 4 and a high, medium, or low confidence flag.
- [ ] Every window is labelled inferred and shown as a range from the close date.
- [ ] Uncovered Tier 3 and Tier 4 names have a window that opens at close, not later.
- [ ] Watches are live for product sunset, repo archive or transfer, domain migration, and title remaps.
- [ ] Every name has a logged status and reason, and client and contract checks ran before jurisdiction.
- [ ] UK and EU names are on hold until counsel has reviewed them.
- [ ] Every cleared name has a first-touch date, and the slate is sorted by window, then by fit.

After a full cycle of windows, compare your logged reply rates by tier with the windows in this guide. Where your data disagrees with them, trust your data. It will be the only measured timing evidence you have.

## Frequently asked questions

### When should I reach out to employees after their startup is acquired?

It depends on their tier. The broad team and uncovered mid-level staff are open from close onward, because first-year departures run highest and many have no stay bonus. People on a single one-year package are best approached at close plus 12 months. Founders and executives mostly leave from year two, so start a light conversation around month 12 and make the main approach after month 24. Treat every one of these windows as inferred, not measured.

### Can I recruit from a company that was just acquired if the deal had a non-solicit?

Usually yes, if you aren't a party to the deal. Deal-stage non-solicits bind the acquirer and the target, and many also cover indirect approaches through third parties working for them, which can catch an agency hired by either side. An unrelated outside recruiter isn't a party. Before you clear anyone, check your own client contracts and agency agreements, because those apply whatever the deal clause says.

### How do I find out when an acquisition actually closed?

Look for the closing filing, not the announcement. A US public acquirer files an 8-K Item 2.01 within four business days of close, but only when the deal is above 20% significance. For smaller deals, check Companies House director and PSC changes (due within 14 days), the date of the GitHub repo transfer redirect, and press releases. If no source pins the date, label it estimated and write down how you got it.

### Do acqui-hire employees really leave in the first year?

Many do. In Kim's Census study of 4,000 US startup acquisitions, 33% of acquired employees left within the first year, against 12% of comparable regular hires, and departures fell every year after that. Top earners are the exception. Their extra departures only show up about two years after the acquisition, which Kim links to vesting cliffs. Only 63% of acquired CEOs stay into their second year.

### How do I know whether a specific person has a retention bonus?

From the outside, you usually can't. Bonus terms for private targets aren't public. Infer it from the tier instead: senior leaders are usually covered, and broad salaried staff often aren't, since only 19% of acquirers cover more than a fifth of them. Label the window inferred, show it as a range, and let the candidate tell you their real timing on the first call. Don't guess their package in writing.

---

*From the Refolk guide library. I revise these guides rather than replacing them, so the current version is always at https://www.refolk.ai/guides/acquired-startup-talent-window*
