How to scope a website budget in Canada

Define the work the website has to perform.

Write down the main customer, the service or product they are evaluating and the action the site should support. A focused enquiry site, a multilingual catalogue and a store with complex fulfilment rules are different projects even when their menus contain a similar number of items.

Then separate the first release from later additions. A feature belongs in the launch scope when it is necessary for the core journey or an agreed business requirement. Record optional ideas separately so a useful initial budget does not become an unpriced wish list.

Count content responsibilities, not just pages.

Ask who writes service copy, gathers evidence, selects images and approves the finished content. A design quote that assumes complete supplied material is not equivalent to one that includes discovery, writing, image sourcing and editorial review. Language versions and specialist approvals also require explicit scope.

Identify the types of page and the amount of original work each needs. Twenty location pages with distinct buying guidance involve different editorial work from one reusable directory. The proposal should explain how content is created, checked and maintained rather than treating every page as an interchangeable unit.

Describe integrations as complete journeys.

A contact form needs more than visible fields. The scope should cover submission handling, validation, spam controls, receipt confirmation, lead storage or routing and the team’s ability to find the request. Chat also needs approved information, clear boundaries and a working handoff when a person must respond.

For commerce, booking or business systems, document the existing accounts and the intended behaviour. Ask what is included in setup, what depends on another provider, who pays recurring fees and what happens when an integration fails. A named integration alone is not a complete specification.

Separate launch work from ongoing ownership.

List domain, hosting, platform, support, content and third-party service costs with the correct billing period and currency. Clarify which accounts the business owns and which costs are paid directly. Avoid comparing an initial build price with a package that also includes a period of ongoing service.

Define what support means in practical terms. Does it include content edits, security maintenance, technical troubleshooting or new features? Agree how changes are requested and priced. The goal is to understand the continuing commitment rather than discover it after the website is live.

Compare proposals against the same brief.

Create a simple comparison using the same categories: discovery, design, content, development, integrations, search setup, analytics, launch and handover. Mark each item as included, excluded or requiring clarification. Ask providers to explain the result they deliver, not just the tools they use.

At Surf, the brief is the starting point for that conversation. Share the current site if there is one, the priority services, the desired customer action and any fixed requirements. A grounded scope can then distinguish essential work from choices that change the budget or schedule.

Your planning checklist

• Define the primary audience, offer and customer action.
• Assign ownership of copy, imagery and approvals.
• Describe each form, chat or integration through to completion.
• Compare build costs and recurring costs in the same currency.

Common questions