How to Write a Website RFP That Gets Accurate Quotes from Calgary Agencies

A vague website request usually produces vague pricing. If one Calgary agency assumes a 10-page brochure site while another prices content migration, SEO preservation, integrations, and post-launch support, their quotes aren’t really comparable. A strong website RFP Calgary businesses can use should remove those assumptions before agencies start estimating. This guide shows you what to include, what to leave open, and how to compare proposals without choosing on price alone.

Key takeaways

• An RFP should define the business problem and project boundaries, not prescribe every design decision.
• Separate required functionality from optional ideas so agencies can price the core project consistently.
• Give agencies the current sitemap, expected page count, content responsibilities, integrations, and migration requirements.
• Define what success means in measurable terms, such as qualified form submissions, online bookings, purchases, or easier content management.
• For a redesign, explicitly address redirects, analytics, existing SEO assets, and content migration.
• Ask agencies to identify assumptions and exclusions. Those details often explain large price differences better than the total quote.
• Compare proposals using the same evaluation criteria rather than treating the cheapest bid as automatically equivalent.

Why website RFPs produce inconsistent quotes

A request for proposal for web design is essentially a shared definition of the project. It tells potential agencies what exists now, what needs to change, what the finished website needs to do, and which responsibilities belong to each party.

It is different from a short website project brief. A project brief may be enough for an initial conversation. An RFP goes further because you want several agencies to respond to substantially the same requirements.

That distinction matters when you want comparable quotes.

Consider these two requests:

We need a modern new website for our Calgary company. It should look professional, rank on Google, and be easy to update.

And:

We need to replace our current 32-page WordPress site. The new site will retain six core service pages, consolidate 14 older pages into four resources, include an editable project portfolio, connect three forms to HubSpot, preserve existing indexed URLs where practical, and redirect removed URLs. Our team will provide approved copy and photography.

The first request leaves agencies to invent the scope. One may assume 10 pages. Another may assume 30. One may include copywriting, while another expects finished copy. One may budget for SEO migration work, while another simply builds the new layouts.

The second request gives each agency a much narrower estimating problem.

That is the purpose of a useful RFP. You are not trying to design the website before hiring a designer. You are defining the problem clearly enough that qualified agencies can propose their own approach to the same project.

For Calgary businesses, the requirements may also include local considerations that would be irrelevant to a generic national website. A contractor serving Calgary and nearby communities may depend heavily on service-area pages and local enquiries. A downtown professional services firm may care more about credibility, recruitment, thought leadership, and lead qualification. An Alberta company selling nationally may have little reason to build the project around local search at all.

The location should influence requirements only where it affects the business.

What a website RFP Calgary agencies can price accurately

The strongest web design RFPs give agencies enough detail to estimate effort while leaving room for professional recommendations.

You do not need to know the final technology stack, page design, or navigation before requesting proposals. You do need to explain the business, users, content, functionality, constraints, and expected responsibilities.

Start with the business problem, not a design wish list

Give agencies a short explanation of why the project exists.

Useful background might include:

• The current website no longer reflects the services the company offers.
• Sales receives too many enquiries from prospects who misunderstand pricing or scope.
• Mobile visitors struggle to complete an important form.
• Marketing cannot create new landing pages without developer assistance.
• The site has grown without a clear information architecture.
• A rebrand requires a substantial redesign rather than a visual refresh.
• The business is entering additional Alberta or Canadian markets.

Then define two or three primary website goals.

For example:

1. Increase qualified consultation requests from Calgary-area prospects.
2. Make service information easier to find from mobile devices.
3. Allow the marketing team to publish landing pages without editing code.

These statements are much more useful than saying the goal is to “have a better website.”

If you are still deciding how broad the project needs to be, reviewing the elements commonly included in Calgary web design services can help you separate design, development, testing, launch, and ongoing support before writing your scope.

Describe the current website

For a redesign, agencies need to know what they are inheriting.

Include:

• Current website address
• Content management system (CMS)
• Approximate number of live pages
• Blog or resource library size
• eCommerce functionality, if applicable
• Forms and lead-routing tools
• CRM integrations
• Booking or scheduling software
• Membership or login functionality
• Analytics and tag-management tools
• Hosting arrangement
• Any known technical problems

