Prepared by
For
Existing codebase support
We get an inherited or unfinished application running, tell you what state it’s in, and help you decide what to do next.
What’s delivered
- A list of everything it depends on. Every account, service, domain and password the application needs, who owns each one, and what needs transferring to you.
- A working build. The application running on our machines and on a test server, with the setup steps written down.
- A written report. The state of the code, the software it relies on, the data and the hosting, with risks listed by how much damage they could do.
- Options with estimates. Usually a choice between making it safe, finishing what’s there, or replacing the parts that can’t be saved, each with its own estimate.
What’s needed to start
- Access to the code
- Hosting and service accounts
- Any documents or history
- Contact details for the last developer
- What you need next
What affects the cost
- How big the application is and how many services it uses
- Whether it currently runs anywhere
- Whether there are documents, or developers we can ask
- How many accounts need transferring
- How thorough the review needs to be, for example before buying a business
Usually included
- Reviewing web applications and writing up what we find
- Setting up development, test and live environments
- Recovering and transferring access you’re entitled to
- Fixing, finishing or maintaining it afterwards, if you’d like
Not included unless agreed
- Recovering accounts you don’t have a legal right to
- Formal security penetration testing
- Disputes with a previous supplier
- Guaranteeing the previous developer’s work
Dependencies
The review depends on access. If someone who won’t reply holds the accounts, getting them back through the provider’s support team can take longer than the technical work.
Indicative summary. Scope, timeline and cost are confirmed in a written quote for each project.