Case studies
Tangible results from intangible problems. Here's what modernization looks like when it actually works.
Featured / MSP Services Portfolio
A $300,000 monthly recurring revenue service carrying years of undocumented technical debt. No clear ownership. No framework for measuring what "fixed" even looked like. A 9-month engagement that changed all three.
35%
Profit increase
$300K
Monthly recurring revenue
9mo
Time to results
2.5yr
Full portfolio transformed
The methodology
Most technical debt conversations start at the technology layer. Mine start at the human layer — the decisions that created the debt, who owns them now, and what incentives are keeping the debt in place.
The framework I built creates a complete map of debt across a service: tooling, process, workflow, and organizational. It produces something most organizations have never had — a shared language for what's broken and why.
Once you have the map, the prioritization becomes obvious. The execution becomes systematic. And the results become measurable.
Sit in the service. Not as an auditor — as a participant. Map every process, every handoff, every place where work slows down or disappears.
Categorize debt by type, age, ownership, and blast radius. Make it visible to everyone — not just engineering, but leadership and customers.
Work through debt in the order that unlocks the most value — not the order that's easiest. Measure results at each stage.
Redesign the processes, teams, and incentives that created the debt in the first place. If you don't change the conditions, you'll regenerate the same debt.
Additional work
Applied the same debt-mapping methodology across a group of smaller services following the flagship success. Systematic replication of a proven approach across varied service sizes and team structures.
Extended the framework to the organization's largest and most complex service — significantly larger scope, deeper cross-functional dependencies, and higher organizational resistance to change.
Built and owned compliance programs across SOC 2, SOX, and FedRAMP environments. Embedded compliance into engineering workflows to make governance proactive and scalable rather than reactive and audit-driven.
Hired, promoted, and developed engineering teams through periods of significant organizational change. Built teams that continued to perform — and improve — after my departure.