Transaction Preparation

Reducing founder dependence before a transaction.

How operating responsibility, commercial records, and management visibility shape the business presented for review.

A founder may hold the customer relationships, pricing judgment, technical knowledge, and day-to-day authority that keep a business moving. Preparing for a transaction requires an account of how those responsibilities are shared and how the business would operate through a change in ownership.

Locate the operating dependencies.

The starting point is a practical review of recurring decisions. Who approves a quotation? Who resolves a delivery problem? Who knows why a major customer renewed, or where a contract is stored? Where does the team still wait for the founder before it can proceed?

The purpose is to identify which activities depend on personal knowledge, individual relationships, or undocumented authority. An organization chart alone will not answer those questions. The review needs to follow how work actually moves through the business.

Make responsibility transferable.

A documented process becomes useful when someone other than the founder can operate it. That requires a named owner, defined decision rights, access to the relevant information, and a clear route for exceptions.

For a commercial process, preparation might include shared account histories, pricing parameters, proposal records, and a documented handover from sales to delivery. For operations, it might include scheduling authority, quality controls, supplier responsibilities, and a repeatable reporting cycle.

Automation can support these arrangements once the underlying responsibilities are clear. The design should specify who reviews exceptions and who is accountable for the outcome. Replacing an informal task with an automated workflow does not, by itself, resolve dependence on one person.

Build an operating record that can be examined.

Transaction preparation needs evidence that the revised processes work over time. A new procedure or dashboard is a starting point. Consistent use, management participation, and traceable records provide a stronger basis for discussion.

Commercial visibility
A consistent account of customer relationships, contracted work, pipeline assumptions, and responsibility for each next step.
Operating continuity
Evidence that recurring delivery, reporting, and approval tasks can be completed by the responsible team.
Management readiness
People who can explain their functions, discuss the supporting information, and identify unresolved issues.

Connect the work to transaction preparation.

These changes should inform the materials presented to a counterparty. Management responsibilities, operating information, and the proposed role of the founder after a transaction need to tell a consistent story. Outstanding dependencies should be described clearly rather than left for another party to discover.

Some work can begin well before a transaction timetable exists. Other issues may remain part of the negotiation around transition, continued involvement, or execution risk. Preparation creates a more specific basis for those discussions; it does not predetermine a valuation or a transaction outcome.

We see commercial and operational preparation as part of the advisory process. The objective is to make the business more understandable, its responsibilities more durable, and its remaining dependencies visible before a formal review begins.

All insights

Define the mandate.

Tell us the capital requirement, transaction objective, or counterparty profile. We will assess the scope and fit.

Discuss a mandate