The operating principle
A seat fee cannot describe the whole obligation
Ten staff with a complicated hybrid identity environment may produce more engineering work than forty staff using a straightforward cloud-only tenant. A useful price model can combine a base tenant fee, supported users, defined service modules and separately priced project work.
Compare packages by service boundary
Separate administration, helpdesk, security configuration, licence management, backup/recovery, device support and after-hours escalation. If those categories are unclear, the buyer cannot tell whether an incident is included or billable.
Ask for a response-time definition rather than a blanket promised resolution. Microsoft outages, local networking and client-owned hardware are often outside the support provider's control.
| Service element | Questions for the contract | Common misunderstanding |
|---|---|---|
| User/tenant admin | Which routine changes are included? | Every project is unlimited |
| End-user support | Which products, devices, channels and hours? | 24/7 cover is automatic |
| Security baseline | Review only or remediation too? | The provider supplies a managed SOC |
| Licensing | Who buys, approves and is billed? | All Microsoft licences are included |
| Backup and recovery | Which workloads and verified restore targets? | Microsoft availability equals all-data backup |
| Migrations and redesign | One-off projects or retained service? | All significant changes are free |
What changes the monthly cost?
Number of tenants, supported users, role complexity, device footprint, onboarding/offboarding rates and support time zones are measurable inputs. Ticket history and an agreed fair-use model help establish actual cost-to-serve.
Security and compliance responsibilities increase the need for senior engineering and change management. A low seat price that depends on undefined support limits can be more expensive than a transparent base package.
Price the onboarding and exit too
A new support provider may need to audit the tenant, document undocumented accounts, establish access and migrate tickets from the prior provider. That effort should be explicit rather than hidden behind an apparently free onboarding promise.
The exit process matters just as much. The client should remain the tenant owner, keep admin access and receive documentation for accounts, policies, pending issues and vendor dependencies.
Documented administration controls
- Precise service catalogue and user/tenant counts
- Covered hours, ticket channels and escalation definitions
- Licence inclusion and feature prerequisites
- Base fee, per-user element and project exclusions
- Onboarding, annual adjustments and notice terms
- Documented provider exit and handover process
A managed-service quote should expose the actual labour model
A monthly seat count does not describe ticket demand, tenant complexity or client governance. Ask the buyer for the last three months of request volume, joiners and leavers, Exchange changes, high-risk approvals, number of SharePoint sites, third-party apps, planned projects and the support hours staff genuinely need. Combine those inputs with realistic handling time, escalation and reporting effort to estimate a feasible workload.
The quote should separate onboarding audit, steady-state administration, specialist changes and out-of-hours support. If a business requests 24-hour cover, that requires actual coverage capability and staffing costs; it cannot be implied by an email inbox that accepts messages overnight. Any proposed price must clear a fully loaded internal margin check rather than an arbitrary public tariff.
| Price component | Input to verify | Contract boundary |
|---|---|---|
| Onboarding | Tenant inventory, documentation and inherited issues | One-off onboarding deliverable |
| Routine service | Request counts, effort, working hours | Included volume and support window |
| Specialist changes | Security projects, mail migration, Azure engineering | Written change order and owner approval |
| Exit and handover | Runbooks, account transfer and provider access removal | Retained client ownership and deliverables |
Write a proposal customers can compare
Require one readable scope document with covered Microsoft 365 workloads, ticket channel, working days and time zone, customer responsibilities, excluded work, response targets only where operationally supported and a named escalation route. Clarify whether the provider supplies Microsoft licences or the client owns procurement. A plan that cannot name the requester authorised to approve a permission change is not an operationally complete plan.
For any support-cost calculator on this site, make clear that the editable rate belongs to the visitor. The calculation is an illustrative workload scenario—not a published Pearl Lemon fee, binding SLA or contract offer.
Documented administration controls
- Actual historical ticket demand or explicit assumptions
- Routine versus project work clearly distinguished
- Coverage hours supported by real staffing
- Owner approval and escalation documented
- Exit and access revocation included
A useful managed-service quote lets the company forecast the monthly spend and understand exactly who will do what.
Primary technical references
Check current feature and licence requirements before changing a tenant. A service description is not evidence that a customer has purchased or activated an option.
Commercial next step
Compare a managed-service scope, not a headline fee
Share tenant count, staff size, support windows and the recurring tasks you want covered. Any actual quote follows engineering and margin verification.
Request an administration assessment