Website costs in Canada: scope, pricing and ongoing care

A price becomes meaningful when the work is defined

Two website proposals can describe a “custom website” and contain very different projects. One includes positioning, writing, original photography, migration, and editorial training. Another assumes all content is supplied and covers design and development only. Comparing their totals without reconciling those assumptions produces a false economy.

Begin with a common scope. List the page types, content quantities, required functions, integrations, and languages. Identify what already exists and what needs to be created. A page type is a reusable structure; a page is a particular piece of content. Ten pages built from one structure create different work from ten unique layouts, even when the sitemap looks equally long.

Ask each team to state what its fee includes, what it excludes, and what could change it. Useful answers explain the work rather than defending a number. The aim is not to make every proposal identical. It is to understand whether a higher fee buys more expertise, more scope, more care, or simply a different set of assumptions.

Build five small cost ledgers

Organize the budget into five categories. This makes gaps visible without pretending that every future cost can be known precisely.

• Definition: research, positioning, content planning, information architecture, and technical investigation.
• Creation: design, writing, photography, development, integrations, and content entry.
• Transition: migration, testing, redirects, training, account setup, and launch coordination.
• Operation: hosting, software subscriptions, monitoring, maintenance, and support.
• Evolution: new campaigns, new content structures, experiments, and changes to the business.

For each entry, record an owner, an estimate, its frequency, and the assumption behind it. Some costs are fixed commitments; others vary with usage or the number of changes requested. Keep those differences visible. A low monthly starting fee does not tell you what happens when traffic, editors, or content volume increases.

Choose a planning period that matches your business decisions, such as the next two operating years. Then compare the total commitment over that same period. Do not add speculative features merely to make the forecast look comprehensive. Label unknowns and ask which ones can be resolved before a contract is signed.

Count the work your team must contribute

The website also consumes internal attention. Somebody must find source material, confirm service details, obtain image permissions, review drafts, and settle disagreements. Those hours may not appear on an agency invoice, but they affect both the cost and the schedule.

Make a responsibility sheet for every important deliverable. Specify who supplies it, who reviews it, who approves it, and when it is needed. If the same founder owns all four roles, acknowledge the capacity constraint. An outside copywriter can reduce drafting work, but cannot independently determine facts that only the business knows.

Hypothetical example: a professional services firm plans twelve case studies. Its estimate assumes the marketing lead will supply finished copy. In practice, that person must interview project leads and obtain client approval. The original proposal has not necessarily become inaccurate; its content assumption was incomplete. Budgeting for interviews, editing, and coordination at the start gives the firm a more realistic choice between publishing fewer strong stories and delaying the entire launch.

Internal capacity should influence scope. A smaller site that the team can keep accurate may serve the business better than an ambitious content programme with no owner.

Separate dependable operation from improvement

Maintenance and improvement are different kinds of work. Maintenance keeps the existing service functioning: updates, backups, monitoring, dependency review, and responding to faults. Improvement changes what the service does or how well it serves people. A support arrangement should make the boundary understandable.

MDN’s website security guidance includes keeping software current, backing up data before updates, and testing compatibility. The precise responsibilities depend on the architecture and provider, so ask who performs them for your site. A managed platform may take care of some infrastructure tasks while leaving content, integrations, and account practices with your team.

Accessibility also needs an operating owner. W3C’s planning framework includes sustaining accessibility through monitoring and ongoing review. Publishing new material can introduce issues even when the initial templates were carefully built.

Request plain answers about response times, included work, reporting, and what happens outside the agreement. Then reserve a separate improvement allowance based on likely business needs. Otherwise, every useful change competes with the budget required to keep the site dependable.

Compare three credible scope scenarios

When investment is constrained, ask for different scopes with a clear explanation of the tradeoffs. Avoid applying an arbitrary discount to the same promised work. Less budget should usually mean fewer deliverables, less complexity, a narrower first release, or a different service arrangement.

Build three scenarios: the essential launch, the intended experience, and a later extension. The essential launch must still be coherent and usable. It might include the core offer, representative proof, and a reliable enquiry path while postponing an extensive resource library. The intended experience adds work with a clear present purpose. The extension captures ideas that depend on future evidence or capacity.

For each scenario, write what becomes possible, what remains manual, and what will cost more if added later. Some deferrals are inexpensive, such as publishing another article within an existing structure. Others affect foundations, such as adding a second language to a content model designed without it. Ask the team to explain those differences.

This conversation creates a real budget choice. You can reduce breadth while protecting the quality of the main journey, instead of spreading the available investment across too many unfinished ambitions.

Our starting scopes, in Canadian dollars

Our own starting prices provide a concrete example of how scope affects the quote. They are Nocturnum’s offers, not a survey of Canadian agency pricing:

• Landing Page — from CAD $999. One custom-designed, responsive page with a clear offer and call to action, an inquiry form, search essentials, two refinement rounds and launch handover.
• Premium Website — from CAD $4,999. Custom design for up to five core pages, site structure and content direction, custom development with a CMS, refined interactions, lead forms, search and performance foundations, two refinement rounds and CMS handover.
• Full Service — consultation only. A tailored engagement across brand strategy, identity, website and related creative or technical needs, with the scope defined before work begins.

Website packages use your existing brand and supplied content. Extra pages, copywriting and functionality are scoped separately; taxes, hosting, domains and third-party fees are additional. Read the complete service inclusions and compare them with your content and operating needs. A starting price becomes a usable budget only when the proposal makes those assumptions explicit.

If two proposals differ, reconcile the page inventory, content responsibilities, integrations and handover first. Then discuss the unresolved scope, rather than assuming the lower number describes the same work.

Use an investment review, not a price ranking

Bring proposals into a shared comparison document and review them against the same questions. Leave space for uncertainty instead of forcing every judgment into a numerical score.

• What must our team supply, and do we have the capacity?
• Which page types, content quantities, and review rounds are included?
• What happens if a key integration proves more complex than expected?
• Which recurring costs are fixed, variable, or paid to third parties?
• Who owns accounts, source materials, and documentation?
• What does ordinary support cover, and how are improvements priced?
• Which business changes would require significant additional work?

Then write a short rationale for the preferred option. Explain why its scope is appropriate, which assumptions need confirmation, and which responsibilities the business accepts. Keep this rationale with the project records so later decisions have context.

A website investment is easier to manage when the commitment is visible. The goal is a credible relationship between ambition, resources, and care. A thoughtful budget gives the team room to create something distinctive and gives the business a practical way to keep it useful.