Flat-rate vs per-endpoint MSP pricing — decided by SMB size, not by sales pitch

Decision rule by SMB size

A per-endpoint contract bills against the device count on the floor — desktops, laptops, servers, mobile devices enrolled in MDM, and point-of-sale terminals 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. A flat-rate contract (the same shape marketed as per-seat or all-you-can-eat) bills against the count of authorized users, sometimes with a device cap inside the per-seat price — the line item is fixed by tier boundaries that are rarely published in the headline.

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 (per-seat / all-you-can-eat)

What it is. A single monthly number covers a stated scope from one authorized user up to a published tier ceiling, sometimes with a device cap inside the per-seat price. Common in SMB shops that want one predictable line item on the books — a constant read every month, regardless of bring-your-own-device churn.

What it typically hides. Tier cliffs and hidden overages. Tier 1 covers 25 users; the moment you cross 26, the entire flat-rate number jumps to the next tier — sometimes by 40% or more, with no per-user visibility into where the new money goes. A device cap is the second trap: each extra device beyond the cap is a 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 both models hide the same thing when the number is published without scope: what the line covers, what triggers a per-ticket charge, and how the SLA clock behaves under each condition. A per-endpoint contract at $189 with no SIEM bundled is not the same offer as the published baseline that bundles the eight operational layers. A flat-rate number with a tier cliff at 25 users is not the same offer as one with a soft-cap rule on every device beyond the cliff. The scope defines the line.

The decision rule

Which model tends to fit which size of Ohio SMB. These are heuristics, not promises — read against the size of your fleet and the churn in it. Many Ohio SMBs sit between two brackets; the most important signal is whether the fleet grows or stays still over the next 24 months.

• ≤ 10 endpoints, single office, low device churn — flat-rate is safe. One signed scope, one predictable line item, one renewal cadence; the per-endpoint math is harder to justify when the fleet is small enough that the volume ladder never steps.
• 10–25 endpoints, mixed hardware, predictable headcount — per-endpoint usually wins. The volume discount at 10 endpoints (10% off) and at 25 endpoints (15% off) moves the line item at the same shape as the fleet, instead of waiting for the next tier cliff.
• 25–50 endpoints, on-call need, mixed endpoint types — per-endpoint wins. The on-call engineering and SIEM layer that comes with the broader scope ride on the same per-device line, and the device-class definitions stop being a sales line at this size.
• Mixed endpoint types with a strict compliance perimeter (HIPAA / FTC Safeguards / ORC 9.64) — per-endpoint is the safer reading. Adding a server or a POS terminal mid-contract moves the line item by an exact amount instead of triggering a flat-rate tier review.
• Stable workforce, identical device profile, low byod count — flat-rate is viable. Predictability on the books is worth a small premium if the device mix will not change for the next 24 months.
• Mobile-heavy fleet, multi-office, endpoint count grows quarterly — per-endpoint is the right call. The line item moves by the next single dollar as the fleet grows, instead of waiting for the next flat-rate cliff.
• 50–100+ endpoints, IT complexity layered on top — per-endpoint wins on the math. The 50-endpoint (20% off) breakpoint is the largest published discount step; below that ceiling, the per-endpoint line item is almost always cheaper than a flat-rate tier at the same scope.

Two tools

The rule of thumb keys off employee count, endpoint count, and fleet churn — the walkthrough form on the pricing page translates those signals into the published line item against your numbers. An Ohio-based engineer reads the submission against your size bracket — replies from a real inbox during business hours.

The pricing model on the contract decides how the monthly bill steps; the helpdesk side of the contract decides what happens when an Ohio SMB owner calls at 8:42am about a stuck laptop, a VPN drop from a remote contractor, or a printer that will not talk to the server. The model chosen does not change the helpdesk experience — the same on-call rota rides on every managed endpoint regardless of whether the line item is per-endpoint or flat-rate.

The model selected at signing decides how the monthly line item steps as the fleet grows or shrinks — but the line item being signed against the SLA clock running at the helpdesk is the second question every Ohio SMB owner should ask. The same stop-clock language and business-hours wording that moves the SLA also moves the dollar.