How long could we be down before customers start to leave?
We map the dependencies, set recovery targets, name the owners and test the plan, so recovery is rehearsed rather than filed.
How it works: five steps, one Principal Engineer
One Principal Engineer leads it from the first call until your team has adopted the work and trusts it. Each step shows what it means for this engagement.
- Step 01
Discovery Call
30 minutes with the Principal Engineer who would lead this engagement. Free, and no sales handoff.
- Step 02
Direct Assessment
ImpactWorkshops to rank processes by the cost of downtime.
- Step 03
Shared Roadmap
MapDependencies, owners and recovery targets.
- Step 04
PE-Led Delivery
ValidateTest restores and the security of the backup system.
- Step 05
Outcome Assurance
RehearseA tabletop that tests the plan with leadership.
What changed for a client
A distribution cooperative mapped about 120 dependencies, and its first tabletop moved the continuity trigger from hour 12 to hours 2 to 3.
Ready when you are
Thirty minutes with the Principal Engineer who would lead the work. Pick a time on the spot, or email us.
Prefer email? Send us a note instead.
What you get
- Business impact analysis workshops with the people who run operations
- Dependency maps and recovery time targets for top-tier systems
- Named owners and backups for every critical system
- Backup and restore validation, including the admin accounts around them
A Principal Engineer, not a salesperson
Likely lead: Max Dinges or Kyl Gaston. You talk to the engineer who does the work on Business Continuity & Disaster Recovery Planning.
Questions buyers ask
We already have backups. Isn't that enough?
Backups are one part. Recovery also depends on who decides, in what order systems come back, and whether attackers can reach the backups. We test all three.
Can we do this ourselves?
Yes. Our free Business Continuity Framework gives you the templates. We help when you want it done faster or tested independently.
How long does it take?
A focused BIA and plan for top-tier systems usually takes a few months. One cooperative went from untested beliefs to tested plans in eight months.
More detail
Plans on paper do not bring systems back. We run the business impact analysis, map the dependencies, set recovery targets and name the owners, then check that backups and recovery actually work. Recovery ends up rehearsed rather than filed.
Related offerings
- Dependable
Ransomware & Incident Tabletop Exercises
"When it happens, who makes the first call, and do they know it?"
- Dependable
Cloud Migration & Cost Optimization (Azure, AWS, M365)
"Can we move or merge this without breaking our apps?"
- Dependable
Firewall Migration & Network Modernization
"Which part of the network is one bad day from taking the business down?"
Not sure this is the right fit?
Take the blind spot check. Four questions to start, then go deeper on one dimension.
Take the check
