The opening MSP scenario below is a composite, drawn from procurement-cycle interviews across a sample of South African MSPs in late 2025 and early 2026. Numbers throughout are illustrative; live quotes and currency conversion change with FX and contract terms.
A South African MSP with 1,200 seats across nineteen tenants ran a procurement exercise in February. They had been on a stack of five vendors for the past three years, one for M365 backup, one for Entra identity protection, one for eDiscovery and compliance, one for endpoint backup, one for MSP billing, and the renewals were converging in the same quarter. The owner had been told, by every consolidated-platform vendor in the market, that they could save money by switching to a single platform. He wanted to know whether that was actually true for his book.
The procurement exercise took six weeks. The output was a forty-page model that answered, per tenant, whether consolidation reduced cost, increased cost, or was approximately neutral. The answer was different for different tenants. For roughly half, consolidation was clearly cheaper. For a smaller subset, it was clearly more expensive. For the rest, the math was within 5%, close enough that the operational arguments dominated the financial ones.
The MSP consolidated. Not because the platform was always cheaper, but because the analyst hours saved on operational reconciliation paid for the cases where it was more expensive. The math told the truth, and the truth was nuanced.
This article walks through that math. The numbers are in ZAR. The per-seat figures are illustrative, your renewal quote will be different, but the structure of the comparison is what matters. The structure tells you whether to consolidate or not, regardless of which vendor's pricing you plug in.
The five things every MSP needs to deliver M365 protection in 2026
The procurement question starts with the surface area. An MSP delivering competent M365 protection in 2026 has to provide five capabilities to its tenants:
M365 backup, Exchange, OneDrive, SharePoint, Teams. Item-level point-in-time restore. Long retention with regulatory templates. Per-tenant cryptographic isolation. Audit trail. Cost driver: per-seat, sometimes with storage overage.
Entra ID protection, backup and point-in-time restore of the directory and its policy surface, drift detection, Conditional Access What-If simulation, and identity threat detection across tenants. Cost driver: per-tenant, in capability tiers.
eDiscovery and compliance, litigation-grade search across backed-up mailboxes and sites, legal holds that block disposition, and POPIA-aligned compliance scoring. Cost driver: per-tenant, in capability tiers.
Endpoint and server backup, image and file-level protection for workstations and servers, restore to the same or new hardware. Cost driver: per protected device.
MSP billing, per-seat invoicing, recurring profiles, dunning, accounting integration, tenant-side payment. Cost driver: usually flat per-MSP plus per-tenant overage.
These are the five capabilities. There are adjacent options, security-awareness training, richer analytics, longer evidence retention, but those are typically procurement-optional in 2026. The five above are what an MSP cannot deliver M365 services without.
The total cost is the sum of the five. The sum can be assembled in two ways.
The stack approach
The conventional approach is to assemble the stack from best-of-breed point products. Each product is selected for the specific capability it delivers; integration is achieved through APIs, webhooks, or, most commonly, manual reconciliation in operational dashboards.
The stack approach has real advantages. The MSP can choose the strongest product in each category. The MSP is not locked to a single vendor's roadmap. The MSP can swap individual products without disrupting the rest of the stack. The pricing is sometimes cheaper per capability because point-product vendors compete on a narrow surface.
A representative stack for a 500-seat tenant in 2026 might look like:
- M365 backup: ~R65–R110 per seat per month, depending on retention and storage bundle - Entra ID protection: ~R650–R4,600 per tenant per month, scaling with drift, orchestration, and identity threat detection - eDiscovery and compliance: ~R280–R760 per tenant per month, depending on hold volume and search scope - Endpoint and server backup: priced per protected device, scaling with device count and image-versus-file scope - MSP billing: ~R3,500–R8,000 per MSP per month, plus per-tenant fees
For a 500-seat tenant under an MSP managing fifteen such tenants, the stack pricing assembles to a per-seat-equivalent in the low hundreds of rand once the per-tenant and per-device lines are amortised across the seat count, before adding the MSP-level platform fees. The range is wide because the upper-end products in each category are 2–3× the lower-end products, and not every MSP needs the upper end on every capability.
These figures are deliberately illustrative. Actual quotes vary substantially by region, volume commitment, contract term, and salesperson incentive. The point is the structure: a stack accumulates per-seat charges across five capability categories, and the total compounds.
The hidden costs of stacking
The per-seat figures are the visible cost. The hidden costs are operational.
Multiple audit chains. Each product in the stack maintains its own audit log. An incident that spans backup and identity, a compromised account whose mailbox was exfiltrated and whose directory roles were altered, produces a forensic record split across two products' audit systems, with different timestamps, different actor identifiers, different export formats. The investigator has to reconcile the two by hand. For a regulator or auditor asking for an incident timeline, the reconciliation work is non-trivial.
Multiple policy surfaces. A retention rule set in the backup product does not know about a legal hold placed in a separate eDiscovery product, which does not know about a Conditional Access exception made in a separate identity product. The same custodian under investigation has to be pinned, held, and access-restricted in three tools separately, often with different identifier formats. A change in one does not propagate to the others.
Multiple alert queues. The SOC analyst working the tenant has multiple dashboards open. An alert in one dashboard may be related to an alert in another, but the relationship has to be established by the analyst, not by the system. Alert fatigue scales with the number of dashboards.
Multiple licensing surfaces. Each product has its own per-seat or per-tenant licensing logic, its own renewal cycle, its own commercial-terms negotiation, its own price escalation. The MSP's procurement and finance teams spend more time on stack management than on customer acquisition.
Integration drift. APIs change. Webhooks deprecate. The integrations between products are maintained, by the MSP, not by the vendors, and the maintenance work compounds when any one product ships a breaking change.
For an MSP at 7,500 seats across fifteen tenants with mature operations, the hidden costs can be quantified. Industry observation suggests roughly 4–8 analyst hours per week per tenant of operational overhead specifically attributable to stack reconciliation. At loaded SA SOC analyst rates of approximately R450–R650 per hour, the operational overhead for fifteen tenants runs roughly R108,000–R312,000 per month. This is real money, and it does not show up on any product's invoice.
What single-vendor adds beyond price
A consolidated platform replaces stack reconciliation with a unified data model. The architectural changes that result are not cosmetic.
One audit chain. Every event, backup, restore, retention, drift detection, identity change, billing action, lands in the same SHA-256-chained audit ledger. An investigator working an incident sees a single timeline. An auditor asking for a forensic export gets a single bundle with cross-referenced records.
One policy surface. A retention change, a legal hold, or an identity access restriction is expressed once against a single custodian record and is honoured by backup, eDiscovery, and identity together. A custodian placed on hold is pinned across their mailbox backup, their SharePoint content, and their Entra audit history in a single write. The propagation is automatic.
One posture per tenant. The tenant's overall security and compliance posture is computed from identity risk, backup integrity, configuration drift, and compliance-control scoring, in a single tenant-wide model.
One licensing surface. The MSP negotiates one renewal, manages one price escalation, processes one set of per-tenant changes. Per-seat math is per-tenant rather than per-product-per-tenant.
One integration boundary. The platform's external integrations, to the MSP's PSA, to the tenant's SIEM, to accounting systems, to identity providers, are maintained by the platform vendor as a single integration layer. Breaking changes are absorbed by the vendor; the MSP does not bear the maintenance cost.
The result is that the MSP runs operationally simpler infrastructure with fewer points of integration drift, lower analyst overhead, and a unified forensic surface. The cost saving from consolidation is not just the per-seat math; it is the operational hours that get redirected from reconciliation to customer-facing work.
Consolidation is not always the right call. If the MSP has a mature SOC team that is already efficient at multi-product operations, if the MSP requires the absolute strongest product in a specific category and no single platform delivers it, if the MSP has long-running contractual commitments to specific vendors that have not yet expired, or if the MSP is in a procurement environment where vendor diversity is itself a requirement, the stack approach can be the right answer. The honest version of "consolidation is cheaper" is "consolidation is cheaper for the operational profile of most MSPs most of the time, but not all of them." The MSP's specific profile determines which case applies.
VaultFuzion's pricing model, the structure
The platform's per-seat pricing is published. The structure is a single M365-backup product on a five-band volume ladder plus optional per-tenant add-ons, with USD as the canonical pricing unit and ZAR conversion at the prevailing rate at the time of invoice generation.
The volume ladder, per seat per month, month-to-month, with committed-seat bands:
- Starter, $1.99/seat (R29.99) (1–9 committed seats). The full M365 backup product, Exchange, OneDrive, SharePoint, Teams, with item-level point-in-time restore, hash-chained audit, and POPIA-aligned retention. - Growth, $1.49/seat (R22.99) (10–99 committed seats). The same product, at a lower per-seat rate. - Scale, $0.99/seat (R14.99) (100–999 committed seats). The same product again, cheaper per seat as the committed count grows. - Volume, $0.79/seat (R11.99) (1,000+ committed seats). The same product at the volume rate. - Enterprise, custom-quoted. The same product with custom commercial terms, white-label MSP branding, custom SLA, and dedicated account management.
Billing is on committed seats. The band is set by the seat count the MSP commits to, and the per-seat rate steps down as that commitment crosses each band boundary. There is no capability floor to clear and no minimum-tier gate, the same full backup product ships at every band; only the per-seat rate changes. A tenant that grows from 90 to 120 committed seats moves from the Growth rate to the Scale rate on the seats it commits.
Per-tenant add-ons (not per-seat), available at any band. VentraID identity protection: Backup $35/R649.99, Intelligence $75/R1,389.99, Orchestration $150/R2,774.99, Advanced $250/R4,624.99 (Advanced includes RiskE identity-threat intelligence). EvidenceVault: eDiscovery $40/R739.99, Legal Holds $25/R464.99, Compliance Scoring $15/R279.99. All per tenant per month.
Managed Storage is the one seat-level add-on: R16/seat per month for pooled managed storage (50 GB per seat, R1/GB overage), or R0 when the tenant brings its own S3 bucket (BYOS). Endpoint and server backup is priced separately per protected device in a Base and a Pro tier.
Commitment discounts: 10% / 18% / 25% on the per-seat backup rate for 1-year / 3-year / 5-year commitments. The per-tenant add-ons carry their own commitment terms negotiated at the same points.
The PayI billing engine, per-seat and per-tenant invoicing, multi-currency, Xero/QBO sync, dunning, MSP and client portals, is included in the platform at no per-seat charge.
The fully-loaded envelope: backup plus every add-on
A fully-loaded configuration is the backup product plus every optional add-on switched on. It is built from published line items, not a bundle tier.
The per-seat line. The M365 backup product at the band the committed-seat count lands in, from $1.99/R29.99 per seat at Starter down to $0.79/R11.99 per seat at Volume, with the 1-year/3-year/5-year commitment discount applied. Managed Storage adds R16/seat where the tenant does not bring its own bucket, or R0 under BYOS.
The per-tenant lines. The full VentraID identity suite, Backup, Intelligence, Orchestration, and Advanced, and the full EvidenceVault suite, eDiscovery, Legal Holds, and Compliance Scoring, each billed per tenant per month at the rates published above. These do not scale with seat count, so their per-seat impact falls as the tenant grows.
The per-device line. Endpoint and server backup for any protected workstations and servers, priced per device in the Base or Pro tier.
In ZAR, a large tenant on the Volume band pays R11.99 per seat for backup before the commitment discount; the per-tenant VentraID lines list from R649.99 to R4,624.99 and the EvidenceVault lines from R279.99 to R739.99, each amortised across the seat count. Currency conversion locks at invoice generation; live quotes will reflect the prevailing rate.
What the fully-loaded envelope delivers, capability-by-capability: M365 backup with 6-snapshots-per-day cadence, item-level restore, content-addressed storage with per-tenant encryption, 365-day retention bands, and S3 Object Lock support on bring-your-own-storage; EvidenceVault eDiscovery, legal holds, and POPIA-aligned compliance scoring; a hash-chained audit ledger with verify-on-demand; VentraID four-tier Entra protection (backup, intelligence, orchestration, advanced) with drift detection, cross-tenant Conditional Access What-If, and identity threat detection; endpoint and server backup; white-label MSP branding and MSP cockpit cross-tenant operations; PayI billing, per-seat and per-tenant, multi-currency, Xero/QBO sync; three portals, Admin, Partner, Tenant, with the full impersonation flow.
Reconstructing the same surface area through separate point products in 2026 typically costs more, sometimes substantially more, when you include MSP billing as a separate line item. The exact delta depends on which products are chosen and what commitment terms are negotiated, but the consolidated envelope is competitive against best-of-breed stack assembly for the same capability set across the operational profiles we have modelled.
Worked example: 7,500-seat book, 15 tenants, on the Volume band
Consider a representative SA MSP managing fifteen tenants of approximately 500 seats each, 7,500 seats in total. Committed as one book, 7,500 seats sits in the Volume band at R11.99 per seat. The MSP needs all five capabilities on every tenant.
Stack approach (illustrative, mid-range pricing): M365 backup at ~R80/seat = 7,500 × R80 = R600,000. Entra identity protection at ~R1,400/tenant × 15 = R21,000. eDiscovery and compliance at ~R740/tenant × 15 = R11,100. MSP billing at ~R5,000/MSP + ~R150/tenant × 15 = R7,250. Endpoint and server backup is a separate per-device line on both sides, excluded from this seat-and-tenant comparison. Stack capabilities subtotal: R639,350. Operational overhead, reconciliation, alert correlation, hold and retention propagation, at ~6 hours/week/tenant × R550/hour × 4 weeks × 15 tenants (illustrative): R198,000. Stack TCO: ~R837,350/month.
Consolidated platform (Volume band, published ZAR list prices): M365 backup at R11.99/seat = 7,500 × R11.99 = R89,925. Managed Storage (where not BYOS) at R16/seat = 7,500 × R16 = R120,000, or R0 under BYOS. VentraID identity protection at R1,389.99/tenant × 15 = R20,850. EvidenceVault eDiscovery at R739.99/tenant × 15 = R11,100. MSP billing: included. Platform capabilities subtotal: R241,875 with Managed Storage, or R121,875 under BYOS. Operational overhead at ~1 hour/week/tenant × R550/hour × 4 weeks × 15 tenants (illustrative): R33,000. Platform TCO: ~R274,875/month with Managed Storage, ~R154,875 under BYOS.
On capabilities alone, the platform with Managed Storage comes in roughly 62% below the stack; the TCO including operational overhead is roughly 67% below. Under BYOS the gap widens further. The bigger number is the more accurate one, it reflects the actual cost the MSP is bearing.
These figures are illustrative. Per-seat pricing varies. Operational overhead varies. Currency conversion varies. The point of the worked example is the structure of the comparison, not the specific numbers. An MSP doing this exercise on their own book should plug in their actual quotes, their actual analyst hours, and their actual tenant mix. The structure will produce an answer that is honest for their situation.
For tenants where the capabilities-only comparison is closer, a very small tenant at the Starter band, or one that needs only backup and no add-ons, the operational savings often close the gap and produce net savings overall. For tenants where the capabilities-only pricing already favours the platform, the operational savings compound the win.
A platform that prices in USD and converts to ZAR at customer-billing time exposes the MSP to FX volatility. A 10% ZAR weakening between renewal and the next month's invoice is a 10% margin compression for the MSP. The platform's 1Y/3Y/5Y commitment options, with USD pricing locked at the commitment date but ZAR conversion at invoice, let an SA-revenue MSP negotiate the FX exposure explicitly rather than absorbing it silently. For an MSP whose revenue is ZAR and whose costs are partially USD-denominated, this is non-trivial protection.
What we don't claim
We do not claim that the platform is always the cheapest option. There are MSPs whose operational profile, tenant mix, or commitment to specific point products makes the stack approach the better answer. The procurement exercise has to be done honestly to know which case applies.
We do not claim that consolidation eliminates all integration work. The platform integrates with PSA tools, accounting systems, SIEMs, and identity providers. Those integrations have to be configured and maintained. What consolidation eliminates is the inter-product integration work, the reconciliation between the separate tools that all see the same tenant.
We do not claim that bigger is better in every dimension. Some best-of-breed point products are stronger in their specific category than the consolidated platform's equivalent capability. The platform's value proposition is breadth × integration × operational economy, not domain-specific dominance.
We do not claim that switching is always painless. A migration off a stack to a consolidated platform involves data migration, retraining, customer communication, and the operational disruption of any vendor change. The benefits are real, but they accrue over twelve to twenty-four months. An MSP unwilling or unable to absorb the migration cost should stay on the stack until renewal cycles align.
We do not claim that the worked example numbers are universally correct. They are honest illustrations of the structure. The MSP doing their own procurement should run their own numbers using their own currency assumptions, their own seat counts, their own committed-seat bands, and their own analyst-hour observations.
Pricing notes and disclosures
- Pricing is in USD with published ZAR list prices; ZAR conversion for USD-quoted lines is at the prevailing rate at the time of invoice generation. Examples in this article use USD/ZAR ≈ R16.38 as of 2026-05-08; live billing reflects the rate on the invoice date. - The M365 backup product is one product on a five-band volume ladder: Starter $1.99/R29.99 (1–9 seats), Growth $1.49/R22.99 (10–99), Scale $0.99/R14.99 (100–999), Volume $0.79/R11.99 (1,000+), and custom-quoted Enterprise. The same full product ships at every band; only the per-seat rate changes with the committed-seat count. - Commitment discounts of 10% / 18% / 25% apply to the per-seat backup rate for 1-year / 3-year / 5-year commitments. - Per-tenant add-ons are billed independently of the band: VentraID (Backup R649.99, Intelligence R1,389.99, Orchestration R2,774.99, Advanced R4,624.99) and EvidenceVault (eDiscovery R739.99, Legal Holds R464.99, Compliance Scoring R279.99). Managed Storage is R16/seat per month, or R0 under BYOS. Endpoint and server backup is priced per protected device. - 15% VAT applies to SA invoices per current SARS rates; the previously planned phased increases to 15.5% (May 2025) and 16% (April 2026) were reversed in 2025, and the February 2026 Budget confirmed VAT remains at 15%.
Six months into the consolidated platform, the 1,200-seat MSP from the start of the article has materially fewer dashboards open across their analyst desks, a unified forensic surface, and a single renewal conversation per year. The TCO came out close to the model. The operational benefits arrived in the timeline projected.
The cases where consolidation is the wrong answer remain real. An MSP whose book consists of two enterprise tenants with mature SOC teams may legitimately prefer the stack. An MSP committed to a specific best-of-breed product they cannot replace may stay on the stack until that product retires or is acquired. The consolidation case is not universal.
The math is the answer. Run the numbers honestly, with the volume bands and the FX rate written down. The structure of the comparison will tell you what to do.