Case study · consulting practice
BackupPlan.ca
Backup validation and recovery readiness for Canadian businesses, built on one premise: a backup nobody has restored is a rumour. The entry offer is a Recovery Audit that proves what actually comes back.
The problem in one sentence. Almost every organisation has backups; far fewer have restored one recently, and the gap between those two facts only becomes visible on the worst day of the year.
What I built
- Homepage messaging built around recoverability and proof rather than backup coverage, because coverage is the number that lies.
- A Recovery Audit covering critical system inventory, restore testing, access review, retention, vendor recovery, alerting and a 30/60/90-day roadmap.
- Service positioning for recovery audits, recovery planning, Microsoft 365 review, restore testing and backup monitoring.
- Tiered packages: a snapshot review, a full recovery audit, and an ongoing recovery advisory option.
- A static implementation that keeps the launch path simple and the maintenance burden near zero.
How it is built
Restore confidence, not backup coverage
Every service is framed around what comes back and in what order — restore priority, ownership, runbooks, and the test that proves it.
A named offer
The Recovery Audit is a defined engagement with a defined deliverable, so the buyer is not asked to scope their own project.
Static on purpose
Simple hosting, no backend, nothing to patch. A continuity consultancy whose own site needs babysitting is not a good advertisement.
Written for the buyer
Recovery risk explained in terms a business owner can act on, without diluting the technical work underneath it.
Why it is in the portfolio
This is the direct commercial expression of the work I did for thirteen years at eBackup: knowing what is protected, what has been tested, where the recovery assumptions are weak, and what to fix first.
Turning that into a service someone will pay for — scoped, priced, and delivered — is a different skill from doing the engineering, and worth showing separately.