Education
Recovering a learning platform after its agency walked away
The original agency had stopped responding, there was no documentation, and each attempted fix by a freelancer broke something else.
Reliable, automated deployments restored
Code Audit & Project Rescue
Code audits and project rescue for software that is stuck.
An agency vanished, a developer left, or every release breaks something. We find out what you actually have, tell you plainly, and get it shipping again.
Code Audit & Project Rescue
A rewrite is the last resort, not the first.
Inherited codebases are rarely as bad as they look on the first day, and rarely as good as the previous team claimed. The honest answer is in the details: what is tested, what is fragile, what is merely unfamiliar.
We start with evidence. Most projects can be stabilised and improved in place, which keeps the business running. When a rebuild really is cheaper, we show the working behind that conclusion.
Included
- Architecture, security, performance and dependency review with written findings
- A stabilisation plan ranked by risk and business impact
- Tests, CI and monitoring added around the code that matters most
- Incremental refactoring or a staged rebuild, with the product live throughout
What you end up with
A written, prioritised picture of what is wrong, what it costs to fix, and a product that deploys reliably again.
The difference
A project in trouble vs. a project under control
The code may be largely the same. What changes is how much anyone trusts it.
Stuck project
- Nobody is sure what a change will break
- Deployments happen rarely and go badly
- Bugs come back after being fixed
- Knowledge lives in the head of someone who left
- Estimates are guesses, so the roadmap slips
Recovered project
- Tests cover the paths that earn the revenue
- Automated deploys with a working rollback
- Errors tracked, triaged and trending down
- Architecture and setup written down
- Estimates based on a codebase people understand
What we build
How we step in
Start with the audit. What follows depends on what it finds.
Technical audit
A fixed-price review of architecture, code quality, security, performance and infrastructure, delivered as a written report.
Stabilisation
Critical bugs fixed, error tracking and CI added, and a safety net of tests placed around the riskiest code.
Takeover and handover
Assuming ownership from a departing team or agency: access, documentation, deployment and the things nobody wrote down.
Incremental modernisation
Replacing outdated frameworks and tangled modules piece by piece, with releases continuing throughout.
Process
How the work runs, phase by phase.
Each phase ends with something you can see, use or sign off.
Get access and get it running
Repositories, environments and credentials recovered, and the product running locally from written steps.
Audit
Code, dependencies, data, security and infrastructure reviewed. Findings are ranked by risk, not by how much they offend us.
Report and decide
A plain-language report with costed options: stabilise, refactor in place, or rebuild specific parts.
Stabilise
Monitoring, CI and tests go in first, then the urgent fixes, so later changes can be made with confidence.
Improve or hand over
We continue with the roadmap, or hand a documented, working codebase to your in-house team.
Stack
The tools we reach for.
Defaults, not dogma. If you already run something else, we work within it.
- Review
- Architecture review
- Static analysis
- Dependency audit
- Security
- OWASP Top 10
- Secrets scanning
- Access review
- Safety net
- Playwright
- Jest / Vitest
- GitHub Actions
- Visibility
- Sentry
- Profiling
- Query analysis
- Uptime checks
Timelines
How long it usually takes.
Typical ranges for well-scoped work. Discovery comes first and produces a fixed quote and a date.
- Technical audit
1–2 weeks
Written report with ranked findings and costed options.
- Stabilisation
3–6 weeks
Monitoring, CI, tests on critical paths and urgent fixes.
- Modernisation
Scoped from the audit
Staged refactor or rebuild with the product live throughout.
Case studies
Where we have done this before.
Industries
Sectors where this comes up most.
SaaS & Startups
From the first prototype to a platform that holds up under growth: a senior team for founders without one yet.
Retail & E-Commerce
Storefronts, apps and back-office tooling that load fast, convert and stay in sync with inventory.
Logistics & Field Service
Driver and technician apps, dispatch consoles and tracking that work where the signal does not.
FAQ
Code Audit & Project Rescue: common questions.
Can you take over a codebase another team wrote?
Often, yes. We start with a paid audit: what is salvageable, what is not, and what it costs to stabilise before adding features. Sometimes the honest answer is a rewrite, and we will say so.
What does the audit report contain?
A summary a non-technical owner can act on, followed by detailed findings on architecture, security, performance, tests, dependencies and infrastructure, each with severity, evidence and an estimated cost to fix.
Our previous developer is gone and we have no documentation.
That is the usual starting point. Recovering access and getting the product running from scratch is the first phase, and we write the documentation as we go.
Will you tell us to rewrite everything?
Only if the numbers support it. Rewrites are slow and risky, and improving in place is usually cheaper. Where we do recommend rebuilding, we scope it to the specific parts that need it.
Can you fix things while the product stays live?
Yes. Stabilisation and modernisation are done incrementally, behind tests and feature flags, so customers keep using the product throughout.
Next step
Have something that needs building?
Tell us the problem in a few sentences. We will reply within one business day with an honest read on scope, cost and whether we are the right team for it.