What is an add-on acquisition, and what happens to its records?
An add-on acquisition is the purchase of a smaller company by a private equity-backed platform, which folds the acquired business into its own operations to add customers, services or geography. Add-ons are also called bolt-ons. Integration usually moves the add-on onto the platform's CRM, helpdesk and ERP, so its archived history should be checked before old systems are shut down.
Add-on acquisition definition
An add-on acquisition is a company bought by an existing private equity-backed business, called the platform, and folded into it. The platform is the legal buyer, the deal is funded with some mix of platform debt, fund equity and seller financing, and the add-on's customers, staff and services become part of the larger group.
Sponsors buy add-ons to gain a service line, a region or a customer base faster than the platform could build it organically. Every add-on needs a base to join, which is the platform company the sponsor bought first.
Add-on vs bolt-on vs tuck-in and related terms
Bolt-on is the closest synonym and the two are used interchangeably. Tuck-in usually means a small business absorbed completely, with its brand and tools gone within months.
| Term | What is bought | How it runs after closing | Records question it raises |
|---|---|---|---|
| Add-on | A company acquired by an existing platform | Integrated into the platform to a planned degree | Which of its systems will be retired, and when? |
| Bolt-on | Same as an add-on in most usage | May keep its brand, team or location for a while | Do the records still sit with the acquired entity? |
| Tuck-in | A small company, team or product line | Absorbed fully and quickly | Was anything exported before the tools were cancelled? |
| Platform acquisition | The first, larger company in a sector strategy | Becomes the base for later deals | How many inherited archives does it now hold? |
| Carve-out | A division bought out of a larger parent | Separated from the parent, often with transition services | Which entity keeps the shared historical records? |
A division bought from a corporate parent raises its own separation questions, covered in the explainer on carve-out transactions.
How an add-on acquisition works, step by step
Most add-ons follow the same path, and the records outcome is decided at the end of it.
- Criteria: the sponsor and the platform CEO agree what an add-on must contribute: territory, services, customers or specialist staff.
- Sourcing: the platform's corporate development lead, the sponsor's deal team or intermediaries approach owners, many of them founders new to a sale.
- Letter of intent: price, structure and an exclusivity period are set; the no-shop clause explainer covers what the seller can do while exclusivity runs.
- Diligence: financial, legal, IT and HR reviews, often led by the platform's CFO and operations leaders with outside advisers.
- Closing: a stock purchase, asset purchase or merger, a choice that decides which legal entity holds the add-on's records afterwards.
- Integration: day-one controls, a 100-day plan, then cutover onto the platform's ERP, CRM, helpdesk and email.
- Decommissioning: old subscriptions lapse, servers are switched off and each archive is kept, copied or lost.
Step 7 is where licensable history is most often lost by default, because nobody owns the question.
When does integration put the add-on's archive at risk?
The risk peaks between systems cutover and the date the add-on's old subscriptions end. Migrations tend to carry open work, such as active accounts, open tickets and the current ledger, and leave the closed history behind.
| Deal moment | What is happening | Records question to ask | Who to ask |
|---|---|---|---|
| IT diligence | The buyer lists the add-on's systems | Which systems hold the oldest records, and can they be exported? | The add-on's IT manager or outsourced IT provider |
| Purchase agreement drafting | Purchased and excluded assets are scheduled | Do the records and the right to use them transfer? | Deal counsel |
| Day one | Admin credentials and bank controls move | Who now controls each system's admin account? | Integration lead |
| 100-day plan | Workstreams set cutover dates | Is a full export listed ahead of each cutover? | Integration management office |
| Cutover | Active data moves to platform systems | Was history moved in full, or only open items? | Each system's business owner |
| Renewal or cancellation date | Old licenses lapse | Is a complete export saved before access ends? | Finance or procurement |
Put these questions into the integration plan as a records workstream that runs alongside the finance, people and IT workstreams.
Who owns an add-on's records after closing?
The entity that holds them under the deal structure, but only to the extent the add-on owned them in the first place. Under US copyright law, material an employee prepares within the scope of employment is a work made for hire owned by the employer, while a contractor's work counts as made for hire only in listed categories and with a signed written agreement (U.S. Copyright Office, Circular 30). Founder-led companies that relied on freelancers for proposals, training materials or code may hold records they cannot license without written assignments.
Client contracts matter just as much. An add-on whose records mainly describe its clients' operations, as at many agencies and outsourcers, cannot license them without those clients' agreement. This is general information, not legal, tax or financial advice. Confirm ownership and contract questions with your own counsel before acting.
Why add-ons matter to referral partners
Each add-on can be a separate introduction if it meets the baseline: a US company with 50+ full-time employees at peak (contractors excluded), several years of documented operations, the right to license its data and an authorized sponsor such as the owner, CEO, CFO or an authorized representative. The who qualifies page sets out the full criteria.
Size is the first filter. The pool of potential add-ons is very large: the Census Bureau counted 5.58 million US firms with at least one but fewer than 500 employees in 2023, and only part of that pool reaches the headcount baseline. The words at peak help here, because an add-on that has shrunk since its busiest year can still meet it. A smaller add-on whose archive now sits inside the platform entity is better raised as part of the platform's own inventory.
The introduction moves no data. You make it through the referral form or your referral link; SourceX then works with the company on qualification, the data inventory, pricing and buyer review. Redaction rules are agreed first, and nothing is delivered without an executed agreement and the company's authorization. The company fit checker gives a preliminary, non-binding read before you raise it.
Partners earn 25% of the eligible platform fees SourceX actually collects from the referred company's licensing deals, capped at $100,000 per referred company. Here the fees are SourceX's own, not anything the PE platform earns. The reward is paid only after the buyer pays and SourceX receives its fee, it is never deducted from what the company receives, and no reward is guaranteed. The page for private equity operating partners explains how to fit this into a hold.
Illustrative example
Illustrative and fictional: a managed IT services platform buys a 120-person IT support provider with nine years of tickets and resolution notes in its service desk tool. The 100-day plan moves open tickets to the platform's tools and cancels the old subscription at renewal. The operating partner asks the integration lead to keep a full ticket export first, deal counsel confirms the stock purchase left the records with the acquired entity, and the add-on's CEO applies through the partner's referral link. No records leave the company during the introduction.
What to say to the integration lead
Next step
Pick the add-on with the nearest cutover date and confirm its history has been exported. If it clears the baseline, register as a partner and introduce the CEO, or send them your referral link so they can apply directly at sourcex.si/apply.
- Step 1Share your linkSend your personal link to a company you know.
- Step 2Company appliesThe company applies itself at /apply.
- Step 3Buyer selects and paysThe buyer selects and pays for the data and SourceX receives its fee.
- Step 4You get your rewardYour share of SourceX fees becomes payable.
Common questions
Who signs a data license for an add-on after it has been acquired?
The legal entity that holds the records signs, through an officer with authority to bind it. If the add-on remains a separate subsidiary, its own officers sign, subject to any approvals the platform or fund requires under its governance documents. If it was merged into the platform entity, the platform signs. Confirm signing authority with the company's counsel before price and terms are discussed.
Could licensing an add-on's data affect the seller's earnout?
It could. If the seller's earnout is measured on the add-on's revenue or EBITDA, a one-time license payment may change the result, depending on how the purchase agreement defines those measures and whether non-recurring items are excluded. Agree the treatment in writing with the seller and deal counsel before any license is signed, so neither side is surprised at the measurement date.
What if the add-on's old systems were already cancelled?
Check what survives before ruling the company out. Vendors handle data after cancellation in different ways, so read the contract and ask the vendor directly. Backups, former employees' mailboxes, local database copies and file-share snapshots sometimes remain. If nothing can be exported, the archive cannot be licensed, and the practical lesson is to put an export step ahead of the next add-on's cutover.
Does the 50-employee baseline apply to an add-on on its own?
Yes, it applies to the company being introduced. Headcount is measured at the company's peak, with contractors excluded, so an add-on that has shrunk since its busiest year can still count. If its staff and systems have already merged into the platform entity, ask the platform's sponsor whether the records belong in the platform's own inventory instead.
Does an operating partner need the add-on CEO's agreement before making an introduction?
In practice, yes. A licensing conversation only works with an authorized sponsor who wants to explore it, so speak to the CEO or owner first and explain that nothing is binding until the company agrees price and terms and signs. Share the referral link or submit the referral form once they agree to a call. Partners never send records, samples or system details on the company's behalf.
Related pages
- What is a platform company in private equity, and why do its records matter?
- What is a carve-out transaction, and who keeps the records afterward?
- What is a no-shop clause, and what does it restrict during a sale?
- Which US businesses are a fit for a SourceX data licensing introduction
- Check Company Fit for Data Licensing
- Referral opportunities for private equity operating partners
Free resources
- Client opportunity brief generator — An editable intro email, summary and checklist.
- Days sales outstanding calculator — How many days customers take to pay.
- Business succession planning assessment — Ten questions on successor, transition and documentation.
- All free tools · MCP resource center
By SourceX Partnerships Team · Published 2026-10-09 · Updated 2026-10-09
Know a US company with valuable proprietary data?
Become a referral partner from anywhere we support, get your link and introduce an owner or authorized decision-maker.
Refer a company →I own a business
Explore licensing your company's data to AI developers worldwide. Start a short assessment; no uploads needed.
Start an assessment