Strategy

Red flags when hiring a software development agency

Editorial · Reveneau · July 27, 2026 · Updated November 18, 2026

Red flags when hiring a software development agency

To choose a software development partner, write down what you need, ask every firm the same questions, check the answers against work you can see, start with a small paid first phase, and put ownership and payment terms in the contract before the main build. The warning signs that rule a firm out show in the first two or three conversations, if you know where to look. Reveneau is one such partner: AI writes all of its code, every change has to pass an eval suite written from the specification before it ships, and because it uses AI instead of hiring more engineers, that saving goes into the client's price.

None of what follows requires you to be technical. It requires you to ask direct questions and pay attention to how clearly the answers come back.

How do I choose a software development partner?

Choose on answers you can check, in this order.

  1. Write the brief first. Put down the problem, the people who will use the software, your budget range, your date, and what finished means. Every firm then quotes against the same brief, so the quotes can be compared. How to write a software development RFP covers what goes in it.
  2. Ask every firm the same five questions. Which people will work on the project, and what have they built? How is each change checked before release? What does the quote leave out? Is the price fixed, or billed by time and materials? Who owns the code, and from when?
  3. Check the answers. Ask to see software the firm has built, and speak with past clients whose work was like yours where the firm has them. Ask about a project that went wrong and what the firm did next.
  4. Score the firms side by side. Give each answer a score from 1 to 5, and give more weight to the questions that matter most for your project, so the decision rests on the same evidence for every firm.
  5. Start with a small paid first phase. A short piece of real work shows how a firm communicates and handles a surprise before you sign the large contract. How to structure a pilot before a full engagement sets out its scope and its exit terms.
  6. Put the terms in the contract. Code ownership, payment tied to milestones, how a finished piece is accepted, how a change request is priced, and how either side ends the contract. What to check before you sign a software development contract goes through each clause.

Most guides on this question are written by development firms, this one included, so test every step against your own project. The warning signs below are what wrong answers to steps 2 and 3 sound like. Reveneau takes responsibility for the whole project through production and after release, and the client owns the code.

They cannot say who works on your project

Some agencies present their most senior people in the sales process, then staff the project with whoever is free that month. The person who impressed you in the sales call leaves after the contract is signed, and contractors you never met take over your product.

So ask directly: which people will work on this project, what has each of them built, and how is their work checked before it reaches you? A confident partner answers without waiting. It explains how the team is organized, who is senior and who is learning, and what every change has to pass before release. A vague answer built around "our team" is a warning sign.

When the people who scoped the work are not the people who build it, the understanding of the problem gets lost in the handoff. Decisions that felt obvious in the sales meetings get made again, and worse, after the build starts. Insist on continuity between the people who sell and the people who build, and get it in writing if you can.

Their first deliverable is a document

A team that understands your problem proposes a small, concrete first phase: something working you can look at within the first two weeks. It might be rough. It might be one screen and one real workflow. It runs, and it tells you more about whether this partnership works than a slide can.

If what they propose is a long strategy document, or a discovery phase that produces only diagrams, you are talking to consultants. Strategy work has its place, and you hired an engineering partner to deliver software. Early working code brings up the hard questions while they cost little to answer. At the end of a project, the same answers mean rework.

Ask any agency what you will be able to see and use two weeks after the start. A specific answer is a good sign, and a vague one is a warning.

They want a large payment before any milestone

Reasonable engagement terms tie payment to delivery: a working part of the product, a completed phase, a tested release you can run. A large upfront payment with no defined milestone shifts all the risk onto you before you have seen any working code.

A partner needs commitment too, and a deposit is normal. Paying a large share of the total before there is anything to evaluate is a warning sign. Payment tied to milestones keeps both sides honest. It gives you a checkpoint to slow down or stop working together if the work is not what you expected, and it gives a good team a clear reason to put delivery ahead of billing. Treat an agency that refuses any link between payment and delivery as a firm to avoid.

The contract is unclear about code ownership

You should own the code, the architecture decisions, and the documentation, without exception. This sounds obvious, and it is a common place for founders to get stuck.

Read the intellectual property section of the contract. Contracts that keep licensing rights with the agency, or that tie your product to its own internal tools, private frameworks or hosting, give it power it can use against you later. You feel that power at renewal, when leaving means separating your product from systems you do not control and cannot take with you. An agency that controls the system that puts your software live can charge you for every change to a setting.

Ownership should pass to you as each piece of work is delivered. Waiting for a final payment far in the future leaves you without the code for the whole build. Ask where the code is kept, who has access, and what happens on the first day after you decide to stop working together. A partner building for your benefit answers these plainly. A vendor building so you cannot leave gets uncomfortable.

The timeline or price sounds too good

An agency that promises a date far earlier, or a price far lower, than every other quote you received may be skipping necessary work somewhere you will not see until later. The skipped work is often testing, security, or the plain architecture work that keeps a product running once real users arrive.

