25 Years
in the Room When
Things Break
I’ve spent my career designing, testing, and executing disaster recovery strategy across some of the most demanding environments in enterprise IT and U.S. federal defense. Pro Data Works is how I put that experience to work for smaller organizations that need the same rigor — without the enterprise price tag.
The Gap I Kept Seeing
Across more than two decades in disaster recovery — from federal defense environments to enterprise cloud programs — I kept running into the same pattern in smaller organizations: leadership assumed they were protected, technical teams knew things weren’t quite right, and nobody had a clear picture of where they actually stood.
Enterprise-level DR rigor exists. The problem is that it rarely gets applied outside of organizations with dedicated teams and six-figure consulting budgets. Small and mid-sized businesses face the same operational risks — often with more exposure and less margin for downtime — but without the resources to commission a full program build.
“You don’t need a six-month engagement to get clarity. You need an honest assessment from someone who’s seen what actually breaks — and what doesn’t.”
Pro Data Works is my answer to that gap. A fixed-scope assessment, delivered quickly, written in plain language — so the right people can make informed decisions about recovery risk without needing to translate a technical report.
A Few Principles I Don’t Compromise On
-
Recovery plans are assumptions until they’re tested.
I’ve reviewed hundreds of DR plans over my career. The ones that hold up under pressure share one quality: they’ve been tested against reality, not just written down. My assessments surface the gap between what’s documented and what’s actually true.
-
Business alignment matters as much as technical readiness.
Resilience failures are almost never purely technical. They’re alignment failures — between what leadership expects and what IT can deliver, between documented RTOs and the actual architecture. I work across both sides of that gap.
-
Clarity is the deliverable, not the consulting relationship.
I’m not trying to build a long-term retainer. I’m trying to give you an accurate picture of where you stand — in plain language your leadership team can read — and let you decide what to do with it. No pressure, no upsell.
-
Cloud changes the architecture, not the fundamentals.
RTO and RPO objectives still need to be defined, validated, and owned. Failover still needs to be tested. Ownership still needs to be clear. I bring AWS and Azure-specific expertise, alongside the foundational DR discipline that predates any platform.
Where This Expertise Comes From
My career has covered three distinct environments — each one adding a layer of perspective that informs how I approach resilience assessments today.
Present
Cloud DR Lead — Enterprise Resilience & Recovery
Leading enterprise cloud disaster recovery and resiliency execution across AWS and hybrid environments — identifying recovery gaps, aligning RTO/RPO objectives with infrastructure and application teams, and driving cross-functional DR initiatives that improved cloud DR readiness by 30% and recovery testing efficiency by 25%.
Present
Independent IT DR & Resilience Consultant
Providing independent advisory support to full-time leadership roles — focusing on strategic reviews and recovery readiness rather than day-to-day execution. Pro Data Works is an extension of this practice.
2019
COOP/DR Engineer → Principal Systems Architect → Interim CTO
10 years of progressive roles in continuity of operations and disaster recovery engineering within regulated federal environments — authoring COOP and DR plans, leading continuity exercises and recovery testing, and ultimately serving as Interim CTO. This is where I learned what rigorous, mission-critical DR actually looks like under pressure.