A website design proposal should do more than present attractive visuals and a project price. It should explain what will be built, how the work will be managed, what the business must provide, and what happens after launch.
That level of clarity matters because website projects often involve more than design. They may include strategy, content, development, SEO foundations, integrations, analytics, testing, training, and ongoing maintenance. If those responsibilities are not discussed before work begins, a business can face delays, unexpected decisions, or a finished website that does not support its commercial goals.
This website design proposal checklist is intended for Canadian business owners and decision-makers comparing providers. It does not suggest that every proposal must include the same deliverables. Instead, it identifies the questions that help you understand what you are actually buying.
Start with the business outcome, not the page count
A proposal should connect the website project to a clear business problem. That problem might be an outdated site, poor mobile usability, unclear service information, weak enquiry quality, difficulty managing content, or the need to support a new business direction.
“A new five-page website” is a deliverable. It is not necessarily a useful objective. A stronger proposal explains how the project is expected to help the business communicate its offer, guide visitors, support enquiries, or improve the customer journey.
Before comparing proposals, clarify:
- Which audiences the website needs to serve
- Which products, services, or locations deserve priority
- What is not working on the current website
- Which actions visitors should take
- How the business will judge whether the new site is serving its purpose
The provider may not be able to promise a specific number of leads or sales. Those outcomes also depend on demand, pricing, customer service, sales follow-up, and other factors outside the website project. However, the proposal should still explain the practical role the new website is intended to play.
What the proposed scope should make clear
Scope is the section that prevents two parties from imagining different projects. A proposal should describe the main components in language that a non-technical decision-maker can understand.
Pages and templates
Look beyond the total number of pages. Ask whether the proposal includes distinct templates for service pages, locations, team profiles, case studies, blog posts, product pages, or landing pages where those formats are relevant.
A website with ten pages may still be difficult to expand if every page is treated as a one-off design. Conversely, a smaller site may be sufficient if its structure supports the business’s current needs. The important issue is whether the proposed architecture matches how customers evaluate the business.
Design and responsive behaviour
Clarify whether the provider is creating a custom visual direction, adapting an existing theme, or configuring a pre-built template. None of these approaches is automatically wrong, but they involve different levels of flexibility and design control.
The proposal should also indicate how layouts will be handled on mobile and tablet devices. Responsive design is not simply a smaller desktop screen. Navigation, forms, images, service comparisons, and calls to action may need different treatment on smaller screens.
Development and functionality
Ask which functions are included and which depend on third-party tools or separate subscriptions. Relevant examples may include contact forms, booking systems, ecommerce features, payment processing, email marketing connections, calculators, maps, member areas, or customer relationship management integrations.
If an integration is important to the business, it should not be hidden inside a vague phrase such as “advanced functionality”. Ask what will be connected, who owns the account, what information the provider needs, and how the connection will be tested.
Content responsibilities are often the largest source of uncertainty
Website proposals frequently mention “content migration” or “professional copy” without explaining what that means. Content can involve planning, interviews, writing, editing, photography, video, product information, legal review, uploading, formatting, and approval.
Clarify whether the provider will:
- Develop a messaging structure before writing
- Write new page copy or use client-supplied text
- Rewrite existing content or transfer it unchanged
- Prepare page titles, headings, metadata, and image descriptions
- Source, edit, or simply place images supplied by the business
- Format content for mobile readability
- Handle translations or multilingual page versions
Content production and content strategy are related but different. A provider may be responsible for writing approved pages without being responsible for a broader ongoing content programme. The proposal should distinguish the project’s included content work from future content that would require a separate scope.
If content is supplied by the business, confirm deadlines and formats. A website can be technically ready while launch is delayed because the copy, photography, product details, or approvals are incomplete.
Ask how SEO and measurement fit into the project
A website redesign can affect search visibility if URLs, page structure, internal links, metadata, or important content change. A proposal does not need to promise rankings, but it should explain what search-related work is included.
Depending on the project, useful questions include:
- Will important existing URLs be reviewed before changes are made?
- Will redirects be considered where page addresses change?
- Will the proposed navigation reflect how customers search for the business’s services?
- Will the site include basic technical SEO foundations?
- Will analytics or conversion tracking be configured?
- Who will verify forms, calls, bookings, or other key actions after launch?
Do not assume that a website design project automatically includes an ongoing SEO campaign. Those are separate services unless the proposal specifically combines them. If search visibility is central to the investment, compare the website scope with the broader SEO and online presence service to understand whether ongoing search work may also be relevant.
Measurement should be practical rather than decorative. A report showing visits alone may not help a business decide whether the website is supporting enquiries. Identify which actions matter commercially and how they will be tracked, while recognising that tracking may be affected by consent settings, third-party platforms, phone conversations, and incomplete customer journeys.
Review the working process and approval points
The quality of a website project depends partly on how decisions are made. A proposal should give you a reasonable picture of the stages involved, even if the exact schedule changes as the work progresses.
Look for a process that explains:
- How the provider will gather business information and user requirements
- When the structure or sitemap will be reviewed
- When design concepts will be presented
- How content and functionality will be approved
- How revisions are handled
- Who gives final approval on behalf of the business
- How testing and launch preparation will occur
Pay close attention to revision language. An unlimited revision promise may sound reassuring but can create uncertainty for both sides. A more useful proposal explains how feedback is collected, what counts as a revision, and when a change may require additional work.
The business should also nominate an internal decision-maker. If several people provide conflicting feedback without a clear approval process, even a well-managed project can lose momentum.
Ownership, access, and post-launch support
Ownership questions should be discussed before development begins, not when the relationship ends. Ask who will control the domain, hosting, website platform, plugins, analytics property, advertising integrations, stock licences, and other digital assets used for the project.
This is not only about preparing for a provider change. Clear ownership makes it easier for the business to maintain access, update information, manage security, and coordinate other specialists when necessary.
Also clarify what happens after launch. A proposal may include a limited period for fixing launch-related defects, while updates, new pages, security work, backups, and content changes may be handled separately. The exact arrangement will vary, so ask:
- Is hosting included, and who is the hosting account holder?
- Are backups, security updates, and platform updates included?
- Can the business make routine edits internally?
- Is training included?
- How are post-launch fixes distinguished from new requests?
- What support is available if a form or integration stops working?
For additional context, review what to clarify about website maintenance after launch. Maintenance is not an automatic continuation of the original design project, and it should be treated as its own responsibility or service arrangement.
How to compare two proposals fairly
The lowest quoted fee is not necessarily the least expensive option if it leaves essential work for the business to arrange later. At the same time, a longer proposal is not automatically better. Compare the proposals by what they enable you to understand.
| Area | Questions to compare |
|---|---|
| Strategy | Does the provider explain the audience, priorities, structure, and intended user actions? |
| Scope | Are pages, templates, functions, integrations, and exclusions described clearly? |
| Content | Who plans, writes, supplies, edits, approves, and uploads the content? |
| Technical work | Are hosting, platform, redirects, testing, accessibility, and tracking responsibilities addressed? |
| Process | Are decision points, feedback rounds, client responsibilities, and dependencies explained? |
| After launch | Are training, support, maintenance, ownership, and access clear? |
It is also worth asking each provider to identify exclusions. For example, photography, copywriting, paid plugins, premium software, ecommerce product entry, third-party subscription fees, or complex integrations may not be included. An exclusion is not a warning sign by itself; unclear exclusions are the problem.
If you are comparing a redesign against smaller improvements, a website redesign checklist can help you consider whether the existing site needs a complete rebuild or a more focused intervention.
When professional website design support is appropriate
External support can be useful when the business lacks the time or internal expertise to coordinate strategy, design, content, development, user experience, and launch preparation. It may also be appropriate when the website is an important sales tool but ownership is fragmented across several people or suppliers.
However, not every business needs the same engagement. A company with an experienced internal marketing or development team may only need design direction, technical assistance, copywriting, or conversion-focused improvements. A smaller business may benefit more from a coordinated project that reduces the number of separate decisions it must manage.
The right provider should be able to explain not only what it can deliver, but also what it needs from the business and what falls outside the proposed scope. That transparency is more valuable than a long list of features.
Red Leaf Media supports businesses evaluating how their website should communicate, guide visitors, and support marketing activity. You can review the website design service to understand the relevant area of support, then discuss your current website, business priorities, and project requirements directly with the team.
A clear proposal will not remove every uncertainty from a website project. It should, however, make the important uncertainties visible before you commit. If you can explain the project’s purpose, scope, responsibilities, ownership, approval process, and post-launch arrangements, you are in a much stronger position to compare providers and make a responsible investment.
