Carry the daily request load.
Routine account, access, Microsoft 365 user, application, and device requests—inside an agreed remote-support boundary.
Inspect user-support scopeWhite-label managed IT delivery
Keep the client. Add the delivery team.
For MSPs and IT consultancies that have won the relationship but need a defined team to carry recurring support, Microsoft 365, or managed-service work behind their offer.
You keep Client contract · retail price · client-facing promise
Service lanes User support · Microsoft 365 · Managed cadence
Built forMSPs, IT consultancies, and service firms that own the client relationship
Reference unit$39 / $49 CAD per user, per month
Inspect the delivery pack Check partner fit
Coverage, tools, and final scope are set in the written agreement — not on this page.
Who owns what, before any work moves.
The lane is written before it runs. Nothing on the delivery side dilutes your commercial position.
You own
Contract, retail price, client promise, advisory judgment.
We define together
Client group, service lane, intake, coverage, approvals, return points.
Delivery carries
Accepted recurring work, useful documentation, contextual escalation.
Three service lanes, each with a written boundary.
Start with one coherent client group. The final catalog depends on its users, tools, applications, coverage expectations, and existing technical conditions.
Keep tenant routines moving.
Approved user, group, license, access, and recurring administration work with explicit decision and escalation points.
Inspect Microsoft 365 scopeTurn upkeep into a rhythm.
Defined endpoint, baseline, exception, and review activities where tooling and responsibilities are suitable.
Inspect managed cadenceThe delivery pack: four documents that run the lane.
Before any promise is discussed, you can inspect the paperwork. Every accepted client group runs on these four documents.
Service profileUsers · tools · coverage · approvals · named ownersRequired before delivery
Request recordContext · authorization · work performed · current ownerTemplate
Exception noteSafe stop · decision framed · return pathTemplate
Review agendaDemand · friction · changes · next ownerTemplate
These are blank representative structures—not customer records, platform screenshots, or claims of past performance.
Open every field on the pack sheetsInspect the standards that control the work.
Start with the parts that can be examined before delivery begins. Each should be precise enough to challenge, revise, and place in written scope.
Scope language
What enters the lane, what stays with you, and what requires separate review.
Exception structure
The safe stopping point, context returned, decision needed, and named owner.
Client experience decisions
The front door, identity, update language, closure, and situations that return to your team.
Commercial inputs
The price unit, reference band, exclusions, tools, products, taxes, and separately scoped work.
Two reference rates. One required scope conversation.
Reference pricing is shown in CAD per user per month. It frames the recurring service discussion; it does not include every tool, project, location, coverage window, product, or technical condition.
Essential referenceRuns core user support and agreed Microsoft 365 routines.
$39CAD / user / month
Plus referenceAdds broader managed cadence where explicitly included.
$49CAD / user / month
The rate is an input, not the agreement. Final scope, tools, taxes, and separately scoped work are set in writing.
See what each rate runsBring one client group and the work that keeps slipping.
We can start with a high-level profile and a capacity question. Keep credentials, private records, and regulated information out of public pages and email.