This isn't theory
Eighteen years modernizing one system — without ever stopping it.
Over eighteen years, the same core team modernized Formpak's entire platform while the business kept running every single day. Windows to Linux. Containerized with Docker. The database migrated from DB2 to MSSQL and PostgreSQL. Java upgraded from 1.5 through to 17, across many generations of the stack. AI-assisted development introduced to make the work faster and the system easier to maintain.
None of it happened as a single disruptive rewrite. Each evolution was phased, tested, and rolled out carefully — so the platform stayed continuous while it changed underneath. Formpak grew from a handful of clients to more than a hundred. The team didn't just maintain the software; they came to understand the business.
Happening right now
A ten-year-old product. A team that had said no to AI.
A SaaS company with a product nearly ten years old and a fifteen-person engineering team had, until recently, resisted AI entirely. They added a single Core70 engineer — not to rewrite anything, but to use AI to raise code quality and security on an established codebase. Within weeks, the team itself had started adopting AI in their own work.
This is what modernization usually looks like in practice: not a dramatic replacement, but one engineer showing a cautious team that the system can get safer and easier to work with — without putting the business at risk.
How it actually works
Knowledge first. Then code.
A legacy system is dangerous to change because the knowledge of how it works has leaked away. So that's where we start. A senior engineer learns your system from the inside and builds a structured knowledge base — the business rules, the dependencies, the reasons things are the way they are. With that context in place, AI becomes genuinely useful: it can help reason about impact, generate routine changes, and surface what a rewrite-from-scratch would have missed. The engineer stays focused where judgment matters — architecture, business logic, the decisions a model shouldn't make alone.
We're applying the same approach to our own twenty-year-old internal system right now — so we know exactly what we're asking you to take on.
This is part of how we build everything. See our full approach →