Do not worry if you cannot answer every technical question. Say what you know and give shortlisted agencies access to more information during discovery if required.

A useful attachment is a simple page inventory exported from your sitemap or crawling software. Mark each URL as keep, revise, merge, redirect, or remove.

That single document can reveal far more about redesign effort than a statement such as “the site has about 20 main pages.”

Define audiences and conversion actions

Do not describe the audience as “businesses in Calgary” unless that genuinely represents everyone you serve.

Explain who needs to use the site and what each audience should be able to accomplish.

A commercial construction company might have several website journeys:

• Property owners need to assess services and request a project discussion.
• General contractors may want specific capabilities or subcontracting information.
• Job candidates need current vacancies and employment information.
• Existing partners may need documentation or contact details.

Then define the important conversions.

Examples include:

• Submit a consultation form
• Call the business
• Book an appointment
• Request a quote
• Download a technical document
• Purchase a product
• Apply for a position
• Subscribe to updates

This tells an agency what deserves prominence in the site architecture and user interface.

If local lead generation matters, define the geographic area accurately. Google allows eligible service-area businesses to specify the areas they serve in their profiles, so the website should reflect real operating areas rather than creating artificial location coverage. See Google’s guidance for service-area businesses.

Specify the page scope and content responsibilities

Page count affects design, development, content production, quality assurance, and migration effort.

Do not write “approximately 15 pages” if those pages have completely different requirements. Group them by template or content type.

Content type	Quantity	Requirement
Homepage	1	New structure, messaging, and design
Service pages	6	Shared template with unique copy
Industry pages	4	Flexible content sections and case examples
Project portfolio	12 entries	Reusable project template
Blog	Existing archive	Migrate current posts
Contact	1	Form, map, and lead routing
Legal pages	2	Existing approved text

Also specify who produces the words and visual assets.

Does your company provide final copy? Does the agency revise existing text? Are interviews required? Who sources photography? Are staff headshots available? Does a third-party branding firm control the design system?

Content delays can disrupt an otherwise realistic website schedule, so assign responsibility before asking agencies to commit to a launch date.

List functionality as requirements, not vague features

“Interactive website” is not a technical requirement.

Describe what the user needs to do and what should happen afterwards.

Instead of:

We need CRM integration.

Write:

When someone completes the consultation form, create a contact in HubSpot, record the selected service, and notify the Calgary sales inbox.

Instead of:

We need eCommerce.

Write:

Customers must be able to purchase approximately 40 physical products, pay online, receive transactional emails, and select shipping based on our existing fulfilment rules.

This distinction gives agencies enough information to evaluate plugins, APIs, custom development, testing, and licensing requirements.

If WordPress is already a requirement, explain why. Perhaps your marketing team already knows the platform, or existing systems depend on it. Reviewing what is involved in professional WordPress development can also help you identify CMS editing, integration, and custom-functionality requirements worth including in the RFP.

If the platform is still open, describe what your staff needs to accomplish rather than choosing a CMS solely because it is familiar.

Include SEO and redesign migration requirements

SEO should not appear in an RFP as a single line that says “website must be SEO friendly.”

For a new website, define the foundations you expect, such as crawlable navigation, editable metadata, sensible heading structure, XML sitemap support, mobile usability, and indexable page templates.

A redesign needs additional planning because existing URLs may already have search visibility, backlinks, or recurring visitors.

Ask the agency to explain its approach to:

• Existing URL inventory
• Page consolidation
• URL mapping
• Permanent redirects
• Metadata migration
• Internal links
• XML sitemaps
• Canonical tags
• Robots directives
• Structured data already in use
• Google Search Console
• Analytics continuity
• Pre-launch crawling and post-launch checks

Google recommends mapping old URLs to appropriate new destinations when URLs change, using permanent redirects, testing the migration, and monitoring the new site after launch. Its site move documentation is a useful reference when defining migration requirements.

If organic search is already an important acquisition channel, make that visible in the RFP. An agency should know that preserving existing search assets is part of the project rather than something to discover during launch week.

It also helps to distinguish redesign-related SEO from a continuing marketing engagement. Ongoing Calgary SEO services may cover work beyond the website build, while an RFP for a redesign may only require technical preparation, migration safeguards, and launch checks.

