MSP Asset Purchase: Define What You Receive and Owe

Reconcile the Proposed Book Before Counting Its Fees

Assume a hypothetical book contains 35 clients, each with 20 seats billed at $225 per seat monthly. The starting calculation is 35 × 20 = 700 seats, then 700 × $225 = $157,500 in monthly managed fees. That arithmetic assumes every listed client belongs in the purchase and the stated service and fee continue.

Now assume the inclusion of a client with 20 seats remains unresolved. Its monthly fee is 20 × $225 = $4,500, so the remaining proposed fees are $157,500 − $4,500 = $153,000. Put the $4,500 in the unresolved column until the responsible reviewers settle its treatment; don't call it transferred revenue because it appears in the seller's export.

Keep included, excluded, and unresolved entries mutually exclusive when reconciling the totals. Otherwise you can count the same agreement in the operating forecast and in the exception list. This calculation checks the scope of your assumptions, not client retention or the price you should pay.

Give Each Item a Receiving Owner and a Condition

Have your transaction counsel establish the document references and the conditions for the proposed transfer. A condition is something that must be resolved under the agreed terms before the relevant action can proceed. Your role is to provide complete records and make the delivery consequence of an unresolved item explicit.

Use a schedule the commercial and technical teams can read together. Keep the treatment of each item separate from evidence that the receiving person can use it. A contract marked for inclusion and a working support login answer different questions.

A blank status is not a decision. Use an explicit unresolved status when the evidence is missing, and record who must provide it. If the answer changes the supported scope or costs, take that change back to the transaction decision before updating the operating plan.

Track Contract Decisions Without Making Them on the Desk

For each client, give counsel the agreement actually in force, including the amendments you have located. Ask them to determine which transfer steps and client actions apply to the proposed transaction. Record their conclusion beside the document reference, with the person responsible for following it through.

Keep a client's commercial agreement separate from a convenient contact record. Identify who coordinates any required communication and what can be said at that stage. Don't let a technical request for credentials become an unplanned announcement of a transaction still being negotiated.

If an agreement's treatment remains unsettled, show the operating consequence. That might mean holding the corresponding fee out of the confirmed forecast or delaying a handover task, depending on the advisers' decision. Don't use a generic claim that all contracts transfer, or none do, in place of checking the actual arrangement.

Confirm Vendor Arrangements Before Planning Their Use

Ask the seller to identify each relevant vendor account and the commitment behind it. Reconcile those records with the tools your team expects to use for the acquired clients. Ask the vendor and your advisers what the proposed change requires rather than assuming the seller's login or subscription can simply become yours.

Give every unresolved vendor item a temporary operating plan. Record who will provide the service while the arrangement is being settled and the cost your finance team should use. Avoid forecasting a saving from removing a tool until delivery has confirmed the replacement work and the responsible reviewer has settled the commitment.

Keep client-owned equipment distinct from equipment being sold by the MSP. Have the advisers settle ownership questions, then ask the receiving technician to check the agreed inventory against the actual devices. A serial number is more useful here than a folder called miscellaneous assets.

Plan an Authorized Information Handover

Identify the information the receiving team needs for the agreed service and ask the responsible reviewers to approve how it will be shared. Keep access permissions separate from possession of a file. A copied document doesn't establish that the team has the authority or working access needed to act on it.

Have the technical receiver test the approved access with the person coordinating the handover. Check the client and environment actually reached before recording completion. Keep secrets in the approved credential system, with the handover record pointing to the record rather than repeating the secret.

Record missing information as work with an owner. Specify what the receiving technician must be able to do, and use that task to check the result. A folder delivered and an account created are activities; you still need a confirmed route for the agreed support work.

Give Continuing Work an Explicit Decision Route

Identify which work still depends on the seller after the proposed handover. Name the buyer-side person receiving that responsibility and ask the advisers to confirm the seller's continuing assignment. Build toward recurring profitable business that doesn't depend on the former owner remaining the hidden approval point.

Jenny Clift describes a previous DWM practice in which field technicians could buy a needed part within a defined spending limit, escalated larger requests, and sent the purchase to accounts for invoicing. The useful operational connection is between permission and the next person's work. For an acquired client, I would check both who can approve a replacement device and who turns the approved purchase into the correct invoice.

Don't assume the seller's authority routes will survive unchanged inside your MSP. Give the receiving team the route you have actually approved, with a contact for exceptions. Keep any staff arrangements with the people lead and advisers rather than making promises through a technical handover meeting.

Close the Schedule With Confirmed Outcomes

Review the schedule with finance and delivery before the proposed completion, the point when the purchase takes effect under its agreed terms. Take unresolved transfer questions back to counsel. Then check the operational items against the conclusions they have confirmed.

1. Finance reconciles the included fees and commitments to the proposed scope and keeps unresolved amounts separate.
2. Counsel confirms the transaction documents and identifies outstanding conditions or decisions for the deal lead.
3. Each receiving owner checks the agreed handover task and records the result against the matching item.
4. The deal lead resolves exceptions with the responsible adviser and delivery owner before treating the affected work as ready.

My preference is to approve a specific scope with visible exceptions rather than a broad promise that everything important is included. When an item changes, update the financial assumption and the receiving person's assignment together. The result you need is a book your MSP is authorized and equipped to serve, with its commitments identified before you start counting the benefit.