ProductIntegrations
Multi-tenant enterprise platform: evolving safely around legacy systems
- What this was
- Safe evolution of an active enterprise platform: administration, plans, branding and synchronisation without breaking legacy workflows.
- My role
- Frontend and backend within the product team
- Period
- 2024–2026
- Outcome
- New features shipped into a live multi-client system without downtime.
Context and original problem
A live system with multiple clients, a shared admin area and tenant environments. Every change can affect legacy behaviour and active client processes.
Business task
Evolve the product safely: add administration, plans and branding, improve synchronisation and protect established workflows.
Constraints and unknowns
- AngularJS and modern Angular running together
- Separate master and tenant environments
- MySQL and PostgreSQL in one product architecture
- Changes in a live multi-client system
My responsibility
Frontend and backend delivery within the product team, working with the existing architecture, APIs, data and integrations.
Key decisions and trade-offs
- Introduce changes in stages and test connected workflows
- Keep legacy paths until migration is demonstrably safe
- Validate features against real client data rather than idealised fixtures
What changed
- Client management in Super Admin
- Plan and branding settings
- Creation and editing of billing parameters
- Reports and alerts for synchronisation errors
Disclosure and outcome boundaries
Next step for a similar task
For a similar multi-client system, begin with a map of dependencies and release risks.