Per-endpoint vs flat-rate MSP contracts — two numbers, two line items, two Ohio SMB scenarios
A close read of the two MSP contract shapes an Ohio SMB (10–50 employees) actually signs — what each one bills against on paper, what each hides in the fine print, and how each maps to a real Ohio-headquartered fleet. The benchmark is Central IT Dept's published $189 per-endpoint baseline, line-itemed in writing.
Walk into ten quote conversations as an Ohio SMB owner — Cleveland, Cincinnati, Dayton, Akron, Toledo, Canton, plus the Lancaster / Carroll corridor where Central IT Dept is headquartered — and nine of the line items on the table will sit in one of two shapes. The first is per-endpoint: a single dollar figure multiplied by the device count on the floor, with the volume discount stepping as the count grows. The second is flat-rate (often marketed as all-you-can-eat): a single monthly number covering a stated scope from a floor up to a tier ceiling, with the next device above the cliff bumping the whole line to the next tier. These two — per-endpoint and flat-rate — are the ones that compare straight across a walkthrough, and the ones to press on before signing.
An endpoint is a single device covered under a managed contract: a laptop, a desktop, a server, a phone or tablet enrolled in MDM, and a point-of-sale terminal each count as one. Network gear (firewalls, switches, access points), building gear (cameras, card readers, access controllers), and bandwidth-monitoring probes ride under the same per-endpoint contract as unbilled infrastructure — they do not add a separate line item, even when they show up as a deliverable in the attached scope. Without a precise endpoint definition, the per-endpoint and flat-rate numbers read on different scales — the way a per-endpoint $129 with no SIEM is not the same offer as a per-endpoint $189 with SIEM bundled in.
Flat-rate (the all-you-can-eat label is the same thing in marketing copy) buys a stable monthly line item on the books — one predictable number under one signed scope, regardless of fleet size, until the next tier cliff. The flat-rate line is what most Ohio SMBs reach for when they want the line item to stay still from month to month: one budget entry, one signed scope, one signed renewal cadence. The cost is that the number is fixed by tier boundaries that are rarely published in the headline. Crossing the boundary bumps the entire line item — not by the marginal device, but by the next tier. Press on the tier boundary and the soft cap before signing; both are usually buried on page two of the contract.
Central IT Dept default — Per-endpoint
What it is. Billed per device covered: laptops, desktops, servers, mobile devices under MDM, and point-of-sale terminals each count as one endpoint. Network, building, and bandwidth-monitoring gear sit on the same contract without a per-device line item.
What it typically hides. Tier-cliff-first: vendors who count "endpoint" differently, who class servers or POS terminals as a non-billable line, or who treat mobile devices under MDM as a separate add-on. The per-device line item looks the same on a quote until you read the attached scope — and the device definitions are rarely in the headline.
Typical Ohio SMB range. For Ohio SMBs with 10–50 employees, the typical published range is roughly $120 to $220 per endpoint per month. The spread is driven by what is bundled in (SIEM, on-call, MDM, network monitoring), not by the per-device number itself. The volume ladder at 5 / 10 / 25 / 50 endpoints, stepping through 5% / 10% / 15% / 20%, sits on top.
How Central IT Dept, LLC compares. Central IT Dept publishes $189 per endpoint as the Starter baseline, with the volume ladder stepping to 5% / 10% / 15% / 20% off at 5 / 10 / 25 / 50 endpoints. The eight operational layers ride on the same line item from the helpdesk through the SIEM — no scope amendment is needed at signing, and adding one endpoint mid-contract moves the line item by one $189 (or the discounted rate at the current count).
Alternative model — Flat-rate (all-you-can-eat)
What it is. A single monthly number covers a stated scope from one endpoint up to a published threshold. Common in SMB shops that want one predictable line item on the books — a constant read every month, regardless of fleet size, until the next tier cliff.
What it typically hides. Tier cliffs and hidden overages. Tier 1 covers 25 endpoints; the moment you cross 26, the entire flat-rate number jumps to the next tier — sometimes by 40% or more, with no per-device visibility into where the new money goes. A soft cap is the second trap: each device beyond the cap is per-ticket or per-month surcharge, and the surcharge code is rarely in the headline. A "flat-rate" label can also bundle less than the comparator per-endpoint line — exclude SIEM, exclude MDM, exclude network bandwidth — while still presenting as comparable.
Typical Ohio SMB range. For Ohio SMBs with 10–50 employees, the typical published range is roughly $1,500 to $8,000 per month, depending on scope. The wide spread is mostly tier boundaries and which security layers are bundled — not differences in service quality.
How Central IT Dept, LLC compares. Central IT Dept does not publish a flat-rate line item. Per-endpoint keeps every device under the same scope and steps the volume discount automatically against endpoint count — there is no tier cliff and no per-ticket surcharge, so adding a single endpoint moves the line item by exactly one $189 (or the discounted rate at the current count). The flat-rate shape is reachable on request, but the published contract shape is per-endpoint.
Both per-endpoint and flat-rate quotes land on the books as one monthly line — but what moves that line, contract to contract, is rarely the headline figure. The volume ladder at 5 / 10 / 25 / 50 endpoints, stepping through 5% / 10% / 15% / 20% off the $189 baseline, is the part most Ohio SMBs skip. Adding five endpoints should not move a vendor away from the published baseline; that is supposed to be the volume discount stepping to the next breakpoint automatically. The same is true in reverse — removing five endpoints should not unlock a penalty fee, since the discount was applied to a percent, not a contract prepay. The math at 7 endpoints, 27 endpoints, 53 endpoints, and 70 endpoints is the same logic — count endpoints, look up the breakpoint, apply the percent. The point is that the line item should never be re-quoted as the fleet grows; the discount grows with it.
Per-endpoint is right for the Ohio SMB whose headcount is growing or shifting — a Lancaster manufacturer scaling from 18 to 28 endpoints over two years, a Cleveland professional services firm onboarding four seasonal contractors, a Cincinnati multi-site operation rolling up a third office. The per-endpoint line item absorbs each change as a single multiplier: one new device is one dollar figure (or the discounted rate at the current count), and the volume discount steps automatically at the next breakpoint. The line item is honest about growth. Per-endpoint loses to flat-rate in one scenario: the static, fixed-fleet Ohio SMB — 12 endpoints at the same address for three years, no contractors, no second office, no seasonal spiking. A flat-rate contract at the right tier ceiling locks the cost down to one line item for the contract term and pays for the predictability. The model is wrong the moment the fleet moves: adding the 13th device at a fixed-fleet Ohio SMB bumps the entire line to the next tier, with no per-device visibility. Press the scenario question on every walkthrough — the right model is the one that survives the next two years of fleet change at the same scope.