I've sat on both sides of this table — as the agency pitching a client, and as the consultant brought in to clean up after a different agency's failed project. The patterns are remarkably consistent. The clients who get burned almost always missed the same handful of warning signs at the proposal stage. And the agencies that burn clients almost always sell on the same handful of techniques.
This post is the evaluation framework I'd give a friend who was about to spend $20k – $100k on a website build. It assumes you've already narrowed your choices to two or three agencies. The goal is to figure out which (if any) is the right call — before you sign.
Why this matters more than people realize
A failed web project costs you in three ways, and most clients only count the first one:
- The money you paid. Usually $10,000 – $50,000.
- The time you lost. 3 – 9 months while the wrong partner thrashed.
- The opportunity cost. Every month your site doesn't ship is a month you don't acquire customers through it. For a business doing real lead generation, this is often the biggest number.
If you pick the wrong agency, the total bill is roughly double what the right agency would have cost. I've seen this play out enough times to be certain about the pattern.
The five hard red flags
If you see any of these, do not sign. The rest of the agency's pitch doesn't matter:
1. They quote you before doing real discovery
A real proposal requires understanding your business, your audience, your goals, and the project scope. If an agency drops a number after a 30-minute intro call, they're either guessing or pattern-matching to a template. Either way, the number will be wrong — and they'll either lose money (and cut corners to compensate) or charge you "scope changes" later.
2. Their portfolio sites are slow, broken, or outdated on mobile
This is the most underused signal. Pull up three of their recent client sites on your phone right now. Run them through PageSpeed Insights. If the people building websites can't ship a fast, working website for their own clients, they will not ship one for you.
3. They won't tell you who'll do the work
Many agencies have a "senior consultant" pitch the project and a "junior developer" execute it. Insist on knowing exactly who is on your team. If the principal who's pitching you is not the principal who will run your project, you're buying a different product than you think.
4. The contract doesn't transfer IP on final payment
You should own the code, the design files, the hosting accounts, the domain, the analytics property, and the source repository. If any of those stays with the agency, you're renting instead of buying. Walk away.
5. They badmouth the previous developer without seeing the codebase
If they trash your existing site in the first meeting, they're trying to anchor you toward "everything needs to be rebuilt." Sometimes that's true. Often it isn't. The agencies that lead with honest assessment ("we'd need to audit before making that call") are the ones worth working with.
The green flags worth weighting heavily
- A clear, written process. Discovery → design → build → QA → launch → post-launch. Each phase should have deliverables and acceptance criteria.
- They've turned down work before. A good agency will tell you when you're not a fit for them. The agencies that take every project are the ones that fail most often.
- They explain why they recommend their tech stack. "We use Next.js because [specific technical reasons related to your situation]" beats "we use Next.js because it's modern."
- They have a real care plan for after launch. Most site failures happen in months 2 – 12, not on launch day.
- The senior people are in the room. Discovery and design should involve the principals, not just account managers.
- They give you references you can actually call. Not testimonials on the site — phone numbers of past clients.
The 12 questions to ask in your first real meeting
- Can you walk me through your most recent client project — discovery to launch — with specific dates and people?
- Who specifically will be on my project, and what is each person's role?
- What does your typical timeline look like for a project of this size, and what causes timelines to slip?
- How do you handle scope changes mid-project? Show me the change-order process.
- What's your payment milestone structure? What deliverables trigger each payment?
- What happens if I'm not happy with the first round of design?
- How do you handle SEO, structured data, and performance during the build?
- What's your accessibility standard, and how do you verify it?
- What does post-launch support look like — for how long, and at what cost?
- Who owns the source code, the design files, the domain, and the hosting accounts at the end?
- What's your communication cadence — and what's your response-time commitment?
- Can I speak with two clients you've worked with in the last 12 months?
You don't need to ask all twelve in one meeting. But you should leave with answers to all of them before you sign.
The contract clauses people forget
Most clients sign whatever standard agreement the agency hands over. That's a mistake. Insist on these clauses:
- IP transfer on final payment. All source code, design files, content, and account credentials transfer to you when the final invoice is paid.
- Written scope and acceptance criteria. The contract should define what "done" means for each deliverable.
- Change-order process. A clear path for handling scope changes, with cost estimates approved in writing.
- A defined warranty period. 30 – 90 days of bug fixes included at no additional cost after launch.
- Source code delivery, not just a hosted product. You should have the full repo, not just access to a hosted site.
- Account ownership. Your name on the hosting account, your name on the domain, your access to the analytics. Not theirs.
- A termination clause that protects you. If the project goes sideways, what's the exit? Refund? Partial deliverables? Define it before you sign.
- Confidentiality and data-handling terms. Especially important if you're in a regulated industry.
How to read between the lines of a proposal
A proposal tells you almost everything you need to know if you read it carefully. Things I look for:
- Line-item pricing vs lump sum. Line-item is honest. Lump sum is sometimes fine for fixed-scope projects, but you should be able to ask "what does X cost separately?"
- Specific deliverables vs marketing language. "We will deliver: homepage design (3 revisions), product page template (2 revisions)..." is real. "We will craft a stunning visual experience" is not.
- Timeline tied to your inputs. A real timeline names when you need to deliver content, approve designs, and so on. "8 weeks" without input dependencies is fantasy.
- Assumptions section. Good proposals list assumptions clearly. "We assume X provides content by Y date" protects everyone.
- Out-of-scope section. What's explicitly NOT included. Anyone who hasn't written this section will charge you for it later.
The cost of getting it wrong (with real numbers)
The clients I've onboarded after a failed first attempt typically went through:
- Initial cheap quote: $4,000 – $12,000.
- Months of delay: 3 – 9.
- Final state: site that's slow, buggy, doesn't match the brand, or doesn't function.
- Cost to remediate (or start over): $15,000 – $40,000.
- Total: $19,000 – $52,000 for a site that should have cost $15k – $30k done right the first time.
The lesson isn't "always go expensive." The lesson is: if a quote is dramatically lower than the others, understand specifically why before assuming you're getting a deal.
The freelancer vs studio vs agency decision
I wrote a separate post on this for the South Florida market specifically, but the short version applies anywhere:
- Freelancer ($2k – $20k): Right for small, well-scoped projects. Risk: single point of failure, no bench depth.
- Boutique studio ($10k – $60k): The sweet spot for most growing businesses. Senior execution, transparent process, manageable cost.
- Full agency ($50k – $250k+): Right for large, complex, or multi-channel projects. You pay for capacity and process layering.
Frequently asked questions
What's the biggest mistake clients make when choosing an agency?
Going with the cheapest quote without understanding why it's cheaper. The price difference usually reflects who's doing the work, what's actually included, and what corners get cut.
Should I work with a local agency or remote?
Local matters more for relationship-driven industries (law, real estate, healthcare) and for projects involving photography or on-site discovery. For pure execution, remote can work fine — but time-zone matters during launch and incident response.
How do I verify an agency's portfolio is really theirs?
Look up the case-study sites on the Wayback Machine to check launch dates. Search the team's individual portfolios on LinkedIn or personal sites. Call one of the listed clients and ask. Real portfolios survive scrutiny; padded portfolios don't.
What if the agency wants me to sign an NDA before they'll quote?
Unusual but not always a red flag. Ask what they're protecting. If it's their pricing structure, that's a yellow flag. If it's a sample of their work, fine.
How long should the evaluation process take?
2 – 4 weeks is typical. One intro call, one detailed discovery meeting, one proposal review, one negotiation pass. If you're being rushed to sign in 48 hours, that's a tell.
Can I get a refund if the project goes badly?
Only if the contract says so. Most agency contracts don't include refund clauses. Best practice: insist on milestone-based payments tied to deliverables, so a stalled project doesn't keep getting invoiced.
The bottom line
Picking a web development agency is fundamentally a trust decision wrapped in a procurement process. The framework above turns it into a structured evaluation, but the underlying question is the same: do I trust these people to do what they're saying, and to be honest with me when something goes wrong?
If you'd like an honest read on whether we're the right fit for your project — and we'll tell you if we're not — book a free 30-minute call. You can also see how we approach custom web development and what our pricing structure actually looks like.
