Skip to content
Web design for businesses

How to choose a web design studio: what to check before you sign

A good-looking portfolio is a start. To choose well, you also need to understand how the studio works, what the proposal includes, and what you'll have after handoff. These are the questions I'd ask before signing.

Two hands reviewing a website layout together on a studio meeting table

In short

To choose a web design studio, start with what your business needs, open a few live sites, on your phone too, and ask what was done on each project. Compare proposals by scope, responsibility, and support, not just by price or page count. Before you sign, make sure you know who you'll be working with, how you'll manage the content, what access you'll get, and what the costs will be after launch. The right studio should explain its decisions and set expectations you can check.

You can open three portfolios, look at three good-looking websites, and come out just as confused as you went in. Everyone talks about design, user experience, and a website that will move your business forward. So how do you know who’s actually right for you, and what’s behind the quote?

The way I see it, the real choice starts when you move from “I like the design” to “I understand how this person thinks and works.” Design matters, no question. But you also want to know who will ask the right questions, who will help you make decisions, and what you’ll have when the work is done.

I’m writing this guide as someone who builds websites for a living. So every question here is one you can, and should, ask me too. The goal is for you to walk into that first call with a little more confidence, and to compare proposals by what matters to your business.

1. Before you choose a studio, define what you need from the website

You don’t need to show up with a finished project brief. Part of the job of whoever you hire is to help you figure out what’s right to build. But it helps to come with a basic picture of your business and of what you’d like to improve.

“I need a new website” is a start. “I want customers to understand the difference between my services, see relevant work, and reach out with a clearer request” opens up a completely different conversation. From there, you can start thinking about structure, content, and how people get in touch.

Before the call, write down:

  • Who needs to use the website? Individual customers, purchasing managers, patients, business owners, or several different audiences.
  • What should they understand? What you do, who it’s for, how you work, and how your services differ from one another.
  • What should they be able to do? Send an inquiry, book an appointment, buy something, read about a project, or find information without having to call.
  • What already exists? A website, branding, photos, copy, content that already gets traffic, or a connection to another system.
  • What are you working with? A rough budget, a target date, and who in the business can supply materials and approve decisions.

“I don’t know yet” is a legitimate answer too. Better to say so than to make up a list of requirements just to get a price. You can ask for a separate discovery phase, and find out what it includes and what you’ll get at the end of it.

From here on, I’ll focus on choosing who will plan and build the website with you.

2. Look past the first image in the portfolio

A portfolio usually shows a website at its most flattering moment. That’s natural. To get a real sense of the quality, open a few live sites and check what doesn’t appear in the big image at the top of the page.

Open a site on your phone and try to make sense of it

Pick two or three projects, ideally ones with needs similar to yours. Open them on your phone, go to a service page or a project page, and look for the way to get in touch. There’s no need to send a test form to someone else’s business. It’s enough to see whether the contact options are easy to reach and whether it’s clear what you’re being asked to fill in.

Notice the simple things. Is the text comfortable to read? Is the menu clear? Do buttons cover the content? Can you tell what the business does without hunting for the information? A website can look impressive in a screenshot and still be exhausting to use.

And not everything that isn’t to your taste is a flaw. An architect’s website and an industrial company’s website can have different goals and a different visual language. The question is whether the choices serve the business on the screen.

Ask what was actually done on the project

A good question to ask: “What was the challenge on this project, and how did what you built solve it?” You’ll learn more from the answer than from a list of technologies.

Ask, too, who was responsible for design, development, and content, and whether the site has changed since it was handed off. Sometimes the person built the site from a design someone else supplied, and sometimes they led the whole process. Either can be a good fit. What matters is knowing which kind of experience you’re looking at.

For example, on the Maze Roofing project, I had to make room for different services, two service areas, the local teams, and the company’s completed projects. In a conversation about a site like that, I’d also look at how the information connects: how you get from a service to the relevant area, and how the completed projects help explain what the company does. Those are decisions you can’t judge by the color of a button.

If you’re shown business results, ask how they were measured, over what period, and what else changed at the same time. An increase in leads may also have to do with advertising, traffic, or the offer itself. A screenshot of a chart with no context doesn’t tell the whole story.

Project cards in different sizes, with a wide website layout next to a narrow mobile layout

