FAQ

Fair questions.

Will you tell us to rewrite everything?

Almost never. Rewrites lose years and six figures, and most legacy apps don't need one. We stabilize what you have and modernize it incrementally — piece by piece, while it keeps running.

Our code is embarrassing.

We've seen worse — truly. Code that's quietly run a business for a decade deserves respect, not judgment. We don't critique, we triage.

What if we just want the audit?

That's fine. The Legacy Health Check report is yours to keep, and you can take it to any developer you like. No strings attached.

What do you cover?

PHP in all its versions, CakePHP and other PHP frameworks, MySQL and Postgres, heavily customized WordPress and WooCommerce — and the hosting environments they live on.

We don't have the code — only the live server.

That's more common than you'd think. Part of the Health Check is locating a complete copy of your code and database, getting both into version control, and making sure a tested backup exists somewhere other than the server itself.

Will the app go down while you work?

No. Stabilization work happens against a staging copy, and changes are rolled out carefully. Keeping your app running is a hard requirement of every engagement.

How do we get started?

Book a Legacy Health Check. You talk directly with the two of us, we get read-only access to what exists, and two weeks later you have a written report ranking what's urgent, what can wait, and what it costs.

Still have a question?

Ask us directly.