The deal closed on Friday. By Monday morning, someone owns every technology decision at the company you just bought, and in most acquisitions nobody has said who. The first two weeks are not for transformation. They are for making sure the unglamorous questions have owners before something breaks.
The short answer: in the first two weeks, establish decision rights, incident authority, and an access review. Everything else, including the integration roadmap, works better once those three exist.
Decide who decides, before the first decision arrives
In the gap after close, decisions arrive that cannot wait for a steering committee. A vendor renewal hits its notice window. A key engineer gives notice. A customer demands a security answer. Each of these needs a named person with authority to act, and a clear line for what must come to the investor or the board.
Write it down in a page. Which technology decisions the portfolio company CEO makes alone, which need the operating partner, which need the board. The page matters less than the conversation, but the conversation does not happen without the page.
Set incident authority explicitly
If the company has a security incident in week three, who is in charge? The acquired company’s IT lead, the platform’s security team, an outside firm, the insurer’s panel? In the first two weeks, answer that question while it is still hypothetical. Confirm the incident contacts actually work: phone numbers, after-hours paths, and who can approve emergency spending without a meeting.
This is also the moment to learn what monitoring exists and who watches it. An alert nobody owns is a liability you now own.
Review access while it is still easy
Access accumulates. Former employees, departed contractors, vendors from two years ago, and in carve-outs, people who now work for the seller. In the first two weeks, get the list of who has administrative access to what, and remove what should not be there. This is cheap, fast, and much harder to do credibly six months in.
What to leave alone
Resist the urge to start the rebuild. System replacements decided in the first two weeks are usually decided on the thinnest information you will ever have about this company. The governance work above creates the structure that makes later decisions good. Let it do that job first.
Frequently asked questions
Is two weeks really enough time to set up governance?
For the three items here, yes. Decision rights, incident authority, and access review are each a few days of focused work. The full integration plan takes longer and should.
What if the acquired company already has good processes?
Then the two weeks confirm them and connect them to your escalation paths. The failure mode is assuming someone else’s process covers your accountability.
Should the platform’s IT team take over immediately?
Usually no. Immediate takeover breaks accountability before you understand what you bought. Observe first, assign authority, integrate deliberately.
If you have just closed a deal and the technology governance question is still “we’ll figure it out,” the first two weeks are the cheapest time to fix that. CTO Input works with investors and portfolio companies on exactly this window. If it would help, we should talk.