Does this apply to a one-person freelancer or only to agencies?

It applies more, not less. A freelancer has fewer buffers than an agency, which means the questions about scope, ownership, and exit matter more, not less. The framework is the same. The answers you accept should be at least as concrete.

What should I prepare before the first call with a web designer?

A short brief: what the site needs to do (calls, bookings, ecommerce, leads), who it is for, a rough budget range, and a list of two or three sites you like and why. A designer who can run a useful first call without that brief is either very experienced or improvising; you cannot tell which from the call itself.

How can I check the result before I pay the final invoice?

Ask for a staging link you can click through on a phone and a laptop, ask for the Search Console and analytics accounts to be transferred to your ownership before the final payment, and ask for a short written summary of what was built and what is still pending. If any of those three is refused, the final payment is the wrong time to find out.

Should the site be managed after launch, or can I run it myself?

Both are reasonable. The honest answer depends on whether you want to spend evenings learning the platform, or whether the site has a revenue job that makes a monthly fee worth the trade. The managed versus one-time guide walks through that decision in detail. The thing to avoid is paying for both at once, or assuming a managed plan will quietly convert to a one-time handoff at the end of the first year.

Questions to Ask a Web Designer Before You Sign a Contract (2026)

The most useful questions to ask a web designer before you sign are not about features. They are about what happens when the relationship ends. Here is what to ask, why it matters, and the red flags that mean you should walk away.

If you are about to hire a web designer, the most useful questions are not about features. They are about what happens when the relationship ends, who owns what during the engagement, and how the cost compares to the alternatives. This guide walks through what to ask before you sign, with a short list per stage, and the red flags that mean you should walk away.

A short note on scope. The article assumes you have already decided that a custom or designer-built site is the right path. If you are still comparing a custom build to a DIY builder, our website builder versus web designer guide (in progress) walks through that trade-off. If you are still deciding whether to spend money on a website at all, the complete cost guide frames the realistic range for a Canadian small business in 2026. This article picks up the conversation once those decisions are made and the next step is the contract.

What kind of decision you are actually making

Hiring a web designer is not a product purchase. It is a service engagement with a person or a small team, and the contract is the working agreement. The reason this matters more than the feature list is that you are not just buying a finished website. You are buying a working relationship for the weeks of the build, the handoff at launch, and the period after — which is when most of the cost, the trust, and the regret actually live.

A good designer knows this and is happy to answer the questions. A bad one deflects. The single best signal of a designer you can work with is whether they answer the awkward questions directly: who owns the code, what happens if you want to leave, and what their last three clients did after the project ended.

The three paths you are choosing between

A "web designer" in 2026 is a label that covers three distinct relationships, and the questions you ask change depending on which one you are walking into. The package README for this cluster groups the three options together because the same owner questions recur across all of them.

A DIY builder (Wix, Squarespace, GoDaddy)

A DIY builder is software, not a person. The three platforms most Canadian small businesses encounter are Wix, Squarespace, and GoDaddy Canada's website builder. The questions here are about the platform, not a person: who owns the design files, what an export looks like, what the renewal pricing is after the first year, and what the platform does to your search visibility.

A freelance designer or small studio

A freelance designer or a small studio is the path most owners picture when they say "web designer." It is the one where the questions about who owns what, what the exit looks like, and what the handoff includes matter most. The deliverable is usually a finished site plus the source files, with the option to add a maintenance arrangement after launch.

A managed website plan (design plus ongoing service)

A managed website plan is the third shape, and the one that has the most contractual surface area. The studio builds the site and continues to run it for a monthly fee. The owner gets a live site and minor changes on request, but the code, the design files, and often the hosting account stay with the studio. The managed versus one-time trade-off (covered in a separate guide, in progress) is a separate decision; for the questions stage, the key point is that the same ownership questions recur, and the answers look different when there is a recurring fee attached.

What you will be asked to do during the build

