About the client
The client sells compliance-first software to companies that develop medical devices. Its requirements management platform helps customers maintain regulatory traceability and collaborate securely. As larger enterprise customers began evaluating the platform, its original architecture became a constraint, and any change had to keep traceability intact and avoid interrupting service for existing users.
Making regulated software ready for enterprise buyers
- Scale. The architecture limited performance and slowed the addition of new capability.
- Enterprise identity. Without tenant isolation and single sign-on, it could not meet the access-control expectations of large medical device organisations.
- Fragmented notifications. User and system events had no single delivery mechanism, so time-sensitive compliance activity did not reliably reach the right people.
- A legacy interface. The jQuery frontend made consistent design hard to maintain and slowed delivery of new screens.
- Live compatibility. Backend endpoints and data structures had to change while the admin app remained in daily use.
What FiftyFive built
FiftyFive carried out a full-cycle modernisation, sequenced so existing users kept working throughout: SAML-based multi-tenant authentication with tenant-level isolation; a central backend notification service for user and system events; a migration of the frontend from jQuery to React with a unified design system; optimised backend endpoints and data structures; updates to the existing admin app so it runs against the upgraded APIs.
How the solution works
Identity and tenancy
- SAML integration provides the single sign-on enterprise customers expect.
- Each customer organisation is isolated at tenant level, and the access-control model is designed for regulated environments.
Notification service
- Event delivery that had been spread across the platform now runs through one dedicated service, which sends real-time alerts for user actions and system updates.
React frontend and design system
- The jQuery interface was replaced with a component-based React frontend governed by a unified design system, so screens follow consistent patterns and new workflows reuse existing components.
Backend and migration path
- Endpoints and data structures were restructured to match the new architecture and make integrations simpler.
- The legacy admin app was updated to use the new endpoints, giving a migration path without a hard cutover.
Technology stack
What the solution enabled
Business transformation
Faster development turnaround
Shorter integration time
Enterprise single sign-on with tenant-level isolation
40% faster development turnaround
After the React migration and design system.
30% shorter integration time
After backend endpoint and data-structure optimisation.
Enterprise single sign-on
With tenant-level isolation and access control.
No interruption to operational workflows
During modernisation, because the admin app was moved onto the new APIs.
FiftyFive Technologies modernised the requirements management platform of a health-technology company whose compliance software supports medical device makers. The platform's architecture could not meet enterprise customers' needs for identity, tenant isolation and scale. Over ten months, FiftyFive added SAML-based multi-tenant authentication, migrated the frontend from jQuery to React with a unified design system, built a central notification service and optimised backend endpoints while the existing admin app stayed in use. Development turnaround fell by 40% and integration time by 30%.
Technical questions
How do you modernise a regulated SaaS platform without disrupting users?
FiftyFive Technologies sequenced the work so the existing admin app was updated to use the new APIs before old paths were retired, avoiding a hard cutover. For a medical device compliance platform, this allowed SAML multi-tenancy, a React frontend and backend optimisation to ship without interrupting operational workflows.
What did moving from jQuery to React change for delivery speed?
On this platform, FiftyFive Technologies replaced jQuery screens with React components governed by a unified design system. New screens reuse shared components and patterns, and the client's development turnaround fell by 40% after the migration.