The decision that costs more to get wrong than to get right
A bad agency engagement does not just waste the money you spent. It wastes the time you lost, the internal momentum that died, and the months of catching up you have to do afterward. The average mid-size business website project runs somewhere between $8,000 and $60,000 depending on scope. Getting it wrong can mean doing it twice. So the vetting process is worth doing seriously.
Start with your own clarity, not their portfolio
Before you contact a single agency, you need to know what success actually looks like for your project. Not in vague terms — in specific ones. Are you trying to generate more inbound leads? Sell direct to consumer? Reduce support requests by making self-service easier? Migrate off a platform that is costing too much to maintain? The clearer you are about the outcome, the better you can evaluate whether an agency actually understands how to get you there.
Agencies are good at showing you what they have already built. They are not always good at asking what you actually need. If you walk into a conversation without defined goals, you will walk out with a proposal that sounds impressive and may not move the needle on anything that matters to your business.
What their portfolio is actually telling you
A portfolio shows you taste and capability, but it does not tell you how the project actually went. The real questions behind any portfolio piece are: did the client get what they asked for, did they get it on time and on budget, and is the relationship still intact? Those answers are not in the case study.
What you should look for in a portfolio is evidence that the agency has worked on projects similar to yours in scope and industry. Not identical — similar. An agency that has only built brochure sites for restaurants is not necessarily the right fit for a custom web app with complex user roles and API integrations. The technical challenge gap matters.
Pay attention to how they talk about their work. Agencies that can articulate the business problem behind each project — not just the visual choices — are agencies that understand that design and development exist to solve something, not just to look good.
The questions that actually separate good agencies from the rest
Skip the questions you think you are supposed to ask. Instead, try these in any discovery or pitch conversation:
Who will actually build my project? Many agencies pitch senior talent, then hand work off to junior developers or overseas contractors. This is not always bad, but you deserve to know the real team. Ask by name. Ask about their experience. Ask how communication with that team will work.
What does your QA process look like? Agencies that have a real answer here — specific testing steps, browser coverage, device coverage, accessibility checks — are agencies that care about shipping something that works. Agencies that stammer or pivot to talking about their design process are probably not thinking much about what happens after code is written.
What happens when something breaks after launch? This question reveals the warranty and support posture. Some agencies disappear after handoff. Others have structured maintenance retainers. Neither is wrong by default, but you need to know which you are getting and whether it matches your needs. Understanding what maintenance actually costs before you sign helps you evaluate whether their post-launch model is realistic.
Can I see a recent project that went sideways and how you handled it? This question makes most agencies uncomfortable. That discomfort is useful data. Every agency has had a project hit turbulence. The ones worth working with have learned from it and can talk about it honestly.
Red flags that should end the conversation early
Some patterns in the agency pitch process are genuinely worth walking away from, regardless of how good the portfolio looks or how competitive the price seems.
An agency that cannot give you a clear timeline or a timeline that keeps shifting during the pitch phase is telling you something important about how they operate under pressure. Timelines are hard to nail down perfectly, but a professional agency should be able to give you a realistic range and explain what would cause it to move.
Proposals that skip the discovery phase entirely and jump straight to a fixed price for a project they barely understand are a red flag. Good agencies know that requirements need to be defined before scope can be accurately estimated. A proposal that arrives in 24 hours for a complex project is either too high or based on assumptions that will bite you later. Understanding how long websites actually take to build helps you recognize when a timeline is unrealistically compressed.
Watch out for agencies that lead entirely on aesthetics and never ask about your users, your conversion goals, or how the site will be maintained after launch. A beautiful site that does not convert is an expensive decoration. The agency you hire should have an opinion about what makes a website work for your business, not just what makes it look impressive in their portfolio.
Pricing transparency and what it signals
Agencies that hide their pricing or refuse to give ballpark ranges before a lengthy sales process are usually doing one of two things: protecting the ability to anchor high, or genuinely unaware of where their work falls in the market. Neither is a great start.
You do not need a fixed price upfront. But you should be able to get a range based on scope. If an agency cannot tell you whether your project is a $5,000 engagement or a $50,000 one after an initial conversation, something is off in how they assess work.
Also pay attention to how they structure payment. Milestone-based payments aligned to deliverables protect both sides. Large upfront payments with vague milestone definitions tend to protect one side more than the other.
The contract conversation nobody wants to have but should
Before you sign anything, make sure you understand who owns the code when the project is done. This sounds obvious but many agencies retain licensing rights to code, themes, or plugins that mean you cannot move your site to another developer without paying again. Ask directly: after final payment, do I own all the assets and code built for this project? The answer should be yes without caveats.
Get clarity on scope change pricing before you need it. Change orders are a normal part of development projects. The question is what process and rate applies when scope shifts. Agencies with clear, pre-agreed change order rates are easier to work with than agencies that handle it case by case, which often means slower responses and awkward negotiations mid-project.
The right agency fit matters more than the right agency brand
Some of the most expensive web development agencies in the country produce mediocre results for clients who were not the right fit for them. Some of the best builds come from smaller shops that were deeply aligned with what the client actually needed. Agency size, awards, and client logos do not predict whether your specific project will go well.
What predicts it is: shared understanding of what success looks like, honest communication before a contract is signed, a process that fits how your team works, and a post-launch plan that does not leave you stranded. Find the agency where those things are true, and you will get more value out of the relationship than any portfolio could have told you.
Ready to talk to an agency that is straight with you?
Tell us what you are building. We will tell you what it actually takes.
No runaround. No proposal for a project we have not understood. Just an honest conversation about what your website or app needs to do and whether we are the right fit to build it.