{"id":1237,"date":"2026-11-17T07:02:34","date_gmt":"2026-11-17T12:02:34","guid":{"rendered":"https:\/\/vight.ai\/blog\/msp-model\/"},"modified":"2026-11-17T08:13:35","modified_gmt":"2026-11-17T13:13:35","slug":"msp-model","status":"publish","type":"post","link":"https:\/\/vight.ai\/blog\/msp-model\/","title":{"rendered":"The MSP Model Explained: How Managed Services Make (or Lose) Money at the Service Desk"},"content":{"rendered":"<p>You sign a 40-seat client at a flat monthly fee. Six months in, the agreement looks fine on paper: the invoice goes out, the client pays, the time logged against them is reasonable. Then a tech mentions that the office manager calls &quot;a couple of times a day,&quot; and you realize half of those calls never became a ticket, and the ones that did say &quot;assisted user, 0.25.&quot; Under break-fix, that client would be one of your best customers. Under managed services, they might be your worst, and your reports can&#039;t tell you.<\/p>\n<p>That inversion is the whole MSP model in one sentence: <strong>you stop selling hours and start selling an outcome for a fixed price, which turns every hour of work from revenue into cost.<\/strong> The rest of this guide covers how the model makes money, where it quietly loses money, and what to measure so you know which one is happening on each agreement.<\/p>\n<h2>What is the MSP model?<\/h2>\n<p>The MSP (managed service provider) model is a way of running an IT services business where the provider manages a client&#039;s IT under an ongoing agreement for a recurring fee, usually per user, per device or as a tiered bundle, instead of billing by the hour when something breaks. The provider takes on the risk of how much work the client will need. Profit on each agreement is the recurring fee minus what it actually costs to deliver: technician time, tool licensing and overhead.<\/p>\n<p>The model works when the provider can make the client&#039;s IT steadier over time, so the work needed per user falls while the fee stays flat. It fails when the provider can&#039;t see how much work each client really takes. For background on the term and its history, see the <a href=\"https:\/\/en.wikipedia.org\/wiki\/Managed_services\">managed services article on Wikipedia<\/a>.<\/p>\n<h2>Break-fix vs. managed services: who holds the risk<\/h2>\n<p>The easiest way to understand the MSP model is to compare it with what it replaced.<\/p>\n\n<figure class=\"wp-block-table\"><table><tr>\n<th><\/th>\n<th>Break-fix<\/th>\n<th>Managed services (MSP model)<\/th>\n<\/tr>\n<tr>\n<td>How you get paid<\/td>\n<td>Hourly or per incident<\/td>\n<td>Recurring monthly fee per user, device or bundle<\/td>\n<\/tr>\n<tr>\n<td>Who carries the risk of a bad month<\/td>\n<td>The client<\/td>\n<td>The MSP<\/td>\n<\/tr>\n<tr>\n<td>What a ticket is<\/td>\n<td>Revenue<\/td>\n<td>Cost<\/td>\n<\/tr>\n<tr>\n<td>Incentive<\/td>\n<td>More problems, more billable hours<\/td>\n<td>Fewer problems, fewer hours to deliver the same fee<\/td>\n<\/tr>\n<tr>\n<td>What you have to measure<\/td>\n<td>Billable hours<\/td>\n<td>Effort per client against the fee<\/td>\n<\/tr>\n<\/table><\/figure>\n<p>Under break-fix, a missed time entry is lost revenue, so people chase it. Under managed services, a missed time entry doesn&#039;t cost you anything on the invoice. It costs you something worse: it hides the true cost of the agreement, so you renew underpriced contracts and can&#039;t explain why the business is busier than the margin says it should be.<\/p>\n<h2>How an MSP makes money: three lines on every agreement<\/h2>\n<p>Strip away the bundles and tiers and every managed services agreement comes down to three numbers:<\/p>\n<ol>\n<li><strong>Recurring revenue.<\/strong> The monthly fee, set by your pricing unit. We cover the units in <a href=\"https:\/\/vight.ai\/blog\/msp-pricing-models\/\">MSP pricing models<\/a> and how to define a &quot;user&quot; in <a href=\"https:\/\/vight.ai\/blog\/msp-per-user-pricing\/\">MSP per-user pricing<\/a>.<\/li>\n<li><strong>Delivery cost.<\/strong> Mostly service desk labor (reactive tickets, calls, after-hours work), plus per-seat or per-device tool costs such as RMM, security and backup licensing, plus the proactive work you promised in the agreement.<\/li>\n<li><strong>Agreement margin.<\/strong> Revenue minus delivery cost.<\/li>\n<\/ol>\n<p>The tool costs are predictable: they scale with seats or devices and you can read them off a vendor invoice. Proactive work is something you schedule. <strong>Reactive labor is the variable.<\/strong> It&#039;s the one cost that depends on the client&#039;s behavior, their environment and how well your team documents what it does, and it&#039;s the hardest one to measure.<\/p>\n<h3>A worked example (illustrative numbers)<\/h3>\n<p>Take one agreement with made-up but plausible-looking figures:<\/p>\n<ul>\n<li>Monthly fee: $4,000<\/li>\n<li>Per-seat tool costs: $400<\/li>\n<li>Loaded technician cost: $60 an hour<\/li>\n<\/ul>\n<p>If the PSA shows 25 hours of reactive work this month, the agreement looks healthy: $4,000 \u2212 $1,500 labor \u2212 $400 tools = <strong>$2,100, a 52.5% margin<\/strong>, and an effective rate of $160 an hour ($4,000 \u00f7 25).<\/p>\n<p>Now suppose the real number is 40 hours, because a stream of short phone calls never got a ticket and several tickets were closed with a quarter hour when the call ran longer. Same client, same fee: $4,000 \u2212 $2,400 \u2212 $400 = <strong>$1,200, a 30% margin<\/strong>, and an effective rate of $100 an hour.<\/p>\n<p>Nothing about the price changed. The only thing that changed is whether the work was recorded. That&#039;s why we argue in <a href=\"https:\/\/vight.ai\/blog\/msp-profit-margins\/\">MSP profit margins<\/a> that the busiest clients often look the most profitable: the more they call, the more of their work goes unlogged.<\/p>\n<h2>Where the MSP model actually breaks: the service desk, not the price sheet<\/h2>\n<p>Most writing about the MSP model spends its time on pricing: per user vs. per device, good-better-best tiers, all-you-can-eat. Those choices matter, but they&#039;re downstream of a more basic question: <strong>can you see how many hours each client actually takes?<\/strong> If you can&#039;t, no pricing unit saves you, because you&#039;re setting the price blind and renewing it blind.<\/p>\n<p>Effort tends to escape the record in the same few places:<\/p>\n<ul>\n<li><strong>Phone calls.<\/strong> A tech solves something in eight minutes on the phone and moves to the next call. Writing the ticket takes another few minutes they don&#039;t have, so it gets a one-line note, a rounded-down time entry or no ticket at all. Calls are especially easy to lose because the work is already finished before anyone opens the PSA. More on that in <a href=\"https:\/\/vight.ai\/blog\/msp-time-tracking\/\">MSP time tracking<\/a>.<\/li>\n<li><strong>Hands-on work after the call.<\/strong> Remote sessions and research that follow a call often land in a time entry written from memory at the end of the day.<\/li>\n<li><strong>After-hours work.<\/strong> On-call techs handle problems at night and enter them the next morning, if at all. If your agreement includes after-hours coverage, that&#039;s real cost; see <a href=\"https:\/\/vight.ai\/blog\/should-msps-charge-for-after-hours-support\/\">should MSPs charge for after-hours support<\/a>.<\/li>\n<li><strong>Duplicate and vague tickets.<\/strong> Three tickets for one outage, or a ticket titled &quot;help,&quot; split the effort across records and make per-client reporting noisy.<\/li>\n<li><strong>Note-writing itself.<\/strong> Documentation time is real labor under a flat fee. Whether you bill it on non-agreement work is a separate question, covered in <a href=\"https:\/\/vight.ai\/blog\/should-msps-bill-for-ticket-note-time\/\">should MSPs bill for ticket note time<\/a>, but on agreement work it&#039;s pure delivery cost.<\/li>\n<\/ul>\n<p>The point of view here is simple: <strong>the MSP model is a bet that you can measure and reduce reactive effort per user.<\/strong> Pricing is how you place the bet. The service desk is where you win or lose it.<\/p>\n<h2>What to measure on each agreement every month<\/h2>\n<p>You don&#039;t need a BI project to run the model well. You need a handful of numbers per agreement, pulled from the PSA, and you need to trust that the time behind them is complete:<\/p>\n<ul>\n<li><strong>Reactive hours per user per month.<\/strong> The core cost driver. Compare clients against each other and against their own trend.<\/li>\n<li><strong>Effective hourly rate.<\/strong> Monthly fee divided by total hours delivered. It&#039;s the fastest way to spot an agreement that has drifted underwater.<\/li>\n<li><strong>Tickets per user per month.<\/strong> Useful as a second signal, but a ticket count without time behind it can mislead you.<\/li>\n<li><strong>Share of tickets with a time entry<\/strong>, and how many of those entries sit on a round default value. A high share of default entries usually means time is being guessed, not recorded.<\/li>\n<li><strong>Calls with no ticket.<\/strong> If your phone system can report calls by client and your PSA can&#039;t show matching tickets, the gap is unrecorded work.<\/li>\n<li><strong>After-hours pages and hours<\/strong>, per client.<\/li>\n<\/ul>\n<p>We go deeper on building a weekly version of this in <a href=\"https:\/\/vight.ai\/blog\/msp-kpis\/\">MSP KPIs<\/a>, and on what these numbers mean for headcount in <a href=\"https:\/\/vight.ai\/blog\/it-staffing-ratios\/\">IT staffing ratios for MSPs<\/a>.<\/p>\n<h2>MSP vs. MSSP vs. break-fix vs. co-managed IT<\/h2>\n<p>These terms come up alongside &quot;MSP model&quot; and are often confused:<\/p>\n<ul>\n<li><strong>MSP (managed service provider):<\/strong> manages a client&#039;s IT for a recurring fee under an agreement, usually covering the service desk, device management, patching and some level of security.<\/li>\n<li><strong>MSSP (managed security service provider):<\/strong> a provider whose managed service is security specifically, such as monitoring, detection and response. Many MSPs now deliver security services too, but an MSSP&#039;s core product is security, not general IT support.<\/li>\n<li><strong>Break-fix:<\/strong> the provider bills by the hour or per incident when something goes wrong, with no ongoing agreement.<\/li>\n<li><strong>Co-managed IT:<\/strong> the client has its own IT staff and the MSP handles part of the work, such as the service desk overflow, after-hours coverage or tooling, under an agreement scoped to that split.<\/li>\n<\/ul>\n<p>The same economics apply to all the managed variants: a fixed fee against variable effort.<\/p>\n<h2>Where AI fits in the MSP model<\/h2>\n<p>AI doesn&#039;t change the MSP model. It changes the delivery-cost line, in two ways that matter for the economics above.<\/p>\n<p>First, it can <strong>recover the effort data<\/strong> the model depends on. If every support call is transcribed, matched to the client and ticket, and written up with a time entry, the phone work that used to vanish shows up in your per-client hours. That&#039;s the difference between the 25-hour and 40-hour versions of the example above.<\/p>\n<p>Second, it can <strong>cut the documentation and intake work<\/strong> that sits on top of every ticket: writing notes, chasing missing details from the requester, cleaning up titles and merging duplicates.<\/p>\n<p>That&#039;s the problem Vight is built around. It works inside ConnectWise PSA, Autotask, HaloPSA and Syncro: it pulls recorded calls from the phone system, writes a summary of the issue, troubleshooting and resolution into the right ticket as a note, and logs a time entry for the time worked. It also runs ticket agents (title rewrites, categorization, deduplication), <a href=\"https:\/\/vight.ai\/triage\">triages new tickets<\/a> in ConnectWise, Autotask, HaloPSA and Syncro by asking the requester for missing details, and can answer after-hours calls and open a ticket with the caller&#039;s details. Plans are priced by usage with unlimited users, so it doesn&#039;t add a per-technician cost to the agreement math; details are on the <a href=\"https:\/\/vight.ai\/pricing\">pricing page<\/a>.<\/p>\n<p>None of that fixes a badly priced agreement. What it does is give you the real hours per client, so you can find the badly priced ones before renewal instead of after.<\/p>\n<p>If you want to see what your phone work looks like once it lands in the ticket, <a href=\"https:\/\/vight.ai\/demo\">book a demo<\/a> and we&#039;ll walk through it with your PSA.<\/p>\n<h2>FAQ<\/h2>\n<p><strong>What is the MSP model in simple terms?<\/strong><br>An IT provider manages a client&#039;s technology for a fixed recurring fee instead of billing hours when something breaks. The provider takes on the risk of how much work the client needs, and earns its margin by keeping that work low and predictable.<\/p>\n<p><strong>How do MSPs make money?<\/strong><br>From the gap between the recurring agreement fee and the cost of delivering it, mostly technician labor and per-seat tool costs, plus project work and hardware or software resale outside the agreement. Agreement margin depends mainly on reactive service desk hours per client.<\/p>\n<p><strong>Is the MSP model more profitable than break-fix?<\/strong><br>It can be, because recurring revenue is predictable and steadier clients get cheaper to support over time. But a managed agreement can lose money in a way break-fix can&#039;t: if a client needs far more work than the fee assumed, you absorb it. Profitability depends on knowing actual effort per client.<\/p>\n<p><strong>Should MSPs price per user or per device?<\/strong><br>Pick the unit that tracks your work. If most of your effort follows people (calls, accounts, Microsoft 365), per user usually fits. If it follows endpoints, per device can. We compare them in <a href=\"https:\/\/vight.ai\/blog\/msp-pricing-models\/\">MSP pricing models<\/a>, and typical rates are covered in <a href=\"https:\/\/vight.ai\/blog\/how-much-do-managed-service-providers-charge\/\">how much managed service providers charge<\/a>.<\/p>\n<p><strong>What&#039;s the biggest risk in the MSP model?<\/strong><br>Underpriced agreements you can&#039;t see, usually because reactive work, especially phone calls and after-hours work, never makes it into the PSA with accurate time.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>You sign a 40-seat client at a flat monthly fee. Six months in, the agreement looks fine on paper: the invoice goes out, the client pays, the time logged against them is reasonable. Then a tech mentions that the office manager calls &quot;a couple of times a day,&quot; and you realize half of those calls [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-1237","post","type-post","status-publish","format-standard","hentry","category-msp-operations"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v28.8 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>The MSP Model Explained: How Managed Services Make (or Lose) Money at the Service Desk<\/title>\n<meta name=\"description\" content=\"The MSP model trades hourly billing for a fixed fee, so every hour becomes cost. How agreements make money, where they leak, and what to measure.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/vight.ai\/blog\/msp-model\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"The MSP Model Explained: How Managed Services Make (or Lose) Money at the Service Desk\" \/>\n<meta property=\"og:description\" content=\"The MSP model trades hourly billing for a fixed fee, so every hour becomes cost. How agreements make money, where they leak, and what to measure.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/vight.ai\/blog\/msp-model\/\" \/>\n<meta property=\"og:site_name\" content=\"Vight Insights | AI for MSPs\" \/>\n<meta property=\"article:published_time\" content=\"2026-11-17T12:02:34+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-11-17T13:13:35+00:00\" \/>\n<meta name=\"author\" content=\"Nathan Spitalny\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Nathan Spitalny\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"10 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/vight.ai\\\/blog\\\/msp-model\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/vight.ai\\\/blog\\\/msp-model\\\/\"},\"author\":{\"name\":\"Nathan Spitalny\",\"@id\":\"https:\\\/\\\/vight.ai\\\/blog\\\/#\\\/schema\\\/person\\\/d256cba1d191205aed6403d4604a2794\"},\"headline\":\"The MSP Model Explained: How Managed Services Make (or Lose) Money at the Service Desk\",\"datePublished\":\"2026-11-17T12:02:34+00:00\",\"dateModified\":\"2026-11-17T13:13:35+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/vight.ai\\\/blog\\\/msp-model\\\/\"},\"wordCount\":1987,\"publisher\":{\"@id\":\"https:\\\/\\\/vight.ai\\\/blog\\\/#organization\"},\"articleSection\":[\"MSP Operations\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/vight.ai\\\/blog\\\/msp-model\\\/\",\"url\":\"https:\\\/\\\/vight.ai\\\/blog\\\/msp-model\\\/\",\"name\":\"The MSP Model Explained: How Managed Services Make (or Lose) Money at the Service Desk\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/vight.ai\\\/blog\\\/#website\"},\"datePublished\":\"2026-11-17T12:02:34+00:00\",\"dateModified\":\"2026-11-17T13:13:35+00:00\",\"description\":\"The MSP model trades hourly billing for a fixed fee, so every hour becomes cost. How agreements make money, where they leak, and what to measure.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/vight.ai\\\/blog\\\/msp-model\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/vight.ai\\\/blog\\\/msp-model\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/vight.ai\\\/blog\\\/msp-model\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/vight.ai\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"The MSP Model Explained: How Managed Services Make (or Lose) Money at the Service Desk\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/vight.ai\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/vight.ai\\\/blog\\\/\",\"name\":\"Vight Insights | AI for MSPs\",\"description\":\"AI Automation, MSP Growth Strategies &amp; Smarter IT Operations\",\"publisher\":{\"@id\":\"https:\\\/\\\/vight.ai\\\/blog\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/vight.ai\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/vight.ai\\\/blog\\\/#organization\",\"name\":\"Vight Insights | AI for MSPs\",\"url\":\"https:\\\/\\\/vight.ai\\\/blog\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/vight.ai\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/vight.ai\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/vight-logo-square.png\",\"contentUrl\":\"https:\\\/\\\/vight.ai\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/vight-logo-square.png\",\"width\":800,\"height\":800,\"caption\":\"Vight Insights | AI for MSPs\"},\"image\":{\"@id\":\"https:\\\/\\\/vight.ai\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\"}},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/vight.ai\\\/blog\\\/#\\\/schema\\\/person\\\/d256cba1d191205aed6403d4604a2794\",\"name\":\"Nathan Spitalny\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/850f7fc4c9dff63a9b775252efe7c5b5bf78f8a543e3791de6c9775be5539970?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/850f7fc4c9dff63a9b775252efe7c5b5bf78f8a543e3791de6c9775be5539970?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/850f7fc4c9dff63a9b775252efe7c5b5bf78f8a543e3791de6c9775be5539970?s=96&d=mm&r=g\",\"caption\":\"Nathan Spitalny\"},\"sameAs\":[\"http:\\\/\\\/127.0.0.1\"],\"url\":\"https:\\\/\\\/vight.ai\\\/blog\\\/author\\\/user\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"The MSP Model Explained: How Managed Services Make (or Lose) Money at the Service Desk","description":"The MSP model trades hourly billing for a fixed fee, so every hour becomes cost. How agreements make money, where they leak, and what to measure.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/vight.ai\/blog\/msp-model\/","og_locale":"en_US","og_type":"article","og_title":"The MSP Model Explained: How Managed Services Make (or Lose) Money at the Service Desk","og_description":"The MSP model trades hourly billing for a fixed fee, so every hour becomes cost. How agreements make money, where they leak, and what to measure.","og_url":"https:\/\/vight.ai\/blog\/msp-model\/","og_site_name":"Vight Insights | AI for MSPs","article_published_time":"2026-11-17T12:02:34+00:00","article_modified_time":"2026-11-17T13:13:35+00:00","author":"Nathan Spitalny","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Nathan Spitalny","Est. reading time":"10 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/vight.ai\/blog\/msp-model\/#article","isPartOf":{"@id":"https:\/\/vight.ai\/blog\/msp-model\/"},"author":{"name":"Nathan Spitalny","@id":"https:\/\/vight.ai\/blog\/#\/schema\/person\/d256cba1d191205aed6403d4604a2794"},"headline":"The MSP Model Explained: How Managed Services Make (or Lose) Money at the Service Desk","datePublished":"2026-11-17T12:02:34+00:00","dateModified":"2026-11-17T13:13:35+00:00","mainEntityOfPage":{"@id":"https:\/\/vight.ai\/blog\/msp-model\/"},"wordCount":1987,"publisher":{"@id":"https:\/\/vight.ai\/blog\/#organization"},"articleSection":["MSP Operations"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/vight.ai\/blog\/msp-model\/","url":"https:\/\/vight.ai\/blog\/msp-model\/","name":"The MSP Model Explained: How Managed Services Make (or Lose) Money at the Service Desk","isPartOf":{"@id":"https:\/\/vight.ai\/blog\/#website"},"datePublished":"2026-11-17T12:02:34+00:00","dateModified":"2026-11-17T13:13:35+00:00","description":"The MSP model trades hourly billing for a fixed fee, so every hour becomes cost. How agreements make money, where they leak, and what to measure.","breadcrumb":{"@id":"https:\/\/vight.ai\/blog\/msp-model\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/vight.ai\/blog\/msp-model\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/vight.ai\/blog\/msp-model\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/vight.ai\/blog\/"},{"@type":"ListItem","position":2,"name":"The MSP Model Explained: How Managed Services Make (or Lose) Money at the Service Desk"}]},{"@type":"WebSite","@id":"https:\/\/vight.ai\/blog\/#website","url":"https:\/\/vight.ai\/blog\/","name":"Vight Insights | AI for MSPs","description":"AI Automation, MSP Growth Strategies &amp; Smarter IT Operations","publisher":{"@id":"https:\/\/vight.ai\/blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/vight.ai\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/vight.ai\/blog\/#organization","name":"Vight Insights | AI for MSPs","url":"https:\/\/vight.ai\/blog\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/vight.ai\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/vight.ai\/blog\/wp-content\/uploads\/2026\/11\/vight-logo-square.png","contentUrl":"https:\/\/vight.ai\/blog\/wp-content\/uploads\/2026\/11\/vight-logo-square.png","width":800,"height":800,"caption":"Vight Insights | AI for MSPs"},"image":{"@id":"https:\/\/vight.ai\/blog\/#\/schema\/logo\/image\/"}},{"@type":"Person","@id":"https:\/\/vight.ai\/blog\/#\/schema\/person\/d256cba1d191205aed6403d4604a2794","name":"Nathan Spitalny","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/850f7fc4c9dff63a9b775252efe7c5b5bf78f8a543e3791de6c9775be5539970?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/850f7fc4c9dff63a9b775252efe7c5b5bf78f8a543e3791de6c9775be5539970?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/850f7fc4c9dff63a9b775252efe7c5b5bf78f8a543e3791de6c9775be5539970?s=96&d=mm&r=g","caption":"Nathan Spitalny"},"sameAs":["http:\/\/127.0.0.1"],"url":"https:\/\/vight.ai\/blog\/author\/user\/"}]}},"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/vight.ai\/blog\/wp-json\/wp\/v2\/posts\/1237","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/vight.ai\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/vight.ai\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/vight.ai\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/vight.ai\/blog\/wp-json\/wp\/v2\/comments?post=1237"}],"version-history":[{"count":1,"href":"https:\/\/vight.ai\/blog\/wp-json\/wp\/v2\/posts\/1237\/revisions"}],"predecessor-version":[{"id":1238,"href":"https:\/\/vight.ai\/blog\/wp-json\/wp\/v2\/posts\/1237\/revisions\/1238"}],"wp:attachment":[{"href":"https:\/\/vight.ai\/blog\/wp-json\/wp\/v2\/media?parent=1237"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/vight.ai\/blog\/wp-json\/wp\/v2\/categories?post=1237"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/vight.ai\/blog\/wp-json\/wp\/v2\/tags?post=1237"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}