Key takeaways
- Most failing projects show the same warning signs long before they collapse.
- The first priority in any rescue is making sure you own and can access everything.
- A full rebuild is rarely the cheapest answer. Most apps can be stabilised step by step.
- An independent code review gives you facts before you make a big decision.
Software projects rarely fail all at once. They drift: releases slow down, bugs come back, and the people who understand the system become harder to reach. By the time it feels like a crisis, the warning signs have usually been there for months.
These are the signs we hear about most often from businesses that come to us for a project rescue. If several of them sound familiar, it is time to act.
Warning signs about people and access
1. Your developer has gone quiet. Replies take days, estimates keep slipping and you are not sure what is being worked on. Sometimes there is a good reason. Often it means the project has become hard to work on, or has been quietly deprioritised.
2. You are not sure you own everything. Is the code in a Git repository in your company's name? Are the server, domain, DNS and email accounts yours? If a supplier holds the keys, you are exposed.
3. Only one person understands it. If one developer left tomorrow, could anyone else deploy a fix? Knowledge held by a single person is a risk, however good that person is.
Warning signs in the software
4. Every release breaks something. Fixing one bug creates another, and releases have become stressful. This usually means there are few automated tests and the code is tightly tangled together.
5. Simple changes take weeks. A new field on a form, a tweak to an email or a small report should not be a project. When they are, technical debt is slowing everything down.
6. It is getting slower. Pages that were fast at launch now take seconds, or time out, as data grows. Common causes are missing database indexes, inefficient queries and heavy work done during page loads.
7. Errors are discovered by customers. If you hear about problems from support tickets rather than alerts, there is no error tracking or monitoring in place.
8. It is stuck on an old version. The app runs on Laravel 5, 6 or 7 and an old PHP version, and every attempt to update packages fails. Those versions no longer get security fixes. Our version support tracker shows the dates.
9. Nobody understands the code. This is increasingly common with applications built quickly using AI tools. The app works, but it grew without a plan, and now nobody can safely change it.
Warning signs in operations
10. Deploys are manual and scary. Releasing means someone logging into a server and running commands by hand, and only at weekends.
11. You have never restored a backup. There may be backups, but nobody has checked they work, or where they are stored.
12. Security questions get vague answers. When you ask about patching, access control or data protection, the answers are not specific. That is often because nobody is actively looking after it.
What to do next
If several of these sound familiar, these steps will make things better, whoever ends up doing the work.
Secure access first. Make a list of every account the application depends on: code hosting, servers, domain registrar, DNS, email sending, payments, storage and any third-party services. Make sure each one is in your company's name, and that you can log in.
Get the facts. An independent code review, or a vibe code review for AI-built apps, tells you what you actually have, what is urgent and what can wait. It costs a few hundred pounds and gives you a basis for every decision that follows.
Stabilise before you rebuild. It is tempting to start again from scratch. Sometimes that is right, but most struggling applications can be stabilised step by step: add monitoring and backups, fix the critical issues, add tests around the most important features and then improve the code area by area. That is usually faster and cheaper than a rebuild, and you keep a working product throughout.
Put maintenance in place. Once things are stable, a regular support and maintenance plan stops the same problems coming back.
How we can help
We take over Laravel projects in every state, from a tidy handover to a supplier who has disappeared. The first step is always a free call to understand what is going on. From there, our Laravel rescue service gets you back in control.