3. Listen to the questions they ask you

On a first call, I expect to talk about the business before we get into fonts and animations. Which services do you most want to promote? What do customers ask before they get in touch? What makes them hesitate? What happens after a lead comes in? And what on the current site already works well?

The answers shape the decisions on the site. If customers don’t understand the difference between two packages, you may need a clearer explanation. If a lot of the inquiries you get aren’t a fit, maybe the site is missing information about who the service is for or what it involves. Adding one more “Contact us” button won’t necessarily fix that.

You know your business. The person you hire has to know how to listen, sort things out, and turn that knowledge into a website other people can understand. They also have to be able to say, “I see why you asked for that, but I think it’s worth looking at another option,” and explain why.

Automatic agreement with every idea can feel nice in a conversation, but it doesn’t always help the project. On the other hand, someone who shoots down every request with “that’s how it’s done” isn’t necessarily listening either. Look for a conversation where you can think together, and where the recommendations rest on a clear need.

You shouldn’t expect a full discovery for free before you sign. It is reasonable to expect an explanation of how they think, which questions still need answers, and how decisions will be made along the way.

4. Compare proposals by scope, not just by price

Two proposals that both say “five-page business website” can cover very different work. In one, you supply finished copy and photos and get a customized template. In the other, the price includes discovery, work on the content, and the design and development of several page types. Without the details, it’s hard to know what you’re comparing.

I don’t think a low price automatically means poor work. Sometimes the proposal is simply narrower and fits the need exactly. By the same token, a high price is no proof of careful planning or good support. You have to read what’s inside.

This table can help you compare proposals on the same terms:

Topic What to ask What the proposal should spell out
Discovery and structure Who defines the pages and the order of the information? A discovery phase and what it produces
Content Who writes, edits, and uploads the copy and photos? Who is responsible for what, and how much content entry is included
Design What’s designed for this project and what’s based on a template? The page types and the approval stages
Development and integrations Which functions and systems does the site include? The specific forms, integrations, and features
Testing How are mobile use, accessibility, and speed tested? The tests that are included and who is responsible for fixes
Handoff What do you get so you can keep working with the site? The access, walkthrough, and documentation you agreed on
Ongoing costs What costs money after launch, too? Hosting, licenses, maintenance, and add-ons

Spell out revisions, add-ons, and the timeline too

“Revisions included” doesn’t say much without an explanation. Find out how many rounds of feedback are included, at which stages you can ask for changes, and what happens if you decide to add a service, a language, or a system that wasn’t in the plan.

Ask them to separate fixing something that doesn’t work as agreed from a new request. A form that doesn’t send the inquiry, for example, is a different matter from adding a new sign-up flow. That distinction should be clear to both sides up front.

The timeline also has to account for the materials and approvals that depend on you. “Four weeks” with no date for delivering the content and no approval stages is only half a plan. A realistic schedule, with milestones and clear payment terms, beats a fast promise nobody knows how to keep.

As you compare proposals, look at what the year after launch will cost, too.

Two proposal pages laid out next to a planning board with three project stages

5. Know who you’ll be working with and how decisions get made

“Studio” can mean one person, a small team, or a business that brings in partners project by project. The name alone doesn’t tell you who will design the site, who will build it, and who you’ll write to when something isn’t clear.

Ask who your point of contact is, who does each part, and who’s responsible for tying it all together. If you talked to a salesperson, will you also meet the person who’ll manage the project? If the work includes a copywriter or a photographer, who coordinates with them and who approves what they deliver?

Working with one person gives you continuity and someone who knows your business. A bigger team can divide the roles more widely. The right fit depends on the project and on how you like to work.

Beyond how the business is set up, agree on the working routine: where feedback is collected, when you meet, who approves decisions, and what response times to expect. A reply that doesn’t arrive within the hour isn’t necessarily a sign of trouble. Ongoing confusion about who handles what, on the other hand, is worth raising.

Ask to speak, with their permission, to one or two clients who went through a similar process. Instead of only asking whether they’re happy, ask what happened when they requested a change, how the timeline went, and whether they got what they thought was included. Details like these can help you picture what working together is like.

6. Ask to see how you’ll manage the site

