A useful website budget starts with what someone needs to do on the site. A business introducing its services has a different scope from a membership platform taking payments and managing bookings.
The ranges below are planning examples used in this guide, not a survey of Canadian agencies or a fixed westcode price list. A project quote needs an agreed scope. All figures are in Canadian dollars; confirm taxes and third-party fees separately.
A practical starting budget
| Type of build | Planning range | What shapes the scope |
|---|---|---|
| Focused landing page or small launch site | $3,000–$5,000 | One main offer, a small content set and a clear inquiry path |
| Business website | $5,000–$15,000 | Distinct layouts, service content, content editing and integrations |
| E-commerce website | $8,000–$15,000+ | Product data, shipping rules, payments, migration and operations |
| Custom web application | $15,000–$50,000+ | Accounts, permissions, workflows, integrations and testing |
A higher page count does not always mean a larger build. Twenty pages using one well-designed template may take less work than five pages with completely different interactions. Ask which parts are reusable and which need individual design and development.
What the quote should explain
A quote becomes useful when you can see what is included. Compare these items across proposals:
- Content: who writes the pages, supplies photographs and moves existing material?
- Design: which layouts are custom, how is feedback handled, and what does mobile include?
- Functionality: are booking, payments, search and account management actually in scope?
- Editing: what can your team change after launch, and what needs a developer?
- Launch: who handles redirects, domain setup, analytics and quality checks?
- Handover: which accounts, source files and instructions do you receive?
For a redesign, list the URLs and content that already bring useful visits. The project needs to account for that history, even if the new design looks very different.
Three examples of different scope
A local service business: the important work may be explaining services and coverage, showing evidence, and making it easy to call or send a useful inquiry. Booking software may already exist and only need connecting.
An online shop: the visible pages are part of the work. Product variations, inventory, shipping, tax configuration, refunds and the team's order-management process can determine the real complexity.
A membership product: our Founder Feast project connects applications, payments and event operations. That operational work belongs in the budget alongside the public website. A homepage screenshot cannot tell you the full scope.
These examples describe different jobs. They are not quotes for those named projects.
Budget beyond launch
Separate the initial build from recurring costs. Ask for an itemized list of hosting, domain renewal, paid software, payment-processing charges, maintenance and content work. Establish who owns each account and how you can change providers later.
Not every project needs a monthly development agreement. Some need occasional changes; others need regular releases, support and monitoring. Define the actual responsibility before choosing the arrangement.
When a website builder is a sensible choice
A website builder can work well for a straightforward offer, a small budget and a team comfortable managing content. Custom work becomes more useful when the design, integrations or customer journey need behavior that is awkward to achieve within the chosen platform.
Neither approach automatically produces good SEO or a useful website. Compare the content, accessibility, speed, editing needs and ongoing ownership. Our custom website versus builder guide gives you more questions to consider.
Bring these five things to the first conversation
- What you do and who the website needs to help.
- The main action you want a visitor to take.
- Your current site and the parts that work or frustrate you.
- Any systems it must connect to.
- A budget range and a target date, including what drives that date.
You do not need to arrive with a complete specification. These details are enough to start a useful scope discussion and decide what deserves a place in the first release.