Define performance, accessibility, and testing expectations

“Fast” and “accessible” are not sufficiently precise acceptance criteria.

For performance, ask agencies how they test important templates and how they handle images, third-party scripts, caching, fonts, and front-end code.

Google’s Core Web Vitals currently assess loading performance through Largest Contentful Paint, responsiveness through Interaction to Next Paint, and visual stability through Cumulative Layout Shift. The Core Web Vitals documentation provides definitions and recommended measurement approaches.

Do not turn performance metrics into an unconditional contractual promise without considering real-world dependencies. Advertising scripts, embedded booking platforms, consent tools, hosting, and other third-party services may affect results.

For accessibility, identify the standard you expect the agency to design and test against. The World Wide Web Consortium publishes WCAG 2.2, which provides testable accessibility criteria at different conformance levels.

If your organization has statutory or contractual accessibility obligations, confirm the applicable requirements with an appropriate legal or accessibility professional. A website build should not be assumed to create legal compliance automatically.

Your RFP can also define practical testing expectations such as:

• Current versions of major browsers
• Representative mobile and desktop breakpoints
• Keyboard navigation
• Form validation and error states
• Internal and external links
• Analytics events
• Checkout or booking workflows
• Staging-site review before launch

State budget, timeline, ownership, and post-launch needs

Hiding the budget rarely makes estimates more accurate.

A budget range lets agencies explain what can realistically fit within it. If procurement rules prevent you from disclosing a figure, ask agencies to separate essential scope from recommended or optional enhancements.

Also include:

• RFP issue date
• Deadline for questions
• Proposal deadline
• Shortlist or interview dates
• Desired kickoff
• Target launch window
• Any fixed event or campaign deadline

Clarify ownership as well. Ask who controls the domain, hosting, CMS administrator account, source files, premium plugin licences, design files, analytics properties, and other accounts after launch.

Finally, describe the support you expect after launch. A proposal containing ongoing updates, backups, security monitoring, and technical support should not be compared directly with one that ends at deployment. Reviewing the scope of website maintenance services can help you decide which responsibilities belong in the initial project and which belong in a separate ongoing agreement.

A step-by-step process for writing your web design RFP

You do not need a 40-page procurement document. For many small and medium-sized businesses, a focused RFP with useful attachments is easier for agencies to respond to and easier for your team to evaluate.

1. Audit what you already have

List the current pages, forms, tools, integrations, analytics accounts, hosting arrangements, and known problems.

Record what must survive the redesign. If a section can disappear, say so. If a URL receives valuable organic traffic or supports an active campaign, mark it for review rather than assuming it can be deleted.

2. Define outcomes before deliverables

Write three to five statements describing what should be easier or better after launch.

For example:

• Prospects can identify the correct service without calling for clarification.
• Marketing can publish campaign pages internally.
• Sales receives form submissions with enough information to qualify each lead.
• Existing high-value organic landing pages remain accessible after migration.

Then translate those outcomes into project requirements.

3. Build a scope table

Create a spreadsheet with pages or templates in one column and requirements in the others.

Record content owner, migration status, functionality, approval owner, and whether each item is required for launch.

This exposes hidden work quickly.

4. Separate must-haves from optional items

Use three categories:

Required for launch: The proposal must include it.

Preferred: You want it included if the budget allows.

Future phase: The architecture should accommodate it, but agencies do not need to build it now.

A membership portal planned for next year should not inflate the current quote unless the first release genuinely needs development work to support it.

5. Ask agencies to structure their responses

Give respondents a common proposal format.

Ask for:

1. Recommended approach
2. Project phases
3. Deliverables
4. Timeline
5. Project team and responsibilities
6. Price by major phase or workstream
7. Third-party costs
8. Assumptions
9. Exclusions
10. Post-launch support

This makes comparison far easier than receiving one two-page estimate, one 30-page presentation, and one unexplained lump-sum quote.

6. Allow questions before final proposals

A serious agency will probably have questions.

That is useful rather than inconvenient. Questions about content ownership, CRM behaviour, product data, redirects, approval workflows, or technical constraints often reveal where your own project definition needs work.

