The replacement was already underway.

01 / Architectural assessment

A fragile platform at the center of the business.

The company's e-commerce platform handled its primary sales journey. An architectural review revealed structural technical debt and security weaknesses, leaving the business particularly exposed ahead of its busiest season.

For a custom manufacturing business with annual revenue in the $2–5 million range, December through February accounted for roughly 40–50% of yearly revenue. A serious failure at that moment could jeopardize more than $1 million in seasonal revenue.

These were not simply issues to put on a maintenance list. The risks called for a replacement architecture and an operating plan that would preserve the customer journey throughout the change.

02 / Contingency planning

Start the replacement while there is still time.

I initiated parallel development of a modern platform with an established international development partner, while the legacy system remained in use. The approach preserved a path to a planned transition while preparing for the possibility of an earlier deployment.

We chose Vue.js, Nuxt.js, and Laravel, worked to preserve useful prior development investment, and concentrated on the functions essential to the purchasing journey.

Preparation created choices. When the incident arrived, the team had something real to deploy.

That contingency became critical when security breaches forced the organization to accelerate the change. The system was already substantially developed; the problem became delivering the core platform under pressure, rather than starting from scratch.