Seven Signs a Software Agency Is Going to Disappear on You
The most expensive software project is the one that gets 70% finished and then stops. These are the warning signs, most of which show up before you sign anything.
The worst outcome in a software project is not overspending. It is paying seventy per cent of the budget for something that does not work, held together by a team you can no longer reach.
It happens often, and it is usually visible in advance. Here is what to watch for.
1. They quote before they understand
If a firm gives you a price in the first meeting, they are guessing. That guess will be wrong in one of two directions: too high, and you overpay; too low, and they discover it in month two, at which point they either cut quality or come back for more money.
What good looks like: a paid discovery phase, a written specification, and a price quoted against that specification. A firm confident enough to charge for thinking is a firm that has thought before.
2. You never meet the people who will build it
Sales meetings led by people who will vanish after signing is the oldest pattern in the industry. The senior engineer in the pitch is not on your project.
Ask directly: who will write the code, and can I meet them this week? Watch what happens next.
3. There's no working software until the end
"We'll show you at the end of the sprint cycle" is where projects go to die quietly. If you have not clicked on something by week two, you do not know whether anything is being built.
What good looks like: working software on a schedule you can set your watch by. Not a demo video. Not a percentage. Something you can open and use.
4. Everything is a yes
A firm that agrees to every request is not being accommodating; it is avoiding a conversation that will happen anyway, later, worse.
Real expertise includes "that's a bad idea, and here's why" and "that's outside what we're good at." A vendor who never pushes back is either not listening or not experienced enough to know what will hurt.
5. The contract has no exclusions section
Every good contract says what is not included. Its absence means either they have not thought about scope, or they are relying on ambiguity to bill more later.
While you are in there, read the IP clause. Standard templates often assign everything to the vendor, or leave it unclear. You want it explicit: you own the deliverable.
6. You can't see the code
If the work lives on their servers and you cannot access the repository, you are one disagreement away from having nothing.
What good looks like: code in a repository you own, from day one, with your account as owner rather than collaborator. Not handed over at the end. Yours from the first commit.
7. The price is dramatically lower than everyone else's
If three firms quote around $30,000 and one quotes $8,000, the cheap one has either misunderstood the scope or is planning to make it back later. Both end the same way.
Real cost differences between competent firms are maybe two to three times, driven by seniority and overhead. Ten times is not a discount; it is a different thing being sold.
What to actually ask
- Who writes the code, and can I meet them?
- When do I see working software, and how often after that?
- What's explicitly excluded from this scope?
- Who owns the repository during the build?
- What happens if it takes longer than you estimated?
- Can I talk to someone you've built something similar for?
That last one matters most, and the answer tells you plenty either way. A firm early enough not to have references should say so directly, then show you something else instead: the systems they have built, their code, a technical breakdown of how they solved a hard problem. A firm that dodges the question entirely is telling you something too.
The general principle
Almost all of these reduce to one thing: can you tell, at any given week, whether the project is going well?
If the answer is yes, you can course-correct early. If the answer is no, if you are waiting for a reveal, you have no way of knowing whether things are fine until it is far too late to fix.
Structure the engagement so you always know. Everything else follows from that.
We'd rather be measured against this list than avoid it. Book a call and ask us all seven.