If several agencies ask the same question, send the answer to every bidder so they continue pricing the same project.

Practical example: a Calgary professional services redesign

Imagine a hypothetical Calgary engineering consultancy requests quotes for “a modern 25-page website with SEO.”

Agency A quotes $8,000. Agency B quotes $16,000. Agency C quotes $24,000.

It appears that Agency A is dramatically cheaper, but further review shows that each company priced something different.

The business rewrites its RFP and specifies 21 standard pages, nine project entries, five team profiles, HubSpot form integration, migration of 80 existing articles, redirect mapping, GA4 event tracking, WordPress editing, an agreed accessibility target, staff training, and 60 days of post-launch support.

The second round of proposals may still differ in price, but now the differences are meaningful. One agency may recommend more discovery. Another may include custom development. A third may use a different content approach.

You can evaluate those differences because the underlying project is finally the same.

How to compare Calgary web design proposals fairly

Do not start with the final price.

First determine whether each agency has priced the requested scope.

A simple evaluation table can help:

Evaluation area	What to check
Scope coverage	Does the proposal address every required deliverable?
Assumptions	What has the agency assumed you will provide?
Exclusions	What expected work is specifically not included?
Content	Who writes, edits, uploads, and approves content?
Technical approach	Does it fit your CMS, integrations, and internal capabilities?
SEO migration	Are redirects, metadata, indexing checks, and analytics addressed?
Project process	Are milestones, review rounds, responsibilities, and approvals clear?
Ownership	Who owns accounts, files, licences, and website assets after launch?
Support	What happens after deployment, and for how long?
Price	What is fixed, estimated, optional, or billed separately?

A higher proposal is not automatically more complete. A lower proposal is not automatically missing work. Read the assumptions.

For example, one quote may include copywriting for 20 pages while another expects your team to deliver final copy. One may include premium plugin licences for the first year while another lists them as recurring client expenses.

Ask agencies to clarify these differences before choosing.

You should also ask shortlisted agencies to show work that resembles the problem you are solving. Look beyond screenshots. Review navigation, mobile behaviour, information architecture, editing requirements, integrations, and the complexity of the content involved.

Common RFP mistakes that make quotes less reliable

A useful RFP reduces uncertainty. Several common practices do the opposite.

Writing a design specification before hiring a designer

It is reasonable to describe brand requirements and examples you like. It is less useful to dictate every layout, component, and technology without understanding the tradeoffs.

Define the problem and constraints, then evaluate how each agency proposes to solve them.

Treating page count as the entire scope

Twenty basic pages are not equivalent to 20 pages containing calculators, gated downloads, searchable resources, product data, interactive maps, or custom forms.

Templates and behaviours often matter more than the raw number of URLs.

Asking for “SEO included” without defining SEO

Different agencies can reasonably interpret this as metadata setup, keyword research, technical SEO, redirect management, copywriting, local SEO, or an ongoing campaign.

State what needs to happen during the build and whether continuing SEO is part of the engagement.

Forgetting content migration

Moving 300 blog posts is work even when none of them receives a redesign.

Someone must export, import, format, validate, preserve media, check links, and review the result. If old content needs to be consolidated or rewritten, the task becomes larger.

Providing an inflexible launch date without approval deadlines

Your team is part of the project schedule.

If five stakeholders need to review designs, legal must approve copy, and product photography will not be ready for six weeks, include those dependencies. Otherwise, agencies can only estimate the development side of the timeline.

Comparing totals instead of scope

The useful question isn’t, “Which agency gave us the lowest number?”

Ask, “What exactly would we receive for this number, what remains our responsibility, and what additional costs could reasonably appear?”

That turns a stack of estimates into a purchasing decision.

Give agencies enough information to price the same project

The best RFP does not tell an agency how to design your website. It defines the business problem, users, required capabilities, project boundaries, and responsibilities clearly enough that agencies can propose different solutions to the same assignment.

Before sending your RFP, do one final review from a bidder’s perspective. Could an agency determine how many pages and templates are involved? Who supplies content? Which integrations matter? What needs to survive a redesign? How will the site be evaluated before launch?

If those answers are clear, the quotes you receive will be much easier to compare, and the differences between them will tell you something useful.

FAQs