Updated June 2026
11 Red Flags When Hiring a Dev Agency
The expensive mistakes are visible before you sign. Watch for agencies that put senior people on the sales call and juniors on your code, quote hourly with no fixed scope, dodge IP ownership, show no working software until the end, or cannot name a single client you can verify.
The wrong agency rarely blows up on day one. It fails quietly. A polished pitch, a vague contract, three months of silence, then a product that does not work and a bill that does not stop. By the time you notice, your money and your runway are gone. Here is the good part: almost every bad outcome shows up during sales, if you know what to look for. Below are the eleven warning signs we see most often, what each one costs you, and the green flag to demand instead.
The 11 red flags
1. Senior people sell, juniors build
The impressive person on your sales calls vanishes the moment you sign, and your project lands with whoever is free. You paid for expertise and got training, on your dime. Green flag: the agency names the actual senior people who will write your code, and you meet them before you pay.
2. Hourly billing with no fixed scope
Open-ended hours mean the slower they work, the more they make, and the overrun is your problem, not theirs. Green flag: a fixed price tied to a defined scope, so the delivery risk sits with the agency.
3. They dodge IP ownership
If the contract says nothing about who owns the code, the agency might keep it, and you are renting your own product. Green flag: the contract assigns 100% of the IP to you on payment, in writing, no exceptions.
4. No working software until the end
A big reveal at the finish line means months of “progress” you cannot check, and zero leverage when it turns out wrong. Green flag: you see working software in a live demo every week, before each payment.
5. No client you can actually verify
Logos on a slide are not references. If you cannot speak to a past client or click a live product, you have no proof they ship anything. Green flag: they hand you verifiable clients and shipped work you can check yourself.
6. The estimate is suspiciously cheap
A quote far below everyone else usually means the scope is underspecified, and that gap comes back as change requests. The cheap build becomes the expensive rebuild. Green flag: a realistic price with the assumptions and exclusions written out.
7. Vague, non-technical answers
If they cannot explain how they will handle auth, data, or scale in plain language, they have not thought it through, or they are hiding who actually does the thinking. Green flag: straight technical answers and a clear architecture you can follow.
8. No process, no project lead, no roadmap
“We will figure it out as we go” means you become the project manager for a team you are paying. Green flag: a named point of contact, a written plan, and milestones with dates.
9. Heavy upfront payment, weak guarantee
A big deposit with nothing tied to delivery puts all the risk on you and none on them. Green flag: payments tied to milestones you have approved, and a clear scope-and-revisions guarantee.
10. They overpromise on timeline
An unrealistically fast estimate wins the deal, then quietly slips, or ships something fragile to hit the date. Green flag: an honest timeline with buffer, and a willingness to push back on your scope.
11. Communication is already slow during sales
If they are slow to reply while they are still trying to win you, it only gets worse after you sign. Green flag: prompt, specific communication and a stated response cadence from the first call.
Red flag vs green flag
Use this as a one-page screen before you sign anything.
| Red flag | Green flag |
|---|---|
| Senior on the call, juniors on your code | Named senior team builds your project |
| Hourly billing, no fixed scope | Fixed price tied to a defined scope |
| Silent or evasive on IP ownership | 100% IP assigned to you, in writing |
| No software shown until the end | Live weekly demos before each payment |
| Logos only, no verifiable clients | References and shipped work you can check |
| Big upfront deposit, weak guarantee | Milestone-based payments and a clear guarantee |
| Vague, no process, no project lead | Named lead, written plan, dated milestones |
How to run the screen in one call
You do not need a procurement department. On the first call, ask four questions and watch how comfortable they are answering. Who specifically writes my code, and can I meet them? Is this a fixed price for this scope? Do I own the code outright on payment? Can I see working software every week before I pay for it? An agency built to deliver answers all four without flinching. For the full version of this conversation, see our list of questions to ask an MVP development company.
Is an agency even the right choice?
Some of these risks are a fit problem, not a quality problem. A solo freelancer, an agency, and an in-house hire each fail differently, and the right answer depends on your stage, your budget, and how much you can manage directly. Our breakdown of agency vs freelancer vs in-house walks through the trade-offs so you screen for the right thing in the first place. If you already know you want a senior-led team, here is how we work.
Want a second opinion before you sign?
We do a free 15-minute build audit. Bring the proposal or your half-built product, and we will tell you the specific gaps, the risks, and what it actually takes to deliver. No obligation, no pitch.
FAQ
What is the biggest red flag when hiring a development agency?
Refusing to name who will actually write your code. When senior people sell and juniors build, you pay for expertise you never receive. Insist on meeting the senior team assigned to your project before you sign or pay anything.
Should a software agency charge a fixed price or hourly?
For a defined project, a fixed price tied to a clear scope is safer for you, because it puts the overrun risk on the agency instead of your budget. Open-ended hourly billing with no scope rewards slow work and leaves cost uncapped.
Who owns the code an agency writes for me?
You should, fully, the moment you have paid. Get it in writing: the contract must assign 100% of the intellectual property to you on payment. If an agency is vague or evasive about IP ownership, treat that as a serious warning sign.
How can I verify an agency before signing?
Ask for clients and shipped products you can independently check, not just logos on a slide. Then confirm you will see working software in a live demo each week before you release the next payment. Verifiable proof beats a polished pitch every time.