10 Questions to Ask Any Web Designer Before Signing

You are sitting across from a web designer who shows you some work, quotes you a price, and slides a contract in front of you. Everything feels right — they seem competent, the work looks good, and the number is in your ballpark. But something nags at you. You do not know enough to know if you should be worried.

Most business owners do not discover the gap until months later. The site launches. Three months in, you need a small change. Your designer is no longer responding to emails. Or they want to charge more than expected. Or the site is hosted under their account and you cannot move it. Or they never explained what would happen to the design or domain if the relationship ends.

By then, money has changed hands and the mess is yours to untangle. This guide exists to surface those answers before you sign. The right questions — asked upfront — make the difference between a straightforward partnership and an expensive surprise.

Why these ten questions

These are not gotcha questions. They are not designed to make any particular vendor look bad. They are the questions whose answers reveal how a provider actually works — their processes, their maturity, and whether they have thought about what happens beyond launch day.

A good designer or agency will have clear, confident answers to all of these. Vague answers, evasions, or deflections are meaningful information. They suggest the vendor has not thought through the detail, or does not want you to know the answer. Either way, that is data worth paying attention to.

1. What exactly is included in this price?

Proposals have a way of being specific about dollar amounts and vague about what that money covers. One designer's "website build" might include copywriting, photography, and unlimited revisions. Another's might mean a template with your content plugged in. The dollar number tells you nothing without understanding what comes with it.

A proposal that says "Custom website design and development: $8,000" is incomplete. You need a detailed list of what that includes — every deliverable, every service, every resource that comes with the price.

What a good answer sounds like: A detailed breakdown showing design, development, strategy, copywriting, photography, revision rounds, testing, launch support, and any other work included. It also specifies what is not included, so you can see the edge where the scope ends.

What a red flag sounds like: "It's all in the proposal" without spelling out the components. Pushing back when you ask for clarification. Listing price but not deliverables.

2. What is NOT included?

This is the inverse of the first question and it is equally important. A proposal that lists inclusions but not exclusions leaves too much room for confusion. You think something is included and they do not. Someone is disappointed.

The specifics matter less than the clarity. It is fine if copywriting is not included — but it needs to be clear upfront, not discovered when they hand you a site with placeholder text.

What a good answer sounds like: A separate section in the proposal spelling out what is out of scope. "Not included: client copywriting, photography, third-party integrations beyond standard setup, SEO content strategy, ongoing maintenance, annual hosting."

What a red flag sounds like: Silence on the question. Or defensive pushback — "Well, it depends on what you mean."

3. Who owns the site when it is done?

Ownership is complex because there are different kinds of ownership: the domain name, the hosting account, the design files, the codebase, the content. Each of these can live in different hands. The answer matters because it determines what happens if the relationship ends or if you need another vendor to make changes.

Some vendors build on platforms they control, so you never own the underlying site. Some register the domain in their name. Some keep design files proprietary. Some give you everything. You need to know which is which.

What a good answer sounds like: Clarity on each component. "You own the domain, registered in your name. You own the code and can host it anywhere. Design files are yours after final payment. Content is yours. You have full admin access to the hosting account from day one."

What a red flag sounds like: "I keep the design files." "The domain stays registered under my account." "The code is proprietary." "You do not get direct hosting access." These are not automatically disqualifying, but they shift control away from you. You should know that before signing.

4. What does ongoing maintenance cost?

Many proposals stop at launch day. But a website needs ongoing work: security updates, plugin maintenance, backups, occasional content updates, troubleshooting when something breaks. This work has a cost whether you do it yourself or pay someone else.

A proposal that ignores year two is incomplete. You need to understand the maintenance picture before launch, not discover the costs after.

What a good answer sounds like: "Hosting is $X per month. Security and basic maintenance run $X per month. Content updates that you handle yourself cost nothing; updates we handle cost $X per hour or come with a retainer." Or: "Our care plan is $X per month and covers hosting, maintenance, standard content updates, and support."

What a red flag sounds like: "You can handle maintenance yourself." If you could and wanted to, you probably would not need a designer. "We can talk about that later." You cannot plan a budget if the answer is not on the table. "Most clients do not need much maintenance." They do, they just do not think about it until something breaks.

5. How do I request changes after launch?

After launch, you will need changes. Not because the site was wrong, but because your business changes. Hours shift, services evolve, testimonials need adding. You need to know the mechanics: Can you make small changes yourself or do you always go through the designer? How long does a change take? How is it billed?

The answer matters because it affects how responsive and flexible the site can be. If every change requires the designer and costs money, you will make fewer of them. The site will become outdated.

What a good answer sounds like: "Small text and photo updates, you can do yourself through a content management system. More complex changes, you send to us with a change request and we handle them. We charge hourly." Or: "All updates come through us but they are included in your care plan, so you do not worry about the cost."

What a red flag sounds like: "Everything goes through us." That locks you in. "We will deal with it after launch." You need the process defined upfront. Vague timelines and pricing for change requests.

6. What happens if I want to leave?

This is the most important question you might never need to ask. It surfaces how confident the vendor is and how much they have designed the relationship for flexibility versus lock-in.

If a vendor gets defensive when you ask this question, that is a signal. A vendor who has thought it through and has a clear, client-friendly answer demonstrates maturity. They are confident enough not to fear you leaving. They know if you stay, it is because they are delivering value, not because you are trapped.

