How to Choose a Web Design Agency: 7 Questions to Ask Before You Hire.

Every web design agency's portfolio looks polished by the time a prospective client sees it, that's the whole point of a portfolio. It tells you almost nothing about how the agency will actually treat your project: who's assigned to it, what happens when a deadline slips, or whether you own the site you're paying for. The seven questions below are the ones that actually separate a good agency from a bad one, and each comes with what a good answer, and a red-flag answer, actually sounds like.

Why the portfolio isn't the differentiator you think it is

A portfolio shows you the best few projects out of however many the agency has shipped, often built by a senior designer who's no longer there, for a client with an unusually generous budget and timeline. It's a reasonable filter for baseline design taste, but it tells you nothing about process, communication, or what happens when your project is the average one instead of the showcase one. Use it to get past a first screen, then move to questions that actually predict your experience.

Question 1: Who exactly will be working on my project?

Agencies range from a single freelancer operating under a company name to a large studio that assigns junior staff to smaller accounts while senior talent works the portfolio pieces. Neither is automatically wrong, but you should know which one you're hiring. Ask for the specific name and role of who will design, build, and manage your project, not just "our team." A good answer names a person. A vague answer, "you'll be assigned a dedicated specialist," is worth pushing on.

Question 2: What does your process look like, week by week?

• ▸Good sign: a specific sequence with named deliverables, e.g. "week 1 is a strategy call and sitemap, week 2 is a homepage design for your approval, weeks 3-4 are build and revisions"
• ▸Red flag: a vague answer like "we'll get started and keep you updated," with no defined checkpoints or approval stages
• ▸Good sign: a stated number of revision rounds included in the price, so you know where the line is before you're billed extra
• ▸Red flag: unlimited revisions promised with no scope boundary, which usually means the timeline is unlimited too

Question 3: Will I actually own the website when it's done?

This question catches more businesses off guard than any other on this list. Some agencies build on a proprietary or locked-down platform, so "finishing" the project doesn't mean you can take the files and leave, it means you're now dependent on that agency for every future change. Ask directly: if we part ways in a year, do I keep the code, the domain, the hosting account, and the CMS access? A legitimate agency answers yes without hesitation. One that hedges, or that builds exclusively on a platform only they can edit, is selling you a rental, not an asset.

Question 4: Is SEO actually included, or is it an upsell after the fact?

"SEO-friendly" on a proposal can mean anything from full technical SEO and schema markup built in from day one, to literally nothing beyond the site technically being crawlable. Ask what specific SEO work is included at the price quoted: meta tags, structured data, sitemap submission, Core Web Vitals targets, and whether ongoing optimization is a separate retainer, worth pricing out honestly rather than guessing. A precise answer with named deliverables is a good sign. "We build everything with SEO best practices in mind," with no specifics, usually means none of it was actually budgeted.

Question 5: What happens the day after launch?

Launch day is often treated as the finish line by both sides, which is exactly backwards, a site is a piece of software that needs ongoing maintenance to stay secure and fast. Ask what support is included after launch and for how long, whether there's a maintenance plan, and what a bug reported in month two actually costs to fix. An agency with a clear, priced answer has thought about this. One that seems surprised by the question probably treats every project as a one-and-done transaction.

Question 6: Can I talk to a current client, not just read a testimonial?

A written testimonial is curated and, occasionally, entirely fabricated. A 15-minute call with a real, current client tells you things a quote never will: did the project finish on time, did communication stay good after the deposit cleared, would they hire the agency again. Most legitimate agencies can arrange this for at least one reference. Reluctance to connect you with any actual client, ever, is worth taking seriously.

Question 7: What's actually included at the price you quoted?

The number on a proposal means little without knowing its scope. Get a detailed budget breakdown before you sign anything: page count, revision rounds, stock vs. custom photography, copywriting, and whether SEO and post-launch support are bundled or billed separately. Two agencies quoting "$1,500 for a website" can be describing completely different scopes of work, and the cheaper number often has more left out of it, not less work involved.

Red flags that should end the conversation

• ▸Pressure to sign or pay a deposit before you've seen a proposal in writing
• ▸No clear answer on who owns the code, domain, or CMS after the project ends
• ▸A price dramatically below every other quote you've gotten for the same scope, with no explanation for the gap
• ▸Reluctance to name a specific person who'll be working on your project
• ▸No mention of what happens after launch, as if the relationship ends the moment the site goes live

Choosing an agency is less about finding the most impressive portfolio and more about finding one you can trust to answer these seven questions honestly, including the parts of the answer that aren't flattering. If you want to see how we answer all seven, get a free quote and ask us directly, we'd rather you compare us against a real standard than take a polished pitch at face value.