Client: National media publisher — gated content + subscriptions Role: Systems architect — technical-debt assessment + recovery roadmap Stack: Custom subscription platform, WordPress, API layer, GA4

The problem. Hundreds of cloned modules layered with inconsistent logic. Up to 30+ API calls per page load, triggering performance failures and recursive bugs. Invisible dependencies spanning three codebases — every minor update risked core business systems. The business couldn't build, test, or scale without risking systemic failure.

What I did. Ran a full staging audit to surface logic duplication, critical paths, and API bottlenecks. Isolated the high-risk dependency clusters across API, app, and DB layers, then designed a modular, API-first architecture that cleanly separated business logic from platform operations. Delivered a multi-phase recovery plan with technical milestones, architecture diagrams, and team-specific implementation tickets so the rebuild could execute cleanly.

A clear transition roadmap adopted across the dev teams

~30% projected performance gain from removing redundant API logic alone

Estimated 60% fewer debugging hours; governance clarity to cut future risk

Leadership equipped with a platform strategy that scales with the subscription business