Development Agency Red Flags: How to Spot a Bad Web or Software Partner Before You Sign
The most reliable red flags when hiring a development agency show up before any code gets written: a detailed price quoted before anyone asked about your business, a portfolio with no live links or named outcomes, contracts where the agency keeps ownership of your code, domain, or hosting, and a sales process where you never once speak to the people who will actually build your product. Each of these is checkable in the first meeting, and any two of them together is a reason to walk away.
Why this post exists
Bad agencies do not look bad in the sales meeting
Nobody hires a bad agency on purpose. The pitch deck looks sharp, the portfolio looks full, the quote arrives fast, and the sales contact answers messages within minutes. Every one of those things can be true of an agency that will ship you a broken product four months late, and some of them, like the instant quote and the lightning fast sales replies, are actually mild warning signs dressed up as service.
A meaningful share of the work that comes to us is not new builds. It is rescues: a site or product someone else built that the owner cannot update, cannot move, and sometimes does not even legally own. Almost every rescue traces back to a red flag that was visible before the contract was signed, which is what makes this list worth writing down. None of it requires technical knowledge to check. It requires knowing what to look at.
Before you sign
The red flags that predict a bad build
A price before a single question
A real estimate requires understanding your workflow, your users, and your constraints. An agency that quotes a firm number in the first call is either guessing, planning to make it back on change orders, or fitting you into a template regardless of what you actually need.
A portfolio you cannot click
Screenshots prove nothing. Ask for live URLs and check them yourself: do the sites load fast, work on a phone, and still exist at all. An agency whose past work has quietly gone offline is telling you what happens to its clients after launch.
Results described in adjectives, not numbers
Stunning, modern, and seamless are not outcomes. Faster load times, higher conversion, a ranking, a sales lift, those are outcomes. An agency that has genuinely delivered results can name at least a few, with the client attached.
You never meet the builders
If every conversation runs through a salesperson and the people writing your code are never in the room, the knowledge of what you actually need will not survive the handoff. The gap between what you said and what gets built lives exactly there.
Ownership stays vague on purpose
Who owns the code, the domain, the hosting account, and the content when the contract ends? If the answer is not clearly and contractually you, you are not buying a product. You are renting one, and the rent goes up the day you try to leave.
Everything you suggest is a great idea
A partner who never pushes back is not agreeing with you, they are avoiding the effort of thinking about your problem. The best predictor of a good build is an agency that argues with your scope in the first meeting, because it means they are already doing the work.
Translation table
What the pitch says, and what it often means
Sales language is not lying, exactly. It is compression. This is how to decompress the phrases that should trigger a follow up question.
| What they say | What it can mean | What to ask |
|---|---|---|
| We can start Monday | No discovery process exists, and your project drops into a queue with whoever is free. | What do you need to learn about my business before writing code, and how long does that take? |
| We use AI to deliver faster | Sometimes a real productivity gain. Sometimes unreviewed model output shipped straight into your product. | Who reviews the output, and what does your testing process look like before anything reaches production? |
| Unlimited revisions | The scope is undefined, so revisions are how the project will be steered, slowly, toward whatever is easiest to deliver. | Can we define what version one includes, in writing, before we start? |
| We handle hosting for you | Convenient, and sometimes fine. Also the classic setup for hostage hosting, where leaving the agency means losing the site. | If we part ways, what exactly do I walk away with, and what does the migration process look like? |
| Our proprietary platform | Your product will be built on something only this agency can maintain, which converts you from client into captive. | Could another developer take this over tomorrow using standard tools? If not, why not? |
None of these phrases is disqualifying on its own. The pattern to watch is what happens when you ask the follow up: good agencies answer specifically, bad ones change the subject.
The other side
Green flags, because they are rarer and worth naming
They narrow your scope
A partner who talks you out of features in the first meeting is protecting your budget and their ability to ship. The instinct to cut before building is close to the single strongest green flag there is.
They show you the boring parts
Staging environments, testing process, handover documentation, what happens when something breaks at 2 am. An agency that volunteers this unprompted has been through enough launches to respect them.
They put ownership in writing without being asked
Code, domain, hosting, and content ownership spelled out in the contract by default, because they have seen what happens to clients of agencies that do the opposite.
Their old clients still talk to them
Ask to speak to a client from two years ago, not last month. An agency confident in that conversation has nothing to manage. An agency that hesitates has told you everything.
The vetting process
A one week vetting routine that filters out most bad agencies
This takes a few hours spread over a week, which is nothing against the months and the budget a bad pick costs.
Click every portfolio link
Open each one on your phone. Run the ones that matter through a free page speed test. Dead links, slow loads, and sites that look nothing like the screenshots are each individually disqualifying.
Ask for two references, one old
A recent client tells you about the honeymoon. A client from two years back tells you what maintenance, support, and the relationship after the invoice actually look like.
Request a written scope before a price
Any agency worth hiring will insist on this order anyway. If the price arrives before the scope, the price is fiction and the scope will be whatever makes that fiction profitable.
Meet the actual team
Ask for fifteen minutes with the developer or designer who would own your project. How they talk about their current work tells you more than the entire sales deck.
Read the exit clause first
Before signing, read what happens when you leave, not what happens while you stay. Ownership, handover, and data export terms are where bad agencies hide the lock in, because nobody reads that section while excited about a kickoff.
Our answer to the same test
We expect to be vetted the same way
This list is not written from a safe distance. Every project on our work page has a live link, a named outcome, or both: a sports academy taken from an SEO score of 55 to 100 and the top spot on Google, a real estate developer whose existing site we modernized in place rather than pushing the rebuild that would have paid us more, a temple billing system a client fully owns, down to the database. When Avittam Homes came to us, the platform underneath their site was sound, so the honest recommendation was the smaller project. That is the scope narrowing habit described above, applied to our own revenue.
The point is not that we pass every test on this page, though we work at it. The point is that a good agency should welcome the tests, because vetting filters out exactly the competitors that make clients distrust this industry in the first place. If an agency reacts to these questions with impatience, that reaction is itself the answer.
The cheapest moment to fire a bad agency is before you hire them. Every red flag on this page is visible from the outside, before a contract, before a deposit, before a single line of code. The clients who get burned are almost never the ones who lacked the information. They are the ones who saw the flag and signed anyway because the quote was attractive.
One last honest note
Price the project with more than one kind of firm
None of the red flags above correlate with price. Expensive agencies fly them, cheap ones sometimes do not, and smaller studios frequently pass every test on this page while quoting far below the firms that fail them. The only way to know what your project costs from a trustworthy builder is to describe it to a few and watch how they respond to the questions in this post.
We are happy to be one of the firms you test. Bring us the project, ask us everything on this page, and get a quote that itemizes scope before price. If we are not the best value on your shortlist after that, you will have lost nothing but an hour.
0→1 Product Studio
This is exactly what we build.
See how AiVirex approaches 0→1 product studio, and what it looks like to work with us.
FAQ
Questions, answered
What is the single biggest red flag when hiring a development agency?
Unclear ownership. If the contract does not clearly state that you own your code, domain, hosting, and content when the relationship ends, everything else about the agency is secondary, because you are building your business on something you can lose in a dispute.
Is a cheap quote from an agency always a red flag?
Not by itself. Rates genuinely vary by region and overhead. It becomes a red flag when the low price arrives instantly, before any scoping conversation, because a number produced without understanding the work is either a guess or the opening move of a change order strategy.
How do I check an agency's portfolio properly?
Open every live link on your phone, check that the sites load fast and work well, and run one or two through a free page speed tool. Then ask for a client reference from at least two years ago. Screenshots and recent testimonials are the easiest things in the industry to manufacture.
What should happen if I want to leave my current agency?
You should be able to walk away with your complete codebase, your domain, admin access to your hosting, and your content, in a form another developer can take over using standard tools. If any of those is missing or resisted, that is the hostage pattern, and it is worth getting help untangling it sooner rather than later.
Sources
The research behind this post
Want help with this?
Tell us where you're stuck and we'll tell you what's actually possible, then scope it and give you a clear, tailored quote.