What to ask a web designer before hiring one

The short answer

What should you ask a web designer before hiring one? Ask the same questions every candidate gets: show me live sites you built for businesses like mine, who will own the domain and the website, what exactly is included in the price, how long it will take, what you need from me, what platform you will build on and why, whether the site will be mobile-friendly and fast, what SEO is included, whether I can update it myself, what support exists after launch, and how we will measure success. Then ask yourself whether the answers were specific enough to check, or just reassuring enough to end the conversation.

This article gives you all 12 questions, explains what a good answer sounds like for each, and flags the red flags that should make you pause. If you are weighing the DIY route at all, read website builders versus web developers first - the decision to hire a designer at all is worth making deliberately. And if you want to know what the project should cost in Canada before you collect quotes, how much a website costs in Canada gives you the real numbers.

Why asking the right questions matters

A website is the only marketing channel your business fully owns, and a bad web design hire is one of the most expensive mistakes a small business can make. Not just because of the money lost on a site that does not work, but because of the months spent waiting for it, the leads that quietly went to competitors while your forms were broken, and the cost of paying someone else to rebuild it properly. Most of these disasters were preventable with the questions in this article.

The pattern behind almost every horror story is the same: the owner hired on price and portfolio alone. Portfolios show finished designs, but they do not show whether the sites load fast, rank on Google, bring in enquiries, or were still editable a year later. Price tells you even less - a low quote with no scope attached is not a deal, it is an IOU you will pay later. The questions below exist to get you past the pretty pictures and the reassuring sales pitch, to the working relationship underneath.

1. Can I see live sites you built for businesses like mine?

A portfolio is the first screen, but look at it like an investigator, not a fan. Screenshots are not enough: visit the actual live sites on your phone. Are they fast? Readable? Easy to use with your thumb? Look for businesses similar to yours - a portfolio full of portfolios and agencies tells you little about what a designer will do for a plumbing company or a physiotherapy clinic.

Then ask for references, and actually call one or two. Ask the past client how the project went, how communication was, whether it launched on time, and whether they would hire the designer again. Any professional should offer references without hesitation. A designer who goes quiet at this question is telling you something important.

2. Who will own the domain, the website, and the content?

This is the single most important question on this list, and the one most often skipped. Ownership disputes are a real and ugly pattern in this industry: a designer registers your domain in their own account, builds the site under their own hosting plan, and you discover years later that you cannot leave, cannot edit, and technically do not own the website you paid for.

