Website RFP template: write a brief agencies can quote fairly
For owners and department heads about to ask agencies for a quote: a fill-in website RFP template, a scoring table and red flags, so every quote compares line by line.
On this page
You are about to ask three or four agencies for a quote, and you want the answers to line up. A website RFP template gives every agency the same questions in the same order, so you compare scope, price and risk instead of writing styles.
The short answer: a good brief states your business goal, the numbers that define success, the systems the site must connect to, your budget range and how you will judge the answers. Write those five things down and the quotes that come back can be compared line by line.
Search for the best agencies and you get lists of names and rankings. Those lists do not tell you how to compare quotes. This guide covers the step before them: the brief. If you already have a shortlist, questions to ask a web development agency pairs well with it, and how to choose an agency by goal explains the decision that follows.
Key takeaways
- Your brief should state the goal, two or three success numbers, the systems to connect, a budget range and how you will score answers.
- Every agency should answer in the same format, with scope split into lines, assumptions and exclusions written down.
- Set the scoring weights before you read any quote, so a polished deck cannot decide for you.
- A short discovery call turns a vague quote into a written one you can compare.
- This week you can write the goal and success numbers in one sitting and send the brief to three agencies.
What a website RFP template must include
A website RFP, or request for proposal, is a written document that asks agencies to propose how they would reach your goal, at what price and with what risks. It works because every agency reads the same facts. Without it, each one fills the gaps with its own guesses, and the quotes stop being comparable.
RFP or brief: which one you need
A full web development RFP suits a larger project: a rebuild, an online store, a site tied to your CRM or ERP. It runs to a few pages and also asks for the team, references and a plan. A project brief is the one-page version: goal, numbers, systems, budget and date.
If your need is small, a few pages and one integration, send a one-page brief to two agencies and stop there. A smaller fix may also be the better buy than a new site, for example speeding up the one you have or connecting a form to your CRM. Say in the brief that you are open to a smaller change if it reaches the goal.
The five parts every agency can quote against
Whatever the size, the same five parts make a request for proposal for web design easy to answer:
- Goal: the result your business needs, in one sentence.
- Success numbers: two or three figures you already track, with today's baseline.
- Systems to connect: CRM, ERP, payments, analytics and the person who edits content.
- Budget range and timeline: what you can invest and which dates cannot move.
- How you will judge answers: the criteria and weights you will use to score each quote.
The next sections fill in each part. Copy the fields into one document and send the same file to every agency.
Fill in the goal section of your website RFP
This is the part that decides whether three agencies price the same project or three different ones. Spend most of your time here.
Write the goal in one sentence
State the result in your business, not the pages. 'Redesign the website' is a task. 'Bring in more qualified enquiries from distributors in Mexico and Colombia' is a goal an agency can price against and challenge.
Use this shape: who, what changes, by when. For example: 'Our sales team receives more qualified quote requests from the site by the end of the year, and spends less time on manual follow-up.'
Pick two or three success numbers
Choose numbers you already track: enquiries, sales, bookings or hours saved. Add today's baseline from your analytics or your CRM. No honest agency can promise a result, but each one can explain how its plan moves toward it.
Here is an illustrative example. A B2B distributor gets 40 enquiries a month from the site, and its sales staff spend about 10 hours a week copying form entries into the CRM. The brief asks to raise qualified enquiries from that baseline and to send every form straight to the CRM. Now each agency prices the same two outcomes.
Two or three numbers are enough. With more, agencies cannot tell which one matters most.
Add speed, accessibility and search basics as requirements
These three are cheap to ask for at the start and costly to add after launch. Name the standard so every agency prices it the same way.
For speed, use Core Web Vitals, Google's measures of how fast a page loads, how fast it answers a tap and how steady it stays. web.dev publishes the thresholds (opens in a new tab) you can paste into the brief.
2.5s
LCP target
Largest Contentful Paint, Google's good threshold, 75th percentile
200ms
INP target
Interaction to Next Paint, Google's good threshold
0.1
CLS target
Cumulative Layout Shift, Google's good threshold
For accessibility, ask for conformance with WCAG 2 (opens in a new tab), the W3C standard for sites people can use with a keyboard or a screen reader. Name the level you expect (AA is the common target) and ask who tests it.
For search, ask the agency to follow the Google SEO starter guide (opens in a new tab): pages that can be crawled, clear titles, readable URLs and redirects from old addresses if you rebuild. These fields go straight into your brief:
- Business goal in one sentence
- Two or three success numbers, each with today's baseline
- Pages, flows or features in scope, and what is out of scope
- Speed and accessibility targets, such as the Core Web Vitals thresholds and WCAG 2 level
- Launch deadline and any date that cannot move
List your platform, systems and content owner
Integration work is where quotes drift furthest apart. One agency prices a CRM connection, another assumes it is outside the scope. Naming each system up front puts that work on the page, so you pay for it in the quote and not as a surprise later.
Current platform and what stays
Say what the site runs on today (WordPress, Webflow, Shopify or custom code) and what you want to keep: the platform, the design, the URLs, the content. Say also if you are open to changing platform. An agency that knows the platform can move may propose a cheaper route.
Add two lines on what hurts today in the words your team would use: 'forms land in an inbox nobody checks', 'the product page takes too long to edit'. Agencies read those lines first.
Integrations to connect
List every system the site must talk to. For each one, write the name, what data moves, in which direction and who holds the access.
- CRM: which fields from a form or an order should arrive, and who follows them up.
- ERP or inventory: prices, stock and orders, and how often they sync.
- Payments and invoicing: gateways, taxes, invoices and currencies.
- Analytics and email: the tools that must keep working after the change.
If you do not know whether a system has an API (a way for other software to read and write its data), write 'unknown' and ask each agency to check it in the discovery call.
Who owns content and code after launch
Name the person who edits content and how often. That decides how the CMS, the place where your team edits pages, is built. A marketing lead who publishes weekly needs a different setup from a site updated twice a year.
State your expectation on ownership too: the code repository, the licences, the domain and the accounts should be yours. Ask each agency to confirm it in writing. This single line often separates two quotes that look equal.
Share your budget range and timeline
Agencies size a project by its budget as much as by its scope. Giving them the range is a way of getting the right size of proposal, not a way of paying more.
Why a range gets better quotes
Without a range, quotes arrive from very small to very large and you learn nothing from the spread. With a range, each agency shows what it would build inside it, and what it would leave out. Ask for two options: what you get at the low end and what you get at the top.
If you are not sure what to put, what a website costs helps you set a realistic range before you write the section. Mark your must-haves and your nice-to-haves, so an agency can cut the second group first.
Fixed dates and flexible dates
Separate dates that cannot move (a trade show, a campaign, a season) from dates that can. Then add what affects the schedule on your side: how fast your team can review, content that is not yet written, approvals that need several people.
Agencies price the delays they expect. If you tell them yours, they plan for them, and the schedule in the quote is one you can keep.
Score proposals with one comparison table
Decide how you will judge before you read any quote. Once you have seen a low price or a polished presentation, staying fair is hard. One table, agreed in advance, keeps the comparison on your goal.
Set the weights before you read
Start from the weights below and change them to match your goal. They add up to 100. A store that sells every day may weigh post-launch support higher, while a company with a developer in house may weigh ownership higher. The weights are a starting point, not a standard.
| Criterion | What to look for | Weight | Score (1 to 5) |
|---|---|---|---|
| Fit with your goal | The plan names your success numbers and how the work moves them | 20 | |
| Scope clarity | Lines split by page type, integration, content and testing | 15 | |
| Assumptions and exclusions | A written list of what is assumed and what is left out | 15 | |
| Testing and quality checks | Devices, speed, accessibility and integrations checked before launch | 10 | |
| Post-launch support | Who answers, how fast, what is included and what costs extra | 15 | |
| Code and content ownership | Repository, licences, domain and accounts in your name | 15 | |
| Team and references | Named people, their roles and projects you can ask about | 10 |
Price is not in the table on purpose. Compare it after you score, for the same scope, so a low number cannot hide a missing line.
Score each line from 1 to 5
Give each agency a score from 1 to 5 on each line, multiply by the weight and add up the total. A 1 means missing, a 3 means stated but thin, a 5 means specific and in writing. Ask two people to score separately, then compare.
A gap of more than one point on a line rarely means a difference of taste. It usually shows something unclear in the quote, which is exactly what the discovery call is for.
Quote comparison path
- 01Brief goes outOne brief sent to three agencies
- 02Same formatEach agency answers in the same structure
- 03One scoring tableQuotes scored from 1 to 5 in one table
- 04Discovery callGaps closed, revised quote in writing
- 05Shortlist readyScored shortlist to pick from
Five-step flow from sending one brief to three agencies to a shortlist scored in one table
When the scores are in, how to choose a web development agency covers the decision itself: fit, references and what to ask before you sign.
Red flags to spot in agency quotes
A quote shows how an agency thinks about your project. These signs tell you where to ask more, before you compare totals. None proves a provider is weak: many agencies write short quotes out of habit, and a question usually clears it up.
Vague hours and bundled lines
A single line such as 'website development' with one total tells you nothing you can compare. Ask for lines split by page type, integration, content migration, testing and project management. Ask also for the roles behind the hours: who designs, who builds, who tests.
Watch for these in particular:
- One total price with no breakdown.
- 'Unlimited revisions' with no limit or process for requests.
- A team described as 'our experts' with no names or roles.
- Integrations mentioned in the pitch but missing from the lines.
- Support after launch with no scope, hours or response time.
Ask this first
A quote that cannot say what is excluded cannot be compared. Ask every agency for its exclusions in writing before you look at anything else.
No handover or testing plan
A good quote says what you hold on launch day: access to the code and the repository, admin accounts, documentation and a walkthrough for your team. It also says how the work is tested: on which devices, by whom and with which checks for speed, accessibility, forms and integrations.
When those lines are missing, the cost tends to return after launch as new invoices. When they are there, you know what 'done' means before the work starts.
What a discovery call should settle
A discovery call of 30 to 45 minutes turns a general quote into a comparable one. You are not there to be sold to. You are there to close the gaps your scoring table showed. If you want a longer list to draw from, questions to ask a web development agency before you hire has one.
Questions that close the gaps
Run the call in this order, and take notes on the answers you will need in writing.
Confirm the goal
Ask the agency to repeat your goal and success numbers in its own words. Any difference now is a cost later.
Test the assumptions
Ask which assumptions the price depends on, such as content ready, an API available or a number of templates.
Name who does the work
Ask who designs, builds and tests, and who is your point of contact each week.
Agree how changes are handled
Ask what happens when scope moves: how a change is requested, priced and approved.
Ask for the revised quote in writing
Ask for an updated quote that includes everything said on the call, with a date to receive it.
What you should have in writing afterwards
After the call, each agency should send an updated document. It should contain:
- The scope split into lines, with assumptions and exclusions.
- The named team and the role of each person.
- The process for change requests.
- The handover list: code, accounts, documentation and training.
- The support terms after launch, and who owns code and content.
If an agency answers all five clearly, you have a quote you can score. If one cannot, that is useful information too.
How werun.dev answers a brief
You set the goal, we build the way there. When your brief arrives, we read it the way you wrote it: goal first, systems second, budget third.
From brief to written proposal
Send your brief through the contact page and a person replies in under 2 hours on business days. We then book a short call to confirm the goal and test the assumptions. We read your current site first, so you hear what we found before any quote.
The written proposal follows with scope in lines, exclusions, the named team, testing, handover and support after launch. We have looked after 200+ sites over 12+ years, and a clear brief is the easiest thing to build from. If a smaller fix reaches your goal, we say so in the proposal, even when it is smaller than what you asked for.
Small, Medium, Large and Custom projects
Your brief maps to one of four project sizes. The engagements page explains each one, along with the monthly Retainer and the Care plan for what comes after launch.
Small
A focused change
A few pages, one integration or a fix to the site you have. You get a clear scope and a quick start.
Medium
A new site or store
A site or store with a few connected systems. You get a plan by page and by integration.
Large
A rebuild across teams
A larger rebuild or a multi-market site. You get phases you can review one at a time.
Custom
A build around your process
A web app or workflow that fits no standard size. You get a proposal written around how you work.
We do not ask you to fit your project into a size. We write the proposal around your goal and tell you which size it matches.
Where to start your website RFP this week
You can finish the first draft in a day. Do it in this order:
- Write the goal in one sentence and pick two or three success numbers, each with today's baseline.
- List your platform, the systems to connect and the person who edits content.
- Set your budget range, your fixed dates and the scoring weights.
- Send the same document to three agencies, or two if the need is small.
- Book a 30 to 45 minute call with each one and ask for a revised quote in writing.
If you would like us to be one of the three, tell us your goal on the contact page and a person replies in under 2 hours on business days. If you want to see how a quote maps to a project first, start with the engagements page.
Frequently asked questions
What should a website RFP include?
A website RFP should include your business goal, two or three success numbers with today's baseline, the systems the site must connect to, who edits content, a budget range, key dates and how you will score the answers. Add what is in and out of scope.
How long should a website RFP be?
For a rebuild or a store, a few pages is enough. For a small project, one page covering goal, numbers, systems, budget and date works well. Length matters less than whether every agency can answer the same questions.
How many agencies should I send a website RFP to?
Three is a good number: enough to see a spread, few enough to read each quote with care and hold a discovery call with each. For a small project, two agencies are enough.
How do I compare web design proposals fairly?
Set your criteria and weights before reading any quote, ask every agency to answer in the same format, and score each line from 1 to 5. Compare price last, for the same scope, and ask for exclusions and assumptions in writing.
Should I put my budget in a website RFP?
Yes, give a range. It lets agencies propose the right size of project and show what they would leave out. Without it, quotes vary so widely that the spread tells you nothing about fit.
What is the difference between a website RFP and a project brief?
A project brief is a short document with your goal, success numbers, systems, budget and dates. An RFP is the longer version for bigger projects: it also asks for the team, references, a plan and a scoring method.