How to prepare succession for a managed IT services business

Define continuity from the customer's perspective

For each customer, map services, SLA, hours, escalation, renewal, termination, pricing and named service owner. Add the systems and vendors required to deliver. A successor needs to see how a ticket becomes a response and how an incident becomes an escalation.

The Swiss SME Portal says documented processes and shared know-how reduce key-person dependence. Its succession financing guidance also recommends consistent management information and clear responsibilities.

Build a contract and margin baseline

An MSP can invoice monthly while carrying very different revenue risks. For each customer, separate the managed-service base fee, per-user or per-device charges, cloud consumption, licence resale, hardware, projects and emergency work. Reconcile the register to invoices and accounting, then identify notice periods, automatic renewal, indexation, service credits, minimum commitments, assignment and change-of-control provisions.

Calculate service margin using a stable policy. Include service-desk and engineering time, monitoring and security tools, vendor support, hosting and other direct delivery costs. Show central overhead separately and disclose where time records or allocations are estimates. A customer with high revenue but extensive undocumented support may contribute less transferable earnings than the headline suggests.

Customer diagnostic

• Annualised contracted fee and variable elements
• Gross margin under the documented allocation policy
• Contract end, renewal and earliest termination date
• Open service credits, disputes and unbilled work
• Primary and secondary relationship owner
• Vendor, licence and subcontractor dependencies
• Consent, assignment and control-change requirements

Aggregate concentration by customer group, not only billing entity. Then stress the operating plan for the earliest possible loss of a major account without inventing a probability of departure.

Test vendor, security and data responsibilities

Map every critical platform to commercial owner, technical owner, backup person, contract, renewal, certification requirement, tenant arrangement and exit method. Confirm whether licences can be reassigned, whether partner status depends on named people or revenue thresholds, and how customer data can be exported and deleted. Do not assume a portal login proves the company owns the underlying relationship.

For privileged access, record who can enter each customer environment, how approval works, where secrets are stored, how emergency access is logged and how access is removed. Review customer separation, endpoint and network tooling, backup immutability where used, restore testing, vulnerability handling, incident records and notification duties. The Swiss Federal Office for Cyber Security describes baseline protection as a combination of governance, inventory, protective measures and recovery planning in its current baseline guidance.

A buyer will also ask which party is controller or processor for personal data, which subprocessors are involved and where data is stored or accessed. Build the map from actual contracts and systems. Legal conclusions and cross-border questions require qualified review.

Build a service team with real backup depth

List sales, onboarding, service desk, engineering, security, billing and vendor management decisions that still require the owner. Name an authorised primary and backup for each. Give the backup supervised practice, not merely a document.

Run controlled absence tests: can the team handle a priority incident, approve an exception, restore a backup and brief a key customer without the founder? Record where escalation stalled. Link remediation to the founder dependency plan.

Use one continuity matrix

Add every critical platform and material customer exception. Link to controlled evidence rather than copying it, and record the last successful test and remediation owner.

Set decision rights before the handover

Write a transition governance sheet covering commercial approvals, service-risk acceptance, security exceptions, hiring, supplier changes, customer communication and incident authority. Name the person who decides before completion, during any overlap and after completion. Where the former owner remains involved, define hours, response expectations, access, reporting line and end date rather than relying on goodwill.

Prepare a decision log for exceptions that could outlive the transaction, such as an unsupported system, an SLA concession or a temporary shared process. Record the customer affected, risk, compensating control, approver, review date and closure evidence. The successor should understand inherited exceptions before accepting responsibility.

Staff retention discussions also need evidence. Map roles, notice periods, on-call responsibilities, restrictive clauses where valid, training needs and succession coverage. Do not promise that named employees will remain. Show instead how knowledge, authority and customer trust are being distributed and how departures would be handled.

Design and test a 90-day transition

A transition plan should name decisions, not only meetings. Divide the first 90 days into pre-completion preparation, controlled handover and stabilisation. For each item record current owner, successor, evidence, rehearsal date, customer communication trigger and fallback.

Consider an illustrative MSP with CHF 1.8 million annual revenue. A customer representing CHF 360,000 has a 60-day notice period, the founder owns its executive relationship, and only one engineer has completed a restore for its primary workload. The 20% concentration is a diagnostic, not a benchmark or automatic valuation adjustment. Review contract economics and service history, introduce a second relationship owner at the authorised time, train a second engineer and complete a witnessed restore. Record the result, exceptions and next test.

During transition, monitor SLA attainment, ticket backlog, recurring margin, customer escalations, staff departures, privileged-access exceptions, restore outcomes and vendor notices. Define who may change pricing, staffing, tooling and risk acceptance. Weekly review should close actions rather than merely report them. If an incident occurs, customer protection and contractual duties take priority over presenting a smooth transaction.

Stage the handover and communication

1. Confirm route, authority and confidentiality group.
2. Close critical contract, access and backup gaps.
3. Agree leadership roles and decision rights for transition.
4. Prepare staff, vendor and customer messages with timing and owners.
5. Introduce the successor to priority relationships when authorised.
6. Track SLA, churn, staff departures and incidents through the handover.

A handover plan cannot guarantee customer retention. It can show that responsibilities, evidence and contingencies have been considered.