How it works
From your first message to production in 30 days.
Send the system today. A fixed price in 48 hours, working slices every few days, cutover with zero downtime by day 30. Here is every day of it.
Hour 0–48
Quote
Describe the system or give us read access. Within 48 hours a senior engineer sends back the scope, a start date and a fixed price.
You get
- Scope of work
- Fixed price per phase
- Start date
We need
- A short description of the system
- Read access, if you can share it
Days 1–3
Map
The platform parses the whole codebase in one pass. You get a map of every module, dependency, scheduled job and line of dead code.
You get
- Dependency graph of the whole system
- Dead-code and risk report
- Proposed service boundaries
We need
- Repository, build scripts and runbooks
- One engineer for an hour of questions
Days 4–5
Plan and lock the price
We agree the order of slices, the cutover plan and the parity criteria. The price and the date go into the contract.
You get
- Slice-by-slice plan with dates
- Cutover and rollback plan
- Signed fixed price
We need
- Sign-off on the plan
- Recorded production traffic, or access to capture it
Days 6–24
Rewrite and verify
Models rewrite slice by slice, a senior engineer reviews every one, and the parity harness proves each against your traffic.
You get
- Working slices every few days
- Tests written against real behavior
- Parity reports per slice
We need
- Reviews from your team as slices land
- Decisions on any accepted differences
Days 25–30
Cutover and handover
Traffic moves over slice by slice with the old system on standby. On day 30 your team takes the keys.
You get
- New system in production
- Repository, tests and documentation
- Up-to-date dependency map
We need
- A cutover window agreed with operations
Engagement
Three ways to start. Pick one today.
5 days
Assessment
The map and the priced plan on their own, delivered in 5 days. The fastest way to know exactly what you are dealing with.
30 days
Single phase
One system, rewritten and running in production at one fixed price.
30 days per phase
Program
Above a million lines we split the work into 30-day phases, each with its own fixed price and date.
In writing
Every one of these is in the contract.
- § 1
Fixed price
Agreed per phase before work starts. No hourly meter running in the background.
- § 2
30-day delivery
A date in the contract, not an estimate on a slide.
- § 3
Behavior parity
The new system matches the old one on your own recorded traffic, or the phase is not done.
- § 4
You own everything
Code, tests, documentation and the dependency map. No licence, no runtime, no lock-in.
- § 5
NDA first
Signed before we see a single file. Your paper or ours.
- § 6
Zero downtime
The old system keeps serving customers until the new one has proven it can.