Access
Domain registrar, DNS, hosting, content system, code repository, analytics, Search Console, forms, email delivery, payment, booking, and third-party services.
Buyer template · Updated August 2026
Web Design RFP Template
A useful request for proposal gives qualified website partners enough information to recommend an approach while keeping responses comparable. Copy this structure into your procurement document, remove sections that do not apply, and answer what you know without pretending every decision is final.
1. Business context and project outcome
Introduce the organization, customers, locations or service area, products or services, current sales process, and why the project exists now. Name the business problem and the decision the website should help a visitor make.
Template prompt: Our organization helps [audience] achieve [outcome]. The current website creates [problems]. This project should improve [measurable business outcomes]. The primary visitor actions are [actions].
Separate outcomes from deliverables. A new homepage is a deliverable. More qualified consultations from organic search is an outcome. Vendors need the outcome to decide which pages and capabilities matter.
2. Audience, journeys, and evidence
- List the primary and secondary audiences and what each already knows.
- Describe common questions, objections, comparison criteria, and trust requirements.
- Share useful analytics, Search Console, customer interviews, sales notes, and support themes.
- Identify priority locations, languages, devices, accessibility needs, and buying stages.
- State which claims, credentials, project examples, team details, and policies can be published.
Do not ask a vendor to invent proof or customer facts. Name the internal people who will provide and approve business information.
3. Current website inventory
Assets
Brand files, fonts, photography, video, copy, downloads, legal text, product data, staff profiles, reviews, case studies, and licences.
Performance
Important pages, organic queries, backlinks, conversions, traffic sources, site search, support issues, speed, accessibility findings, and security concerns.
State whether the vendor will receive access during proposal preparation or only after selection. Sensitive access should be shared securely and only when required.
4. Scope and responsibilities
| Workstream | Questions to answer |
|---|---|
| Research | Are interviews, analytics, keyword research, content inventory, and competitor review required? |
| Architecture | Who defines navigation, page hierarchy, templates, URLs, and internal links? |
| Content | Who interviews, writes, edits, sources media, enters content, and approves claims? |
| Design | Which components, breakpoints, states, prototypes, and revision rounds are expected? |
| Development | Which platform, forms, integrations, roles, search, payments, and administration are needed? |
| Migration | Which pages, media, records, metadata, redirects, accounts, domains, and DNS must move? |
| Quality | Which accessibility, performance, security, browser, device, tracking, and acceptance tests apply? |
| Operations | Who hosts, updates, backs up, monitors, supports, reports, and improves the site after launch? |
5. Proposal response format
- Understanding of the business problem and recommended approach.
- Deliverables, responsibilities, assumptions, dependencies, and exclusions.
- Project phases, decision points, milestones, and client time required.
- Named team roles and relevant examples that can be verified.
- Platform, hosting, security, accessibility, performance, analytics, and SEO approach.
- Migration and launch plan, including redirects, rollback, and post-launch checks.
- Project price, optional items, payment schedule, taxes, currency, and change process.
- Ownership, licences, account control, documentation, training, warranty, and ongoing support.
Ask vendors to list unanswered questions and risks. A thoughtful proposal should expose uncertainty rather than hide it behind a fixed number.
6. Evaluation scorecard
Set weights before proposals arrive. A practical scorecard can consider business understanding, recommended approach, content and search strategy, user experience, technical quality, accessibility, security, migration, measurement, delivery confidence, ownership, support, and total value.
Use mandatory gates for issues that cannot be traded away, such as business ownership of the domain, exportable content, acceptable privacy and security, direct redirect planning, and clear administrative access. References and examples should be checked, not accepted as decoration.
North Star provides website design across Canada. Send the completed brief or use it internally before a scope call so the proposal can address the real project.
Frequently asked questions
Web Design RFP Template FAQ
What is a web design RFP?
A web design request for proposal explains the organization, project outcomes, audiences, current website, required scope, responsibilities, constraints, response format, evaluation method, and commercial expectations so qualified vendors can recommend and price comparable approaches.
How detailed should a website RFP be?
It should be detailed about the business problem, required outcomes, responsibilities, known constraints, systems, ownership, and evaluation. It does not need to dictate every design or technical decision when the selected partner is expected to provide expertise.
Should a website budget be included in the RFP?
A realistic budget range helps vendors recommend an appropriate scope and avoid proposals built around incompatible assumptions. If the budget is not shared, require vendors to separate essential work, options, exclusions, and the effect of major scope decisions.
How many web design proposals should a business request?
There is no universal number. Invite enough qualified providers to compare approaches without creating an evaluation burden. A short, well-researched list usually produces more useful conversations than sending the RFP indiscriminately.
Who should evaluate web design proposals?
Include the business owner of the outcome plus people responsible for marketing or content, technology, security or privacy where relevant, accessibility, operations, and procurement. Define each person’s decision role before proposals arrive.
Turn the plan into a website that sells
North Star designs, rebuilds, hosts, and supports business websites remotely across Canada. Bring the checklist or brief to a scope call and we will translate it into a clear proposal.
Request a Website ScopeExplore Web DesignResearch expansion
Add a weighted evaluation model
Score strategy, content, accessibility, technology, security, performance, analytics, SEO migration, ownership, maintenance, team, timeline, risk, references, and total cost using published weights and written evidence.
mandatory requirements
weighted score
risk notes