Software projects don't fail overnight. They fail slowly, one missed deadline at a time. By the time most business owners realise something's wrong, they've already burned through budget and patience.

Here are five warning signs we see repeatedly — and what to do about each one.

1. Your Developer Has Gone Quiet

No updates. No status reports. When you ask for progress, you get vague answers or promises that it's "almost done." Silence is the single biggest red flag in any project. Good developers communicate regularly, even when the news isn't good. If your developer has gone quiet, something is wrong.

What to do: Demand a written status update with specific deliverables and dates. If you can't get one, it's time to bring in a second opinion.

2. "Almost Done" Has Lasted for Months

The 80/20 rule is brutal in software: the first 80% of features take 20% of the time. The last 20% takes 80%. If your developer keeps saying "almost done" but nothing is shipping, they're likely stuck on complexity they underestimated.

What to do: Ask for a feature-by-feature breakdown. What's done? What's in progress? What's blocked? Vagueness is the enemy.

3. Scope Creep Is Out of Control

The original spec said "simple booking system." Now it has AI recommendations, a loyalty programme, and real-time notifications. Scope creep is natural — but unmanaged scope creep kills projects. Every new feature adds complexity, testing time, and risk.

What to do: Freeze scope. Ship what you have. Add features in phases after launch. A delivered product beats a perfect plan every time.

4. The Codebase Is a Black Box

If you ask how something works and your developer can't explain it in plain language, that's a problem. If you've never seen the code, never had access to the repository, or don't know where it's deployed — you don't own your product. You're renting it.

What to do: Insist on access to your source code, deployment credentials, and documentation. If your developer resists, that tells you everything.

5. You've Lost Confidence

Gut feeling matters. If you've started looking for alternatives, if you dread the next status call, if you're quietly rebuilding in your head — trust that instinct. The cost of restarting is almost always less than the cost of continuing with the wrong team.

What to do: Bring in an independent technical advisor to audit the project. A fresh set of eyes can tell you in a week what took you months to figure out.

We Specialise in Project Rescues

If any of these sound familiar, we can help. We've rescued projects with missing source code, broken deployments, and zero documentation — and gotten them back on track. Let's talk about where your project stands.