Bad agencies rarely look bad in the sales call — that is the one thing they are reliably good at. But failed projects leave fingerprints you can spot in advance. Here are twelve, from years of inheriting other people's rescues.
Before the proposal
1. They agree with everything. You describe six months of scope; they nod. A real partner pushes back on something — scope, sequence, a feature that will not matter. Universal agreement means they sell hours, not outcomes.
2. No questions about your business. If the conversation is all features and never "who pays for this and why," they will faithfully build your mistakes.
3. Portfolio you cannot touch. Screenshots instead of links, apps not in stores, "under NDA" for everything. One live product you can use beats fifty logos.
4. The team you meet is not the team you get. Insist on meeting the actual engineers. Senior sales face + junior delivery bench is the industry's oldest trick.
In the proposal
5. A quote with no scope document. A number without written features and acceptance criteria is a fee schedule, not a commitment.
6. Suspiciously cheap. 40% below every other quote means they bid to win and plan to renegotiate mid-project — when switching costs make you captive. (What honest numbers look like: our cost guides.)
7. Everything is "yes, easy". Complex integrations, AI features, tight deadlines — all easy? Estimation honesty predicts delivery honesty.
8. Big upfront payment. 50%+ before work starts, or IP transferring only at final payment — see the contract guide for what fair terms look like.
During early work
9. No working software by week 3–4. Slides and "architecture phase" instead of a demo. Real teams ship a thin slice early.
10. Repos in their account, reluctantly shared. Your code in your account from day one is non-negotiable; friction here predicts hostage dynamics later.
11. Silence between meetings. Async updates, decision logs, and demo recordings are what functioning delivery looks like (the rhythm we recommend); status-meeting-only communication hides drift.
12. Blame arrives before problems do. "That will be extra because you…" energy in week two tells you exactly how disputes will go in month four.
What good looks like
Scope pushback in the first call, a written proposal with acceptance criteria and fixed milestones, the real team on camera, working software weekly, your repos, clean exit terms. That list is also, not coincidentally, how we work. If you are comparing agencies right now, send us the same brief — calibrating quotes against each other is free.
Frequently asked questions
What are the biggest red flags when hiring a software agency?
Agreeing with everything you say, no questions about your business model, portfolios you can't actually use, meeting sales instead of engineers, quotes without scope documents, suspiciously low prices, and no working software in the first month.
Why is the cheapest software quote usually a trap?
A bid 40% below every competitor usually means winning now and renegotiating mid-project — once switching costs make you captive. Compare quotes against realistic market ranges and ask what the cheap quote is skipping: usually testing, security, or data work.
How early should an agency show working software?
A thin working slice by week 3–4. Weeks of slides, architecture documents, and status meetings without a demo is the classic pattern of teams that can't ship — demand demos of running software weekly.
What does a trustworthy agency look like instead?
They push back on scope in the first call, propose written acceptance criteria with fixed milestones, put the real engineers on camera, keep code in your repositories from day one, demo weekly, and offer clean exit terms without being asked.