How to Choose the Right Web Designer or Agency

Who this guide is for

This guide is for a local service business owner who is trying to hire someone to build or rebuild a website and is not sure how to tell a good option from a risky one.

Maybe you have two proposals in front of you and no way to compare them beyond the total at the bottom. Maybe a friend recommended a freelancer and you want a sense of what to ask before saying yes. Maybe you are weighing a DIY platform against paying someone, and you are not sure which is actually the better use of your time and money.

None of this requires design or technical knowledge. It requires knowing what a good process looks like before you are in the middle of one.

The short answer

There is no universally correct choice between a freelancer, an agency, and a DIY platform. There is only the choice that fits your budget, how much guidance you want, and how much this particular website matters to your business right now.

What matters more than which type of vendor you pick is whether the scope is written down clearly, whether you understand what happens after launch, and whether you would still know what to do if the relationship ended tomorrow. Those three things separate a good arrangement from a risky one, regardless of who you hire.

Freelancer, agency, or DIY — a plain comparison

Each is a reasonable choice under the right circumstances. None is automatically better.

A freelancer is often the most affordable route to a genuinely custom site, and you typically work with the same person throughout, which can make communication simpler. The tradeoff is capacity — one person has one calendar, and if they are unavailable for a stretch, your project waits.

An agency usually brings more structure: a defined process, more than one person who can pick up a question, and often broader experience across different kinds of businesses. That structure costs more, and you may work through a project manager rather than directly with whoever is doing the work.

A DIY platform costs the least upfront and puts you in full control of changes. It asks the most of your own time, and the result depends heavily on how much you are willing to learn and maintain. It is a reasonable choice when the budget genuinely is not there yet, and a harder one when the site needs to do real commercial work from day one.

The mismatch to avoid is picking based on price or reputation alone rather than fit. A freelancer with a full calendar is not a good choice for a business that needs a site running in three weeks. An agency's structure is wasted on a one-page site that needs no ongoing coordination.

What should be explicit before you sign anything

A good proposal answers these plainly, without you having to ask twice:

• What is included, and what is not. Specifically who writes the content, how many pages, and how many rounds of revisions are built in.
• Who owns what when it's finished. Your domain, hosting, and analytics accounts should end up registered to your business, not the vendor's. This deserves its own real answer, not a line item — the website ownership guide covers exactly what to confirm and why it matters.
• How content and SEO are handled, especially if an existing site is being replaced. If pages or addresses are changing, ask what happens to search visibility you already have. The redesign guide covers this in depth if that's the situation you're in.
• Whether accessibility and basic tracking are part of the build, or something you would need to add afterward.
• What happens after launch. Who fixes something that breaks in month three, and whether that is included or a separate arrangement.

None of this needs to be complicated. It needs to be written down, not implied.

How to compare two proposals that look nothing alike

The number at the bottom of a proposal tells you very little on its own. Two quotes for "a website" can describe genuinely different amounts of work.

Line up the scope before you compare the price. Does one include writing the content and the other assumes you will supply it? Does one include a set number of revision rounds and the other leave that open-ended? Does one include launch support and testing and the other end at handoff? A cheaper number that excludes real work is not automatically the better deal, and a higher number is not automatically the safer one — you can only tell once you know what each is actually pricing. The website pricing guide goes deeper on the specific things that drive a quote up or down, if you want to understand the mechanics behind the numbers themselves.

Evaluating portfolios and case studies

A portfolio tells you more about fit than it tells you about skill in the abstract.

Look for businesses similar to yours — local, service-based, and in a comparable price range — rather than the most visually striking project in the collection. A beautiful site for a national retail brand tells you less about how someone will handle your local service business than a plain, functional one built for a business like yours.

Check the sites on a phone, not just in the portfolio screenshots. Most of your customers will arrive on one, and a portfolio that only looks good on a desktop monitor is showing you half the picture.

Be cautious about outcome claims attached to past work — traffic, rankings, or leads credited to a specific site are hard to verify and easy to overstate. A portfolio that shows clear, working, well-organized sites for businesses like yours is more useful evidence than a slide claiming a specific result.

What to ask about the working process

The process matters almost as much as the output, because it determines how smoothly you get there.

Ask who your actual point of contact will be, and whether that changes partway through. Ask how revisions work in practice — through email, a shared document, a formal review round — and how disagreements between people on your team get resolved. Ask for a realistic sense of timeline and what would change it, rather than a single date that assumes everything goes perfectly.

None of these questions are unusual to ask, and a vendor who has done this before will have straightforward answers.

Signs worth pausing on

None of these automatically mean something is wrong. They are reasons to ask a direct follow-up question before moving forward.

• A scope that stays vague even after you ask. "We'll figure it out as we go" is sometimes true collaboration and sometimes a sign that nothing is actually planned.
• Pressure to sign quickly, especially paired with a discount that expires today. A legitimate proposal survives a week of thinking about it.
• No willingness to explain their process or show real past work. Reasonable privacy around specific clients is normal; an inability to describe how they typically work is not.
• A single point of failure with no backup plan. Worth knowing in advance, not discovering when someone becomes unavailable mid-project.
• Reluctance to put ownership of accounts in writing. This is a fair, ordinary question, and a vendor who treats it as an odd one is worth a second look.

Finding one of these is not a verdict. It is a reason to ask the question plainly and see how it is answered.

Is the cheap option actually a good deal?

Sometimes. The honest way to tell is to find out what it excludes.

A lower price because someone works efficiently, keeps overhead low, and has a tight, well-practiced process is a genuinely good deal — you are paying for the work, not for extra layers around it. A lower price because content, revisions, testing, or post-launch support have quietly been left out is the same job, priced for less of it. Neither is dishonest on its own. The problem is only when the exclusion isn't stated plainly and you find out later.

Complexity works the same way in reverse. A proposal padded with scope you do not need is not more thorough — it is more expensive for no reason that serves your business. The right proposal is the smallest one that actually solves your problem, clearly priced, with nothing important left unstated.

What we recommend

Pick based on fit, not on which option sounds most impressive.

Get the scope in writing, confirm what you will own when it's finished, and ask what happens after launch — before you sign anything, not after. A vendor confident in their work will answer all of that plainly, and a proposal that holds up to those questions is a good sign regardless of whether it comes from a freelancer, an agency, or somewhere in between.