Red Flags When Hiring a Software Development Agency

The biggest red flags when hiring a software development agency are a firm price on a vague brief, no written change process, code and hosting kept in the agency's own accounts, and nobody named as your day-to-day contact. Any one of these can be fixed in negotiation. Two or more together, and you should walk away.

Most failed software projects do not fail because the developers could not code. They fail because the warning signs were visible early and nobody acted on them. This checklist is arranged by stage, so you can use it as you go: during sales conversations, when reading the proposal, before signing, and in the first month of work. If you want a benchmark for how a healthy project runs from start to finish, our end-to-end custom software guide sets it out.

What are the red flags in the first sales conversation?

The first call should feel like an interview of your business. If it feels like a product demo of the agency, take note.

• They quote before they understand. A price on the first call, based on a two-line description, is a guess. Either it is padded heavily or it will grow through change requests.
• They never say no. Every feature you mention is "easy" and "no problem". Good agencies push back on scope because they know what drives cost and delay.
• They cannot explain their work in plain language. Jargon is sometimes a cover for not understanding your problem. If they cannot explain an API to you in one sentence, they will struggle to explain a delay.
• The portfolio is all screenshots. Ask to see something live, or to have someone walk through how a feature works. Mock-ups prove design skill, not delivery.
• The salesperson is the only person you meet. Ask to speak to whoever will lead the build. If that is not possible before signing, you are buying blind.

A good first call ends with the agency asking you more questions than you asked them.

What should worry you in the proposal?

A proposal is the agency's best behaviour in writing. If it is vague now, it will be vaguer once money has changed hands.

Read it with a pen and look for these:

1. Features described as nouns, not behaviours. "User management" could mean a login page or a full permissions system with audit logs. Good proposals describe what users can do.
2. No list of exclusions. Every quote leaves things out: hosting, third-party licence fees, content loading, app store accounts, training. If none are listed, you will discover them on invoices.
3. No discovery or design phase for a complex build. Jumping straight to development on anything bigger than a small tool means decisions will be made in code, where they are most expensive to change. Our explainer on why a software discovery phase saves money shows what you should get from that phase.
4. One giant payment milestone. Large upfront payments with nothing tangible delivered until the end shift all the risk to you.
5. Timelines with no assumptions. "Twelve weeks" means nothing unless it states what you must provide and by when.

Which contract terms are dealbreakers?

Contract red flags matter most because they decide who holds the power if things go wrong. These are the ones we would not sign.

Contract model matters too. A fixed price on an unclear scope and an open-ended hourly arrangement with no cap are both risky in different ways. Our breakdown of the three main software contract models explains which fits which kind of project.

What are the warning signs once work has started?

The first four weeks reveal how the next six months will go. Watch the behaviours, not the promises.

• You have not seen working software after three or four weeks. Even early, you should be able to click through something on a test site. Slide decks and status emails are not substitutes.
• Demos keep getting postponed. One cancellation happens. A pattern means there is nothing to show.
• The team changes without warning. If the developers you met are replaced by people you have never heard of, ask why, and ask for a handover plan.
• Questions go unanswered for days. Slow replies early are rarely followed by faster ones later.
• Every issue is someone else's fault. The hosting provider, the payment gateway, your team's feedback. A healthy agency owns its share of problems.
• You cannot get access to the code. If you ask to see the repository and get excuses, treat it as a serious warning.

Security is an area where honesty is especially telling. Real systems have bugs, and a trustworthy agency tells you when it finds one. On our own website, for example, we discovered that the login rate limit could be bypassed because the code trusted an IP header that a visitor could fake. We fixed it and documented it. An agency that claims it has never had a security issue is either very new or not looking.

Are there green flags that look like red flags?

Yes. Some behaviours feel uncomfortable at first but are actually signs of a careful partner.

• They charge for discovery. Free discovery often means a rushed one. Paid discovery means someone is accountable for a proper result.
• They recommend building less. Cutting your wish list for version one protects your budget and gets real users testing sooner.
• They suggest an off-the-shelf tool instead. An agency that tells you a subscription product will do the job is putting your interests ahead of a sale.
• Their quote is not the cheapest. A noticeably lower quote often has less testing, less project management, or a narrower definition of "done".
• They ask about your budget early. This is not a trick to charge the maximum. Without a budget, they cannot suggest sensible trade-offs.

What should you do if you spot red flags mid-project?

Act early and in writing. Problems that are named in week three are cheap; the same problems named in month five are expensive.

1. Write down the specific concern. "We have not seen a demo in four weeks" is actionable; "we are unhappy" is not.
2. Ask for a recovery plan with dates. A good agency will respond with concrete steps, not reassurance.
3. Secure your assets. Make sure you have access to the repository, hosting, domain and any third-party accounts. Do this calmly and before tensions rise.
4. Pause new scope. Do not add features while delivery is in doubt.
5. Get an independent review if needed. A few hours of an outside developer's time reviewing the code can tell you whether to continue or switch.

If you are still choosing, pair this list with our guide to the 15 questions to ask a custom software development company, which helps you spot strengths as well as weaknesses.

Frequently asked questions

Is a low quote always a red flag?

Not always, but it always needs explaining. Ask the agency to walk you through what is included, how much testing they budget, and who manages the project. A low price with a narrow scope can be fine; a low price that claims to cover everything usually is not.

What is the single biggest red flag in a software contract?

Code, hosting or domain ownership staying with the agency. Everything else can be fixed by renegotiation, but if they control the assets, they control your options. Insist on ownership transfer and accounts in your name.

Should I avoid agencies that use offshore developers?

No. Location matters far less than communication, process and ownership terms. Many offshore teams deliver very well; what you should check is overlapping working hours, a named point of contact, and regular demos.

How do I check an agency's references properly?

Ask for two or three past clients and speak to them directly. Ask what went wrong and how the agency responded, whether the project finished on budget, and whether they would hire them again. Reluctance to provide references at all is itself a warning sign.

Can a red flag be fixed, or should I walk away?

Many can be fixed by asking. Missing exclusions, unclear milestones and ownership wording are often oversights the agency will correct quickly. If they resist reasonable changes to ownership or termination terms, walk away.

Want a second opinion on a proposal?

If you have a proposal in hand and something feels off, we are happy to look at it with you and point out what we would question, whether or not you hire us. You can also see how we work in our portfolio, or talk to us about your project.