How to choose a web developer or agency in Canada: what to ask, what to avoid

What kind of help do you actually need?

Before you start talking to developers, spend some time being clear about what you are actually trying to accomplish. The market for “website help” in Canada ranges from $12/month DIY platforms to $50,000+ custom builds, and the right answer for your business depends entirely on what you need the site to do.

A local service business — a plumber, accountant, physiotherapist, or restaurant — typically needs a clean, fast, professional site that communicates what they do, where they are, and how to contact them. This is a brochure site, and a skilled freelancer or small studio can deliver it well. A platform that lets customers book appointments, place orders, or manage their own accounts is a more complex undertaking that requires a developer with genuine technical depth. An e-commerce operation with inventory management, payment processing, and customer accounts falls into a different category again.

The other dimension to consider is ongoing ownership and management. If you want to log in and update your own content regularly, you need a CMS (content management system) like WordPress, and the developer needs to train you on it. If you would rather hand the whole thing off and call someone when something needs to change, a managed arrangement makes more sense. If you are comfortable with technology and want maximum control, a static site or a minimal CMS might be the right fit. Knowing which of these describes you will help you evaluate proposals more clearly.

Questions to ask before signing anything

A developer worth hiring will answer these questions readily and specifically. Vague or evasive responses are themselves information.

Can I see your portfolio, and can I speak to past clients?

Any developer with a track record will have work to show you. Look at portfolio sites critically: do they load quickly? Do they look like they were designed with a real audience in mind, or do they look like templates with client names dropped in? Visit the sites on your phone as well as your desktop. Ask for two or three references you can contact directly — not testimonials on the developer's website, but real clients you can email or call. References rarely lie about fundamental problems like missed deadlines, disappearing acts after launch, or sites that broke within months.

Who will own the files, the domain, and the hosting after launch?

This question matters enormously and is too rarely asked upfront. In a clean engagement, you own everything: the domain is registered in your name at a registrar you control, the hosting account is in your name, and the finished website files are delivered to you at the end of the project. Some developers register your domain in their own account or maintain control of your hosting as leverage. If you want to leave, you either cannot, or leaving is painful and expensive.

Ask directly and get a clear written answer. “You will receive all the source files and credentials at project completion” is the answer you want. “We manage the hosting on your behalf” requires follow-up: what does that mean for your access, and what happens if you stop working together?

What does the timeline look like, and what do you need from me to hit it?

Website projects slip because of two things: developer workload and client delays. A good developer will give you a realistic timeline and be honest about what they need from you to maintain it — content, images, approvals at specific milestones. Be honest with yourself about your own capacity to deliver those things on schedule. A project that stalls because you could not get the developer your approved copy for three months is not the developer's fault.

Understanding contracts: ownership, IP, and lock-in

A written contract is not a sign of distrust — it is the document that makes a working relationship functional. Any developer who resists putting the terms in writing is telling you something important about how they operate.

Who owns the code?

In Canada, copyright in original creative work vests in the creator by default unless there is a written agreement to the contrary. This means that code written by a freelance developer may belong to that developer unless your contract specifically assigns the intellectual property to you. For custom-built sites, make sure your contract includes an explicit IP assignment clause stating that all work product becomes your property upon payment in full.

This matters less for sites built on platforms like WordPress using off-the-shelf themes and plugins, since the copyright situation there is governed by the relevant open-source licences. But for any custom theme, custom functionality, or bespoke application, get the IP assignment in writing.

Domain and hosting lock-in

Domain lock-in happens when your developer registers your domain name through their own account and either will not transfer it or charges a fee to do so. Avoid this by registering your domain yourself before the project starts, at a registrar like Hover, Namecheap, or Google Domains. You then grant the developer access to configure DNS settings rather than handing over ownership.

Hosting lock-in is subtler. Some developers build sites that only run properly on their proprietary hosting environment, or bundle hosting with their ongoing services in a way that makes migration prohibitively complex. Ask explicitly: “If I want to move to a different host in two years, what does that involve?” A clear answer should involve no more than migrating standard files.

What happens at the end of the relationship?