What a good answer sounds like: "You own everything — domain, code, design files, hosting account. You can move whenever you want. If you are on a monthly plan, thirty days notice ends it. If there is a contract with a minimum, we give you thirty days to transition and you do not owe anything beyond that. We can recommend someone to take over if you need help with the transition."

What a red flag sounds like: "There is a long-term contract." That is not automatically wrong, but you should understand the terms. "The domain stays with us." Now you are trapped. "You cannot move the site, it is built on our proprietary platform." Vendor lock-in. Penalties or surprise fees if you leave before a certain date.

Ask this question specifically because vendors reveal themselves in how they answer it. Their comfort or discomfort tells you a lot about how they structure the relationship.

7. Can I see examples of similar work?

Portfolio review is standard. But the specific examples matter. You want to see work that looks like what you want for your site, done for businesses like yours. A designer who builds boutique ecommerce stores might produce beautiful work but have no experience with service business websites.

Ask not just to see the work but to talk to past clients. How did the relationship go? Would they hire the designer again? Did the site perform as expected? Designers will refer you to happy clients, but those conversations are gold — you hear what the relationship is actually like.

What a good answer sounds like: Showing relevant work with context. "Here is a plumbing service website we built. Here is what we were solving for — they needed to showcase work and get more calls. Here are the results." And offering client references who will speak candidly.

What a red flag sounds like: No portfolio or a portfolio that is not relevant to your needs. Reluctance to provide references. Work that looks pretty but does not tell you anything about what the business achieved.

8. What is your timeline, and what could delay it?

A project timeline is a shared commitment but delays happen. The designer gets sick. The hosting provider has an outage. You do not provide content on schedule. You need to understand the base timeline and the variables that could change it.

A proposal that says "Eight weeks" is incomplete. What does the timeline assume? What happens if you are slow to provide feedback or content? What is actually on the designer and what is on you?

What a good answer sounds like: "Our estimate is eight weeks from signed contract to launch. That assumes you provide content and feedback within five business days of our requests. Major delays — if content is not provided — can extend the timeline. We will flag delays as soon as they are obvious, not the week before launch."

What a red flag sounds like: A fixed timeline with no caveats or conversation about what could change it. "We will launch on this date, guaranteed" usually means they are not accounting for the real variables. Unwillingness to discuss contingencies or delays.

9. How do you handle revisions?

Revisions are inevitable. You will see design direction and want changes. You will review the site and find things that do not feel right. The question is whether the designer has a reasonable process for handling that or if revisions feel like an awkward negotiation.

Some designers include unlimited revisions. Some include a set number. Some charge for additional rounds. There is no universally right answer, but you need to know which world you are in before you sign.

What a good answer sounds like: "We include two rounds of design revisions. If you have feedback beyond that, we can do additional rounds at $X per hour." Or: "We include unlimited revisions within scope. Big departures from the approved direction are scoped separately." The designer has a defined process and clear boundaries.

What a red flag sounds like: "Revisions are extra" without defining what is included first. No framework for what counts as revision versus new work. Pushback when you request reasonable changes.

10. What does year two actually cost?

This question is the capstone. It takes everything from the previous nine questions and summarizes what you are actually committing to in the medium term.

If the designer designed year two clearly — knowing what hosting costs, what updates cost, what support costs, what ongoing changes cost — they should be able to tell you. If they get vague or uncertain, it is a sign they have not thought through their own offering deeply enough.

What a good answer sounds like: A clear breakdown. "Your year-two costs are: $X for hosting, $X per month for maintenance and updates — unless you handle updates yourself, then just the hosting — and hourly rates for change requests beyond standard updates. Or, we have a $X/month care plan that bundles it all."

What a red flag sounds like: Uncertainty or evasion. "We can figure that out when we get there." If they have not figured it out, you are taking on planning risk. Dramatic cost jumps from year one to year two without explanation.

The question behind the questions

These ten questions are not actually about getting specific information — though the information matters. They are about evaluating three things:

• Transparency. Does the designer answer straightforwardly or dance around the question? Can you trust what they tell you?
• Process maturity. Have they thought through their approach deeply or are they making it up as they go? Do they have a repeatable system that works?
• Beyond-launch thinking. Do they see the relationship as ending on launch day or as an ongoing partnership? Are they thinking about what happens in month six and year two?

A designer who answers all ten clearly and confidently has already solved most of the problems that plague website projects. One who gets defensive or vague is signaling that you are probably going to discover gaps later.

You are not evaluating whether their answer is the only right answer. You are evaluating whether they have thought it through and can explain it clearly.

What happens next

After you have the answers to these ten questions, you have enough information to make a real comparison. You can see what you are actually buying, what you are committing to, and what the true cost is over the first two years.

This is the point where you should also talk to the designer's references. Ask them: "Did the relationship feel as described in the proposal? Were there surprises? Did the site do what you needed it to do?" Those conversations often reveal more than the proposal ever will.

The goal is not to grill the designer or look for reasons to walk away. It is to make sure you have a clear understanding of what you are signing before you sign it. A straightforward designer wants you to ask these questions. They want you to know what you are getting. The ones who want to rush you past this step are the ones worth being cautious about.

Ready to start a website project?

If you are evaluating a web designer and these questions have made the criteria clearer, use them in your conversations. If you are considering Evident Sites, you can expect clear answers to all ten.

The first step is a short discovery call where we talk through your goals and the right approach for your business. You will see the strategy and design before any billing starts, so you can decide from a place of clarity, not hope. There is no pressure and no commitment until you have reviewed the work.

Book a free discovery call to talk through your website and see if Evident is the right fit for your business.