Response and restore targets by severity, coverage hours, escalation path, what is in-scope vs project work, and how exceptions are reported. If those five items are missing, you do not have an SLA — you have a hope. Production SLAs are scoped per Growth or project agreement.

What does onboarding look like?

Access, asset inventory, backup and patch baseline, ticket routing, and a named escalation list. Onboarding is complete when the first real ticket can be taken under the SLA — not when a kickoff slide is sent.

Home / Blog / Managed IT services for mid-market

September 14, 2026 Commercial Managed IT Discovery · Consulting · Starter

Managed IT for Mid-Market: MSP vs Co-Managed

Q: In-house vs outsource — which is right for mid-market IT?

Keep in-house what is unique to your business (applications, data owners, vendor relationships). Outsource or co-manage what must be covered 24/7 and what you cannot staff deeply: monitoring, patch, backup, and the after-hours queue. Co-managed is the usual mid-market fit. See /blog/co-managed-it-vs-msp/.

Q: How much do managed IT services cost at Zion?

Published entry ladder only: Discovery $99, Consulting $499, Starter ZG06 $2,500, Growth $8,000/mo on /plans/. Discovery maps ops; Consulting designs the model; Starter implements one agreed ops improvement; Growth is ongoing co-managed coverage. No invented per-seat averages.

Q: Can you support healthcare / HIPAA environments?

Yes — start with /healthcare-it-hipaa/ and the companion /blog/hipaa-compliant-it-services/ instead of a generic MSP conversation when clinical or BAA constraints apply.

Mid-market IT is rarely “fully outsource or fully in-house.” A 40–400 person company usually has an IT owner, a pile of vendors, and a gap after 6 p.m. Useful managed IT names the model — classic MSP vs co-managed — writes an SLA finance can live with, and keeps refresh next to support. This restore explains how Discovery $99 → Consulting $499 → Starter ZG06 → Growth fits, and when to Consulte instead. We will not invent uptime percentages.

See if co-managed is the right model

Discovery $99 for the IT ops map · Consulting $499 when the blocker is a decision · Pay Starter ZG06 when one owned improvement is written · Consulte when multi-site politics is the product.

Discovery $99 Pay Starter ZG06 Consulte

Service framing lives on managed IT services. The official commercial menu is plans. Model deep-dive already live: co-managed IT vs MSP. Adjacent live cuts: ITIL service desk, IT vCIO service, service desk automation, IT outsourcing. Cost and ops reinforce each other — companion restore: FinOps consulting services and hub FinOps consulting. If you are in a regulated clinical environment, start with healthcare IT / HIPAA and HIPAA-compliant IT services instead of a generic MSP conversation.

We will not invent uptime %, seat averages, named client case metrics, or open-ended “unlimited tickets” without a written catalog. Pay CTAs go to /plans/ with the label Pay Starter ZG06 — never a raw Stripe URL, never Calendly, never a dead /pricing/ door.

Model comparison: MSP vs co-managed vs staff aug

Classic MSP

The provider owns the queue, the tooling, and most of the environment. Your staff become requestors. This fits when you have little internal IT, or when you want a single throat to choke. It fits poorly when your applications team still needs admin rights and context the MSP will never have.

Co-managed

You keep identity, application owners, and business-facing IT. The partner takes monitoring, patch, backup, after-hours, and the overflow queue. Access is shared. Escalation is written. Nobody pretends one party “owns everything.” This is the model we use most for mid-market — detail in co-managed IT vs MSP and on the hub managed IT services.

Staff aug (not the same thing)

Buying extra hands without an SLA is contracting, not managed IT. Useful for a project. Fragile as a standing model — when the contractor is out, coverage is out. Choose the model by who must approve a production change at 2 a.m., not by a brochure. If that person is still yours, you want co-managed.

Hire a partner when at least two of these are true: after-hours coverage is a hope, not a roster; patch and backup tests are overdue; ticket backlog grows while projects stall; finance cannot explain what the monthly IT number includes; leadership wants AI helpers on the service desk before the queue has severity definitions. Do not hire a partner to “modernize IT” as a slogan. Hire when you need a written RACI and a first operating cut — including the decision to keep work in-house.

