Users and endpoints
Covered users, workstation counts, device types, operating systems, and the endpoint package selected for each group.
Pricing and fit / Service Guide 2026-07-11
A clear scope before a credible quote.
A single per-user or per-device number without context is rarely a reliable managed IT quote. We price the environment that will actually be supported, then put the selected services, quantities, exceptions, and commercial terms in writing.
Strong fit
Who managed service is built for
- You want one documented support and escalation model.
- You need defined coverage for users, endpoints, systems, and locations.
- Continuity, security discipline, and living documentation matter.
- Your internal IT team needs clearly scoped co-managed capacity.
- You are willing to address inherited risk instead of hiding it inside an unrealistic recurring fee.
Different model
When another approach may fit better
- You only need isolated break-fix work with no ongoing support relationship.
- You want a one-time project without recurring operational ownership.
- You expect hardware, projects, physical work, unmanaged systems, and every after-hours request to be included in one recurring fee.
What shapes the quote
Price follows responsibility, not a teaser rate.
Discovery and scoping establish the quantities, dependencies, risks, and service expectations needed for a defensible quote.
Servers and cloud
Separately selected servers, cloud tenants, identity platforms, applications, and administrative responsibilities.
Locations and field needs
Sites, network closets, connectivity dependencies, travel, physical access, and any written on-site coverage.
Security and compliance
Required telemetry, backup coverage, evidence needs, risk profile, and any separately scoped framework work.
Support expectations
Covered systems, normal support channels, priority handling, vendor dependencies, and written exceptions.
Inherited condition
Documentation quality, unsupported systems, access gaps, remediation needs, and the work required to stabilize the environment.
Package orientation
Two endpoint packages. Other responsibilities are selected separately.
The Service Guide remains the scope authority. These summaries point buyers to the right starting place without turning a capability list into a blanket promise.
Managed Endpoint Basic + Unlimited Remote Support
Managed Endpoint Basic is the recurring endpoint package for covered endpoints that do not need included endpoint backup protection. It includes unlimited remote support during standard support hours for covered endpoint users, plus endpoint monitoring, patching, security telemetry, asset tracking, ticketing, and standard remote remediation. Endpoint backup protection is not included.
Read the exact scopeManaged Endpoint Complete + Unlimited Remote Support
Managed Endpoint Complete is the primary endpoint package for covered endpoints that need support, endpoint security visibility, SIEM alert triage, and backup monitoring. It includes everything in Basic, plus endpoint backup monitoring, standard restore operations, EDR/XDR-style visibility, SIEM alert triage, and enhanced endpoint security monitoring.
Read the exact scope| Service | Typical use | Scope anchor |
|---|---|---|
| Managed Server Support & Protection | Servers that require monitoring, patching, backup oversight when in scope, and remote remediation. | Server administration and monitoring for covered servers, with backup and recovery duties only where backup scope exists. |
| Managed Network Closet | Switching, uplinks, MDF/IDF equipment, or inherited network closets that need recurring oversight. | Monitoring, configuration coordination, visibility, and standard remote network administration for covered closets and devices. |
| Hosted Voice Platform and Seats | Hosted phone service, users, numbers, E911 registrations, channels, and calling usage. | Managed hosted PBX administration, call-flow maintenance, user seats, number service, and defined telecom add-ons. |
| Microsoft Licensing and Cloud Administration | Email, office apps, identity, SSO, Microsoft security add-ons, and tenant administration. | Licensing is billed separately from managed support. Administration is included only where selected or tied to a covered package. |
A package name identifies a service scope. It does not mean every technology task is included. The current Service Guide and the client quote define selected coverage.
Recurring when selected
Normal managed operations
- Remote support for covered users and systems during standard support hours.
- Endpoint monitoring, patching, ticketing, and routine remediation when selected.
- Contracted security telemetry, backup monitoring, and standard restores when selected.
- Selected Microsoft cloud administration and routine vendor coordination.
- Documented priorities and P1 escalation for covered clients.
Normally separate
Quoted or written into scope
- Onboarding and inherited-environment stabilization.
- Projects, migrations, deployments, and infrastructure redesign.
- On-site physical work, cabling, hardware repair, and office moves.
- Non-P1 after-hours work and third-party vendor projects.
- Incident response beyond initial containment and work on uncovered systems.
Commercial source hierarchy
The website explains the model. Written documents control the relationship.
A credible quote identifies exactly what is selected, separately priced, passed through, or excluded for the client.
Agreement
Controls legal and business terms such as payment, liability, confidentiality, data ownership, and disputes.
Quote, Order Form, or SOW
Controls selected services, quantities, commercial terms, pass-through costs, and client-specific exceptions.
Service Guide
Controls service scope, support priorities, operational boundaries, exclusions, and billable work.
Buyer questions
Answers before the proposal conversation.
Why do you not publish one universal price?
The same user count can represent very different support, security, server, location, and recovery requirements. We explain the pricing model rather than publish a low number that does not describe the eventual scope.
Can you provide a budgetary estimate?
After a discovery call and a minimum environment inventory, we can determine whether a budgetary estimate is appropriate. Final commercial terms require written scope and quantities.
Is onboarding included?
Onboarding and stabilization depend on the inherited environment. The quote identifies any one-time work and charges.
Is on-site work included?
On-site and physical work are included only when the written service selection says so. Otherwise, they are separately scoped.
Does unlimited support mean every IT task is included?
No. Unlimited remote support applies to normal day-to-day support for covered users and covered systems during standard support hours. Projects, major changes, physical work, unmanaged systems, and other exclusions remain subject to the Service Guide and quote.
Get a quote that matches the environment.
Start with a discovery call. If the fit is right, we will gather the minimum information needed to recommend scope and prepare written commercial terms.