How to choose a web design agency: red flags

Five proposals sit in your inbox, all promising a beautiful, effective website, all quoting different numbers, all showing similar-looking portfolios. Choosing among them by gut feeling is how founders end up with a provider who disappears mid-project, delivers something generic, or leaves them technically dependent for years.

Learning how to choose a web design agency or freelancer is really about learning what questions separate a real process from a confident sales pitch. This guide gives you the specific questions to ask, the red flags that should end a conversation, what belongs in a proper contract, and how to actually evaluate a portfolio instead of just admiring it.

What questions should I ask a web designer before hiring?

Six questions, in order, each revealing something a polished pitch deck will not.

1. Walk me through your process, phase by phase. Listen for a defined sequence: strategy, content, design, development, testing, roughly matching the stages in how long a website takes to build. A vague answer, "we just get started and figure it out," predicts a vague project.

2. What do you need from me before you can quote accurately? A real answer includes questions about your goals, audience, competitors, and content readiness. An instant, unconditional quote means the price was set before your specific situation was understood.

3. Who exactly will work on my project? For agencies especially, confirm the people in the sales call are the people doing the work, not a senior team pitching followed by a junior team executing without oversight.

4. What happens if I want to change providers later? Ask directly whether you will own the domain, receive full source files, and retain admin access. The answer to this single question predicts how the entire relationship will feel, a concern covered fully in website maintenance.

5. How do you handle scope changes and revision rounds? A clear answer names specific numbers: 2 to 3 defined revision rounds, and a process for handling requests beyond scope. Unlimited revisions sounds generous and often signals the absence of a real process, a pattern we explore for logo pricing in how much a logo costs that applies equally here.

6. Can you show me a project similar to mine, and can I speak to that client? A confident provider offers this without hesitation. Reluctance, or portfolio pieces that all look suspiciously alike regardless of the client's actual industry, both deserve follow-up questions.

What are red flags when hiring a web design agency?

Watch for these 6 patterns, each observed repeatedly across disappointing projects.

An instant quote with no discovery questions. As above: pricing without understanding your specific situation is pricing a guess.

Portfolio sameness across unrelated industries. If a law firm, a bakery, and a tech startup all received visually identical sites from the same provider, the process is templated regardless of what the pitch claims, undermining the differentiation a real identity should provide, the exact concern raised in what makes a good website.

No written contract, or one covering only price and timeline. Scope, ownership, revision limits, and what happens if either party wants to exit should all be explicit in writing before any work begins.

Pressure to decide immediately. Legitimate providers welcome you comparing options and taking time to decide. Urgency tactics on a project this consequential are a warning sign, not a sales technique to respect.

Payment structures that front-load risk onto you. 100 percent payment upfront, with no milestones tied to actual delivered work, removes your leverage entirely if the project stalls or disappoints.

Vagueness about who owns what after payment. If direct questions about domain ownership, file access, or platform control receive evasive answers, assume the arrangement is designed to create dependency, not partnership.

The best proposal is the one that survives your hardest questions.

What should be included in a web design contract?

A proper contract protects both parties and should explicitly cover 6 areas.

Scope of work, itemized: exact number of pages, specific functionality, what is included and what would constitute an additional charge. Vague scope is the single most common source of project disputes.

Timeline with named milestones, not just a final delivery date. Dates for strategy approval, design approval, and development completion give both sides accountability throughout, not just at the finish line.

Payment schedule tied to milestones, typically a deposit, a milestone payment at design approval, and a final payment at launch. This structure protects your leverage if the relationship needs to end early.

Ownership and IP transfer, stating explicitly that you own the final design, code, and content upon final payment, and that you will receive complete files and access credentials, not just a live site you cannot independently modify.

Revision terms, specifying the number of included revision rounds per phase and the rate for work beyond that scope.

A clear exit clause, describing what happens if either party wants to end the engagement early: what you receive, at what stage, and at what cost.

If a provider resists putting any of these 6 items in writing, treat the resistance itself as the answer to whether you should proceed.

How do I evaluate a designer's portfolio?

Portfolios impress visually by design, which is exactly why evaluating them requires looking past the visuals to 3 specific questions.

Does the work vary appropriately by client? A portfolio where every project shares the same layout patterns, color approach, and structure regardless of the client's actual business signals a template being reskinned, not a strategic process being applied fresh each time.

Can they explain the reasoning behind specific decisions? Ask about one project directly: why this structure, why this color, what was the client trying to achieve. Strong answers reference the client's actual goals and audience. Weak answers describe only aesthetic preferences.

Do the sites actually perform well, not just look good in a screenshot? Visit 2 or 3 live examples from the portfolio yourself. Check load speed with PageSpeed Insights, test the mobile experience, and try the contact form. A portfolio full of beautiful screenshots of slow, broken live sites tells you everything a screenshot alone cannot.

Weight process evidence, discovery questions, explained reasoning, defined phases, at least as heavily as visual polish. The visual quality predicts what the site will look like. The process evidence predicts whether it will actually work for your specific business.

A side-by-side scoring method for comparing multiple proposals

