We take over an app from another team and keep developing it
We start with an audit of the code and access, add tests around the risky parts and sort out deployments. Then we develop the app like our own code.
Four steps of a takeover
The app keeps running the whole time; users don't notice the team changed.
- 1AuditWe read the code and check dependencies, the database and servers. You get a list of risks, most urgent first.
- 2AccessRepos, servers, domains and third-party accounts move to your company.
- 3Safety netWe add tests where a change could break the most, and set up automated deployments.
- 4Ongoing developmentWe take on requests and new features in your order of priority, releasing every week.
Signs it's time to change teams
Your vendor has no time
The developer left
Every change breaks something
You don't have the code
Which apps we take over
Including technologies nobody wants to touch anymore.
Front end
Back end
Databases
CMS
Infrastructure
No documentation
How we check the results
After the takeover we track production errors, time from request to release and failed deployments.
- 1Production errors
- 2Time from request to release
- 3Failed deployments
- 4Audit risks closed
The audit's risk list closes item by item, and you see it every month.
Common questions
What if the previous vendor won't hand over access?
We help recover it through domains, servers and accounts registered to your company. If the code is only on the server, we start from there.
Will you rewrite the app from scratch?
Usually not. We rewrite only the parts that cost more to maintain than to replace, and we base that on the audit.
Will users notice the change of team?
They shouldn't. The app keeps running, and our first changes go out only with tests in place.
Can we start with just the audit?
Yes. The audit is a separate stage and stays yours whatever you decide next.
Describe the app to take over
Tell us what the app is built with, who maintains it today and what isn't working. We reply within one business day.