← Back to blog

MSP Service Catalog: What It Includes and How to Read One

November 3, 2026
MSP Service Catalog: What It Includes and How to Read One

An MSP service catalog is the written menu of everything a managed service provider sells: each service, what it covers, what it costs, and what response and delivery times to expect. If you run a provider, it is the document that keeps sales, engineers and clients describing the same thing. If you buy from one, it is the best way to see what you are actually getting before you sign.

This guide covers both sides: what belongs in a catalog, which items most providers list, how to build and maintain one, and what a business owner should check before trusting one.

Mindpodtech
Make IT Services Clearer
Mindpod helps smaller companies plan practical technology, security, cloud and backup services without building a large internal team.
Explore Mindpod’s services

TL;DR

  • A catalog lists each service with a plain-language description, price or price range, service levels, dependencies and how to request it.
  • It describes services from the customer's point of view: benefits, outcomes and deliverables, not internal procedures.
  • Core items usually include monitoring, a ticketed service desk, patching, backup and recovery, security and cloud management.
  • Buyers should compare the catalog to the contract. Anything not written down in both places is a future dispute.
  • Providers should build it by inventorying services, writing, pricing, grouping, setting service levels, testing, publishing and then updating it as offerings change.

Table of Contents

What an MSP service catalog is

MSPAlliance, a professional body for managed service providers, describes the catalog as a comprehensive listing of the services an MSP offers, with descriptions, pricing and scope. The same source frames it as a sales and marketing tool too: it communicates the value of each service and gives the provider a natural way to upsell and cross-sell.

Two audiences read it, and a good catalog serves both:

  • Prospects and clients want to know what is covered, what is extra and how to ask for help.
  • The provider's own team needs the same definitions so that what sales promised matches what engineering delivers.

The point of the customer-facing version is perspective. Oregon's Enterprise Technology Services, for example, writes its service catalog from the customer's point of view, stressing benefits, outcomes and deliverables rather than internal support processes. A line reading "Tier 2 escalation via PSA queue" tells a business owner nothing. A line reading "A technician responds to your ticket within the stated window and fixes or escalates it" does.

Catalog versus a consulting menu

A managed services catalog and a consulting menu look similar but behave differently. Info-Tech Research Group notes that MSP catalogs center on recurring, bundled operations such as managed network services, while consulting catalogs cover project-based work with a defined start and end. That difference changes how you read the document:

Managed services catalogConsulting or project catalog
BillingRecurring, often per user, device or serverFixed fee or time and materials
DurationOngoing, with renewal termsDefined start and end
What you checkService levels, coverage hours, exclusionsDeliverables, milestones, acceptance criteria
Main riskScope creep and unlisted extrasUnclear end state

Many providers publish both in one document. If yours does, make sure you know which lines are monthly commitments and which are one-off projects.

What goes into a customer-facing catalog

Be specific about each entry. Every service should answer the same set of questions in the same order, so you can compare lines at a glance.

ElementWhat it should sayWhy a buyer cares
Description and benefitWhat the service is, its purpose, the outcomeYou can tell if it addresses your problem
Price or rangeUnit (user, device, server), billing periodYou can budget and compare
Service levelsResponse, resolution and delivery targetsYou know what to hold the provider to
Availability hoursBusiness hours, after hours, 24/7Avoids surprises during an outage
DependenciesPrerequisites and linked componentsYou know what must be in place first
Security detailsControls, access, data handlingSupports your own risk review
How to request itPortal, email, phone, approvalsFewer delays when you need something

This list follows the guidance published by a service-management software vendor on customer-facing catalogs; the elements are consistent with how public-sector catalogs are written.

Dependencies get skipped most often, and they cause the most friction. If endpoint detection requires a particular operating system version, or backup restores require a certain license, the catalog should say so before you order, not after the first failed restore.

Common items you will see

Most catalogs are variations on the same core. TechTarget's glossary of managed services lists remote IT management and monitoring, IT support, data backup and recovery, cybersecurity and cloud services management as typical offerings, and says managed security can include security monitoring, vulnerability risk assessment, threat intelligence, and intrusion detection and response.

