Anonymised by industry. This case study describes a framework-built MSP platform in active production with an Australian managed-service provider — the kind of integrated operational surface we deliver to MSP delivery partners.
Industry shape
A Brisbane-based managed services provider supporting SMB and SME clients across Microsoft 365, Azure, CSP licensing, security posture management, and standard service-desk operations. Multi-tenant client base with the typical MSP mix.
What the operational surface delivers to clients
This is the lead. The MSP service runs on an integrated platform that gives clients one operational surface across:
- Procurement and asset lifecycle — hardware, software licences, devices, equipment — tracked end-to-end with approval workflows routed through the same identity layer as the service desk
- IT project management — deployments, migrations, refreshes managed on the same platform as day-to-day operations
- Desktop / server / backup operations — monitoring, patch status, backup verification surfaced on the same dashboard the service desk team works from
- Security framework — Microsoft-native security stack integrated with CSP licensing, incident workflow, and compliance evidence — replaces 3–4 separate vendor SaaS products that typical MSPs assemble piecemeal
- Multi-entity / multi-tenant billing flexibility — bill different entities from one M365 tenant, or one entity from multiple tenants; parent-company administration across all child tenants from a single portal. Not a feature standard PSAs offer.
- CSP licensing reconciliation — Pax8 + Prism distributor APIs against actual consumption
- Client portal — the operational surface for the client’s own team to manage their IT day-to-day
- Compliance evidence — generated by normal operation; ISO 27001 aligned; audit-ready on demand
The security framework specifically
Instead of assembling security service from a stack of third-party SaaS (security posture reporter + compliance evidence collector + phishing simulator + vulnerability scanner + password manager dashboard), the platform consolidates these into one integrated module that pulls from Microsoft 365 and Azure native security telemetry, reconciles with CSP licensing, and surfaces through the same client portal.
The eat-our-own-dogfood proof
The MSP we run our own MSP business on is the MSP service we’d sell to a new client. Same Microsoft-native stack. Same framework. Same modules. Same security framework module. Same audit discipline. We don’t run on third-party PSA — we built the platform, we run the platform, and we control the platform.
Velocity
- Phase 1 + Phase 2 (Telemetry) shipped to production; Phase 3 (Cost Tracking) Epic Active
- A substantial codebase across the operational entity set — far beyond what a typical MSP buys per-seat
- Estimation variance on completed work packages: single-digit percentage
Hours comparison
Compression: 4–6×.
The framework’s multi-portal pattern, automatic work-tracking, audit-log infrastructure, and Microsoft Graph integration patterns are all canonical, not invented per engagement.
Alternative for context: the typical MSP pays ongoing per-seat fees to its PSA / RMM / CSP-portal / security-vendor / backup-vendor chain for the same functional surface — and never owns the platform.
Proof beat
Integrated operational surface that replaces multiple vendor SaaS products with one platform.
Most MSPs deliver a service desk plus a stack of vendor portals — clients learn five logins, watch five dashboards, export five reports. The platform delivers procurement, project management, desktop / server / backup operations, security framework, CSP licensing, and client-team productivity surface as one integrated module set. The security framework alone replaces 3–4 separate SaaS products.