How to Hire a Software Development Agency: 12 Red Flags

To hire a software development agency well, check five things before you sign: whether they have shipped something like your project, whether they can explain their process in plain language, who will actually do the work, how they handle change and bad news, and whether you will own everything at the end. Most bad engagements trace back to a warning sign visible in the first two calls. The 12 below are the ones that matter most.

This is written from the agency side, so we are describing our own industry's failure modes. If you are still deciding what to build, begin with how to build an MVP and choosing a tech stack.

#Key takeaways

• Vague scope produces vague results. Good agencies ask more questions than they answer on the first call.
• Ownership must be explicit. Code, designs, data and accounts should end up with you.
• Communication is the best predictor. How they handle the sales process is how they will handle the project.
• Evidence beats claims. Ask for relevant work, references and a live product you can try.
• A small paid discovery step reduces risk for both sides.

#The 12 red flags

#1. A fixed price with no discovery

If a quote arrives after one call with no questions about users, integrations or constraints, it is a guess. Either the scope will balloon later, or corners will be cut to hit the number.

#2. They never push back

An agency that says yes to every feature is not protecting your budget. Good teams challenge scope and suggest a smaller first release.

#3. No relevant work to show

Look for projects of similar complexity and type, ideally live ones you can click through. Screenshots alone prove little.

#4. Reluctance to offer references

Past clients are the best source of truth. Ask what went well, what went wrong and how problems were handled.

#5. You never meet the people who will build it

The pitch is delivered by sales, and the work goes to a team you have not met. Ask who will lead the project, who writes code, and whether they will be on your calls.

#6. Unclear ownership terms

You should own the source code, designs, content, data and third-party accounts. Beware of arrangements where the agency retains the repository, hosts everything under their accounts or charges to release your code.

#7. No process you can describe

Ask how a typical project runs: discovery, design, build, testing, release, handover. If you hear buzzwords instead of a sequence, the process may not exist.

#8. No visibility during the build

You should see working software regularly, not just reports. Ask about demos, staging environments and how progress is tracked.

#9. Vague answers on testing and quality

How do they test, review code and prevent regressions? See testing strategy guide for what good looks like.

#10. Silence on risk and technical debt

Every project makes trade-offs. A trustworthy agency tells you where shortcuts are being taken and what they will cost later. See technical debt management.

#11. Pressure tactics

"This price expires Friday" or "we only have one slot" is sales pressure. Real scoping takes time.

#12. No plan for after launch

Hosting, monitoring, bug fixes and handover documentation should be discussed before you sign, not after. Ask what happens if you want to move to another team.

#Questions to ask in the first call

1. Which of your past projects is closest to this one, and what was hard about it?
2. Who will work on it, and what is their experience?
3. How do you handle scope changes and delays?
4. What do I own at the end, and what do you retain?
5. How will I see progress each week?
6. What is not included in this quote?
7. What would you cut to launch sooner?
8. What have you learned from a project that went badly?

The last question is the best filter. Honest agencies have an answer.

#What a healthy engagement looks like

• A short discovery step that produces a written scope, a plan and an estimate in weeks.
• A small first release that validates the riskiest assumption.
• Regular demos of working software.
• Clear change handling: what is in, what is out, and the cost of changes.
• Full handover: code, documentation and accounts, with no lock-in.

You can see the logic of weeks-based estimating in MVP development cost and timeline, and a cost-driver view in how much it costs to build an AI agent.

#Comparing proposals fairly

Put proposals in a table: scope, assumptions, exclusions, timeline in weeks, team, ownership terms and post-launch support. The cheapest quote is often the one that excludes the most. Ask each vendor what is missing from theirs.

#Talk to us

We are happy to be held to this list. Tell us what you want to build and we will answer these questions about your project, including what we would leave out of the first release. Talk to us about your project, or look at the timeline logic in the estimator.

#FAQ

#How do I choose a software development agency?

Check relevant experience, who will do the work, how they communicate, how they handle change and what you own at the end. Ask for references and a live example of similar work.

#Should I choose a fixed price or time and materials?

Fixed price works when scope is clear and small. For uncertain scope, a phased approach with a short paid discovery is usually safer than a fixed quote that hides assumptions.

#How much should discovery cost?

It should be small relative to the build, since its job is to reduce risk. Beware of free "discovery" that is really a sales pitch with a quote attached.

#What should I own after the project?

The source code, designs, content, data and any accounts created for the project, with documentation to maintain or move it.

#How do I avoid vendor lock-in?

Insist on ownership of the repository and accounts, standard technologies and handover documentation from day one.

#Sources and further reading

Primary documentation, standards and research on the topics covered in this article:

• Manifesto for Agile Software Development
• Martin Fowler: Technical Debt
• OWASP Top 10