Software development
Web apps, SaaS platforms, APIs and the systems underneath them.
Six to twenty weeks depending on scope.
Replace a legacy system without stopping the business
Map what it actually does, including the undocumented behaviour people rely on. Then replace it in slices with both running side by side, so each slice can be reversed on its own instead of betting the business on one cutover.
The problem
Something critical runs on software that is a decade old, unsupported, or written by someone who left. It cannot be switched off for a weekend and nobody fully knows what it does.
How we approach it
Map what it actually does, including the undocumented behaviour people rely on. Then replace it in slices with both running side by side, so each slice can be reversed on its own instead of betting the business on one cutover.
What changes
The old system retired, the data migrated and reconciled, and no day where the business could not operate.
The service this falls under
Cloud and infrastructure
Edge, databases, single sign-on, CI, observability and cost control.
Two to twelve weeks.
Last reviewed · Site changelog