How do you modernise a platform that professionals depend on daily — without ever letting them feel the change?

01 — Problem

Wolters Kluwer is a Fortune 500 company. Their software is what tax lawyers, accountants and compliance teams open every morning. At ArdentCode, we were responsible for building and evolving parts of that platform — complex, regulation-heavy domain logic, a user base that could not afford outages, and a codebase that had grown over years of accumulated decisions. Modernising it meant making changes that were invisible to end users.

02 — Constraints

• Regulatory domain — incorrect UI is not a UX problem, it is a compliance risk
• US and European product lines with divergent legal requirements sharing a core architecture
• Long-tenured users with established workflows — every interaction change had to be justified and gradual

03 — Architecture

A hybrid migration — AngularJS modules were progressively replaced with React components sharing the same data layer, so both ran in production simultaneously without a big-bang rewrite. A shared API layer abstracted US and EU product differences so the frontend remained consistent. Jenkins pipelines enforced deployments across both markets with environment-specific configuration injected at build time.

04 — Solution

Led the incremental migration from AngularJS to React across multiple product surfaces, replacing modules one at a time without disrupting live users. Designed the client-facing architecture for several new workflow features, gathered requirements directly with Wolters Kluwer product teams, and delivered solutions that respected both the regulatory constraints and the habits of experienced professional users. Over five years, grew from a developer executing tasks to the engineer setting frontend direction.

• Software Engineer → Senior Frontend Lead
• Frontend architecture across React and AngularJS codebases
• Client-facing requirements, solution design and delivery

05 — Outcome