Need a written RACI — not another MSP brochure?

Start with Discovery $99, or Consulte when procurement needs a human before a card.

Discovery $99 Consulte

SLA that mid-market finance can live with

24/7 coverage is a coverage statement, not a promise that every ticket is P1. An SLA that mid-market finance can live with names:

Severity definitions (what is down, degraded, or a request).
Response and restore targets per severity — and whether they are clock hours or business hours.
The escalation path: who is called, in what order, including your side.
What is in-scope (monitor, patch, backup, standard requests) vs project work.
How missed targets are reported. If they are never reported, they are not targets.

We will not invent an uptime percentage for marketing. Uptime is measured on the systems you put in the contract. If a vendor leads with a number and cannot show the measurement method, treat it as decoration. Commercial response on inquiries stays within 24h; production SLAs are scoped in Consulting, Starter, or Growth — Discovery maps gaps first so you do not buy coverage you do not need.

When the first improvement is service-desk shaped, read ITIL service desk — Pay vs Consulte and service desk automation. When leadership wants a fractional decision path without a full CIO hire, read IT vCIO service. When the question is handoff vs keep, pair with IT outsourcing.

Write the SLA before you buy more tooling

Discovery $99 for the ops map · Pay Starter ZG06 when one owned improvement is written · Consulte when multi-site RACI is the product.

Discovery $99 Pay Starter ZG06 Consulte

Refresh + support (both, or the fleet ages out)

Support without a refresh plan is how mid-market shops end up with a fleet nobody will touch. The operating model should include both:

Support: the ticket, the after-hours path, and the standard request catalog (access, device, mailbox, VPN).
Refresh: a living inventory, a replacement cadence for endpoints and aging infrastructure, and a rule for when “repair” becomes “replace.”
Hygiene: patch windows, backup tests (restore, not just “job succeeded”), and a named owner for each critical system.

Refresh is planned work. It should not hide inside the monthly ticket pile. If you need the partner to run both, say so in the SOW — that is how co-managed stays honest. Cloud cost hygiene sits next door: idle environments and unowned spend show up in FinOps the same week they show up as support noise — see FinOps consulting and FinOps consulting services.

Optional AI on the service desk comes after basics are stable: known-error playbooks, governed deflection, and stop rules — not a chatbot bolted onto an undefined queue. Product framing: autonomous AI agents and autonomous AI agents for business. Sequencing with consulting: AI consulting services for business.

Pricing clarity (one page finance can explain)

Mid-market pricing should be explainable on one page:

What is included in the monthly number (coverage hours, device or user count, monitoring, backup, patch).
What is excluded (projects, major version upgrades, net-new sites, work outside the catalog).
How it scales when headcount or sites change — a unit, not a surprise true-up.
How you start — Discovery at $99, then a written scope on the published ladder at plans.

If the quote is only “per user” with no catalog, you will pay for the same work twice: once in the retainer and again as a project. Ask for the catalog. Hub for that conversation: managed IT services. Same ladder honesty as Zion plans ladder, Discovery vs Starter, and Pay vs Consulte.

Name the job before you pick the sticker

Diagnostic, decision, scoped pilot, or ongoing ops — then choose the matching rung on /plans/.

See plans Discovery $99 Consulte

Discovery → Consulting → Starter → Growth

The sequence is fixed so you are not paying for coverage while the model is still fuzzy. Official stickers on plans.

Discovery — $99 — IT ops map: gaps, risks, quick wins, recommended model (keep / co-manage / outsource slices). A 30-minute session. It does not implement. Book on Discovery.
Consulting — $499 — operating model and roadmap when the blocker is a decision, RACI, or leadership alignment — not a missing asset list. Still not coverage.
Starter — $2,500 (ZG06) — scoped pilot. One agreed ops improvement or automation with a definition of done. This is the Pay path.
Growth — $8,000/mo — ongoing managed / co-managed coverage after the operating cut is real. Not a discount on Starter. Not an invented universal SLA %.

