LenderHawk analysis. Not affiliated with or endorsed by Acquisitions Anonymous.
Acquisitions Anonymous brings on Dmitry Marinovich to discuss the operational side of buying a business after closing, with an emphasis on integration planning, employee retention, and the systems that can break if they are changed too quickly. The conversation focuses on practical post-close checklists for small-business acquirers, especially around banking, vendor transitions, payroll, accounting, and ERP risk.
First-time and repeat small-business buyers who need a practical playbook for surviving the first 90 days after closing.
Set up banking infrastructure before closing because vendors, payroll providers, and wire/ACH approvals can take longer than expected.
Asset deals create more post-close transition work than equity deals because vendor change-of-control forms and payment accounts often need re-underwriting.
A post-close checklist should be split into pre-closing and post-closing tasks, assigned to named owners, and stored in a system that supports notes next to each task.
The fastest way to build an integration checklist is to start with the credit card statement and follow every money flow in and out of the business.
Key employees should be contacted before close, even if the conversation is short, so they feel noticed and are less likely to leave after the transaction.
Day-one changes should focus on payroll, benefits, onboarding, and accounting systems, while larger operational changes should be phased in later.
ERP systems are high-risk to change immediately after acquisition because a mistake can disrupt operations for a prolonged period.
A dedicated integration point person is essential after closing because small requests, employee issues, and vendor follow-ups otherwise get lost.
Notion can be used to manage acquisition checklists for roughly $10 per month on a corporate subscription, or about $50 per year for a personal subscription as mentioned in the episode.
Dmitry recommends using Notion to track pre-close and post-close task lists.
Some banks require federal ID and other onboarding documents before setting up accounts, debit cards, credit cards, and wire capabilities.
The guests discuss banking setup as a pre-close integration item.
Payment processors are often personally guaranteed by the seller, so they do not automatically transfer to the buyer.
The panel explains why credit-card processing can be delayed after closing.
In one UK software acquisition, it took nearly two months for the buyer to gain access to the business’s money.
The conversation uses an international deal to show how banking and payment transitions can become slower outside the US.
The team typically meets key stakeholders two to four weeks before closing for clinical acquisitions.
Dmitry describes the timing he uses to meet employees and managers before close.
The team sometimes gives employees a $500 to $1,000 welcome bonus and a second bonus 90 days later if they remain employed.
Bill describes a retention tactic used to encourage staff to stay after closing.
For especially important employees, a stay bonus worth half a year of salary can be justified.
Bill gives a larger retention example for a critical team member.
The hosts recommend waiting about a year before touching the ERP if the buyer does not yet understand all the ways the business uses it.
The discussion warns that ERP rollouts can damage operations if done too early.
Build a pre-closing banking checklist and confirm wire and ACH permissions with the bank before closing day.
Why: Some smaller banks cannot activate transfer capabilities quickly enough, which can stall deal execution and payroll.
Collect vendor change-of-ownership forms before closing and get the seller to sign what requires the current owner’s authorization.
Why: Vendor approvals and merchant processor updates can take weeks after close if you wait until day one.
Start the integration checklist by reviewing the seller’s credit card statement and mapping every recurring payment.
Why: Anything the seller pays for is likely operationally important and will need to be transferred or replaced.
Meet key employees before closing and keep the conversation short, personal, and focused on their importance.
Why: Early relationship-building lowers the risk of losing the people who actually know how the business runs.
Avoid promising that nothing will change on day one.
Why: Change is inevitable after acquisition, and false certainty can damage trust later.
Handle payroll, benefits, onboarding, and accounting system transitions on day one.
Why: Those items are foundational and delaying them creates immediate operational friction.
Delay ERP changes until you fully understand how the business runs, and use a manual mid-layer if you need cross-company comparability now.
Why: ERP mistakes can break the business, while a manual bridge preserves operations during the transition.
After one acquisition, the buyer discovered the credit-card processor was not ready to transfer, so the seller had to funnel money to them for about a month while the buyer got set up. The story highlights how payment processing can become a hidden bottleneck if it is not addressed before closing.
Lesson: Payment infrastructure should be validated before close, not after the deal is done.
The guests described buying a software company in the UK and waiting almost two months to access the company’s money. The example shows that cross-border banking and payment transitions can be much slower than domestic deals.
Lesson: International integrations can create cash-access delays that materially affect operations.
Bill described giving new employees a small bonus immediately after close and a second bonus 90 days later, with larger stay-bonus packages for critical staff. He framed it as inexpensive insurance against early turnover.
Lesson: Retention bonuses can be a low-cost way to buy time and goodwill during transition.