Even good working relationships end. Developers retire, change their business focus, raise their prices, or simply are not the right fit any more as your business grows. Your contract should specify exactly what you receive at the end of the engagement: a handover package including all files, databases, third-party service credentials, and documentation of how the site is structured. A developer who cannot articulate this, or who treats handover as an afterthought, is creating future leverage over you.

Pricing: what is reasonable in Canada in 2026

Canadian web development pricing varies enormously, and understanding why helps you evaluate quotes more intelligently. Location, experience, specialization, and whether you are working with a solo freelancer or a team all affect price.

For a standard brochure site — five to eight pages, no e-commerce, no custom functionality — you should expect to pay somewhere between $2,500 and $8,000 from a competent Canadian freelancer or small studio. Work in this range done properly will include custom design (not just a purchased template with your logo dropped in), proper SEO fundamentals, mobile optimization, and basic post-launch support. Quotes below $1,500 for a full custom site almost always mean a template with minimal customization, inexperienced work, or a race-to-the-bottom situation where corners will be cut.

E-commerce projects start higher — $5,000 to $15,000 is a realistic range for a proper small-business online store with product management, payment processing, and order handling — and scale up from there depending on the complexity of the catalogue and any custom requirements. Custom web applications, booking systems with complex business logic, or API integrations with third-party platforms move into a different price tier entirely and should be scoped carefully with a detailed requirements document before anyone commits to a number.

Pricing structures matter too. Fixed-price projects work well when the scope is clearly defined at the outset. Hourly rates give you flexibility for evolving or uncertain projects but require more trust and communication to manage well. Retainer arrangements — a fixed monthly fee for a set number of hours or services — suit ongoing maintenance and content relationships. None of these is inherently better; they suit different working styles and project types.

Red flags worth walking away from

No single red flag is necessarily fatal, but patterns matter. Here are the situations that should prompt serious caution or a firm “no thank you.”

A developer who cannot or will not show you previous work, or whose portfolio consists entirely of sites they claim to have built with no way to verify, is an immediate concern. Experience in web development is demonstrated, not described. If the portfolio looks like a collection of generic templates, that is what you are buying.

Suspiciously low pricing is a reliable signal. A quote of $800 for a custom five-page site with original design, SEO, and mobile optimization either means the developer does not understand what they are quoting, or it means something important is being left out. Either way, the project will not go as planned. Similarly, a verbal quote with no written breakdown of what is included leaves you with no recourse when deliverables fall short of your expectations.

Pressure to decide quickly — “I only have one project slot left this month” — is a sales tactic, not a fact. A developer who is good at their work does not need to rush you. Take the time you need to do reference checks and compare options.

Finally, if a developer responds to your detailed questions about ownership, contracts, and post-launch support with impatience or dismissiveness, that is the working relationship modelled in miniature. The sales process is usually the most attentive you will ever get. If questions about ownership and deliverables are inconvenient now, they will be actively avoided later.

Making the relationship work after launch

Most website projects are described as a build: a project with a beginning, middle, and end, after which the website exists and the relationship winds down. In practice, a website is a living asset that needs ongoing attention — content updates, software updates, occasional fixes, and periodic redesigns. The most successful client-developer relationships treat the launch as a beginning rather than a conclusion.

Be clear with yourself and your developer about what post-launch support looks like. If you want the developer to handle all updates and maintenance, ask them to quote a monthly retainer. If you want to manage things yourself and only call them for significant changes, say so — and make sure you receive proper training on your CMS before the project closes. If you want to take the site to a different developer for ongoing work, confirm you will receive a full handover package.

Communication norms matter as well. How quickly do they typically respond to emails? Do they prefer phone or written communication? What is the process for requesting a change, and how are ad hoc changes billed? Getting clear answers to these questions before the project starts prevents friction and misunderstanding later. The developer-client relationship works best when both parties know what to expect from each other — and the business owner who invests in building a good working relationship will get better work and better responsiveness than the one who treats their developer as a vending machine for deliverables.

The Canadian web development market has no shortage of capable people doing honest, quality work. Finding them requires the due diligence most buyers skip because it feels like extra effort. That extra effort, spent before you sign anything, is by far the cheapest insurance you can buy.