Website proposals can be hard to compare. One agency includes strategy and content support; another quotes for design and development only. And a lower price can look tempting, until you discover what it leaves out.
The figures in this guide are illustrative Canadian-dollar budget bands, not quotes or prices from Arch Impact Studio. They show how scope, timelines and likely outcomes can change as a project budget grows. Your actual cost depends on what your organization needs, what it can provide, and how much complexity the site must handle.
TL;DR: What do the budget bands generally cover?
- Around $5,000: A tightly scoped refresh or small, template-led build. Best when your content and direction are ready.
- Around $15,000: A more considered redesign, often with planning, custom styling and reusable page layouts.
- Around $30,000: More room for discovery, content and migration work, custom design, integrations and a fuller handoff.
- At every level: Ask what’s included, what’s excluded, what your team must supply, and how success will be assessed.
A website budget is really a scope decision. The right amount is the one that addresses your organization’s needs without paying for complexity you don’t need, or ignoring work that will make the project succeed.
What makes a nonprofit website project cost more?
The number of pages is only part of the picture. Costs often shift with the amount of planning, design, content and technical work involved.
Common factors include:
- Content readiness: Are your existing pages accurate and ready to use, or do they need auditing, rewriting, translation or migration?
- Site structure: Is this a small set of pages, or a large archive with complex navigation and multiple audiences?
- Design needs: Will a prepared theme work, or does your organization need a custom visual system?
- Integrations: Does the site need to connect to your CRM, email platform, event system or other tools?
- Review and approvals: How many people need to provide input or sign off?
- Training and support: Does your team need help learning the CMS, launching the site or maintaining it afterward?
Public project briefs show just how much scope can vary. For example, an Ottawa Riverkeeper website RFP listed a budget of $8,000–$15,000, while HUB Cycling’s website RFP set a $75,000 ceiling that included fees, expenses and contingency. These are examples of different projects, not a universal pricing formula.
What does around $5,000 typically buy?
At this level, the project usually needs to stay small, focused and well prepared. A template-led build or limited refresh may be realistic. A from-scratch, custom strategy and redesign with extensive content support is less likely.
Scope you might see
- A modest number of pages using a theme or existing design system
- Basic setup of a content management system (CMS)
- Responsive layouts for common devices
- Light styling and configuration
- Limited content migration, often with content supplied by your team
- A basic handoff or walkthrough
What gets better?
You can get a cleaner, more current web presence without a large undertaking. A CMS setup may also make routine updates easier for staff.
What may not fit?
Extensive discovery, custom branding, new copy across many pages, complex integrations, or migration from a large and messy site can push beyond this band. Timelines may be relatively short (perhaps a few weeks once content and approvals are ready) but waiting on internal review can extend them.
Best fit: A small organization with a clear plan, limited page count and staff who can prepare content.
Watch for: A quote that sounds comprehensive but doesn’t specify the number of layouts, migration work, training, or what happens if the supplied content needs substantial editing.
What does around $15,000 typically buy?
This band may allow room for a more considered redesign. The work can move beyond “make the pages look better” toward organizing the site around the people who use it and the actions your organization wants to support.
Scope you might see
- A discovery or planning phase
- A review of key audiences, existing content and site structure
- Custom styling within a defined project scope
- Several reusable page layouts
- CMS configuration and a clearer editing workflow
- Migration of agreed content, with limits defined upfront
- Basic search-engine optimization setup, quality assurance and staff training
A project like this may take roughly six to twelve weeks, depending on how quickly your team can provide content and feedback. That’s a planning estimate, not a deadline promise.
What gets better?
Your site can become more coherent and easier for staff to manage. A more deliberate structure helps visitors understand what your organization does and where to go next, whether that means exploring a program, applying, volunteering or becoming a customer.
Best fit: An organization with an active program or community, a site that no longer reflects its work, and enough internal capacity to make decisions and provide content.
Watch for: “Custom design” without clarity on how many unique layouts are included. Ask whether the project covers content planning, page migration and redirect handling, or only visual design and development.
What does around $30,000 typically buy?
At this level, there may be more room for a complete project: not just a visual refresh, but the planning, content and systems that help the site work as an ongoing organizational tool.
Scope you might see
- More substantial discovery and stakeholder input
- Information architecture: a plan for organizing and labeling site content
- Custom design across more page types
- More extensive content editing or migration
- Integration planning for relevant third-party tools
- A structured CMS for programs, stories, events or resources
- More in-depth testing, staff training and launch support
The timeline could be two to five months or longer, especially if there is a large archive, multiple reviewers, integrations or content that needs significant revision. A higher budget doesn’t automatically make a project faster; it may fund more thoughtful and complex work.
What gets better?
Your team can get a more adaptable site that supports more of its day-to-day needs, with stronger planning and a more complete handoff. The goal isn’t complexity for its own sake. It’s a website that can evolve as your programs and priorities change.
For a sense of what a conversion-focused rebuild can involve, see our Engrenage project. It’s an example of a website project and its reported outcomes, not a nonprofit result or a promise of what another project will achieve.
Best fit: An organization with broader requirements, a substantial amount of content, or internal needs that a simple refresh won’t address.
Watch for: A bigger proposal that lists impressive features without connecting them to your actual audiences, workflows or priorities.
How can you compare proposals fairly?
Before you take a recommendation to the board, ask each agency to break down the scope in plain language.
- What specific deliverables are included? Ask about planning, page layouts, content work, migration, redirects, testing, training and launch.
- What will our staff need to provide? Clarify content, images, decisions, access to accounts and review time.
- What is not included? Confirm whether hosting, platform fees, software licences, translation, photography and ongoing support are separate.
- How will the site be tested? Ask what devices, browsers, forms and integrations are covered, and what accessibility expectations are included.
- Who owns the site and accounts? Confirm who controls the domain, hosting, CMS, analytics and design files after launch.
- What happens if the scope changes? Ask how added work is approved and priced.
- How will we know the project is complete? Define acceptance criteria and what success means for your organization.
If the project uses Webflow, give staff a sense of the editing workflow with our Webflow training guide. The platform is only one piece of the decision; your team should understand how it will manage the site after launch.
What should you tell the board?
Frame the decision around the work the site needs to do, not just the design it will receive.
Summarize:
- The problem the current site creates for staff or visitors
- The audiences and organizational goals the project supports
- The project scope, timeline and internal staff commitment
- Ongoing platform, hosting and maintenance costs
- What the team will measure after launch
The takeaway? A well-scoped $15,000 project may serve your needs better than an underfunded $30,000 one, or a $5,000 build that leaves essential work undone. For Canadian nonprofits considering non-profit web design, a clear scope is the best way to make the budget accountable.
Organizations in Montreal, Toronto, Ottawa and Vancouver may have different local options and project needs, but the same comparison rules apply: look at deliverables, assumptions and long-term ownership, not just the headline number.
Frequently asked questions
Are these typical agency prices in Canada?
They are illustrative budget bands, not fixed market rates or quotes. Actual proposals differ based on project scope, agency approach, content needs, timeline and technical complexity.
Does a $5,000 budget mean we have to use a template?
Not always, but keeping the project constrained is important. A template or existing design system can help control scope. Ask what can be customized and whether the result will be manageable for your staff.
Should our nonprofit request a $30,000 budget?
Only if the work supports the amount. Identify the requirements first (such as content migration, custom design, integrations or staff training) then seek a proposal that connects those tasks to your goals.
What costs might continue after launch?
Plan for possible platform or hosting fees, paid tools, maintenance, security updates, content work and future improvements. Ask the agency to distinguish one-time project costs from ongoing expenses.
How do we get a realistic estimate for our organization?
Start with your current site, goals, content and must-have functions. Then ask for a scoped conversation, not a number based on page count alone. Talk with Arch Impact Studio about what your website needs to support and what a practical next step could look like.
