Repligen

The challenge

A technology stack that reflected years of rapid growth and acquisition, in an environment where system changes carry real compliance risk.

Repligen scaled rapidly through organic growth and acquisition, and their technology stack reflected that history: disparate systems, manual integration points, and data workflows that had grown complex with the business. The challenge wasn't a single migration or product build. It was a sustained programme of technical modernisation in a highly regulated, operationally sensitive environment where system changes carry validation risk and require careful governance.

What we built

Five years of embedded engineering across concurrent workstreams.

Document Intelligence: automated extraction of structured data from life sciences documentation at operational scale, using Azure Document Intelligence. Replacing manual document processing workflows that created operational bottlenecks.

Enterprise platform integration: connecting Repligen's core systems. SAP via OData for operational data, Snowflake as the analytical data warehouse, ServiceNow for IT service management and workflow orchestration, and Microsoft 365 and Teams for collaboration layer connectivity.

Cloud migration: progressive migration of legacy applications and data to cloud infrastructure, with operational continuity and compliance posture maintained throughout.

Technical approach

Two principles that define how this programme runs.

Forward-deployed engineering model

s-team engineers work inside Repligen's teams rather than as an external vendor. This gives the operational and regulatory context to make sound architectural decisions in a GxP-adjacent environment, and gives Repligen continuity of technical knowledge across a multi-year programme rather than repeated re-onboarding of new partners.

Progressive modernisation

In a regulated life sciences environment, large-scale system changes carry validation and compliance risk. The programme is structured as incremental modernisation: each workstream is scoped to maintain operational continuity, with changes validated before the next phase begins.

Outcome

An ongoing partnership entering its sixth year.

The engagement model — forward-deployed engineers with deep domain and operational context — reflects how s-team approaches complex, long-horizon technical programmes where continuity of knowledge is as valuable as technical capability.

A technology stack that reflected years of rapid growth and acquisition, in an environment where system changes carry real compliance risk.

Five years of embedded engineering across concurrent workstreams.

Two principles that define how this programme runs.

An ongoing partnership entering its sixth year.

Operating in life sciences and modernising your technology stack?