Software someone else built? We can take it over.
The developer left, the code is hard to follow, or every change breaks something. We read it, run it and tell you plainly what state it is in before we touch anything.
- The developer who built it has left, or stopped answering
- Nobody can say how to run it or put changes live
- Every change seems to break something else
- The hosting, framework or libraries are years out of date
- You were told it has to be rewritten and want a second opinion
- You share accessSource code, where it runs, and any third-party accounts. We agree a safe way to share it. Nothing sensitive goes through the web form.
- We get it runningWe rebuild the setup on our own machines. This often shows missing pieces, such as settings that exist only on the old server.
- We review itStructure, security, outdated parts, tests, how it is deployed and where the risks are.
- You get a plain-language reportWhat we found, what is urgent, what can wait, and what each option involves, so you can decide.
- We fix the urgent things firstSecurity holes, crashes and anything that puts the business or your customers at risk.
- We document and improveHandover notes first, then upgrades, tests and new features on solid ground.
- A written report on the state of your software
- Urgent problems fixed
- Notes explaining how to run, deploy and change it
- A recommended order of work, with the reasons
- A team you can keep working with, or hand over to
A good fit if
- You own the software or have the right to change it
- You can give us access to the code and where it runs
Probably not if
- It runs on a closed platform where the code is not yours to take. We will tell you early if that looks like the case
Tell us about your software
Get our 25-point checklist for software someone else built. Use it on your own first.
Get the checklistWhat do you need from us to start?
Access to the source code and to where the software runs (hosting, domain, any third-party accounts). If some of that is missing, we start by working out what exists. Do not send passwords through the form; we agree a safe way to share access first.
Do we need the original developer?
No. It helps if they can answer a few questions, but we can work from the code and the running system.
Will you rewrite everything?
Only if that is the right call. Often it is cheaper and safer to fix and improve what exists. If a rewrite makes sense, we explain why and what it involves before you decide.
What if the code is not ours to change?
If the software sits on a closed platform or the licence does not let you change it, we will tell you early, before any work starts.
Will you sign an NDA?
Yes. Ask for one before you share any code or access.