Before you sign anything, get written confirmation that you will own the domain (registered in your name or your company's name, in an account you control), the website files or CMS login, and all content created for the site. If you ever part ways, you should be able to take everything and walk. If the designer hesitates here, walk away now - it is far cheaper than untangling it later.

3. What exactly is included in the price?

"A website for $2,000" is not a scope, it is a sentence. You need the scope in writing: how many pages, what functionality (forms, booking, payments), whether copywriting and images are included or on you, how many rounds of revisions are included, and what counts as an extra that costs more. Projects blow up when two people silently hold different definitions of what was agreed.

Also ask what you are expected to provide and when: text, photos, your logo, product details. In our experience, the number one cause of delayed launches is not the developer - it is content arriving late. A designer with a real process will tell you exactly what they need from you and what happens to the timeline if it arrives late.

4. What will it cost in total, including the first year?

The build price is only part of the bill. Ask about the recurring costs that start after launch: hosting, domain renewal, SSL certificates, premium plugins or theme licences, and ongoing maintenance. A site quoted cheaply but locked to expensive proprietary hosting or paid plugins can cost more in year one than a pricier build with simple, standard infrastructure.

Ask for the total in Canadian dollars, not just the design fee. Good designers will happily break this down; vague answers here usually mean the bill will grow later. For context on what these ongoing numbers look like in Canada, see our breakdown of website maintenance costs in Canada - it helps you spot a quote that quietly understates the running costs.

5. How long will it take, and what do you need from me?

Get a realistic timeline with milestones: discovery, design approval, development, testing, and launch. Then ask the follow-up that reveals whether the timeline is real: what do you need from me, and what happens if I am slow? The single biggest variable in any website project is how quickly the client supplies text, photos, and feedback - a factor that routinely doubles schedules.

Our guide on how long it takes to build a website gives you realistic Canadian ranges by project type, so you can tell whether a quoted timeline is grounded or optimistic. Be wary of timelines that sound certain before anyone understands the work: a guaranteed launch date quoted without a discovery conversation is usually a sales line, not a plan.

6. What platform will you build on, and why?

WordPress, Shopify, Webflow, custom code - each has real tradeoffs, and the designer should be able to explain why they recommend their choice for your business, not just for their convenience. Ask what the platform choice means for you: can you find someone else to work on it later? How easy is it to update yourself? What are the recurring licence costs?

This matters more than it sounds. The platform decides whether you are building an asset you control or renting space in someone else's system. Our 2026 analysis of whether WordPress still makes sense for business websites walks through the ownership side of this decision in detail.

7. Will the site be mobile-friendly and fast?

Every designer will say yes to this, which is exactly why you should ask what they mean by it. More than half of web traffic now comes from phones, so "mobile-friendly" cannot mean a desktop site that merely shrinks. Ask whether designs are tested on real phones, whether navigation and forms work with a thumb, and how they handle page speed - image compression, lean code, good hosting.

A sharper version of this question: "What speed will my homepage load at, and how will you measure it?" A designer who talks in specifics - caching, image formats, Core Web Vitals - has a real process. One who answers only in adjectives does not. Slow sites quietly bleed customers, and no amount of good design fixes a five-second load time. Our piece on why websites get slow shows what speed problems usually cost.

8. What SEO basics are included?

A beautiful site that nobody finds is an expensive brochure. Ask what the designer includes for search engines: unique title tags and meta descriptions per page, proper heading structure, fast load times, mobile optimization, image alt text, and an XML sitemap. If local customers matter to you, ask about local SEO foundations too: your service areas mentioned clearly on the page, and schema markup that helps Google understand your business.

Watch for the two wrong answers. The first is "we will handle all the SEO" with no detail - real SEO is an ongoing process, not a launch-day checkbox, and anyone promising rankings is overselling. The second is a shrug - a designer who ignores search entirely is building a site that starts invisible. A sensible answer is honest about what the build covers and what ongoing SEO work costs separately. See how much SEO costs in Canada for the real picture.

9. Can I update the site myself after launch?

You should be able to handle everyday updates - text changes, photos, prices, new testimonials - without calling the developer every time. Ask whether the site includes a simple editing interface, and whether training or documentation is provided before handoff. If the answer is "just email us and we will do it," ask what that costs and how fast the turnaround is. Routine edits that require a service ticket and a week of waiting get postponed, and postponed updates become an outdated site.

This question connects directly to ownership. A site you cannot edit is not really yours, even if you paid for it. It is also the practical test of the platform choice from question 6 - some platforms make self-editing easy, others make it a weekly frustration.

10. What happens after launch?

Launch day is the beginning, not the end. Ask what support is included after the site goes live: how long is the warranty period for bugs, what counts as a bug versus new work, what response time you can expect, and what ongoing maintenance is available and at what price. Software updates, security patches, backups, and monitoring need to happen continuously whether or not anything visible changes.

This is the layer where neglect gets expensive. A hacked site or a lapsed SSL certificate costs far more in emergency fixes than routine maintenance ever would. Know the plan before you need it, not during the emergency.

11. How will we measure success?

A website should exist to do a job: bring enquiries, bookings, calls, or sales. Ask the designer how the site's performance will be measured and reported. The honest version of this question is the one from the contractor-focused guide we mentioned earlier: not "will it look good," but "how is this site going to get my phone to ring?"

Look for answers in specifics, not adjectives. Which searches will the site be built to show up for? Where does a quote request go, and is a copy kept besides email? How will you know which page brought in which lead? Analytics and conversion tracking should be part of the build, not an afterthought. A designer who answers in specifics - real search terms, a page list, a live site you can search for yourself - is building a sales asset. One who answers in adjectives is building a brochure.

12. Will you put all of this in a written contract?

Every answer above should end up in writing: scope, deliverables, price, timeline, milestones, revision rounds, ownership, payment terms, support terms, and what happens if either side wants to end the project. A professional designer will insist on a contract; an amateur will treat it as friction. The contract protects both sides, and it is also the final test of everything you have been told - anything a designer will not put in writing was never really promised.

Red flags: when to walk away

If you ask the 12 questions above, the bad candidates usually eliminate themselves. Watch for these patterns:

• Cannot show live work or references. Screenshots only, no live sites, no past client willing to vouch for them.
• Evasive about ownership. Vague answers on who owns the domain and the site are the clearest warning sign in this industry.
• No written scope. A quote with no deliverables list, no revision policy, and no timeline is a disagreement waiting to happen.
• Guarantees first-page Google rankings. Nobody can promise rankings. This claim alone disqualifies a vendor.
• A price that is far below every other quote. A suspiciously cheap quote with no detail usually means hidden costs, outsourced quality, or a site you cannot edit, own, or rank with.
• Ignores mobile, speed, or security entirely. If they do not mention them when asked, they are not thinking about them.
• Confusing jargon instead of clear answers. A good designer explains things so a non-technical owner understands. Fog is not expertise.
• Rushes you to sign. Pressure tactics - limited-time discounts, "I can only hold this slot until Friday" - are a sales technique, not a scheduling reality.

The questions a good designer asks you

Here is a useful flip side: the best designers interview you, too. Before quoting, a serious designer will ask about your business goals, your customers, what action you want visitors to take, your branding, your competitors, and what content you can provide. They may ask what you disliked about your current site, what success looks like to you, and who makes decisions on your end. This is a good sign, not an inconvenience - it means the quote will be based on your project, not a template price. If you want to arrive prepared, knowing your goals, your audience, and your must-have features before the first call makes the whole process faster and the quotes more accurate.

FAQ

How much does it cost to hire a web designer in Canada?

It varies widely: a simple freelancer-built small business site often lands in the low thousands of CAD, while agency builds with custom design run higher, and ecommerce or custom functionality adds more. The honest answer depends on scope, which is exactly why question 3 exists. For realistic 2026 ranges broken down by project type, see how much a website costs in Canada.

Should I hire a freelancer or an agency?

Neither is automatically better. A good freelancer is often faster and cheaper for straightforward small business sites; an agency brings more capacity for larger projects, copywriting, and ongoing marketing. Judge by the same 12 questions either way: specific answers, live proof, and a written scope matter far more than team size. A solo freelancer with a clear process beats a disorganized agency, and vice versa.

What if I already signed with a designer and things are going badly?

First, reread your contract - that is why question 12 exists. If there is no contract, put everything in writing from this point forward: what is owed, by when, and what "done" looks like. Document missed deadlines and scope changes in email. If ownership of the domain or site is in dispute, that is the issue to resolve first, because everything else depends on it. For a site that has stalled so long it no longer reflects your business, our guide on signs your business needs a new website can help you decide whether to rescue the project or start fresh.

How many quotes should I get?

Two or three is usually enough, and the value is in the comparison, not the volume. Ask every candidate the same questions - ideally the 12 in this article - and compare the answers, not just the prices. The right hire is usually the one whose answers you could verify: real search terms, a page list, live sites you can check yourself. The cheapest quote is rarely the best deal once ownership, maintenance, and editing limitations are priced in.

How Webloped works

We are a web design and AI automation company based in Cambridge, Ontario. We answer every one of the 12 questions above the same way before any project starts: you own your domain and your website outright, you get a written scope with a fixed price in CAD, you can update the site yourself after handoff (we train you), and every site ships with mobile-first design, speed optimization, and SEO foundations included. If you are collecting quotes and want to see what specific answers sound like, send us a message or email us directly - we will give you a straight answer with a fixed quote in CAD before any work starts. See our services or check how pricing works first if you prefer.