The first awkward question is the one the designer will ask you, not the other way around: what content do you have, what photos, what copy, what decisions are already made. A designer who tells you they will handle everything is selling you a different product, and the price tag will tell you which one. A designer who asks for the same things twice is warning you that the project will take longer than quoted. The honest version is somewhere in the middle: you provide the raw material, the designer provides the structure, and the project moves when both sides do their part.

The questions to ask at this stage are about expectations and timing. How long does a typical project like this take, from kickoff to launch. What is the cadence for reviews — weekly, at milestones, only at the end. What happens if you miss a review window. What is the cost if you change your mind about the scope halfway through. The answers reveal whether the designer has done this before, or is improvising with your deposit.

Who owns the site, the files, and the accounts during the engagement

Ownership is the question most contracts leave vague, and the one that causes the most regret. Three things need a clear answer before the contract is signed: the design files, the code, and the accounts.

The design files are the layered artwork the designer uses to build the site — the Photoshop, Figma, or Sketch originals. The code is what the designer writes or assembles. The accounts are the things that live outside the designer's laptop: the domain registrar, the hosting account, the Google Search Console property, the analytics account, and any third-party subscriptions like email marketing or booking software.

The question to ask is: at the end of the project, do I own the design files, the code, and all of the accounts, or do you keep some of them as part of a managed arrangement. A reasonable answer is that you own everything except in a managed plan, where the studio retains the code and hosting as the price of the ongoing service. An unreasonable answer is "we will sort that out at the end" or "the accounts stay with us for continuity." Continuity is the studio's convenience, not yours.

What the ongoing cost and the exit actually look like

Most small-business owners budget for the build and forget about the run. The realistic monthly cost of a live site in 2026 includes hosting, a domain renewal, an SSL certificate, an email service if the site has one, and any third-party subscriptions the site depends on. The cost guide covers the full landscape; for the contract stage, the question is whether the designer is going to be the one paying those bills, and what happens if you stop paying them.

The exit question is the one to ask out loud, even if it feels confrontational. What does a handoff look like. What does it cost. How long does it take. What format do the files come in. Can the next designer open them without paying for the originals. If the answers are vague, the contract is vague, and the relationship will end badly. The Google Search Central guidance on creating helpful content is a useful sanity check on what a finished site should be able to show a future owner: clean code, real content, and search signals that survive a rebuild.

A short decision framework

Before the contract conversation, decide three things for yourself: how much you can spend on the build, how much you can spend each month after, and what you want to own at the end. The first number is the budget for the project. The second is the run cost. The third is the non-negotiable: a freelance build with files and accounts handed over, a managed plan where the studio keeps ownership in exchange for the monthly fee, or a DIY builder where you keep ownership and accept the time cost.

If you cannot decide on those three things before the first call, the call will not help. The designer will quote you a range, the range will be wider than you expected, and the cheapest option will look attractive until you ask the exit question. Decide first, then ask.

The questions to ask, organised by stage

A short list of the questions to bring to each conversation. The list is not exhaustive — bring the ones that match your situation — but it covers the categories most owners forget.

Before signing:

What is included in the quoted price, and what would be billed as extra?
Who owns the design files, the code, and the third-party accounts at the end?
What does the timeline look like, and what happens if I miss a review window?
Do you have references I can call — ideally ones from twelve months after launch, not the week of launch?

During the build:

How will reviews work — weekly, at milestones, or only at the end?
What happens if I want to change the scope halfway through?
Who is my day-to-day contact, and what is their typical response time?

At handoff:

What exactly do I receive — files, accounts, documentation?
Can the next designer open everything without paying for licenses I do not own?
What training or run-through do you provide so I can manage the site day-to-day?
What does a maintenance arrangement look like, and what does it cost?

If any answer is vague, slow, or deflected, treat that as the answer. A designer who cannot answer before the contract is signed will not answer better after the deposit is paid.

Questions to Ask a Web Designer Before You Sign a Contract