Proof chips only, as published: Discovery $99 · Consulting $499 · Starter $2,500 (ZG06) · Growth $8,000/mo · response within 24h. No catalog discounts. No invented availability for a Growth cut that has not been scoped.

You still need Discovery when leadership wants “managed IT” and three teams name three different pains; when severity definitions are missing; when success is still “see what’s possible”; when Growth is being discussed as a vibe. Starter fits when one improvement, one owner, access, and a success signal are already written. Consulte via /contact/ when multi-site RACI, multi-vendor control, regulated evidence, invoice-before-card, or a SOW larger than Starter is the real product. Prefer email first? kleber@ziontechgroup.com. Enterprise companion: enterprise AI & IT engagement path and enterprise.

How /managed-it-services/ fits with /plans/

Two live doors, different jobs. Mixing them recreates the fog.

/managed-it-services/ explains the work surface: co-managed model, SLA framing, stack, and how Discovery through Growth apply. It is a hub — not a second mystery menu.
/plans/ is the published entry ladder: Discovery $99, Consulting $499, Starter $2,500 (ZG06), Growth $8,000/mo. Start here when you are choosing a degree of commitment.
/finops-consulting/ is the adjacent spend hub when cost and ops must move together.
/healthcare-it-hipaa/ is the regulated clinical door when BAA and HIPAA constraints apply.
/solutions/ is the commercial grid for adjacent surfaces. It does not replace the ladder.
/contact/ (Consulte) is the door when neither menu is the right unit: custom SOW, invoice-before-card, multi-site politics.

We do not regenerate hubs from this blog and do not deep-link from hubs in this pack (hubs are already clean). Blogs may link to hubs. We do not link dead catalog leaves. The indexable commercial menu is /plans/.

Model, owners, or severity still unnamed → Discovery $99 or Consulte.
Decision / roadmap is the blocker → Consulting $499 on plans, or Consulte if political.
One improvement + one owner + one signal ready → Pay Starter ZG06.
Ongoing co-managed coverage after the cut is real → Growth on plans.
Named high-end recorte already chosen → enterprise.
Custom / regulated / invoice-first → Consulte.

Hub for framing · /plans/ for stickers · Consulte when self-serve is wrong

Discovery $99 · Pay Starter ZG06 · Consulte. Growth only after the operating cut is namable.

Discovery $99 Pay Starter ZG06 Consulte

FAQs

In-house vs outsource — which should we pick?

Keep in-house what is unique to your business. Co-manage or outsource what must be covered 24/7 and what you cannot staff deeply: monitoring, patch, backup, after-hours. Most mid-market teams land on co-managed. Detail: co-managed IT vs MSP.

What is in the SLA?

Severity definitions, response and restore targets, coverage hours, escalation (including your people), in-scope vs project work, and how misses are reported. If those items are missing, you do not have an SLA. Production SLAs are scoped per agreement — not invented for marketing.

What does onboarding include?

Access, asset inventory, backup and patch baseline, ticket routing, and a named escalation list. Onboarding is done when the first real ticket can be taken under the SLA — not when the kickoff deck is sent.

How much do managed IT services cost at Zion?

Published prices only: Discovery $99, Consulting $499, Starter ZG06 $2,500, Growth $8,000/mo on plans. Discovery and Consulting are not coverage. We do not invent per-seat averages or unlimited-ticket retainers without a catalog.

When should we Pay Starter ZG06 vs Consulte?

Pay Starter ZG06 when one ops improvement, one owner, and access are already written. Consulte via /contact/ when multi-site politics, invoice-before-card, or a SOW larger than Starter is the product. Most buyers still start at Discovery $99. Pattern: Pay vs Consulte.

Can you support healthcare / HIPAA environments?

Yes — start with healthcare IT / HIPAA and HIPAA-compliant IT services when clinical or BAA constraints apply, not a generic MSP conversation.