Starter
Best for: small teams that mainly need cleanup + occasional support.
Includes: baseline checks, light documentation, support hours.
Typical: month-to-month, simple scope.
Price: Set after triage
You’ll always know what you’re paying for. These are starting points. After triage, you get a written plan with the real number.
Use these as a baseline. Most small teams land in the middle tier once things are organized.
Best for: small teams that mainly need cleanup + occasional support.
Includes: baseline checks, light documentation, support hours.
Typical: month-to-month, simple scope.
Price: Set after triage
Best for: teams that want stability — patching, monitoring, backups, and clean M365 basics.
Includes: patching cadence, monitoring, backup verification, admin hygiene.
Typical: “we want this maintained, not hero-mode.”
Price: Set after triage
Best for: teams handling sensitive data or that want security tightened without chaos.
Includes: conditional access, device controls, security baselines, audits.
Typical: higher standards + regular reviews.
Price: Set after triage
Best for: migrations, cleanups, network fixes, Intune rollouts, vendor quote reviews.
Billing: fixed quote or hourly depending on scope.
Output: a short plan + “done” deliverable + notes.
Price: Quoted
This is here to reduce anxiety. Real quotes come after triage.
Identity, admin roles, MFA baseline, mailbox sanity, “stop the chaos.”
Typical range: depends on tenant size + mess level.
Dead zones, dropouts, cabling cleanup, gear right-sized, documented.
Typical range: depends on square footage + equipment.
Local + cloud options, restore testing, and a simple “what to do” checklist.
Typical range: depends on data size + RPO/RTO.
Minimum viable security that doesn’t break workflows.
Typical range: depends on users/devices + compliance needs.
This is not a contract. It’s just a sanity-check to set expectations.
Actual price depends on scope. Triage gives you the real number in writing.