Private equity bought your company: engineering's first 100 days

In the private equity first 100 days, a CTO or VP Engineering should expect the new owners to baseline engineering spend, delivery, people and risk, judge the team within 60 to 90 days, and fold it into a value-creation plan. Arrive in week one with your own one-page baseline, cost levers sorted by what protects the roadmap, and named key-person risks with cover. Then you set the terms of the review.

What will private equity ask of engineering in the first 100 days?

Expect three phases on the owners' calendar. Windsor Drake, an M&A advisory firm for founder-led companies, says a new owner usually makes its first management decisions within 60 to 90 days. Bain's Hugh MacArthur gives the target behind that calendar: at least a 3x multiple on invested capital, or a doubling of enterprise value, through three to five value-creation levers. Engineering is one line in that plan, so it's judged by what it does to those numbers.

Days 1-30: be the source of the baseline

The owners will review finances, customers, operations and technology, and compare actual operations with what diligence showed. They'll also install reporting cadences and KPI dashboards early. Your job is to hand them one trusted set of engineering numbers before they build their own. The two-week list in the next section is that set.

Name one liaison for reporting. Bain says it's often the CFO, so build the pack in finance's terms: dollars, owners and dates, not sprint metrics.

Days 31-60: hold your reviews, and settle your people calls

Put yourself into the owners' rhythm. Umbrex, a value-creation primer, describes weekly initiative reviews, a monthly CEO-led value review and a decision log. Run engineering's updates on that cadence and keep the log yourself.

This is also the window where the owners judge the team. Bain's advice on talent is blunt: loyalty to underperformers is a deal killer. Decide on yours before day 60, with evidence, so the call is yours and not the operating partner's.

Days 61-100: put your roadmap into the plan

The plan locks in. CTO Input, a fractional CTO firm, lists what it delivers by day 100: a one-page technology strategy, a 90-day plan, a 12-month roadmap, board-ready reporting and technical debt as a budget line. Write yours before it's asked for. A roadmap and a debt line already on paper make you the editor of the plan instead of the recipient. Raise bad news as soon as you have it.

What should I hand over in the first two weeks?

One page, built before anyone asks. The owners saw the diligence report and this page answers it. If you haven't read the findings since close, start with triaging the diligence findings.

Engineer headcount by role and employment type (employees, contractors, agencies).
Loaded cost per engineer-month, with the layers listed so finance can check them.
Cloud and tool spend, by month.
Your top vendor contracts and their renewal dates.
Delivery measures you already track, in the form you already track them.
Open diligence findings, each with a dollar range, an owner and a trigger date. SaaS BPM's PE technical-debt guide uses that format, and a letter grade gives the owners nothing to act on.

Send it to your liaison and offer a walkthrough. Don't attach a wish list; that belongs in the cost conversation.

How do I answer the cost question without cutting the roadmap?

The owners' lever on engineering is margin, so expect a question about R&D as a share of revenue.

Take a 30-engineer SaaS company with an assumed $15M of revenue, where R&D runs at 28%. In this example the operating partner asks for a margin plan around day 45 and floats 18%. On $15M that's $4.2M down to $2.7M, a $1.5M gap. If all of that R&D is the 30 engineers, $4.2M is $140k loaded per engineer-year, so the gap is about 10-11 engineer-years. That's a third of the team, on paper. Use your own loaded cost from the baseline instead of $140k.

Have your options on the table by day 30, so the day-45 question meets an answer. In the order we'd offer them:

Discretionary spend thresholds for hiring, travel and projects. Umbrex recommends these over an across-the-board freeze, and they let you keep approving the roadmap work that matters.
Tool and cloud consolidation. It's the cheapest saving to defend.
Contractors before core engineers. What to cut first sets out the order. If the owners freeze headcount, find out whether contractors count against a freeze before you assume they do.

Which people are the risk, and how do I keep them?

Start with your own seat. Bain says 50% to 70% of portfolio-company CEOs are replaced during the hold. Your standing depends partly on your CEO's, so ask the deal lead when the management assessment happens and whether retention agreements exist. Equity, earn-outs and severance belong with your own lawyer.

For the team, fix key-person dependence first. SaaS BPM classes it as Tier 1 technical debt, a deal-breaker, with the example of one person who controls a critical system. In a 10-60 person team, expect to find a few. Write down their names, what only they know, and who could cover each. Then start the handover on the most exposed one; a 30-day knowledge-transfer plan works whether the engineer is leaving or not.

Your engineers will also be reading the news. One Hacker News thread from 2016 has an engineer describing layoffs within three months of an acquisition, and hiring only after attrition. It's one anecdote, but it's the story your team will assume. Tell them early what you know, what you don't, and when you'll know more.

If you hold the seat, keep it, and add outside help only for a named gap: board reporting, remediation work or an add-on integration.

What this means for your first 100 days

Two decisions are yours before the owners make them for you.

First, who owns engineering's reporting to the new owners. If that's you, say so by day 10 and name the liaison. If it's nobody, settle it before anything else. Second, what engineering commits to by day 30: the baseline, the cost levers in the order above, and cover for each key person. For the other decisions at this stage, the Startup CTO guides are the next stop.

Hiring a fractional CTO or senior cover through HighCircl

If the seat is empty or the board report has no owner, waiting for a permanent search costs you the window in which the plan gets written. Fractional CTOs through HighCircl are matched in 72 hours, and there's no minimum hour commitment, so you can bring someone in for the baseline and the board pack and stop when the permanent hire lands.

FAQ

What happens when a private equity firm buys a company?

The owners review finances, customers, operations and technology, and compare actual operations with what diligence showed. They install new reporting, assess management and make first decisions within 60 to 90 days, then run a plan with a few levers toward a sale in a few years.

What is a 100-day plan in private equity?

It's the owners' plan for the first three months after close. Umbrex splits it into baseline and risk stabilization, tighter governance, and scaling what works. For engineering it usually means a baseline, a cost position and a roadmap.

Will private equity cut the engineering team?

It depends on the sponsor's plan, which isn't public. Ask the deal lead for the plan for this company, the target R&D ratio in the value-creation plan, and how headcount and discretionary spend get approved. One forum thread describes layoffs within months, so ask early.

Should a fractional CTO join after a private equity acquisition?

Only for a named gap, or when the engineering seat is empty. If you hold the seat, keep it; the baseline, the cost options and the key-person cover are yours to own.