The name of the content management system matters less than whether you can do what you need to do in it. If you plan to add projects, publish articles, or update services, it’s worth seeing how that’s actually done.

Ask for a demo on a sample site or in a demo environment: adding a project, replacing an image, editing a paragraph, and publishing new content. You don’t need access to another client’s site. The point is to understand how many steps it takes, what you can safely edit, and what needs professional help.

I work with WordPress because of the flexibility it gives me in content structure, design, and development. But using WordPress doesn’t by itself guarantee that the site will be easy to manage. The editing side has to be planned around the people who’ll use it, and it should come with a walkthrough of the site that was actually built.

If you already have a site on Wix, Squarespace, or another platform, ask why a move is needed. Sometimes there’s a limitation that justifies it, and sometimes the existing site can be improved. Switching platforms is a decision that also has to cover the content, the existing URLs, and the work that will be needed after handoff.

Get clear on access, ownership, and licenses

“Your website” should also mean something in practical terms. Check whose name the domain is registered under, who manages the hosting account, what permissions you’ll get, and what gets handed over if you later want to work with someone else.

It helps to separate the content and work created for you from third-party services and licenses. A plugin, a stock photo, or a font may come with its own terms and costs. Ask who pays for license renewals and what happens if you stop working together.

Don’t assume that design files, source code, a hosting transfer, or help with a move are included just because they seem obvious to you. If something matters to you down the road, ask for it to be written explicitly into the proposal or the agreement.

7. Find out what actually gets tested before launch

You don’t have to be a developer to ask about the quality of the build. Instead of asking for a list of technical terms, ask which tests are run and how the problems they turn up get handled.

Phones and browsers: which pages and flows are tested, whether the content is readable, and whether the menus and forms are comfortable to use. “Responsive” in a proposal should translate into a site that’s reasonable to use, not just an image that shrinks.

Speed: how images, fonts, and code are handled, and which pages the result is tested on. A single score in a testing tool isn’t the whole story. The test conditions, the hosting, and the content all play a part. Ask for an explanation of the work, not a promise of a perfect score in every situation.

Accessibility: who’s responsible for the testing and the fixes, what they cover, and which requirements apply to your project. Installing an accessibility plugin is no substitute for testing the site. It’s also worth asking how you’ll keep the site accessible as you add new content.

Forms and integrations: who checks that an inquiry reaches the right place, that the confirmation messages are clear, and that the connections to other systems work. These tests should be run on your site before handoff, together with whoever will be receiving the leads.

Search: what the preparation for search engines includes, and who’s responsible for titles, page structure, crawl settings, and checking that the public site isn’t blocked by mistake. All of that is separate from ongoing SEO work on content, search terms, and results over time.

If you have an existing site, ask directly how they’ll handle URLs that are about to change and content that’s already on Google. A redesign shouldn’t start by automatically deleting everything that was built before.

8. Agree on what happens after handoff

On launch day the site should be ready to work, but the life of the business goes on. A service changes, projects get added, software gets updated, and sometimes something breaks. It’s worth knowing in advance who handles each of those.

Ask them to distinguish between three kinds of work:

  • Fixes covered by the handoff or the warranty you agreed on: taking care of things that don’t work according to the approved scope.
  • Technical maintenance: updates, backups, and checks, depending on what the service includes.
  • New development or content: another page, a design change, or an integration that wasn’t part of the project.

Check, too, who’s responsible for backups, what a restore includes, and who you contact if the site is down. Not every site needs the same level of support, and not every studio offers around-the-clock response. What matters is that your expectations match the service you bought.

If you’re offered an ongoing plan, ask for a breakdown of the website maintenance services, the response times, and the work that’s billed separately. And if you choose to handle maintenance somewhere else, find out how the handoff works and what the move requires.

9. Ask how they use AI, too

In 2026, it makes perfect sense to ask whoever is building your website how they use AI. These tools can help with research, writing, code, and testing. Using them doesn’t make the work less professional, and it doesn’t mean the whole project has turned into the push of a button.

I use AI in my own work, but responsibility for the decisions and the result stays with me. I have to understand what fits the business, check the content and the code, and spot the places where I’m handed a solution that looks good at first glance but doesn’t really fit.

