Meraki config backup as a managed service: the math
How MSPs can add Meraki configuration backup as a revenue-generating managed service offering with real margins.
Most MSPs sell “managed network services” without actually protecting the thing they manage. The client’s Meraki configuration, the firewall rules, VLANs, VPN tunnels, and SSIDs that keep their business running, has no backup.
This is a liability. It is also an opportunity.
The pitch
Your quarterly business review with a client goes like this:
“Your network runs on Cisco Meraki. Meraki Dashboard does not back up your configuration. If a technician pushes a bad change, or a device fails, the recovery process is manual reconstruction from memory. That takes 4-6 hours and there is no guarantee everything gets restored correctly. We can add configuration backup with automated scheduling, version history, and one-click restore. Recovery time goes from hours to under 2 minutes.”
That is not a hard sell. The client’s IT director did not know this gap existed. Now they do. And they want it fixed.
The math
NET Backup Vault Premium tier: $59 per Meraki network per year.
A typical SMB client has 5–15 Meraki networks across their sites. At $59/network/year, backing up 10 networks costs $590/year, roughly $49/month in your cost base.
Charge $8–15/network/month for “Managed Configuration Backup.” At 10 networks paying $10/month:
- Monthly revenue: $100 per client
- Monthly cost: ~$49 per client
- Monthly margin: ~$51 per client
At 30 clients averaging 8 networks each (240 networks total):
- Monthly revenue: $2,400
- Monthly cost: ~$1,180
- Monthly margin: ~$1,220
- Annual margin: ~$14,640
The margin scales directly with the number of Meraki networks under management.
The whitelabel angle
With NET Backup Vault Professional, you get whitelabel branding. Custom logo, colors, and domain per customer. Your clients see “Acme MSP Network Backup” at backup.acmemsp.com, not “NET Backup Vault.”
This matters for two reasons:
- Perceived value. A branded portal looks like a mature, professional service. Not a third-party tool you resell.
- Stickiness. When the client sees your brand protecting their network, switching MSPs means losing that protection. It is an additional switching cost in your favor.
What you deliver
The actual deliverable is simple:
- Automated daily backups of all Meraki configuration types across the client’s networks
- Version history with visual diff comparison
- Granular restore capability (restore one feature without touching everything else)
- Atomic rollback (failed restores automatically revert)
- Audit trail (who changed what, when, exportable for compliance)
- A branded portal where the client can view their backup status
Setup takes minutes per client: enter the Meraki API key, select which networks to protect, set the backup schedule. Done.
Positioning in your service stack
Meraki configuration backup slots naturally into your existing managed services stack:
| Service | What it protects | Recovery without it |
|---|---|---|
| Endpoint backup | User files and data | Restore from backup |
| Server backup | Applications and databases | Restore from backup |
| Email archiving | Communication records | Restore from archive |
| Network config backup | Firewall rules, VLANs, SSIDs, VPN | 4-6 hours manual rebuild |
The last row is the gap. Every other critical system has backup and recovery. The network configuration does not. Filling that gap is a straightforward conversation.
Getting started
Start with your own Meraki networks. Run NET Backup Vault internally for a week. Verify that backups run on schedule, that the version history captures changes, and that restore works as expected.
Then pick 3-5 clients for a pilot. Offer the service at your planned price point. Measure adoption, gather feedback, and refine your pitch.
The clients who say yes fastest are the ones who have experienced an incident. They already know the pain. They just did not know a solution existed.