A second TechTarget piece names three foundational deliverables: 24/7 remote network monitoring, a service desk and vendor management. It adds that monitoring commonly includes patch management, antivirus and antispam updates, disk optimization and backup monitoring. Note the date on that guidance (2008): the building blocks have held up, but today's catalogs usually add identity, cloud and security services on top.

That layering matches what ChannelPro describes for a fully managed contract. It lists help desk, patching, monitoring and backups as the included services, with security, cloud, compliance and virtual-CIO services as upsells. So when you read a catalog, sort each line into one of three buckets:

  1. Included in the base fee. Usually help desk, monitoring, patching, backup monitoring.
  2. Optional add-ons. Security stack, compliance support, strategic advisory.
  3. Billed separately. Projects, hardware, after-hours emergencies, onboarding.

If you cannot tell which bucket a line belongs in, ask. That ambiguity is exactly what a catalog exists to remove.

How to read a catalog before you sign

A catalog is more than marketing. MSPAlliance points out that a well-documented catalog works as a legal safeguard, because clear terms and conditions reduce the risk of disputes over scope of work. Use that. Here is a practical review sequence.

1. Check that every service has a measurable level

"Fast response" is not a service level. A response time per priority, with the hours it applies to, is. Ask also how response differs from resolution: a technician acknowledging a ticket in 15 minutes is not the same as your email working again.

2. Find the exclusions

Look for what is not covered: hardware replacement, line-of-business applications, on-site visits, projects such as migrations. Write the exclusions you care about on a single page and ask the provider to confirm them in writing.

3. Compare price units

Providers price per user, per device, per server or as a flat fee, and the totals are only comparable once you convert them to the same basis. Count your own users, workstations and servers first, then multiply.

4. Match the catalog to the contract

The catalog is only as useful as its link to the agreement. Confirm the master services agreement references the catalog, and that you have the version number or date that applies to you. Ask what happens when the provider updates the catalog during your term.

5. Match the services to your risk

NIST's guide to buying IT security services advises assessing a provider against your needs and against the provider's qualifications, capabilities, viability, and ability to protect your systems and information, with the depth of review depending on how critical the service is and your organization's risk. A help desk and a managed security service do not deserve the same level of scrutiny. The guide is from 2003, but the evaluation logic still applies; check current guidance for specifics.

6. Ask who does what

Cloud and security services split duties between you and the provider. If a catalog line says "managed Microsoft 365 security," ask who owns user offboarding, who approves access changes and who responds to alerts at 2 a.m. The idea of a shared responsibility matrix is well developed in security frameworks; a walkthrough of how shared responsibility maps to ISO 27001 controls shows how to turn vague promises into named owners for each control. If your provider cannot answer in that format, treat it as a warning sign.

What the money looks like

Published prices in this market move, so treat any figure as a snapshot. Reporting from the 2018 IT Nation Connect conference described three example tiers of MSP services at $125, $175 and $250 or more per user per month, distinguished by how much security was bundled in. A more recent startup guide for new providers lists workstation tiers of $50 to $75, $90 to $125 and $150 to $225 per device per month, and $150 to $300 per server per month. These are an advisor's illustrations rather than market quotes, and your price depends on region, environment and scope.

What the figures do show is the pattern: tiers are usually built on how much security, monitoring depth and response speed you get. When a provider's catalog is cheaper than that pattern, look for what has been left out. When it is far more expensive, check what is bundled in that you would otherwise buy separately.

Costs you may be paying elsewhere also belong in the comparison. Licenses and SaaS subscriptions often sit outside the managed fee, and reviewing them is worth doing in its own right: our guides on Microsoft 365 license optimization and SaaS cost optimization cover that.

What the money looks like

How an MSP builds and maintains a catalog

