We get a lot of inbound from businesses that have just been burned. The pattern is consistent enough that we can usually predict the story before they tell it: a previous vendor took a deposit, delivered something that mostly worked, went quiet on support, and now the client is paying someone else to unwind the mess.
Choosing wrong costs 6–12 months. Choosing right compounds for years. Here are the warning signs we wish more clients caught on the way in, and the questions that surface them.
Warning sign 1: They can't answer "which CMS, and why"
If the proposal says "we use WordPress for everything" or "we use Webflow for everything," that's not expertise — that's the only hammer they own.
A capable partner can tell you why your project is WordPress, Drupal, Laravel, Next.js, a headless CMS, or something else entirely. They'll describe your content model, your editorial workflow, and your performance requirements, then pick the platform that fits. If the answer is "because that's what we build," you're buying the agency's constraints, not solving your problem.
Ask this: "Walk me through the last three projects you did on three different platforms and what drove each choice."
Warning sign 2: No multi-year clients
Web development is easy to start and hard to finish. A three-month brochure site is not a reliable signal of quality. What's reliable is a client relationship that's still live five years later — because by then every mistake has been discovered, every platform upgrade has been navigated, and the agency is still the one the client trusts.
If every case study is a one-off launch with no "we still manage this" attached, you're looking at an agency that's good at the honeymoon and unknown at the marriage.
Ask this: "Who's your longest-running client, and what's the story?" If they can't name a client they've worked with for five years, look elsewhere.
Warning sign 3: The portfolio is all the same
Twenty real estate sites. Twenty restaurant sites. Twenty law firm sites. All using the same theme with different logos.
This isn't inherently bad — vertical specialization can be valuable. But if you're asking for something outside their template library, you're asking them to do work they've never done. The portfolio tells you what's cheap and fast for them, not what's possible.
Ask this: "Show me a project that required custom development beyond your normal work. What did you build and why?"
Warning sign 4: Hosting is an afterthought
"We'll put it on whatever you already have" or "we can use our shared server" are both red flags.
Hosting is half the performance conversation. Shared hosting kills PageSpeed. Managed WordPress hosts have specific constraints that change how you build. Vercel and Cloudflare have deployment workflows that require knowledge to set up correctly. A good partner has opinions about hosting that match your traffic, budget, and team.
If they shrug at this question, they're optimizing for their margins, not your outcomes.
Ask this: "What hosting would you recommend for a site like this, and why? What would you avoid?"
Warning sign 5: No explicit accessibility or performance standards
"We follow best practices" is not a standard. A real standard looks like:
- "We target WCAG 2.2 AA on every build and run automated axe audits plus manual keyboard testing before launch"
- "We target a 90+ mobile Lighthouse score and we'll show you the PageSpeed Insights report on the day we ship"
If the answer to "what accessibility standard do you hit" is vague, assume they don't hit any.
Ask this: "What's your accessibility checklist, and how do you verify it before launch? Can I see the audit report from your last project?"
Warning sign 6: Fixed-price everything, no discovery
A fixed price on a complex build means one of two things. Either the agency has padded the price enough to absorb unknowns (you're overpaying), or they've underpriced and will cut scope aggressively when reality hits (you're underserved). Neither is good for you.
The right shape for a real project: a short paid discovery that produces a written scope, followed by a fixed-price implementation against that scope. Anyone selling you fixed-price work on a project they haven't scoped is either optimistic or sloppy.
Ask this: "How do you handle unknowns that surface mid-build? What triggers a change order?"
Warning sign 7: You can't tell who's doing the work
Agencies that pitch with a senior team and deliver with junior staff are more common than they should be. You meet the principals, sign the contract, and never hear from them again. The work lands with whoever has capacity, and it shows.
This isn't necessarily a dealbreaker — juniors need to work, and supervised junior work can be excellent. But you should know who's typing the code, who's reviewing it, and who owns the outcome.
Ask this: "Who specifically will be working on my project? Who reviews their code? When do you bring in a senior?"
Green flags
The inverse is a short list:
- Concrete references. Clients you can call, not logos on a page.
- Opinions backed by experience. "We'd use Drupal because your editorial workflow has three approval layers" is a better answer than "we use whatever you want."
- Post-launch plan. A real retainer offering with real response times, not just "call us when something breaks."
- Transparent pricing logic. Not necessarily cheap, but comprehensible. You should know what you're buying.
- Portfolio breadth. Multiple stacks, multiple verticals, multiple scales.
If you're evaluating partners and want a second opinion on proposals you've received, get in touch — we'll give you an honest read.