Legacy modernization
Old code moved to new, checked by your own tests.
Rules convert what they can, agents finish the rest, and your test suite decides what ships.
- 6 to 8 weeks
- to live on real traffic
- Founder-led
- no handoff to juniors
- Fixed price
- agreed before work starts
| Module | Lines | Tests | Status |
|---|---|---|---|
| billing-rules | 18,240 | 186 | Legacy In progress Migrated |
| invoice-export | 9,810 | 142 | Legacy In progress Migrated |
| tax-calculation | 12,460 | 204 | Legacy In progress Migrated |
| customer-accounts | 22,105 | 312 | Migrated |
| order-history | 7,930 | 128 | Migrated |
| report-scheduler | 5,120 | 3 | Legacy |
| legacy-ftp-import | 3,480 | 0 | Legacy |
We have known for years that the old framework must go
The estimate says a full team for eighteen months, nobody can spare that team, and every year the code gets harder to change.
of US federal IT spending goes to running existing systems.
Sourcegao.gov
critical federal legacy systems were modernized six years after the warning.
Sourcegao.gov
of professional developers name technical debt as a top frustration.
Sourcesurvey.stackoverflow.co
Old code moves only when your tests say it still works.
| What changes | Without it | With it |
|---|---|---|
| Timeline | Estimated in years. | Planned in weeks. |
| Who does the work | A team pulled off features. | Rules and agents, with people reviewing. |
| Safety | One big rewrite. | Every change passes your tests. |
What we build
What changes for your teams. We pick the tools to fit the systems you already run.
| Module | Lines | Tests | Status |
|---|---|---|---|
| billing-rules | 18,240 | 186 | Legacy In progress Migrated |
| invoice-export | 9,810 | 142 | Legacy In progress Migrated |
| tax-calculation | 12,460 | 204 | Legacy In progress Migrated |
| customer-accounts | 22,105 | 312 | Migrated |
| order-history | 7,930 | 128 | Migrated |
| report-scheduler | 5,120 | 3 | Legacy |
| legacy-ftp-import | 3,480 | 0 | Legacy |
| Module | Lines | Tests | Status |
|---|---|---|---|
| billing-rules | 18,240 | 186 | Legacy In progress Migrated |
| invoice-export | 9,810 | 142 | Legacy In progress Migrated |
| tax-calculation | 12,460 | 204 | Legacy In progress Migrated |
| customer-accounts | 22,105 | 312 | Migrated |
| order-history | 7,930 | 128 | Migrated |
| report-scheduler | 5,120 | 3 | Legacy |
| legacy-ftp-import | 3,480 | 0 | Legacy |
Measured against where you started
What changes at a company like Acme Inc
Illustrative figures, not a client result. Your own baseline is taken in the first week.
How others built it
Another company built the same kind of system and wrote publicly about how it went.
- AirbnbAccelerating large-scale test migration with LLMs
What they learned
When tests check every change, AI agents can finish in weeks a migration that was planned to take years.
Nearly 3.5K test files migrated in 6 weeks, against an estimate of 1.5 years by hand.
Everything runs in your cloud, and stays yours
You own the config, the tests and the runbooks, so you can swap any part later.
Pull requests that pass your tests, each reviewed by your people.
| Module | Lines | Tests | Status |
|---|---|---|---|
| billing-rules | 18,240 | 186 | Legacy In progress Migrated |
| invoice-export | 9,810 | 142 | Legacy In progress Migrated |
| tax-calculation | 12,460 | 204 | Legacy In progress Migrated |
| customer-accounts | 22,105 | 312 | Migrated |
| order-history | 7,930 | 128 | Migrated |
| report-scheduler | 5,120 | 3 | Legacy |
| legacy-ftp-import | 3,480 | 0 | Legacy |
A progress report of files done, files failing and why.
The recipes and a runbook, so the next migration starts from them.
Typical building blocks: OpenRewrite or ast-grep recipes first, then a headless Claude Code fleet in a test-gated retry loop in worktrees; failures clustered; people review every PR.
Alternatives: AWS Transform custom; Moderne.
Live in 6 to 8 weeks
The work happens in your cloud, with the people who will own it.
- Weeks 1 to 2Pick the module, write the rules and test them on a sample.
- Weeks 3 to 6Run rules and agents across the code, group the failures and fix them in batches.
- Weeks 7 to 8The last files are reviewed and merged, then we hand over the recipes.
- After thatRunning on real traffic
Old code moved to the new framework, checked by your tests.
Before we start
- Write access to the repo and a pipeline that runs the tests.
- A named tech lead who reviews and merges the pull requests.
- About 5 hours a week of review from your engineers.
Is this the right first build?
It fits when
- The migration was estimated in years.
- Agents rewrite code nobody checks.
- A team on your side will own it after we leave.
It does not fit when
- You want a hosted tool picked and resold to you.
- You want a strategy deck in place of working software.
- Nobody on your side can own it after we leave.
What’s included and what isn’t
Included
- One migration on one module, such as a framework upgrade or a library swap.
- Up to 500 files changed, each through a reviewed pull request.
- The rules and the agent setup in your repo.
- A weekly report of files done, files failing and why.
Not included
- Changing what the code does: behaviour stays the same.
- Adding tests to untested code, which is quoted on its own.
- More modules, which start from the recipes after the pilot.
6 to 8 weeks. You get a price range before the call and one fixed number after it. That number is the invoice.
- If the work takes longer than we planned, we absorb the cost.
- You pay 50% at the start and 50% at acceptance. Builds of 6 weeks or more pay 40% at the start, 30% at the midpoint and 30% at acceptance.
- If a build starts within 60 days of your Audit results, the full Audit fee comes off its price.
- We start three new projects a quarter, so your start date depends on when you book.
Questions teams ask before they book
Which tools do you use?
We pick the one that fits the systems you already run. You own the config, the tests and the runbooks, so you can swap any part later. Most often OpenRewrite or ast-grep recipes first, then a headless Claude Code fleet; AWS Transform custom or Moderne when they fit better.
Which migrations fit?
Framework upgrades, language versions, test frameworks and library swaps: work that repeats across many files.
What if our test coverage is low?
We add tests around that code first. Without a test to pass, an agent has nothing to prove, so we do not let it change that code.
Who reviews the changes?
Your engineers. A person reviews every pull request before it merges.
Does our code leave our cloud?
No. The agents run in your cloud or on machines you control.
How long does it take?
6 to 8 weeks for a one-module pilot. The size of the code and its test coverage set the time, and we confirm it after the sample run.
Legacy modernization, running in your cloud in 6 to 8 weeks.
Old code moved to the new framework, checked by your tests. You own the config, the tests and the runbooks.