Most offices fit best in the Managed tier when they want real ownership.
Pricing and Plans
Pricing should make the level of ownership obvious.
Some businesses need a clean support lane. Some need broader monthly ownership across support, networks, Microsoft 365, cloud systems, and recovery. Some need a scoped migration, cleanup, or build. The point is to match the engagement to the actual load and the business risk.
Support, admin, infrastructure, and recovery work can be priced by the level of ownership.
Migrations, cleanup work, and custom builds stay quoted separately when that is cleaner.
Decision frame
How pricing is usually shaped
These lanes exist to show how much ownership moves onto Mox and how much work stays cleaner as a scoped project.
Monthly ownership by scope and business risk
Support, administration, infrastructure, and recovery move into a steadier lane when the environment needs ongoing ownership.
Scoped migrations, cleanup work, and rollouts
Projects stay project-shaped when the business needs a delivered change more than it needs a monthly retainer.
Discovery, build, and rollout phases for custom work
App and workflow work is priced around the actual shape of the problem instead of being forced into a generic support tier.
Choose the operating model, not just the hourly cost.
The right tier should make it clear what Mox is owning, what gets cleaned up proactively, and how much technical responsibility stays on your side.
Monthly
Foundation
For smaller teams that need recurring support handled cleanly, but do not need broader infrastructure ownership yet.
Best when daily support and admin drift are the main problem.- User support and recurring ticket follow-through
- Device setup, joins, moves, and leavers
- Licensing cleanup and vendor coordination
Recommended
Managed monthly ownership
Managed
For businesses that want support, Microsoft 365, networking, backup oversight, and recurring cleanup treated as one environment instead of separate problems.
Usually the best fit for offices that want one real technical owner.- Everything in Foundation
- Firewall, VPN, Wi-Fi, and switching support
- Microsoft 365 admin and tenant hygiene
- Backup monitoring, restore review, and retention checks
Higher oversight
Priority Managed
For environments with more cloud systems, more operational risk, or less tolerance for drift around access, recovery, or hosted infrastructure.
Best when downtime, weak access control, or poor recovery would hurt immediately.- Everything in Managed
- Server and cloud-service administration
- Security hardening, MFA, and permissions review
- Formal backup testing and recovery documentation
Scoped quote
Projects and Builds
For migrations, backup redesign, procurement, documentation cleanup, new site work, and custom business applications that need a defined scope.
Use this when the business needs a delivered change, not monthly ownership.- Migration planning and execution
- Backup, network, and cloud cleanup work
- Procurement and licensing projects
- Custom app discovery, scoping, and build phases
What makes the monthly plans worth paying for
The value is not availability on paper. It is having the messy operational work stop falling back on your staff every time support, infrastructure, and recovery overlap.
Buy the lane that removes the most drag.
Monthly coverage starts paying for itself when support issues keep touching Microsoft 365, the network, backups, vendors, and admin cleanup at the same time.
- Foundation is for support noise and admin spillover.
- Managed is for one owner across support, infrastructure, and recovery discipline.
- Priority Managed is for environments with less tolerance for downtime, access drift, or weak recovery readiness.
Foundation
Best when support noise is the main cost
Use it when the business mostly needs end-user help, device setup, account changes, and someone steady to close the loops.
Typical load- User support and recurring ticket follow-through
- Onboarding, offboarding, and workstation setup
- Licensing cleanup and vendor coordination
Managed
Best when the environment needs one technical owner
Choose this when support, Microsoft 365, networking, backup oversight, and recurring cleanup keep overlapping in the same week.
What moves into one lane- Support plus the work around support
- Network, Microsoft 365, and backup follow-through
- Operational context, so the business stops re-explaining itself
Priority Managed
Best when weak oversight hurts immediately
Step up here when hosted systems, security posture, restore confidence, or access control need more active ownership.
Why teams choose it- Cloud and server systems need steadier administration
- Restore testing and hardening need to stay proactive
- The business cannot absorb long outages or preventable drift
Common scoped engagements
A lot of work should not be forced into a monthly retainer. These are usually cleaner as standalone projects with their own deliverables, sequencing, and rollout plan.
Rollouts and migrations
Move mail, files, identity, Teams, SharePoint, OneDrive, and collaboration habits into a structure that works for daily use.
- Cutover planning and staged migration
- Permissions, MFA, and licensing cleanup
- Training and post-move stabilization
Backup and data protection redesign
Review what matters, where it lives, how it is copied, how long it is retained, and whether the business can actually restore it under pressure.
- Backup architecture and storage review
- Restore testing and recovery steps
- Cloud, file, and database protection planning
Network and hosting cleanup
Resolve the firewall, VPN, Wi-Fi, DNS, SSL, Cloudflare, server, and documentation mess that nobody wants to touch but everyone depends on.
- Network mapping and policy cleanup
- Server hardening and hosted-service stabilization
- Documentation and support handoff
If you are unsure which tier fits, start with the current mess.
Team size, number of sites, Microsoft 365 state, network pain points, backup confidence, and support noise are usually enough to decide whether this should be a monthly relationship or a scoped project.