How is add-on diligence different from a platform deal?

Three ways. First, the timeline is shorter (often 4-6 weeks signed-LOI to close vs. 8-12 weeks for a platform). Second, the thesis is integration into an existing platform, so platform-fit issues dominate the diligence agenda. Third, the team is often smaller (PE counsel + maybe one outside firm) so the per-attorney workload is higher.

What goes wrong most often on add-ons?

Three things. ERP/accounting integration cost gets underestimated. Customer overlap with the platform creates MFN or stacking issues. Founder-departure risk on earnout-heavy deals. Each of these is fixable; missing them is what creates post-close litigation.

How does AI compress the diligence timeline?

Mid-market data rooms (which is what most add-ons have) ingest in under an hour, get classified overnight, and produce a partner-reviewable findings list by Day 2. On a 4-week timeline, that's 25% of the window saved on the front end alone, freeing the team for negotiation and 100-day planning. We covered the workflow in [AI Due Diligence: An Operational Playbook](/guide/ai-due-diligence).

What about founder-led add-ons specifically?

Founder-departure risk is the single biggest issue. The deal is contingent on the founder's transition. Non-compete and consulting-agreement terms matter as much as the headline price. We see deals fall apart in the 100-day window when the founder departs faster than planned and the platform isn't ready.

How does the 100-day plan integrate with diligence?

Run them in parallel. The diligence findings (system fit, customer overlap, founder-departure timeline) become the 100-day plan inputs. PE platforms have a script; align the target's first 100 days to it during diligence, not after.

PE Add-On Diligence: An Integrated Playbook

PE add-on diligence has its own shape. The deal is shorter, the team is smaller, the thesis is platform-integration-first. This is the playbook for PE counsel running add-on diligence at speed without missing the structural issues that turn into post-close litigation.

What makes add-ons different

A platform deal is "is this target a good company at the right price?" An add-on is "does this target fit the platform and accelerate the thesis?" The diligence questions diverge.

Three structural differences:

Timeline. Most add-ons run 4-6 weeks signed-LOI to close. Platform deals run 8-12+. The compressed timeline means diligence has to be more efficient per day; there is less slack for mid-deal re-scoping.
Team size. PE in-house counsel + maybe one outside firm. The per-attorney workload is higher than on platform deals where multiple firms split the work.
Thesis. Integration risk is the dominant axis. A great target that doesn't integrate is worse than a mediocre target that does. The diligence agenda reflects this.

The recurring traps

What we see most often go wrong on add-ons:

System fit. ERP, accounting, billing, CRM systems often don't reconcile cleanly. The integration cost gets underestimated. Reasonable buy-side question to address in diligence: how many months of dual-systems operation are realistic, what's the migration cost, can the target operate on the platform's stack without major re-architecture?

Customer overlap and MFN. Platforms often have customers that overlap with the add-on. If those customers have most-favored-nation pricing, the platform's pricing power becomes constrained by the add-on's pricing, or vice versa. Discovery of MFN issues late in diligence kills deals or forces purchase-price renegotiation. We covered the standalone clause analysis in Most-Favored-Nation Clauses in M&A; the add-on context makes it sharper.

Founder-departure risk. Add-ons are often founder-led. The deal is partly contingent on the founder's transition into the platform structure. Non-compete enforceability, consulting agreement length, performance-conditioned equity rollover — all of these structure the founder's continued involvement. We see deals fall apart 60-90 days post-close because the founder departs faster than planned and the platform isn't ready to absorb.

Earnout structures and post-close litigation. Earnouts are common in add-ons. They're also a recurring source of post-close litigation when integration changes the basis on which the earnout was earned (e.g., if the target's revenue is reorganized into the platform's cost centers, what does "target revenue" mean for earnout purposes?). Get the earnout language right pre-signing.

Geographic and regulatory overlap. Same-industry add-ons inherit the same regulatory layer. Stacking licenses, redundant filings, mismatched compliance programs. Less catastrophic than the others above but it shows up in 100-day plan execution.

What to actually check

A practical add-on diligence checklist, ordered by what most often surfaces issues:

Top customer contracts: change-of-control, anti-assignment, MFN, exclusivity. Cross-reference against the platform's existing customer book to surface overlap.
Founder agreements: employment, equity, non-compete, consulting (if rolled). Look at the actual operative terms, not the LOI summary.
System and IT contracts: SaaS subscriptions, ERP licenses, hosting agreements. Identify renewal triggers and assignment language.
Material vendor contracts: top suppliers, logistics, services. Termination and assignment language.
Real estate: leases, especially headquarters and operational facilities. Assignment, change-of-control, transferability of any zoning/operating permits.
Employee handbook + comp structures: post-acquisition retention is a 100-day plan input.
Open litigation and insurance: tail coverage analysis, R&W insurance gap analysis.
IP assignment chain: especially the founder layer, which often has gaps.

For the broader category coverage, see M&A Trends by Industry which has a dedicated section on PE add-ons.

How AI compresses the timeline

The 4-6 week timeline is where AI-augmented diligence pays off most. The compression looks like this:

Day 1: data room ingested, classified, prioritized. (Manual: Days 1-3.)
Day 2: first-pass risk review complete; partner reviews high-severity findings. (Manual: end of Week 1.)
Day 3-4: gap analysis sent to seller's counsel; outstanding-items list circulated. (Manual: end of Week 1, Week 2 follow-ups.)
Days 5-7: deep review of high-priority issues; memo drafted. (Manual: Weeks 2-3.)
Days 7-14: negotiation and finalization. (Manual: Weeks 3-4.)
100-day plan drafted in parallel from Day 5 forward.

The compressed timeline means more parallel work and earlier 100-day planning. The 100-day plan ships at signing, not after close.

The 100-day plan as a diligence output

PE platforms have a script for the first 100 days post-close. Align the target's first 100 days to the script during diligence, not after.

Inputs to the 100-day plan that come from diligence:

System integration cost and timeline
Customer-overlap remediation
Founder transition timeline (and backup plan if accelerated)
Workforce retention plan (with named roles and incentive structures)
Compliance program harmonization
Reporting and KPI alignment

The output is a Day-1 ready 100-day plan that the platform can execute starting at signing. This is materially better than the standard pattern of building the 100-day plan in the post-close scramble.

Companion reading

How a PE Buyer Identified $5M in Hidden Liabilities — case study on aggregate-liability discovery
How Buy-Side Team Used Mage for Post-Signing Covenant Compliance — sign-to-close tracking
Indemnification Caps and Baskets — the indemnity-package mechanics that matter on add-ons
AI Due Diligence: An Operational Playbook — workflow walkthrough

If you have a current add-on you want to run through Mage end-to-end on a real timeline: request a demo.