// Post-acquisition integration · By industry
The records you inherit with an acquisition, tested one job at a time.
Each company you buy arrives with records kept its own way: an item file, a book of accounts, price sheets, a project setup, a vendor list. Post-acquisition integration covers far more than that, and this page covers one piece of it: a free AI proof of concept that maps one job's inherited records onto your setup, run on copies from a deal you already closed and judged by your own reviewer. We never log in to either company's system.
- Sample
- 20 to 30 records from a closed deal
- Answer key
- What your team set up afterward
- Systems touched
- Neither company's
- Reviewer
- Named by the owner
- Price
- A range before it starts
// By industry
What an acquired company hands you, industry by industry
Distributors: an add-on's orders on its old ERP
- POs that still reach the add-on are drafted in your order format, with your item numbers beside its own.
- Customers who bought from both companies bring two accounts and two price lists, and which one wins goes into the success criteria.
- Neither ERP is touched, and the two are never connected.
Insurance agencies: an acquired book's records
- Each commercial account gets a proposed home in your agency structure, with the seller's companies matched to your carriers.
- Certificate holders with no current policy behind them, and insureds both agencies wrote, go on the gap list.
- Personal lines stay out, and no live policy or certificate changes.
Waste management: a bought hauler's prices on your codes
- Each account is mapped to your service and rate codes, showing how its total moves once your fees apply.
- Renewal dates, notice windows and franchise rates that must hold are listed from the contracts.
- The AI never sends a price notice.
Engineering firms: a bought firm's open projects
- Each open project is mapped onto your projects, phases and billing terms, with its signed contract rates kept.
- Fee, billed to date, retainage and unbilled time are carried over, and every unbilled-time decision stays with you.
- No contract changes and no invoice goes out.
Property management: the prior manager's handover files
- Handover files become an onboarding checklist and setup sheets: vendors, contracts, insurance and reserve components.
- The prior manager's accounts are mapped to your chart of accounts line by line, for your accountant to approve.
- Homeowner and tenant balances never pass through it.
// Same and different
What every inherited set of records has in common
A closed deal is the answer key. Each of these tests runs on an acquisition you already integrated, because your team's finished setup shows what right looks like. The seller's records go in as they arrived, before anyone cleaned them, and every draft is scored against what your team built from them. The reviewer is often whoever ran that part of the integration, sometimes working with a longtime employee of the company you bought.
Records travel with the deal, and the originals stay put. Federal privacy law makes room for customer records changing hands in a sale: the Gramm-Leach-Bliley Act's notice and opt-out rules carry an exception for disclosures made in connection with a proposed or actual sale, merger or transfer of all or part of a business, at 15 U.S.C. 6802(e)(7). Whatever that allows for the deal, the test runs under its own NDA, on copies. The seller's own files still have to be kept, too. The IRS's general rule is to keep records for three years, and records about property until the limitations period ends for the year the property is disposed of. So the test reads copies and deletes nothing.
Some contracts need someone else's yes. Buying the stock rather than the assets doesn't always avoid a consent. In 2021, when a fund's subsidiary agreed to buy the stock of GreenWaste Recovery, the Town of Atherton, California, treated the purchase as a voluntary assignment under its franchise agreement, which allowed no transfer, a change of control included, without the town's prior consent. Private professional contracts carry similar terms: section 10.3 of AIA's owner-architect agreement, B101, bars either side from assigning it without the other's written consent, apart from the owner's lender. That is why the waste page holds franchise accounts at their approved rates and the engineering page records each contract's status. Consents themselves stay with your people.
Old addresses keep working after the close. An add-on's EDI customers send every interchange to the receiver ID the add-on published, the ISA08 field of the X12 envelope, so those orders keep landing in its system until each trading partner is moved; the distributor test takes the POs that still arrive by email. Rental money has its own path. When a California landlord's interest ends by sale or otherwise, Civil Code 1950.5(i) has the landlord pass what remains of each deposit to the successor and tell the tenant, or return it with an accounting. On none of these pages does the AI post a balance, move money or change what a customer pays.
What changes is the shape of the records. Item numbers and units at a distributor, agency structure and carrier names at an agency, rate codes and fees at a hauler, phases and labor categories at an engineering firm, a chart of accounts and reserve components at a management company. Each job page carries its own detail, what to send, how the test is scored and its one hard limit. The scope stays narrow on every one of them: one job's records in the months after a close. The migration, the system cutover and the integration plan stay with your team and whoever you hire to run them.
// How it runs
Three steps, starting from a deal you closed
- Step 01
Copies from one past deal
Once the NDA is signed, send 20 to 30 records from a company you already bought, as the seller kept them, plus what your team set up from them. Nobody signs in to either company's system, and if files can't leave the building, your reviewer helps build look-alikes.
- Step 02
Your reviewer decides
First, the owner picks the reviewer, settles the success criteria in writing and gets a price range for the live job. From then on the reviewer scores every draft against the setup your team built.
- Step 03
About 30 days on live records
After a yes, the same job runs for about 30 days on the next company you buy, or on records still waiting from the last one. A person approves every draft before anything is entered.
Priced per job: a range before the proof of concept, a fixed price before you sign.
The range follows how many records a typical acquisition brings and how far its old setup sits from yours.
// Questions
Questions from companies that buy companies
Do you run the integration or the system migration?
We buy a company every few months. Do we test each one?
Is this only for private equity platforms?
Which job should we test first?
What happens to the seller's systems and records?

Rob Eason, founder
// Book a proof of concept call
Start with a deal you've already closed.
A 30-minute call with Rob. Tell him your company and role, which acquisition you'd test on, and roughly how many records it brought over. Send no files until the NDA is signed.
- Co-owned a 60-employee financial services firm and sold his share to his partner.
- Ran GOSO Technologies, a Boston solar company rated 5/5 across 24 Google reviews.
- 5/5 across 83 reviews in HighLevel's Certified Admin Directory.
- 4.3/5 from 6 Google reviews of Massmarket AI.
- Every directory and Google review, critical ones included, is shown word for word at massmarket.ai/reviews.
- Takes every proof-of-concept call himself.
