Systems and ownership handoff

What "systems" actually means here

"Systems" covers three distinct things that get lumped together but need separate attention: the software and tools the business runs on (accounting, POS, scheduling, CRM), the vendor and supplier relationships that keep operations running (who to call when something breaks, what the informal terms of those relationships actually are beyond the written contract), and the processes that exist only in the seller's head — the sequence of steps for a task that's never been written down because the seller has done it the same way for years and never needed to explain it to anyone.

The first category, software, is the easiest to inventory and transfer — it shows up on invoices and login screens. The second and third categories are harder precisely because they're relational and tacit rather than documented, and they're exactly the parts of the business most likely to quietly break within the first few months if they aren't deliberately captured before the seller leaves.

The knowledge that never made it into any document, and how to extract it

Every business has know-how that exists only because the previous owner has been doing it long enough that it became automatic — which supplier actually delivers on time versus which one just says they will, which customer needs to be handled a certain way, which step in a process exists for a non-obvious reason tied to a past problem it was created to prevent. None of this shows up in a CIM or a diligence document, because the seller usually doesn't think to mention what feels obvious to them.

The extraction method that works better than a general "walk me through how you run things" conversation is task-specific shadowing: have the seller actually do a handful of representative tasks while you watch and ask questions in real time, rather than trying to get a comprehensive download in the abstract. People are much better at demonstrating what they know than at explaining it from memory.

Prioritize the highest-risk knowledge first — anything that, if lost, would cause an immediate operational problem, like an emergency vendor contact, a critical password, or a process where getting it wrong has real cost — over lower-stakes institutional trivia, since the transition period (see the negotiation sticking points guide) is finite and you won't get to everything.

Passwords, accounts, and access — the unglamorous but critical checklist

Build an explicit inventory before closing, not after: every software account, domain registrar, hosting provider, bank and merchant account, social media account, and any shared personal accounts the business has been informally running through — a seller's personal email used for business correspondence is more common than it should be. Confirm who currently has admin access to each, and get a written plan for transferring or resetting that access at closing.

A seller who's cooperative during the deal isn't guaranteed to stay reachable or responsive after the transition period ends. Set a hard deadline tied to closing, not to "whenever it's convenient," for access transfer, and don't let critical accounts remain under the seller's control past that point, even informally.

This is worth treating as seriously as any other closing condition (see the closing conditions guide) — a business that's technically yours but where the seller still controls the domain registrar or the primary bank login is a real operational and security risk, not just an inconvenience.

When to bring in outside help vs. figure it out yourself

A fractional COO, an outsourced bookkeeper, or a transition consultant can be worth the cost when the gap between what you know and what the business needs on day one is large — particularly for a buyer moving into an unfamiliar industry, or a business complex enough that no single person can absorb everything the seller knew within a typical transition period.

The calculation is usually about opportunity cost, not just the fee: time you spend puzzling through unfamiliar systems and processes is time you're not spending on the higher-leverage work of the first 90 days (see the first 30/60/90 days guide) — retaining key employees, reassuring customers, and diagnosing what's actually working versus broken.

Don't wait until something breaks to decide you need help. If you already suspect during diligence that a particular area — bookkeeping, a technical system, an operational process — is going to be beyond what you can absorb solo in the transition window, line up the outside help before closing rather than scrambling for it after a problem has already surfaced.