How to evaluate a web design proposal — Canadian buyer's evaluation scorecard
Buyer's guide

How to Evaluate a Web Design Proposal (2026)

A Canadian buyer's framework for reading web design proposals — line items that matter, hidden cost drivers, and the post-launch SEO risk most agencies omit.

10 min read
·
1,850 words
·
Updated April 30, 2026
·By Martin Vassilev

The decision in one paragraph

A web design proposal is two contracts in one — a creative deliverable and a technical foundation. Most proposals price the creative cleanly and hide the technical foundation in vague language. The five places to look closely: page count, scope of CMS work, content responsibility, redirect mapping, and post-launch performance budget. A redesign that ignores SEO continuity routinely costs 30–50% of organic traffic in the first 90 days post-launch — a cost no proposal lists.

Why a web design proposal is really two contracts

Every web design proposal mixes two distinct deliverables: a creative product (visual design, brand expression, page layouts) and a technical foundation (CMS architecture, performance, schema, accessibility, indexation). The creative product is what the proposal sells. The technical foundation is what determines whether the launch helps or harms the business.

Canadian web design agencies vary wildly in how seriously they treat the second contract. A C$45,000 proposal from a creative-led shop and a C$45,000 proposal from a SEO-aware shop will produce websites that look comparable on launch day — and behave very differently 90 days later.

Reading proposals well means making the second contract explicit. If it's not in the proposal, it's not in the budget, and it's likely not in the work.

The 8 line items that determine real cost

The honest unit-economic drivers of a web design budget. If a proposal doesn't quantify these, ask for them in writing before signing.

  • Total page count (templated + bespoke)
    Most proposals quote a page count without distinguishing between bespoke designs and template variants. A 25-page proposal with 6 unique designs is materially cheaper to build than a 25-page proposal with 25 unique designs.
  • CMS scope and editor experience
    WordPress with ACF, Webflow CMS, Shopify Online Store 2.0 sections, headless Sanity/Contentful — each has very different cost profiles and very different post-launch editor friction.
  • Content responsibility split
    Who writes the copy? Most agencies quote 'design only', and content drift becomes the single biggest cause of project delay. A clean proposal explicitly assigns each page's copy responsibility.
  • Redirect mapping for migrations
    If you're replacing an existing site, every old URL needs a target. A clean redirect map costs C$1,500–C$5,000 to produce well. Most proposals omit it entirely.
  • Performance and Core Web Vitals targets
    Targets like 'LCP < 2.5s on 4G mobile, CLS < 0.1' should be in writing, with the agency liable to deliver them. Without targets, performance becomes a post-launch fire-fight.
  • Schema and structured data scope
    Organisation, LocalBusiness, FAQPage, BreadcrumbList, Article, Product — what's in scope and what's expected to be added later? Without scope, schema gets implemented as 'whatever the theme provided'.
  • Accessibility (WCAG / AODA)
    AODA in Ontario and equivalent obligations elsewhere. Quote a specific level (WCAG 2.1 AA) with a deliverable accessibility audit, or expect retrofit work.
  • Analytics, GTM, conversion-tracking setup
    Often quoted as 'GA4 install' but rarely scoped to events, conversions, or attribution. A serious proposal includes the event taxonomy spec.

Hidden cost drivers most proposals omit

  • Stock or commissioned photography
    Premium stock at C$200–C$1,500 per image; commissioned brand photography at C$3,500–C$15,000 for a meaningful library. Almost never included.
  • Third-party tool subscriptions
    Form builders, scheduling widgets, review aggregators, chat tools — together often C$200–C$800/month. Quoted as 'integration', billed forever.
  • Post-launch revisions outside scope
    Most proposals include 1–2 rounds of revisions per page. Real projects need 3–5. Out-of-scope hourly rates of C$150–C$250 add up fast.
  • Content migration
    Moving 100 blog posts isn't a 'migration', it's content production. Budget C$50–C$150 per post for clean migration with image re-encoding and link updates.
  • Cookie/consent infrastructure
    PIPEDA in Canada, plus Quebec Bill 25, plus cross-border GDPR/CCPA exposure. A compliant cookie banner with a documented data flow is C$500–C$3,500 of work, almost never quoted.

The SEO continuity risk no proposal lists

The single largest hidden cost in a web design project is the post-launch traffic loss that comes from migrating without preserving SEO equity. We've measured 30–50% organic traffic drops in the first 90 days post-launch on Canadian websites where the redesign happened without a continuity plan.

The mechanics are predictable. URLs change without redirects. Page-level schema gets stripped or downgraded. Title tags and meta descriptions get rewritten by designers, not strategists. Core Web Vitals regress under heavier visual frameworks. Internal-link structure resets to the new IA without porting the equity from the old.

A proposal that includes the words 'SEO migration plan' as a deliverable, with a named owner and a sign-off step, has materially less risk than one that mentions 'SEO best practices' in the methodology section. The first is contractual; the second is marketing language.

Every redesign is a controlled experiment in losing organic traffic. The proposals that take this seriously are the ones that mention it.

— Martin Vassilev, founder, Toronto SEO

A scorecard for comparing proposals

Compare proposals on these dimensions, not on topline price. The cheapest proposal often costs the most over a 3-year horizon.

DimensionStrong proposal looks likeWeak proposal looks like
Page count clarityBespoke vs templated breakdown by name'~25 pages'
Content ownershipPer-page copy owner assigned'Client provides content'
Redirect planLine item with C$ valueNot mentioned
Performance targetsSpecific metrics (LCP, CLS, INP)'Fast and modern'
Schema scopeNamed types per templateNot mentioned
AccessibilityWCAG 2.1 AA deliverable'Accessible design'
Post-launch support30–90 day window with hours quoted'Hourly rates available'
Total project timelineWeek-by-week with go-live date'Approximately 12–16 weeks'

Frequently Asked Questions

The questions Canadian operators ask before signing a contract.

Talk to an operator

Want a second opinion before you sign?

Book a 15-minute call. We'll read the proposal, audit, or contract you're considering and tell you what we'd push back on.