An old platform moved to a modern stack, one module at a time.
Your old app keeps running while each module is rebuilt and switched over, so customers never wait for a big release. The same code can ship to iPhone and Android.
Not the right team for a small app with good tests. A careful upgrade will do, and costs less.
- First module
- About 9 weeks
- From
- US$4,799 a month
- Moved to
- React · TypeScript
Six ways an old platform moves forward.
Most rebuilds use all six, planned module by module in the AI blueprint.
Front end rebuilds
An old Angular or Ionic front end moved to React and TypeScript, module by module.
Use case: legacy platform rebuild →Old and new side by side
Each module switches over on its own while the rest of the old app keeps working.
Proof: Parallel Completions →Web and mobile from one codebase
The rebuilt app ships to the web, iPhone and Android from the same code.
Service: AI mobile apps →Backends kept where they work
A working API and database stay, so the budget goes on what people touch.
See the stack →Better modules, not copies
Approvals, admin, search and reports rebuilt the way people now work.
Use case: completions tracking →AI added as you go
Search, drafting or support triage added to the new modules where they pay.
Service: AI features →A field platform, rebuilt while it ran.
Parallel Completions moved from Angular and Ionic to React and TypeScript, on the web, iPhone and Android, with the old app running until each module was replaced.
- 01Blueprint
- 02Build
- 03Live
- 01Blueprint
- 02Build
- 03Live
Illustrations of the build · sample data
A rebuild, one priced module at a time.
You can stop after any module and keep everything built so far. The old app keeps running throughout.
Scoping call
30 minutes on the platform, what slows your team down and what can't break.
- Time
- 30 minutes
- Price
- Free
- Ends with
- A written next step
AI blueprint
The old platform mapped, the new architecture, and a fixed estimate for the first module.
- Time
- 1 to 2 weeks
- Price
- US$1,800 fixed
- Ends with
- A module-by-module plan
First module
One module rebuilt and live beside the old app.
- Time
- About 9 weeks
- Price
- Build plan, US$4,799 a month
- Ends with
- The first module switched over
Every module after
The rest of the platform, web and mobile, one module at a time.
- Time
- Monthly
- Price
- Product team, US$14,399 a month
- Ends with
- The old app retired
Run and grow
Features, fixes and releases on the new stack.
- Time
- Monthly
- Price
- From US$599 a month
- Ends with
- A report every month
In US dollars · monthly plans on the pricing page
Modern, and still boring.
We move you to a stack your next hire already knows, and keep what still works.
React and TypeScript
The most common web stack, so your next developer can work on it. Types catch mistakes the old code let through.
A new front end means retesting every screen.
Keep the backend that works
A working API and database stay in place, as the Java API and PostgreSQL did for Parallel Completions.
Old backend limits stay until they are tackled on their own.
Capacitor for the phones
The rebuilt web app ships to iPhone and Android from the same code.
Heavy camera or offline work may need native code.
One switch per module
Each module moves across on its own, so a problem rolls back one module, not the whole product.
Old and new run side by side for a while, so both need care.
AI coding tools, reviewed by people
Tools such as Claude Code speed up reading and upgrading old code, and every change is reviewed and tested.
A person still owns each switch-over.
A written context file
Every repo explains itself, so any engineer or AI assistant can pick up the code where we left it.
It has to be updated with every change.
Where AI fits in a rebuild.
In the new modules, once the move is under way. Each links to a use case or a client build.
Search
One search across records, tags and documents, on the web and the phone.
Company search →Training videos
Training videos generated from your procedures, as we built for Parallel Completions.
The proof →Support triage
Tickets tagged and answered in draft, with a person sending every reply.
Inbox triage →Document reading
Old PDFs and scans read into the new system, with doubtful ones sent to a person.
Document extraction →Ask your data
Plain-English questions over the platform's database, with the query behind each answer.
Ask your data →Nothing breaks for your customers.
Live customers stay on a working app the whole way through, and access is checked on each new module before it switches over.
- Switch-over
- Each module switches over when your product owner signs it off. Until then the old one is one switch away.
- Your data
- Each module uses your existing data with tighter access rules, checked before switch-over.
- Your accounts
- The new platform runs in your cloud accounts and region.
- Reviews done
- An ISO 27001 and GDPR review for Parallel Completions, by the team that rebuilt and runs the platform.
What people ask first.
Short answers here. The scoping call gets you the long ones for your platform.
Will our customers notice the switch?
Only the better screens. Each module switches over when it's signed off, and the old one stays ready until then.
How long does it take?
The first module took about 9 weeks for Parallel Completions. Each module after is planned on its own.
Can we keep shipping features during it?
Yes. New features go into the new modules as they're built.
What stack do you move to?
Usually React and TypeScript on the web, with iPhone and Android apps from the same code.
Do you need our old developers?
Their knowledge helps, mostly during the AI blueprint. They don't need to stop what they're doing.
What does it cost?
The Build plan, US$4,799 a month, for the first module and the Product team, US$14,399 a month, for the rest, month to month with 30 days of notice.
Get this scopedin 30 minutes.
Bring the platform and the module that hurts most. You leave with a written next step and a price range for the first module.
India time · confirmed on Cal ID