An RFP, or request for proposal, is a short document that describes your project and asks studios to respond with their approach, timeline and cost. For creative work it doubles as a brief: it explains the goal you're achieving, who it's for, and what success looks like, so everyone answers the same question.
It's worth writing one whenever you're comparing more than one studio, coordinating several people on your team, or scoping a project big enough that a vague email would lead to vague quotes. For a small, well-understood task, a short conversation is usually enough, so don't turn a one-page need into a ten-page document.
02
Why a good RFP helps
A clear brief does more than save time. It changes the quality of what comes back to you.
Comparable proposals
When every studio answers the same brief, you can compare approach, scope and price side by side instead of guessing at what each one assumed.
An aligned team
Writing the RFP forces your own team to agree on goals and constraints before outside partners get involved, so you speak with one voice.
A faster process
Studios spend less time chasing missing details, which means you get thoughtful responses sooner and move to a decision faster.
More accurate scope
The more context you provide, the fewer assumptions a studio has to make, so estimates reflect the real work instead of a hedge against the unknown.
A better partner fit
A brief that states your goals, audience and constraints helps you see how each studio thinks, not just what it charges.
03
Mistakes that make proposals impossible to compare
Most of the time proposals don't line up because the brief left too much open. These are the gaps that cause it.
No clear outcomes
Listing tasks without saying what success looks like leaves studios guessing at your real goal, and pricing for different targets.
No budget signal
Hiding the budget entirely usually backfires. Even a range helps studios propose the right scope instead of over- or under-shooting.
Vague scope
"A new website" can mean five pages or fifty. Undefined scope produces estimates that can't be compared because they cover different work.
No evaluation criteria
If you don't say how you'll decide, studios optimize for the wrong things and you're left comparing on price alone.
No single point of contact
When questions have nowhere to go, studios fill the gaps with assumptions. Name one person who can answer them.
Inconsistent questions
Asking each studio for something slightly different guarantees responses you can't lay side by side. Ask everyone for the same format.
04
What to include in your RFP
You don't need every field below for every project, but each one removes a question a studio would otherwise have to guess at. Use the ones that fit your work.
01
About your organization
A few lines on who you are, what you do, and the market you operate in. It gives context for every decision that follows.
02
Project background
Why this project exists now. Describe what prompted it and anything that's already been tried.
03
The objective
State the core objective in plain language. Focus on the need, not a preferred solution, so studios can propose the best approach.
04
Goals and objectives
What you want the project to achieve, and how you'll know it worked. Be specific about the change you're after.
05
Target audience
Who this is for, whether customers, users, or internal teams. Note languages, regions or cultural context if they matter.
06
Scope of work
The boundaries of the project: what's included, what's explicitly out, and where phases might split.
07
Deliverables
The concrete things you expect to receive, such as files, pages, assets or guidelines, and any formats you require.
08
Content and assets
What already exists, such as copy, photography or brand guidelines, and what needs to be created from scratch.
09
Features and functionality
For web or product work, the specific capabilities you need, such as accounts, checkout, search or forms, so technical effort is clear.
10
Integrations
Any systems the work must connect to, such as a CMS, ecommerce platform, CRM or analytics tools.
11
Accessibility and standards
Accessibility targets, performance expectations, or brand and legal standards the work must meet.
12
Roles and who's involved
Who's involved on your side, who approves, and who the studio should work with day to day.
13
Timeline and milestones
Key dates, launch windows and any fixed deadlines. Flag what's firm versus flexible.
14
Budget
A budget or range. It isn't a ceiling to defend; it's the fastest way to get scope that fits what you can spend.
15
Evaluation criteria
How you'll compare responses, whether by approach, relevant experience, timeline or price, and roughly how you'll weigh them.
16
Submission and process
How and when to respond, what format you want, key dates in your decision process, and where to send questions.
05
How to write your RFP
01
Align internally first
Before writing a word, get your team to agree on the goal, the budget range and the deadline. An RFP can't paper over internal disagreement.
02
Frame the context
Open with who you are and why the project exists now. Give studios enough background to understand the decisions behind the work.
03
Define the outcomes
Write down what success looks like in concrete terms. This is the section that keeps every proposal focused on the same goal.
04
Scope the deliverables
List what you expect to receive and where the boundaries are. Be explicit about what's out of scope.
05
Set the constraints
Share your timeline, budget range, required integrations and any standards. Constraints make estimates realistic.
06
Define how you'll decide
State your evaluation criteria so studios know what matters most and you can compare responses fairly.
07
Review and distribute
Have a colleague read it for gaps, then send the same document to every studio with a clear deadline and a single contact.
06
Quick checklist
Before you send your RFP, make sure it answers each of these.
—You've introduced your organization and market
—You've explained why the project exists now
—You've defined clear, measurable goals
—You've described the target audience
—You've stated what's in and out of scope
—You've listed the deliverables and formats
—You've noted required integrations and standards
—You've shared a budget or range
—You've included key dates and milestones
—You've explained how you'll evaluate proposals
—You've set a submission format and deadline
—You've named a single point of contact
Free resource
Download the RFP template
The template is a ready-to-use document with every section above laid out as prompts and examples. Fill in what fits your project, delete what doesn't, and send it out. It's fully editable, so you can adapt it to branding, web, video or campaign work.
Frequently asked questions
What's the difference between an RFP and a creative brief?
They overlap. An RFP formally invites studios to propose and usually covers process, timeline and budget; a creative brief focuses on the context, audience and goals. For creative work, a good RFP includes the brief inside it, which is how this template is built.
When should I use an RFP?
Use one when you're comparing more than one studio, coordinating several people, or scoping a project large enough that a loose email would lead to loose quotes.
When is an RFP overkill?
For a small, well-understood task where you already know who you're working with, a short conversation or a one-page brief is usually enough. Don't turn a simple need into a formal process.
How long should an RFP be?
As long as it needs to be and no longer. Cover the sections that apply to your project clearly, and skip the ones that don't. Most fit comfortably in a few pages.
Do I have to share a budget?
You don't have to, but sharing a range helps. It lets studios propose scope that fits what you can spend instead of guessing, and it makes the proposals you get back far easier to compare.
Related Solutions
Brand & Identity
A brand identity your team can apply without the original designer in the room.
