Add-on acquisitions rarely get platform-level timelines. The deal team has two weeks, the seller has a business to run, and the technology review has to fit inside both. The answer is not to do everything faster. It is to be explicit about what two weeks can establish and what has to be verified after close.
The short answer: in two weeks you can establish what the systems are, where the knowledge lives, and whether anything is actively broken. You cannot establish code quality, deep security posture, or true scalability. Name which is which, and plan the second pass deliberately.
Week one: inventory and people
The first week belongs to the inventory. What systems exist, what they run on, what they cost, and who runs them. Most of this can be assembled from a structured request list plus one working session with the seller’s technical lead. The goal is a complete picture of the estate, not a judgment of it yet.
In parallel, learn the people map. Who built what, who is critical, and who is staying. In a two-week process, the people answers matter more than usual, because they are the fastest reliable signal about what the systems are really like.
Week two: risks that move the deal
The second week belongs to the short list of things that would change the price or the plan. Is anything actively broken or past due in a way that needs immediate money? Is there a dependency, a person, a vendor, a license, that the platform cannot replace? Does anything about the add-on conflict with how the platform already runs?
That last question is the add-on-specific one, and it is the one most often skipped. An add-on that is perfectly healthy on its own can still be expensive because its stack, its hosting, or its support model does not fit the platform it is joining.
What to defer, and say so
Code review, deep security testing, and load testing do not fit in two weeks, and pretending they do produces false comfort. The disciplined move is to say, in writing, what was not examined and when it will be. The first ninety days after close should carry a scheduled second pass on exactly those items.
Use what the platform already knows
The advantage of an add-on is that the platform has a working reference point. Its team knows what healthy looks like in this market. An hour of the platform’s senior technical person in the seller’s systems is often worth days of outside review, because they know which questions matter here.
Frequently asked questions
Can technology diligence really be done in two weeks?
Inventory, people risk, and deal-moving risks, yes. Code quality, deep security posture, and scalability, no. The honest deliverable for two weeks names both halves and schedules the second.
What is the biggest add-on specific risk?
Fit, not health. An add-on can be well run and still expensive to own because its systems do not align with the platform’s stack, hosting, or support model.
Who should do a compressed review?
A small team that has done it before, plus an hour of the platform’s own senior technical person. Speed comes from knowing what to skip, and that takes experience.
If you are running add-on diligence on a compressed clock and want the two weeks spent on what actually moves the deal, that is the kind of work CTO Input does with investors. If it would be useful, we should talk.