Global MSP CommunityMSP growth · Technology partnerships

Technology & vendor partnerships · Analysis

Before you add another technology vendor

A new platform can add useful capability and an enduring delivery burden. Evaluate customer value, operating fit and exit effort together before expanding the service stack.

Offset service layers create gaps and hand-offs, contrasting with a clear enclosing frame and illustrating the operational cost of stack complexity.

Define the job before comparing the products

Start with the customer problem and the current delivery constraint. Is the proposed platform replacing an existing product, closing a capability gap or adding an alternative for a distinct customer group? Those are different decisions. A product that is attractive in isolation can still leave an MSP supporting another exception without enough demand to justify it.

Write a short service brief before the demonstration: eligible customers, expected outcome, current limitations, required integrations and the person accountable for operating it. This creates a basis for comparison and reduces the chance that a compelling feature becomes a service promise the team cannot sustain.

Follow the service lifecycle

Microsoft’s Lighthouse requirements show that management capabilities depend on conditions including licences, customer onboarding and delegated access. The precise rules are product-specific, but the evaluation lesson is broader: a feature demonstration does not establish that every intended customer can use the capability in the same way.

Walk through onboarding, routine administration, incident handling, reporting, renewal and removal. Test a representative customer and a realistic exception. Record the manual steps and which team owns them. The difficult handoffs often reveal more than a comparison of feature checkboxes.

Source context: Microsoft Learn. See source dates and limitations below.

Count costs at the service level

Include licence or consumption charges, deployment, technician training, ongoing administration, integration maintenance and escalation effort. Then add migration and exit work where relevant. Avoid assigning a false precision to unknown costs: mark the uncertainty and test the assumptions that could change the decision.

Consider an illustrative choice between a lower-priced tool needing more monthly intervention and a higher-priced tool that integrates with the existing workflow. Neither is automatically better. The decision depends on customer volume, labour effort, service quality and whether the integration actually works for the supported environment. A discount should not substitute for that analysis.

Agree the boundary of responsibility

The NCSC’s SME buyer guidance emphasises clarity about services and responsibilities when working with MSPs. An MSP needs equivalent clarity in the supplier relationships behind its own offer. Identify who handles an outage, who can access customer systems, how an incident is escalated and what information the customer receives.

Ask for the operating evidence behind a promise: current documentation, support routes, escalation procedures, export options and a workable termination process. Product evaluation is not a substitute for reviewing the applicable contract with suitable professional support where needed.

Source context: UK National Cyber Security Centre. See source dates and limitations below.

Put the proposal through a difficult customer case

Choose a pilot case that resembles the environment the MSP expects to support, including the relevant dependencies and access constraints. A clean demonstration tenant can show the intended workflow but may not reveal the work required in an existing customer estate. Write down where the pilot differs from production so that its result can be interpreted honestly.

Assign an owner to each handoff: customer approval, access, deployment, monitoring, reporting and support escalation. Time the tasks that are expected to recur. Check whether the required information can move into existing service-management processes without repeated manual transcription. Where an integration is promised, verify the current supported behaviour rather than assuming that a roadmap item is available.

Test removal as deliberately as installation. Establish how customer information is exported where applicable, how access is revoked, which dependencies remain and what work a migration would require. A workable exit does not mean that switching will be free or instant. It means the obligation is understood before the product becomes part of a recurring customer commitment.

At the decision meeting, compare the evidence with the original service brief. Record unresolved assumptions and their potential effect. If a capability is useful only for a defined customer group, that can justify a bounded exception to the standard stack. Give the exception an owner and review point rather than treating it as the beginning of unrestricted adoption.

Make the pilot a decision, not a holding pattern

Set the pilot’s customer scope, success measures and stopping conditions in advance. A useful outcome might be adoption for one clearly defined service, replacement of an incumbent, a request for specific changes or rejection. Avoid leaving pilots indefinitely active as another unowned layer of the stack.

For vendors, a transparent explanation of dependencies and limitations can strengthen partner confidence. For MSPs, the aim is a supported service portfolio with deliberate exceptions. A smaller stack is not inherently superior; a stack whose costs and responsibilities are understood is easier to govern.

A framework for the next decision

A proposed evaluation sheet; record evidence and uncertainty rather than inventing a universal score.
Decision area Evidence to request Failure signal
Customer fit Specific use case and eligible environment No identifiable customer demand
Operating fit Permissions, integrations and lifecycle test Repeated manual work without an owner
Economics Full cost and sensitivity assumptions Margin depends on untested labour savings
Support and exit Escalation, data portability and removal plan Responsibilities remain ambiguous
Scope & limitations

This is a general operating framework, not a recommendation of a particular vendor or contractual advice. Product requirements and terms should be checked at purchase. The example contains no observed cost or ROI data.

Sources & further reading

  1. Microsoft Learn: Microsoft 365 Lighthouse requirements · Live documentation checked 2026-11-15
  2. UK National Cyber Security Centre: NCSC: Choosing a managed service provider · Live guidance checked 2026-11-15

Explore the MSP programme

Connect practical analysis with peer exchange, relevant events and commercial insight.

Explore the MSP programme →