When extending the existing platform stops being viable
An international training organisation had successfully grown around an open-source LMS for years — until the operational complexity of the business began exceeding what the platform could realistically support.
Workflows became increasingly difficult to adapt. New requirements required disproportionate effort. The organisation was accumulating operational friction faster than the existing platform could absorb it.
At that point, the challenge was no longer adding features. It was deciding whether continued extension of the existing system was still economically rational.
The organisation chose to replace the platform with a custom Rails application integrating CRM workflows, learning delivery, billing, and video infrastructure into a single operational system.
The technical challenge was not simply building new functionality. It was designing a platform capable of supporting years of future operational evolution without recreating the same constraints that forced the replacement in the first place.
The engagement focused heavily on:
- establishing clear domain boundaries early
- designing for evolving workflows rather than fixed assumptions
- sequencing delivery to reduce operational risk
- helping the engineering team make consistent long-term trade-offs during rapid delivery
Over twelve months, the platform became the operational backbone for the organisation’s global training business.
Sometimes the right technical decision is recognising that the current system can no longer support where the organisation needs to go next. The harder problem is ensuring the replacement preserves the business’s ability to continue evolving safely over time.