How much does a website cost in Canada? What actually drives the price

Short answer: a website’s price depends less on how it looks than on what it has to do. The main drivers are the number of unique pages, custom features, integrations with other systems, who creates the content, SEO and the platform. The best way to get a reliable number is a written quote with a clear scope and milestone payments.

Why two “similar” websites cost very different amounts

A five-page site for a contractor and a banking website can both look clean and modern. One can be ready in a single day; the other has more than 100 pages, calculators and security quizzes and involves coordinating content with departments across a bank. The design is not what separates them. The scope is.

Think of it like renovating: two kitchens can look similar in the photos, but moving plumbing, adding electrical circuits and getting permits change the job completely. On a website, the “plumbing” is features, integrations and content.

The eight factors that drive the price

1. Number of unique pages and templates

Ten pages that share one layout cost less than ten pages that each need their own design. Service pages, case studies and blog posts that follow a template scale well. When you count pages, count templates (distinct layouts) separately from pages (instances of a layout). A site with 50 pages and 5 templates can cost less than a site with 15 pages and 12 templates.

2. Custom features

Contact forms and galleries are standard. Calculators, quizzes, user accounts, dashboards, booking with payments or matching logic are software, and each one adds design, development and testing. Each feature also has “edge cases”: what happens when a payment fails, when a user forgets their password, when two bookings collide. Handling those properly is where much of the work sits.

3. Integrations

Connecting your site to a CRM, an ERP, payment processing, Eventbrite, Instagram or your own database requires development and testing against each system. Integrations also need someone to watch them after launch, because the other system can change.

4. Content

Who writes the text and provides the photos? Content is often the biggest hidden delay. If the agency writes, translates or photographs, the scope grows. On large sites, coordinating content between departments is its own workstream.

5. Languages

Each additional language multiplies content, testing and SEO work. It is not only translation: menus, forms, emails and search engine tags all need to work in each language. Our guide to multilingual websites explains what is involved.

6. SEO and performance

A basic setup covers titles, descriptions and a sitemap. A site built to compete, with one page per service, structured data, speed optimization and a content plan, takes more work and returns more. If you want to be found in AI assistants as well as Google, see how to get recommended by ChatGPT.

7. Platform

A website builder such as Wix is faster to launch and has a monthly subscription. A custom platform costs more to build, but you own the code and can make it do anything. Read our comparison of Wix and custom websites.

8. Who does the work and how

A freelancer, a local agency and an offshore team price very differently. What you are really comparing is accountability: who answers when something breaks, in your time zone, under which contract.

Costs people forget to include

These are the items that turn a reasonable quote into an unpleasant surprise:

• Accessibility. In Ontario, businesses and non-profits with 50 or more employees must make public websites meet WCAG 2.0 Level AA under the AODA. Smaller organizations are encouraged to do the same. See our AODA compliance guide.
• Content migration. Moving pages, projects, products or blog posts from an old site takes time, especially with images.
• Redirects. Mapping old URLs to new ones protects your Google rankings when a site is rebuilt.
• Stock photos, fonts and licences. Some are free; many are not.
• Privacy and legal pages. A privacy policy, cookie notice and terms should match what your site actually collects.
• Training. Someone on your team needs to learn how to update the site.
• Revisions beyond the agreed rounds. Ask how many rounds of design changes are included.

Three example projects, and why they differ

We do not publish prices, but we can show how scope changes the work. These are illustrative profiles, not quotes.

	Local service business	Growing company	Custom platform
Example	A contractor or clinic	A firm with several services and languages	A marketplace or portal
Pages	Home, services, projects, contact	Dozens of pages on templates	Public pages plus logged-in areas
Features	Forms, gallery	Booking, payments, blog	Accounts, matching, admin portal, emails
Integrations	None or one	CRM, payment provider	Several systems and a database
Typical platform	Website builder or simple custom site	Custom site with a CMS	Custom software
Main risk	Launching with thin content	Content coordination	Unclear requirements

Our own work spans all three. Montemayor is the first column: a contractor site with 21 project pages and six service pages, live in a day. Belize Bank is a very large version of the second, with more than 100 pages and interactive tools. Tulindero is the third: a real estate platform with a property map, owner accounts, buyer matching and an admin portal.

Fixed price or hourly: how quotes are structured

Fixed price. You agree on a scope and a total. It works best when requirements are clear. The risk is that anything outside the written scope becomes a change request, so the scope document matters.

Time and materials (hourly). You pay for the time spent. It suits projects that will evolve, such as a new software product. The risk is budget drift, so ask for regular reports and a cap or estimate per phase.

Phased or hybrid. A paid discovery phase defines the project, then the build is quoted as a fixed price. This is often the safest route for custom software, because nobody is guessing.

What a good scope document includes

The scope is the most important page of any proposal. It is what you are actually buying. A useful one covers:

