> For the complete documentation index, see [llms.txt](https://help.alternativepayments.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.alternativepayments.io/analytics/benchmarking-see-how-your-msp-compares.md).

# Benchmarking: See How Your MSP Compares

**See how your MSP's financial and service performance compares to other MSPs, and where to focus next.**

Benchmarking takes the numbers already in your accounting system and PSA and compares them to the industry median, built from anonymized MSP data. It covers about 40 KPIs, split into **Finance** and **Operations**.

**All comparisons use anonymized data. No other MSP can see your numbers.**

***

## What you need

* **A connected accounting system.** Finance KPIs come from your profit and loss.
* **A connected PSA.** Operations KPIs come from your ticket data.
* **Benchmarking on your account.** It can be added on its own or alongside Analytics. To add it, reach out to your Customer Success Manager.

***

## What Benchmarking measures

| Tab        | Comes from                                                                     | Categories                                                                                                   | Example KPIs                                                                                                                                                                     | Why it matters                                                                                                |
| ---------- | ------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------- |
| Finance    | Your accounting profit and loss. Revenue mix can also use your PSA agreements. | Revenue and margins, cost structure, revenue mix                                                             | Revenue growth, gross margin, operating margin, net margin, marketing expense, sales expense, product cost, managed services revenue                                             | Shows whether your pricing and cost structure leave you with healthy margins compared to similar MSPs.        |
| Operations | Your PSA ticket data                                                           | Service outcomes, demand and backlog, workload distribution, where the hours go, capacity and unit economics | Average response time, tickets responded to within an hour, average time to close, same-day close, weeks of backlog, tickets per technician, utilization, revenue per technician | Shows whether your team keeps up with ticket demand and where technician time goes, compared to similar MSPs. |

***

## How to read a card

Each KPI shows as a card with your number next to the peer median.

* **Values or % change:** Toggle between the value for the period and the % change from the previous period.
* **Period picker:** Choose the time period the card covers.

***

## Choose who you compare against

By default, every chart compares your number to the industry median.

To compare against MSPs closer to your size, use **Compare to** and narrow the peer group by number of technicians, annual revenue, or client count. For example, you can view only MSPs with 10 to 25 technicians.

***

## Map your data

Some KPIs work as soon as your systems are connected. Others need you to tell us which of your accounts, agreements, or tickets belong in each category, because every MSP names these differently.

| KPIs                                                       | Mapping needed                                                       |
| ---------------------------------------------------------- | -------------------------------------------------------------------- |
| Revenue growth, gross margin, operating margin, net margin | None. These are pulled automatically from your accounting data.      |
| Cost structure (marketing, sales, product cost)            | Select the profit and loss line items that belong in each category.  |
| Revenue mix (managed services, cloud, resale, security)    | Select which agreements or revenue accounts belong in each category. |
| Operations KPIs                                            | One mapping: select which of your tickets are reactive.              |

***

### Map a KPI

1. Open **Benchmarking** in your dashboard.
2. Find a KPI that shows it needs mapping.
3. Tick the items that belong in that category. For example, tick "Advertising and marketing expense" for **Marketing expense**.
4. Click **Apply mapping**. The chart loads with your data.
5. Repeat for the KPIs that matter to your business.

You don't need to map everything. Start with the KPIs you care about most, and hide any that don't apply to you, such as security revenue if you don't sell security services.

***

### Good to know

* **Revenue mix can use either system.** Sort by your PSA agreements or by your accounting revenue accounts, whichever is better organized.
* **Managed services margin can include labor from other agreements.** If technicians logged time under the wrong agreement, pull that labor in so the margin reflects the real work.
* **Reactive tickets are the ones a technician worked on.** Tickets resolved by automation are left out, so response and close times reflect your team's work.

***

## Ask Alti about your benchmarks

Alti can read your benchmarking data, so you can ask questions instead of reading every chart. Try:

* "How do my margins compare to the industry?"
* "How do I increase my margins?"
* "What makes up my marketing expense?" Alti returns a month-by-month breakdown, which is the fastest way to check a mapping.
* "What does technical labor as a percentage of revenue mean, and what should I map to it?"

Alti can also turn an answer into a report or a recurring routine. See [Routine Reports](/alti/alti/routines.md).

***

## Frequently asked questions

**Who am I being compared against?**

Other MSPs. The data is anonymized, and you can narrow the peer group with **Compare to**.

**Why is there no median line on some charts?**

We show the median only once there is enough accurate data for that KPI. Until then, the chart shows your own numbers.

**A number looks wrong. What should I check?**

Check the mapping first. The result reflects the accounts, agreements, or tickets you selected. Ask Alti what makes up the KPI to see the breakdown, then adjust the mapping and click **Apply mapping** again.

**Do I have to map every KPI?**

No. Map the ones that matter to you and hide the rest.

**Do I need Analytics to use Benchmarking?**

No. Benchmarking works on its own with your accounting system and PSA. On its own, Alti's recommendations are general, such as ways to improve growth or margin. With Analytics, Alti can point to the specific clients and agreements behind a number, for example which agreements to reprice at renewal.

**Love our platform?** Check out our [Referral Program page](https://www.alternativepayments.io/referral-partners/)!


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.alternativepayments.io/analytics/benchmarking-see-how-your-msp-compares.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
