Scaling 700+ Projects: How Nx Became a 'No-Brainer' for Caseware

Caseware is a global leader in audit and analytics software, trusted by financial professionals in over 130 countries. Their platform engineering team maintains and modernizes the development infrastructure behind dozens of products, each with different technical stacks and histories. Managing software development at this scale created fragmentation challenges that became impossible to ignore as the organization grew.

Challenge

Caseware's architecture had grown organically over more than a decade, leaving teams operating in silos with inconsistent toolchains, workflows, and end-user experiences.

• 700+ projects spanning 10+ years of legacy code across Java, C#, and diverse frontend technologies

• Teams operated independently with full autonomy over technology choices, creating fragmented workflows

• Inconsistent user experiences across products as each team built to its own standards

• No shared libraries, components, or styling standards to align development practices

This autonomy had fostered innovation, but it came at a cost. Without conformity across teams, the development overhead grew as the organization scaled — every team had its own expectations, and the end-user product felt noticeably different depending on which team had built it.

There was no conformity, really, so every team had a lot of autonomy. Our end-user product was quite different as you went between one team's product to the next.

What Caseware needed was a path to consolidation that didn't require mandating a disruptive, wholesale migration.

Solution

Caseware's platform engineering team evaluated an incremental consolidation strategy, ultimately building around Nx and the Nx Enterprise tier to unify their monorepo at scale.

• Created a shared frontend monorepo with Angular libraries for reusable UX components and styling standards

• Migrated backend applications into the unified workspace after early frontend gains proved the model

• Onboarded Nx Enterprise via a single-line nx.json configuration change

• Dedicated a migration support team to guide other squads through the transition

• Established regular check-ins with the Nx team for strategic guidance and custom metric reporting

The shared library approach quickly became the de facto standard across the organization. Teams that initially had full autonomy over their technology choices voluntarily migrated their frontend code once they saw the efficiency gains firsthand. From there, the model expanded naturally to full-stack — every application now lives in the unified workspace, creating efficiencies in both local development and CI/CD.

The partnership with the Nx team extended beyond tooling. Regular strategic check-ins provided direction, and the Nx team occasionally produced bespoke metric reports with aggregated data that helped pinpoint specific bottlenecks within the repo — giving the platform team actionable insight they couldn't get elsewhere.

• 93% remote cache hit rate across the monorepo

• 181 days of compute saved every single week

• 5,400+ hours freed per week for faster iteration and delivery

• Voluntary, org-wide migration driven by demonstrated value rather than mandates

Activation of the Enterprise tier required only a one-line configuration change — and when the trial expired, the team's reaction made the business case immediate and unmistakable.

After that trial, once it expired, it was like immediate — 'oh no, what are we going to do?'

Results

93% Cache Hit Rate Reclaims Thousands of Compute Hours Weekly

By leveraging Nx's remote caching across both local development and CI, Caseware achieved a 93% cache hit rate. The cumulative impact is significant: 181 days of compute saved every single week, freeing more than 5,400 hours for faster iteration and delivery across the organization's 700+ projects.

Task-Level Visibility Simplifies Budget Justification

With applications carrying over a decade of legacy code, having granular metrics at the project and task level became essential — not just for engineering insight, but for leadership conversations. Because Nx understands the codebase at the task level, the platform engineering team can pinpoint exactly where time is being saved and where bottlenecks remain, making investment decisions and budget approvals straightforward.

"Being able to log into the Nx site and see all the tasks being run, seeing how much time we were saving — those were all great metrics to provide to the management team to help justify the value add that Nx provides."

Voluntary Adoption Replaced Top-Down Mandates

Rather than forcing migration, Caseware focused on demonstrating value and removing friction. A dedicated migration support team walked squads through the transition, building trust and confidence in the monorepo model. The result was organic, enterprise-wide adoption — teams moved voluntarily once the efficiency gains became undeniable.

An Ongoing Partnership That Compounds Over Time

Caseware's relationship with the Nx team continues to deliver value beyond the tooling itself. Regular check-ins provide strategic guidance, and custom metric reports surface insights that help the platform team stay ahead of emerging bottlenecks — turning what started as a frontend consolidation initiative into a long-term engineering advantage.