• Goals. What the site must achieve, in business terms: more quote requests, online bookings, fewer phone calls about the same questions.
• Sitemap. Every page or page type, grouped by template.
• Features. Each feature described in a sentence or two, including who uses it (visitors, your team, admins).
• Integrations. Every external system, and whether you already have accounts and access.
• Content responsibilities. Who writes, translates, photographs and uploads, and by when.
• Standards. Accessibility level, supported browsers and devices, and performance expectations.
• Exclusions. What is explicitly not included, so nothing is assumed.
• Timeline and milestones. What is delivered at each step and what you need to approve.
• After launch. Warranty on fixes, support and maintenance options.

If a proposal has a price but no scope, ask for one before you compare it with anything else.

Timeline and cost move together

Budget and schedule are two views of the same thing: the amount of work. A few practical consequences:

• Rushed deadlines cost more. Compressing the schedule means more people or longer days, and less time for testing.
• Delays on your side cost too. When content or approvals arrive late, the team loses momentum and the project stretches.
• Change requests add up. A new feature halfway through affects design, development and testing that are already done.

The fastest projects are the ones where content is ready, decisions are made by one person and the scope is agreed before work starts. That is how a contractor site can go live the same day: the projects and photos already existed, and the goal was clear.

A few terms you will see in quotes

• Discovery: the first phase, where requirements are gathered and the scope is defined.
• Wireframe: a simple layout of a page, before visual design.
• CMS (content management system): the tool your team uses to edit the site.
• Staging site: a private copy of the site used for review before launch.
• Change request: a formal request for work outside the agreed scope, usually quoted separately.
• SLA (service level agreement): the response times promised for support after launch.

Ongoing costs to budget for

• Domain renewal
• Hosting or platform subscription
• Paid apps or plugins
• Maintenance: updates, security, backups and small changes
• Content and SEO: new pages, blog posts and improvements that keep the site competitive

A website is closer to a vehicle than a painting: it needs regular care to keep performing. Security matters here too; our cybersecurity basics for small businesses covers what every site owner should have in place.

How to get a quote you can trust

1. Describe the goal, not only the pages. “We want more quote requests from homeowners in the GTA” leads to a better proposal than “we need five pages”.
2. Ask for a written scope listing pages, templates, features, integrations and what is excluded.
3. Pay by milestones, never everything upfront.
4. Ask who does the work and who your point of contact is.
5. Ask about the first year after launch: support, fixes and ongoing costs.
6. Confirm ownership. You should own your domain, your content, and, on a custom build, your code and hosting accounts.

How to compare two quotes side by side

Put the quotes in a table with these rows before you compare totals:

• Pages and templates included
• Features and integrations included
• Who provides content and photos
• SEO work included (basic setup or a plan to compete)
• Accessibility standard the site will meet
• Number of design revision rounds
• Launch support and warranty period for fixes
• Ongoing costs after launch
• Who owns the code, domain and accounts

A lower quote that leaves out half these rows is not cheaper. It is a smaller project.

Common mistakes when budgeting for a website

• Choosing on price alone. The cheapest quote often excludes content, SEO or support, which you pay for later.
• Starting without content. Waiting on text and photos is the most common reason projects run late.
• Building everything at once. Launch with what brings business now, then add features in phases.
• Forgetting the year after launch. Maintenance, hosting and small changes are part of the real cost.
• Not writing down the scope. If it is not in the proposal, assume it is not included.

How we price projects

Every project we take starts with a free discovery call. You then receive a written proposal in CAD with the scope, timeline and milestone payments, before any work starts. No surprises on the invoice. See how our process works, explore our web and mobile development and custom software services, or tell us about your project to get a quote.

Frequently asked questions

Why do website quotes vary so much?

Because they often describe different projects. Quotes differ in the number of pages, custom features, integrations, content creation, SEO work, platform and who does the work. Compare quotes on scope, not only on price.

Should I pay for a website all at once?

It is safer to pay by milestones, with each payment tied to a delivered piece of work, for example a split between the start of the project and launch.

What ongoing costs does a website have?

Your domain, hosting or platform subscription, any paid plugins or apps, and maintenance for updates, security and changes. Ask for these to be listed in the quote.

Is a fixed-price quote better than paying by the hour?

A fixed price works well when the scope is clear and written down, because you know the total before you start. Hourly or time-and-materials billing suits projects where the requirements will change as you learn, but it needs regular reporting so the budget does not drift.

How can I lower the cost of a website without hurting quality?

Prepare your own text and photos, reuse page templates, launch with the features you need now and plan the rest as a second phase. Cutting testing, SEO or accessibility usually costs more later.

Does accessibility add to the cost of a website in Ontario?

Building accessibility in from the start adds little compared with fixing it later. Businesses and non-profits in Ontario with 50 or more employees must make public websites meet WCAG 2.0 Level AA under the AODA, so it belongs in the scope from day one.