If you are on the provider side, the build is a sequence, not a document-writing exercise. A practical order:

  1. Inventory what you actually deliver. List every recurring task your team performs, not what the website says. The gap between the two is where margin leaks.
  2. Write each description from the client's view. Purpose, benefit, what the client gets. Leave internal tooling out.
  3. Price each service. Choose a unit, set tiers, and state what the price excludes.
  4. Group logically. Support, security, backup and recovery, cloud, advisory. Three to six categories is easier to scan than fifteen.
  5. Define service levels and request paths. Response and resolution targets, hours, and how a client asks for something.
  6. Test with real customers and staff. Ask a client to find how to request a new user account using only the catalog.
  7. Publish and set a review cadence. Quarterly is a reasonable default; update whenever a service or tool changes.

This sequence tracks the build process outlined in vendor guidance: inventory, describe, price, group, set service levels, test, publish, update.

Two failure modes deserve attention. The first is the "hero worker" trap. Info-Tech warns that organizations without defined catalogs often scale poorly because delivery depends on individuals rather than standardized processes. If one engineer knows how a service really works, it is not yet a catalog item. The second is drift between the public catalog and the internal fulfillment steps. NinjaOne's guidance stresses aligning internal and external catalogs, because gaps between technical steps and customer expectations break consistency.

Public-sector examples show what mature fulfillment looks like. North Carolina's Department of Information Technology describes catalog requests fulfilled through defined workflows, alongside incident and problem management. Platforms for MSPs follow the same idea, for example by organizing services into categories, publishing them in client self-service portals and automating workflows. Tooling is optional at first; a clean, versioned document beats an unmaintained portal.

Our perspective

We read a lot of service catalogs on behalf of small and midsize businesses, and the pattern is consistent: the weak ones describe tools, the strong ones describe outcomes and owners.

Our view is that a catalog should be a decision document, not a brochure. Before a business owner signs, each service should have a named outcome, a measurable service level, a stated price unit and an explicit line for what is not included. If a provider cannot produce that, the problem is usually not the paperwork but the delivery behind it.

We also think the catalog should be paired with a plan the client owns. That is how we approach engagements: start with a free technology assessment, turn the findings into a prioritized plan written in plain language, and let the client keep it, whoever ends up delivering it. A catalog tells you what a provider sells. A plan tells you which of those things you need, in what order, and why.

For smaller companies that cannot afford a full internal technology team, this matters more than any tier name. Buy the services that map to your actual risks and workflows, and skip the rest.

jaras

Where Mindpod fits

If you are comparing providers and are not sure which catalog lines you need, we can help you sort that out first. Our engagements begin with a free technology assessment that produces a prioritized, plain-language plan you own, and we can then deliver and run it. Depending on your gaps, that may involve fractional CTO leadership, cloud cost and architecture work or AI governance.

Mindpodtech

If you are an MSP yourself, our vertical agent packs include tier-1 ticket triage, and MITB is built for autonomous IT operations across Microsoft, Entra and Azure. Start at mindpodtech.com and book the assessment.

While you evaluate, these related guides help you test what a provider claims: the security hardening checklist, the Microsoft 365 security baseline and the NIST CSF 90-day plan.

FAQ

What is included in a service catalog?

Each entry normally has a description and benefit, a price or range, service levels, availability hours, dependencies, security details and instructions for requesting the service. Public-sector catalogs also frame everything from the customer's point of view, focusing on outcomes and deliverables. If an entry lacks a service level or exclusions, ask the provider to add them.

What is an MSP service?

An MSP service is an ongoing IT function a provider runs for you under a recurring fee, such as remote monitoring, a help desk, patching, backup and recovery, security monitoring or cloud management. It differs from break/fix work, where you pay only when something fails. The catalog tells you which of these functions are bundled and which cost extra.

What are service catalog items?

Catalog items are the individual, requestable offerings in the catalog, for example a new-user setup, a backup restore, a managed endpoint tier or a security assessment. Each item should have a description, an owner, a price or approval path and a target delivery time. Larger catalogs group items into categories so clients can browse them.

Does an MSP service catalog replace the contract?

No. The catalog describes the services; the contract makes them binding. Check that your agreement references the catalog and the version that applies, and ask how changes to the catalog are communicated during your term.

Sources