Most bad agency experiences were predictable. The red flags were there before the contract was signed — founders just didn’t know what they were looking for. After seeing hundreds of projects and rescuing dozens from failed agency engagements, these are the warning signs that reliably predict a bad outcome.
Red Flag 1: They Won’t Commit to a Fixed Scope or Price
Agencies that refuse to provide a fixed-price quote aren’t being transparent — they’re protecting themselves from accountability. “Time and materials” billing transfers all the risk to you and incentivizes slow work.
What good looks like: A detailed scope of work (SOW) with specific deliverables, milestones, and a fixed price (or a guaranteed maximum for T&M). Change orders for scope changes, issued before additional work begins.
Red Flag 2: The Contract Has No IP Ownership Clause
If the contract doesn’t explicitly state that all code, designs, and deliverables belong to you upon completion, you may have no legal right to the work product after the project ends.
Some agencies write clauses giving themselves a perpetual license to reuse components they built for you. Others withhold code until full payment — which is different from ownership but is still a leverage problem.
What good looks like: “All intellectual property created under this agreement is owned exclusively by the client upon completion of payment.” Simple, unambiguous.
Red Flag 3: No Post-Launch Support Offering
The first 30–60 days after launch are always the most bug-dense. Users find edge cases your team didn’t test. The agency who built it is the only one who understands the codebase well enough to fix issues quickly.
An agency that has no post-launch support structure — no warranty period, no retainer offering, no maintenance SLA — is optimised to move on, not to ensure your launch succeeds.
What good looks like: A 30–90 day warranty period for bugs (at no extra charge), plus an optional ongoing maintenance retainer.
Red Flag 4: They Can’t Tell You Exactly Who Will Work on Your Project
“Our team of experienced developers” is a red flag. Who specifically? What’s their experience level? Have they done this before?
Many agencies win work with senior developers in the sales process, then hand it off to junior contractors once the project starts. You pay senior rates and get junior output.
What good looks like: Named developers, their GitHub profiles or portfolios, their role on your specific project, and ideally a 30-minute call with the developer before the contract is signed.
Red Flag 5: They Have No Opinions on Your Tech Stack
An agency that says “we can work with anything” is a generalist-for-hire, not a specialist. Specialists have strong opinions about what tools work well for specific use cases — because they’ve learned from experience.
If an agency is equally enthusiastic about building your SaaS in WordPress, Ruby on Rails, and no-code tools, they haven’t built enough products to have developed expertise.
What good looks like: “For your use case, we’d recommend Next.js + Supabase because [specific reasons]. We’ve built 30 products on this stack and know the tradeoffs.” Opinionated is good.
Red Flag 6: They Don’t Ask About Your Business Model
An agency focused only on technical requirements — without asking how you make money, who your users are, and what success looks like in 6 months — will optimize for shipping code, not for your business outcome.
The best agencies push back on scope that won’t serve your users, suggest features you hadn’t considered, and design the architecture for the business you’re trying to build, not just the features you requested.
What good looks like: Questions about your target users, your revenue model, your competitive landscape, and what you’ll measure to know the product succeeded.
Red Flag 7: References Are Unavailable or Only Positive
Every agency has had a difficult project. Every good agency has learned from it. An agency that can only produce glowing testimonials from cherry-picked clients is hiding something.
Ask for three references from projects similar to yours. Ask the references specifically: “What went wrong, and how did the agency handle it?” If the reference can’t think of anything that went wrong, the project either wasn’t complex enough to be relevant to yours, or the reference was too carefully selected.
What good looks like: References who give honest, nuanced feedback — including things that were hard — and describe how the agency resolved issues. Imperfect but accountable is exactly what you want.
Frequently Asked Questions
What’s the biggest mistake founders make when hiring an agency? Choosing on price. A $5K cheaper agency that delivers 3 months late costs far more than $5K in lost revenue, lost time, and rework.
Should I get a lawyer to review the agency contract? For anything above $20K, yes. A 1-hour legal review ($200–400) is cheap insurance against ambiguous IP clauses or payment terms that put you at risk.
Is a cheaper agency always a worse agency? No. Eastern European agencies, for example, can deliver very high quality at lower rates due to lower operating costs. Evaluate by references and portfolio, not by hourly rate.
What if I’m already in a bad agency relationship? Get the code in escrow (if not already), document all communications, and review your contract for exit clauses. Consult a lawyer if the relationship has broken down completely.
How do I evaluate technical quality before hiring? Ask to see a code review of a past project. Look at their GitHub (if public). Ask about their testing practices, CI/CD setup, and deployment process. Quality developers talk about quality processes.
None of these red flags apply to how we work. At Whipp Studio, every project has a named team, fixed scope, explicit IP ownership, post-launch support, and client references available on request. Book a free strategy call →