Software projects rarely fail all at once. They drift. A demo gets postponed, a question goes unanswered for a week, an estimate quietly grows. Each slip has a reasonable explanation, and by the time the pattern is obvious, a large part of the budget is gone.
The warning signs are usually visible early, if you know what to look for. Here are the ones we would watch for, whether you are working with us or anyone else.
1. You have not seen working software in weeks
Status updates, slide decks, and screenshots are not progress. Working software you can click through is. On a healthy project, you should see something running on a regular rhythm, ideally every week or two.
When demos keep getting pushed, the usual reasons are that the work is harder than estimated, the team is stuck on something they have not mentioned, or not much has been done. Ask to see what exists today, even if it is rough.
2. Everything is "almost done"
Each feature is ninety percent complete, and stays there. This often means the remaining ten percent — edge cases, error handling, integrations — is where the real difficulty was, and it was not accounted for.
Ask for a list of what is finished, meaning tested and deployable, and what is not. "Done" should mean the same thing to both of you.
3. Questions get vague answers
You ask when something will be ready, and the answer is "soon." You ask why a feature is late, and the answer is general. Good teams can explain problems in plain terms, even unwelcome ones. Vagueness usually means the team does not know, or does not want to say.
4. The scope keeps growing, and so does the budget
Some change is normal. Every project learns as it goes. But if new requests are being added without anything coming off the list, and without a clear conversation about cost and timing, the project is expanding by accident.
Every addition should come with a trade: what it costs, what it delays, or what it replaces.
5. You cannot see the code
Your code should live in a repository your business owns or can access at any time. If you are told you will receive it at the end, or access keeps being deferred, treat that as serious. It affects your leverage if anything goes wrong.
6. Nobody is testing
Ask how features are tested before you see them. If the answer is that you are the testing process — finding bugs that should have been caught — quality problems will grow as the system gets larger.
7. Key people keep changing
A new developer every few weeks means knowledge is being lost and rebuilt repeatedly. Some turnover is unavoidable. Constant turnover is a sign of a team stretched across too many projects, or of work being handed to whoever is free.
8. You have stopped asking questions
This one is about you. When a project starts to feel uncomfortable, it is natural to check in less. Unfortunately, that is when attention matters most. Projects recover when problems are raised early, and they fail when everyone waits to see if things improve on their own.
What to do about it
Ask for a frank status meeting. Not a demo, a conversation: what is done, what is left, what is blocking it, and what the team now believes about the timeline. A good partner will welcome it.
Re-cut the scope. If the budget cannot cover everything, decide together what the smallest useful launch looks like and finish that first. A smaller system that works is worth more than a larger one that is still almost done.
Secure your assets. Confirm you have access to the code, the hosting, and every account. Do this before any difficult conversation about the relationship, not after.
Get an outside review. An independent developer can look at the code and the plan and tell you whether the project is recoverable as it is, needs a reset, or should change hands. That second opinion is inexpensive compared to the cost of continuing blind.
If your project is showing some of these signs and you want an outside read, tell us what is going on. We will look at where things stand and give you a direct assessment, even if the answer is that your current team can finish it.