Writing an RFP for web design (with examples and a template)
- Published
- Reading time
- 2 min
- Published by
- Alex

Better material, better proposals
A well-written RFP shortens lead times, cuts down on follow-up questions and makes agencies' proposals comparable. Here are the ten sections it should contain, with examples you can start from.
As a web agency we see the difference straight away: a well-prepared RFP leads to fewer follow-up questions, faster responses and proposals that can be compared. Thin material instead leads to long email threads and quotes based on completely different assumptions.
What is an RFP for web design?
An RFP (Request for Proposal), in Swedish often called förfrågningsunderlag, is a document in which you describe your needs, goals, requirements, budget and timeline and invite agencies to submit a proposal and price.
It is similar to a brief, but has a different purpose. The brief helps an agency understand the assignment. The RFP is used when you want to compare several agencies on equal terms, so it also contains instructions for how proposals should be submitted and assessed.
Common buyers of web projects via RFP:
- Companies – everything from brand sites to ecommerce and customer portals.
- Non-profit organisations – websites for fundraising, campaigns and members.
- Healthcare – websites and services with high demands on security and compliance.
- Public sector – which follows the rules for public procurement.
Public sector: LOU sets the framework
Government agencies, municipalities and regions procure under the Public Procurement Act (LOU). Below the direct award threshold they may buy using a simpler procedure. Above the threshold an advertised procurement is required, and above the EU thresholds the rules of the EU directives also apply.
| LOU threshold for goods and services | Amount |
|---|---|
| Direct award threshold | SEK 700,000 |
| EU threshold, central government authorities | SEK 1,589,140 |
| EU threshold, other contracting authorities, for example municipalities and regions | SEK 2,451,816 |
Source: Upphandlingsmyndigheten, values from 1 January 2026, excluding VAT.
Public-sector websites are also covered by the Act on Accessibility to Digital Public Services, so accessibility requirements belong in the material from the start. The structure below works for both private and public buyers.
Ten sections an RFP for web design should contain
The examples are worded the way you might write them. Square brackets mark what you fill in yourselves.
1. Introduction
Briefly describe the company, the purpose of the project and why you are building new or redesigning. Link to your current website.
Example: We want to redesign our website because it does not support how we communicate today. The goal is to strengthen our presence, attract candidates and showcase case studies. We want to be able to update the content ourselves and get better measurement of traffic and conversion.
2. Company background
Give context: history, offering, values, vision and how you work.
Example: Since [year] we have been working with [offering] for [customer group] in [markets].
3. Project goals
Describe the audience, current state, problems and opportunities. Set measurable goals, for example a better user experience and conversion, more organic traffic or more leads.
Example: The website should be our main communication channel, be available in [number] languages and publish results, news and events. Social channels should be integrated, and the website should be audited against WCAG 2.1 level AA before launch.
4. Specification
The specification is the core of the RFP. Consider splitting it into subheadings:
- Visual identity. Is there a visual identity with logo, colours, typography and image style, or does one need to be created? Example: The website should follow our brand guidelines and show EU co-funding in line with the applicable guidelines.
- CMS. Licence, user roles, multilingual support, templates, integrations and media library. Example: Open source, roles and permissions, templates for duplicating pages, a media library for images, video and PDF.
- Page structure. A simple sitemap gives agencies an idea of the scope. Example: Home, About us, Services, Case studies, Careers, News, Contact.
- Languages. Which languages at launch and later, and how language switching should work. Example: Swedish and English at launch, with the same structure in both.
- SEO. Titles and headings, a clean URL structure, alt texts, 301 redirects from old addresses, Core Web Vitals and conversion tracking.
- Personal data. Forms, analytics and cookies must be handled in line with GDPR, with consent where required.
- Security and maintenance. Updates, security patches, backups, logging and an incident plan.
- Handover and training. Example: Training for [number] editors, a handbook for page modules and publishing routines.
5. References and competitors
List websites that inspire you and your main competitors, with a sentence on what you like or want to avoid. This shows the level and style you expect.
6. Budget range
Give a realistic range for the scope and quality. It makes things easier both for the agencies and for you when the proposals are prioritised.
Example: Budget for design, development and launch: SEK [X–Y] excluding VAT. Ongoing improvements and hosting are budgeted separately.
7. Timeline
Describe the milestones from sending out the RFP to launch.
Example: RFP sent [date]. Deadline for proposals [date]. Agency selected [date]. Project start [date]. Planned launch [date].
8. Phases
Proposals can follow your method or the agency’s. Describe the structure you expect, for example planning, requirements and specification, design, development, accessibility, testing and launch, and support and maintenance.
9. Instructions for the proposal
Describe the format, content, deadline and contact person.
Example: Send your proposal no later than [date] to [name, email]. Describe your company, reference projects, team, process, time estimate and price.
10. Evaluation criteria
Explain how the proposals will be assessed, for example experience, relevant case studies, method, team and total cost, and ideally how the criteria are weighted.
Example: We will choose the proposal that offers the best value for money. Everyone who has submitted a proposal will be notified by email.
Is an RFP for web development different?
Yes. An RFP for design is mainly about the visual side: layout, colour, typography and brand. An RFP for development is about technology: frameworks, CMS, architecture, integrations and hosting. In practice they often overlap. Be clear about what you are procuring now and what may come later.
How long does it take to write an RFP?
Allow one to four weeks depending on how complex the project is. Most of the time goes into gathering material and getting internal stakeholders aligned on goals and requirements – work that pays off later in the project.
Where do you send your RFP?
Send it to a selection of agencies that match the requirements – better five relevant ones than fifty random ones. Look at the agencies’ case studies and industry experience, and ask your network for recommendations. Public buyers advertise procurements above the direct award threshold in a procurement notice database.
Do you have an RFP ready, or would you like help defining the scope of the project? See how we work with digital projects and send the material to us.
Key insights
- 01
Comparable is the goal
The same material, the same questions and the same response format mean you compare proposals – not how good the agencies are at guessing.
- 02
Give a budget range
Without a budget you get proposals that range from a template to a platform. A range lets agencies propose the right level.
- 03
Explain how you will choose
Evaluation criteria set in advance give better responses and a decision you can justify internally.
- 04
The public sector follows LOU
Above the direct award threshold, different rules apply to how the tender is advertised and evaluated.
















