Free template

Website redesign RFP

A blank redesign RFP and a completed example, so proposals answer the same scope, responsibilities and acceptance tests.

What it covers

  • Company goals and the existing site
  • Pages, content types and integrations
  • Constraints and approval dates
  • Deliverables and criteria for comparing proposals

Download it, free, no sign-up

Blank template

Empty fields with guidance, for your own project.

Example

The same fields, completed for an invented business.

Website redesign RFP

  1. Company and contact
  2. Goals and visitor journeys
  3. Current site and constraints
  4. Pages, templates and CMS scope
  5. Functions and integrations
  6. Content, assets and responsibilities
  7. Budget and proposal format
  8. Timeline, dependencies and reviews
  9. Deliverables and documentation
  10. Acceptance criteria
  11. Assumptions and exclusions
  12. Ownership, licences and handover
  13. Recurring costs and support
  14. How proposals will be evaluated
aboutstefan.dev

How to use it

Fill it in, in this order

  1. Start with goals

    Fill in the goals and the current site first.

  2. Add the scope

    List the pages, content and integrations.

  3. Set how you choose

    Add the timeline and how you will judge proposals.

  4. Send it out

    Share it with everyone on your shortlist, with the same deadline for all.

Example

Completed RFP example: Example Instruments

An invented business and scope, to show how the blank template is completed. It describes no real client, price or outcome.

Company and contact
Example business: Example Instruments, an invented company. Project lead: Casey, marketing manager. No real client or result is described.
Goals and visitor journeys
Help technical buyers find the right product, read specifications and request a demonstration. Marketing should publish resources from an approved template.
Current site and constraints
An existing WordPress marketing site; product logins stay on the separate application. The company controls its domain.
Pages, templates and CMS scope
Home, about, contact and three service pages; reusable product, article and case-study templates; 12 product entries and 25 articles to migrate. These are example scope inputs.
Functions and integrations
A demonstration form connected to the existing CRM, a resource filter and newsletter signup. The project lead supplies authorized access.
Content, assets and responsibilities
The company supplies approved copy and product diagrams. The supplier maps migration fields and flags missing content. Translation and new photography are outside scope.
Budget and proposal format
Budget range to be provided by the example buyer. Ask for separate estimates for design, development, migration and any optional work; no public price is suggested here.
Timeline, dependencies and reviews
Work starts after scope and access are confirmed. Product-page design is reviewed before the remaining templates. The buyer supplies one consolidated review at each milestone.
Deliverables and documentation
Responsive designs, the Webflow build, mapped content, tested forms and redirects, an open-issue list, CMS instructions and a recorded handover.
Acceptance criteria
A visitor can find a product and send a valid demonstration request that reaches the intended CRM fields. Test keyboard use, mobile layouts and representative CMS entries. Changed URLs reach relevant final pages with the intended status.
Assumptions and exclusions
Assume one language and supplied product data. Exclude the product application, new brand identity, translation and ongoing campaigns. Any changed requirement gets a separate scope decision.
Ownership, licences and handover
The company controls the Webflow workspace, domain and subscriptions. Name the supplier’s reusable materials and third-party licences. Editors practise adding a resource before acceptance.
Recurring costs and support
Ask suppliers to list the required Site plan, editing seats, CRM or automation subscriptions, renewal responsibilities and the terms of optional support.
How proposals will be evaluated
Compare the same inventory, acceptance tests, assumptions, relevant portfolio roles, editing workflow and recurring costs. Resolve differences before comparing totals.

Compare like-for-like proposals

Ask each supplier to state its assumptions and exclusions beside the estimate. Review migration, integrations, acceptance tests, handover and recurring costs together. Clarify differences before choosing a supplier; a lower total may cover less work.