When 3 or more proposals are on the table, comparing them by memory or general impression favors whichever one made the most confident presentation, not necessarily whichever one would actually deliver the best result. A simple scoring method removes that bias.

Create a table with one row per proposal and columns for each of the 6 questions covered above. For each provider, score their answer from 0 to 2: 0 for no real answer or evasion, 1 for a partial or generic answer, 2 for a specific, confident answer backed by a clear reason. Total the scores.

This exercise reliably surfaces something a gut-feeling comparison misses: the proposal with the most polished visual presentation and the proposal with the highest process score are frequently not the same one. A provider who scores well on process questions but presented a less flashy portfolio is often the safer, more accountable choice, since polish in a sales pitch and rigor in actual delivery are only loosely correlated.

Add 2 more practical checks alongside the scoring. First, compare response time and clarity across your email exchanges with each provider so far: how they communicate during the sales process typically previews how they will communicate during the actual project, when clear timely updates matter considerably more. Second, ask every provider for one reference client specifically similar to your business in size or industry, then actually make that call rather than treating the offer to provide one as sufficient reassurance on its own.

This structured comparison takes perhaps 2 extra hours across a decision that will govern weeks of work and thousands of euros. Treat it as due diligence proportional to the stakes, not an unnecessary formality.

How DIREVO answers these questions

We expect exactly the scrutiny this article recommends, and we structure our proposals so every one of the 6 contract areas above is explicit before any work begins: defined scope, milestone timeline, milestone-based payment, full ownership transfer at completion, clear revision terms, and a transparent exit path if circumstances change.

Our discovery process asks about your business before we quote anything, following the same structured sequence described in how long a website takes to build, and we are glad to connect prospective clients with past ones, because projects like Rewat and Descryptor speak for themselves when the client behind them is asked directly. Full details of our process are on our services page.

Frequently asked questions

What questions should I ask a web designer before hiring?

Ask about their process phase by phase, what information they need before quoting, who specifically will work on your project, what happens to ownership if you switch providers later, how revisions and scope changes are handled, and whether you can speak with a past client from a similar project.

What are red flags when hiring a web design agency?

Instant quotes with no discovery questions, portfolio sameness across unrelated industries, no written contract covering scope and ownership, pressure to decide immediately, payment structures requiring full amount upfront, and evasiveness about who owns files and access after payment.

What should be included in a web design contract?

Itemized scope of work, a timeline with named milestones, a payment schedule tied to those milestones, explicit ownership and IP transfer terms, defined revision limits, and a clear exit clause describing what happens if the engagement ends early.

How do I evaluate a designer's portfolio?

Look past the visuals: check whether the work genuinely varies by client rather than reskinning one template, ask the designer to explain the reasoning behind specific decisions, and visit live examples yourself to test real speed and mobile performance, not just screenshots.

What is a reasonable deposit percentage to expect?

30 to 50 percent upfront is typical for small business projects, with the remainder split across milestone payments described above. A deposit above 50 percent shifts unusual risk onto you before any real work is visible, while requesting none at all is uncommon for legitimate providers, since it removes any commitment signal from the client side.

Should I get everything in the contract even if I trust the provider personally?

Yes, without exception. Trust and good documentation are not competing choices, and even the most reliable relationships benefit from clarity that prevents misunderstanding later. Personal trust protects the relationship day to day; the contract protects both parties if circumstances change, someone forgets a verbal agreement, or the working relationship eventually ends.

What if I have a very tight budget, does all of this still apply?

Yes, arguably more so. Tighter budgets mean less room to absorb a mismatched hire's cost or a stalled project. Even a modest freelancer engagement deserves the same discovery questions, written scope, and ownership clarity covered above, scaled to the project's size rather than skipped because the stakes feel smaller.

Should I choose a local provider or is remote fine?

Remote works well for most website and branding projects in 2026, given how thoroughly video calls and shared documents can replace in-person meetings. Local providers offer easier informal check-ins and occasionally understand regional market nuances better. Neither factor should outweigh the process quality and portfolio evidence covered throughout this guide, since a strong remote partner with rigorous process beats a convenient local one without it.

How many proposals should I actually request?

3 to 4 is usually enough to see genuine variation in process, price, and approach without creating decision paralysis from comparing too many similar options. Requesting more than 5 rarely surfaces meaningfully new information and mainly consumes your own time evaluating increasingly marginal differences.

Is the cheapest proposal ever the right choice?

Occasionally, if your project genuinely needs only simple, template-based execution and the cheaper provider still passes the 6 questions above. More often, the cheapest option achieves its price by quietly removing discovery, revision rounds, or proper file delivery, the same pattern covered in how much a website costs. Compare scope carefully before assuming price alone reflects value.

The one thing to remember

Choosing a web design partner is a due diligence exercise, not a taste comparison: ask the 6 questions, watch for the 6 red flags, and insist the 6 contract elements are in writing before any work begins. The provider who welcomes this scrutiny is the one worth hiring.

If you want a second opinion on a proposal you have received, or want to see how we structure ours, tell us about your project: start a conversation.