So ask what the tools do, who checks their output, and how the site will keep sounding like you. In the content, for example, who verifies professional claims and deletes promises the business never made? In the design, how do you get past the generic look? In development, how do you check that the solution works beyond the first example?

If the work involves customer information or internal materials, also ask what gets fed into the tools and under what terms. It’s a practical question about the process, just like asking who gets access to the site’s admin.

I wrote about the difference between being able to generate a website and the experience it takes to lead the process in my article Anyone can build a website with AI. When you choose a professional, it’s important to understand what their experience adds to the work the tools make possible.

10. Before you sign, check that it all adds up

After you’ve looked at the work and had a few conversations, stop and ask yourself: Do I understand what’s about to be built? Is it clear to me why it fits the business? And do I know what will happen along the way?

Vague answers like “everything’s included” or “it’ll be a perfect website” are a reason to ask for details. A promise of the top spot on Google should raise a flag as well: Google itself says no one can guarantee a #1 ranking. A solid foundation for search is an important part of the work. A guaranteed position is a different promise altogether.

As I see it, before you sign you should be able to answer yes to five questions:

  1. Have I seen live sites and understood what this person did on them?
  2. Did I get a proposal that spells out what’s included, what isn’t, and what depends on me?
  3. Is it clear who I’ll be working with and how decisions and changes get approved?
  4. Do I know what access, walkthrough, and editing options I’ll get?
  5. Do I understand the costs and who’s responsible for what after launch, too?

You don’t have to find someone who agrees with you on everything. You do want someone whose judgment you trust, whose explanations you understand, and who you feel comfortable asking even the basic questions.

At 3Pines Studio, my web design studio, I handle the work personally, from getting to know the business and planning through design and build. That’s the way of working that suits me, and knowing the person behind the business directly is a central part of it.

If you’d like to see whether we’re a fit, we can start with a conversation about your business, your current website, and what you’d like to do differently. From there, we can figure out what really needs to be built and the right way to go about it.

Frequently asked questions

Does the studio have to know my industry?

Experience in your industry can help, but it isn't the only thing to choose by. Check whether the studio understands what your business needs, knows how to ask questions, and has worked on projects with similar requirements. A website from the same industry isn't necessarily similar in scope and complexity to the one you need. In fields with special professional requirements, find out who's responsible for reviewing the content and making the adjustments that are needed.

How many quotes should I get for a website?

Two or three detailed proposals can be a useful starting point, as long as they're all based on the same needs. That's practical advice, not a required number. If the scope differs, ask for clarification before you compare prices. It's better to understand a few proposals well than to collect a lot of prices without knowing what each one includes.

Is a low-priced website proposal necessarily worse?

No. A low price can fit a small site, ready-made materials, or work based on a template. Check what's included in discovery, content, design, testing, and handoff, and what will cost money later. A high price doesn't guarantee a fit either. The question is whether the proposal meets your need and whether it's clear what you'll get.

What's the difference between designing a website and building one?

Design covers, among other things, the look, the hierarchy of information, and how people use the pages. Build and development turn the plan into a working site, with a content management system, forms, and integrations as needed. Sometimes one person does both, and sometimes the work is split. Check exactly what the proposal includes and who's responsible for connecting the stages.

How do I make sure I can update the site and move to another provider later?

Define up front which content you'll be able to edit, ask for a demo and a walkthrough, and agree on which permissions and files you'll receive. Also check whose name the domain is registered under, who holds the hosting account, and what the terms are for plugins and licenses. If being able to move to another provider matters to you, ask for the handoff, the export, and any possible costs to be clear in the agreement.

Should a studio that uses AI charge less?

Using AI may save time on some tasks, but it doesn't set the price of a project on its own. The work still takes planning, fitting the site to the business, testing, and responsibility for the result. Compare the scope, the quality of the work, and the support, and ask how the time saved affects the proposal and the process. There's no reason to assume that any use of AI justifies a particular price.

Does building a website include SEO and maintenance?

Only if that's explicitly agreed. An SEO foundation during the build, ongoing SEO, and technical maintenance are different scopes of work. Ask for a breakdown of the settings and tests included in the build, and of the services and costs after launch. That way you'll know who's responsible for content, updates, backups, and fixing problems.

Want to know what's right for your website?

A short intro call about your business, your customers, and what the website needs to help them do.