IT Due Diligence Checklist: Prove Your MSP Tool Costs

Show What the Tool Cost Actually Covers

Due diligence is the examination of the business and its supporting records before a transaction. For the tool stack, prepare a record that connects supplier commitments to the service you deliver. Don't present a logo list as the evidence behind an annual cost.

Separate the tools you use to deliver managed services from products resold to clients. The model carries those on different revenue and cost lines. Adding recurring product purchases to the delivery-tool total would make the comparison with $22.50 inconsistent.

For the model example, 700 times $225 is $157,500 in monthly managed-services revenue. Divide $15,750 of tools by $157,500 and the result is 10%. Keep both numerator and denominator visible, because a ratio without its scope is easy to misread.

Use your actual supplier invoices and commitments for the business record. Include a clear period and identify the quantity each charge covers. If a credit or an annual payment affects the period, reconcile it rather than comparing cash paid in a month with a monthly service cost.

Build the Evidence Beside the Stack

Map each tool to its delivery purpose and the client population it supports. Then provide the commercial and operating evidence for that mapping. The checklist below covers the tooling part of preparation; the rest of the transaction needs its own work.

Keep the record current enough to reproduce, with its source and owner. An unexplained difference should have an investigation attached to it. Don't force the totals to agree by changing the supported seat count until the ratio looks familiar.

In vendor operating advice, Derik Belair recommends mapping tools to their functions and service offerings, then examining where they add customer or strategic value. He also cautions that frequent switching can discard technician familiarity. That is his recommendation, not evidence that changing to a particular stack increases a sale price.

Reconcile the Managed Inventory

RMM means remote monitoring and management, the tooling used to oversee and manage endpoints remotely. Use its records as part of the inventory reconciliation, rather than treating the dashboard total as the whole supported estate. Check differences against the agreed client scope and the relevant source records.

Give apparently obsolete or unexplained entries a review owner. An entry you don't recognize may need investigation before removal. Don't delete management records merely to make the dashboard presentation tidier for a prospective buyer.

Check who owns the policies and automation used in delivery. Record the purpose and the controlled place where changes are maintained. If a script depends on an undocumented personal resource, show that dependency and the plan to resolve it.

The model calls for one standard technology stack with every technician trained on it. Establish where the deployed environment matches that standard and where it doesn't. A shared vendor name doesn't prove consistent configuration or a usable procedure.

Show the Cost of Exceptions

An exception register should identify the service difference and its actual operating consequence. Record extra supplier commitments separately from the labor needed to support it. Don't assume every exception is unprofitable or that standardizing it produces a fixed saving.

Use the model's cost as a comparison only while holding its assumptions clear. At 700 seats, its $22.50 per seat gives the $189,000 annual tool line. If your supported scope or supplier commitments differ, the model total doesn't establish the cost your business should report.

When proposing a change, calculate the supplier costs that would actually stop and the costs that would begin. Add implementation work and any overlapping commitment to the plan. A cancelled console entry is not evidence that the corresponding payment ended.

Separate a recurring saving from a one-time change cost. If the proposal needs engineering capacity, name the work it displaces. Don't present that time as free because the engineer already has a salary.

Separate Preparation From a Valuation Claim

EBITDA is earnings before interest, tax, depreciation, and amortization. A recurring cost reduction can affect that earnings measure only to the extent it changes the business's actual costs after related effects. A forecast alone isn't a realized improvement.

A standard stack doesn't have a fixed valuation premium in the model. Nor does the model assign a deal-price adjustment to a clean RMM dashboard. Show the operating evidence and actual financial result instead of inventing a multiple uplift for the checklist.

In an exit-planning account, Ray J. Green recalls advice to think of the business as the product a future buyer would purchase. He recommends asking likely buyers which characteristics they value before directing investment toward a sale. That's his practitioner guidance, not a universal buyer requirement.

My view is that a rule of thumb is a poor substitute for a reconciled bill. If a prospective buyer wants a different tool, establish the requested change and its costs before promising it. You may otherwise spend capacity migrating a system the eventual deal doesn't require you to migrate.

Make Delivery Work Without the Owner

The model's enterprise-value position is profitable recurring revenue without reliance on the owner. Include the owner's tool administration and technical knowledge in the handoff check. An administrator list with only the founder on it leaves that dependence unresolved.

• The technical lead checks the standard and records client exceptions against the actual deployment.
• Finance reconciles the tool line to supplier records and keeps resold product costs distinct.
• The tool administrator investigates inventory differences and records the authorized resolution.
• The service lead has another qualified person use the maintained operating procedure.
• The owner assembles open supplier and transaction questions for the people authorized to resolve them.

Keep incomplete items visible with their owners and next actions. The evidence should let another person reproduce the cost and understand how the service continues. Start with the tool line in the current accounts and follow it through to the deployed population; the first unexplained difference is the next useful piece of preparation.