modernlift.

Talk to an expert

Or email us: sales@modernlift.ai
Engagement model

Start small.
Each step earns the next.

Three phases — Discovery, Accelerator, Transformation — and each one de-risks the one after it. You can stop cleanly at any boundary, and you know the cost and the deliverables before work begins.

Book a discovery call Email the team →
Fixed-price Discovery Fixed price per slice Stop at any boundary
Three phases
3–4 wks
Discovery
Assessment & roadmap
6–10 wks
Accelerator
First slice in production
4–18 mo
Transformation
Legacy decommissioned
4–8 wks
Slice cadence
A new slice in production
Marquee 2–3 yrs → 4–6 mo
The short answer

How does an engagement work?

An engagement runs in three phases, each de-risking the next. Discovery (3–4 weeks, fixed price) produces the blueprint, risk assessment, and estimates. Accelerator (6–10 weeks, fixed price per slice) puts the first slice in production behind a strangler facade. Transformation (4–18 months, T&M or fixed) delivers slices at steady velocity until the legacy is decommissioned.

The structure is deliberate. You are never asked to commit to a multi-year program on faith. Each phase produces something concrete and reversible, so the decision to continue is made with evidence in hand rather than at kickoff.

The phases

Three phases. Each de-risks the next.

Every phase has a fixed scope, a clear outcome, and a commercial model agreed before work starts. You see what you are buying.

01
3–4 weeks
Discovery
Assessment & roadmap
Fixed price
AI-accelerated deep-read of your codebase plus workshops with your subject-matter experts. You walk out with a documented baseline, a risk assessment, and effort estimates you can plan against.
You walk out with
  • + Architecture Blueprint
  • + Domain Model
  • + Migration Roadmap
  • + Target Architecture
  • + Test Harness
  • + Traceability Framework
02
6–10 weeks
Accelerator
First slice in production
Fixed price per slice
We modernize one real slice — the highest-leverage one — end to end: design, build, shadow-validate, promote. The strangler facade goes live and the test harness is in place. Your team works alongside ours throughout.
You walk out with
  • + First slice live in production
  • + Test harness in place
  • + Strangler facade live
  • + Behavior parity report
  • + Rollback boundary established
03
4–18 months
Transformation
Replace the rest, slice by slice
T&M or fixed
Continuous slice delivery at steady velocity until the legacy runtime is decommissioned. Duration scales with the size of the estate. Your team takes increasing ownership as our role tapers — no hand-off cliff.
You walk out with
  • + Steady slice cadence (every 4–8 weeks)
  • + Living spec library
  • + Team operating model
  • + Decommissioned legacy
A note on duration
The Transformation phase runs 4–18 months and scales with the size of the system. The four-to-six months figure is the marquee — it belongs to the framing "two-to-three years of work in four-to-six months," based on engineering modeling, with early engagements underway. It is the typical compression, not a guaranteed full-program range.
What Discovery produces

Six artifacts you keep — whether or not we continue.

Discovery is fixed-price and self-contained. Even if you take the output to another team, you leave with a documented, navigable picture of your own system.

Architecture Blueprint
A navigable map of the system as it actually is — components, dependencies, and the seams where slices can be cut.
Domain Model
The business reality the system encodes, captured as living specs your team and the AI both read.
Migration Roadmap
The order of slices, prioritized by business value and risk, with effort estimates against each.
Target Architecture
The modern shape the system is moving toward — stack-agnostic, chosen to fit your constraints.
Test Harness
The scaffolding that lets each slice be shadow-validated against the legacy before it is promoted.
Traceability Framework
The audit trail that ties every modern behavior back to the legacy behavior it replaces.
What we need from you

Three things, and we can begin.

The bar to start is low by design. We do not need a frozen roadmap or a reorganization — just enough access to see the system and the people who understand it.

01
Read access to the codebase
Our AI toolchain reads the system before anything is planned. Read access is enough — we do not need write access to begin.
02
An executive sponsor
Modernization touches more than engineering. A sponsor who can clear organizational blockers keeps the work moving.
03
Workshop time with SMEs
The rules that were never written down live in your subject-matter experts. A few hours of their time turns tribal knowledge into living specs.
You should never bet the business on a cutover date. Each phase ends somewhere safe.
— Why the model is staged