This one is hard for founders because the low number is also the tempting one. A serious estimate comes with a breakdown. Ask to see where the hours go: how much for the core build, how much for testing, how much held back for the unknowns that always appear. When a team can show you the parts of its estimate and explain its assumptions, you can trust the number even when it is higher than you hoped. When it cannot, the low price is a promise it has no plan to keep.

They talk about your industry in generalities

A partner who has delivered software in your industry asks more precise questions about your business than you expected. It knows where the hard parts are: the unusual compliance case, the integration everyone plans too little time for, the workflow that looks simple and never is. It can point to work in nearby fields and explain what carried over and what did not.

General talk about "startups" or "SaaS" gives you nothing to check. Watch how the agency responds when you describe your problem. Does it agree with everything and repeat your own words back to you, or does it challenge you, correct a wrong assumption, and tell you which part will be harder than you think? You want the second kind of conversation. It is uncomfortable at the time, and it saves you months later.

What this looks like done right

None of these checks needs technical expertise, only direct questions and attention to how clearly the answers come back. Put them together and the pattern is consistent: a good partner is specific where a bad one is vague, and makes exact commitments where a bad one avoids the question.

You can read how Reveneau scopes and staffs a full product build or a staff augmentation engagement, or the wider view of its custom software development work.

For the fuller version of this evaluation, see how to choose the right external development team, or the comparison of software development partner vs. vendor if you are trying to name the exact behavior these warning signs point to.

Related guide: How to choose a software development partner.

One more warning sign has come with AI writing code, and it takes two opposite forms. The first is a supplier who will not say how much of your code a model will write, or who treats the question as rude. The second is a supplier who treats AI writing the code as the whole answer and cannot describe what happens between the model producing a first draft and that draft serving real users. Both come from the same failure: no clear account of how the output is checked and who answers for it. Ask what every change has to pass before it reaches your code, and expect the firm as a whole to take responsibility for the project through production and after release.

The signs show early. Ask the direct questions, listen for clear answers, and choose another firm when the answers do not come.

Common questions

How do I choose a software development partner?

Write a brief first, then ask every firm the same questions about its people, how it checks each change, what its price covers and who owns the code. Check the answers against software the firm shows you and against past clients where it has them. Score the firms side by side, start with a small paid first phase, and put ownership, milestones and payment terms in the contract before the main build.

What is a warning sign in how an agency talks about who works on the project?

A vague answer built around "our team", with no names, no past work and no account of how changes are checked. Some agencies present senior people in the sales process, then staff the project with whoever is free that month, and the person who impressed you in the sales call leaves once the contract is signed. Ask which people will work on the project and how their work is checked before it reaches you.

Why is a large upfront payment with no milestones a warning sign?

Reasonable engagement terms tie payment to delivery: a working part of the product, a completed phase, a tested release. A large upfront payment with no defined milestone shifts all the risk onto you before you have seen anything working. A deposit is normal. Paying most of the total before there is anything to evaluate is a warning sign.

Should I worry if an agency guarantees a fast timeline or a low price?

Yes, when the date or the price is far from every other quote you received. That gap usually means work gets skipped where you will not notice it until later, often testing, security, or the architecture work that keeps a product running with real users. Ask for a breakdown of the estimate in place of a single lump sum.

What should the contract say about code ownership?

You should own the code, the architecture decisions, and the documentation, without exception. Contracts that keep licensing rights with the agency, or tie your product to their own tools or hosting, give them power they can use against you later, especially at renewal, when leaving means separating your product from systems you do not control.

How do I evaluate a software development agency before signing?

Ask direct questions in the first two or three calls and watch how clearly the answers come back. A good partner is specific where a bad one is vague, and comfortable giving exact commitments where a bad one avoids the question. None of this requires you to be technical.

What should I be able to see two weeks after a project starts?

Something working that you can look at and use, even if it is rough: one screen and one real workflow that runs. A team that proposes only a strategy document, or a discovery phase that produces only diagrams, is working as a consultant. How specific its answer is to this question shows you how it works.

Why does it matter if the people who sell the project are not the people who build it?

When the people who scoped the work are not the ones who build it, the understanding of the problem gets lost in the handoff. Decisions that felt obvious in the sales meetings get made again, and worse, after the build starts, so insist on continuity between the people who sell and the people who build.

What questions tell you an agency knows your industry?

A partner who has delivered software in your industry asks more precise questions than you expected and knows where the hard parts are, such as the unusual compliance case or the integration everyone plans too little time for. General talk about "startups" or "SaaS" gives you nothing to check.

When should ownership of the code transfer to me?

As each piece of work is delivered. Waiting for a final payment far in the future leaves you without the code for the whole build. Ask where the code is kept, who has access, and what happens on the first day after you decide to stop working together. A partner building for your benefit answers these plainly, while a vendor building so you cannot leave tends to get uncomfortable when you ask for details.

How does Reveneau avoid these warning signs?

AI writes all of Reveneau's code, and every change has to pass an eval suite written from the specification before it ships. Because it uses AI instead of hiring more engineers, the same build takes a small team and that saving goes into the client's price. The client owns the code, and Reveneau takes responsibility for the whole project through production and after release.

Start a project