Every template ranking for "UX agency RFP" is built for agencies writing proposals—the selling side of the table. This one is for the buying side.
Below is a complete, copy-paste RFP with all ten sections, a filled example from a fictional SaaS company so you can see what good looks like, and the handful of rules that determine whether strong agencies take your request seriously. A well-built RFP gets you 5–6 comparable proposals inside two weeks; a vague one gets you quotes from €20,000 to €150,000 that can't be compared at all.
Short on time? Build a structured brief in 15 minutes with the Brief Builder—for projects under ~€15,000 it replaces an RFP entirely. Or download the hiring toolkit with an editable RFP template (PDF).
When You Actually Need an RFP
An RFP earns its overhead when you're comparing multiple agencies on an engagement of roughly €15,000 or more. Below that, a good brief sent to two or three agencies gets accurate quotes without the ceremony.
Here's the distinction in one line: a brief describes the project, and an RFP wraps that brief in the procurement layer that makes proposals comparable. Same project description at the core, plus four additions—a stated budget range, your evaluation criteria, a set of questions every agency answers, and a firm response deadline.
That wrapper is what turns five replies into an apples-to-apples decision. Without it, each agency scopes to a different assumption and quotes on a different basis, and you're left holding a €30,000 proposal next to a €90,000 one with no way to tell which is the better deal. The ceremony only pays for itself above a certain project size—but above that size, skipping it is exactly how buyers end up with proposals they can't read.
The Template
Copy everything in this section into a Google Doc or Notion page and replace the brackets.
1. Company & Project Context
- Company: [Name] — [industry], [stage and size, e.g. "Series A, 25 people"]
- What we do: [2–3 sentences: product, customers, market]
- Current situation: [New build / redesign / adding to existing product — link what exists]
- Why now: [The business trigger — funding, churn, launch, compliance]
2. Project Scope
- What needs designing: [Screens, flows, or product areas]
- Estimated size: [Rough screen/page count]
- Key user flows: [The 3–5 flows that matter most]
- Platforms: [Web desktop / mobile web / iOS / Android]
- Out of scope: [What you are explicitly NOT buying]
3. Users & Context
- Primary users: [Roles, demographics]
- Top use cases: [What users come to do]
- Existing research: [Interviews, analytics, surveys — attach or summarize]
- Markets & languages: [Countries, locales]
4. Goals & Success Metrics
- Business objective: [The one-sentence goal]
- Success metrics: [e.g. activation +X%, task time −X%, support tickets −X%]
- How we'll measure: [Analytics setup, baseline numbers]
5. Timeline & Budget
- Ideal start: [Date] — Target completion: [Date]
- Flexibility: [Hard deadline or flexible?]
- Budget range: [€X–€Y — state it; see why below]
6. Current Assets & Resources
- Brand: [Guidelines exist / need creation]
- Design system: [Exists / partial / none]
- Research done: [What exists]
- Development: [In-house team / outsourced / none yet]
7. Requirements & Constraints
- Must-haves vs nice-to-haves: [Split them]
- Technical constraints: [Stack, integrations, legacy]
- Accessibility: [e.g. WCAG 2.1 AA — required for most EU consumer products]
- Compliance: [GDPR, industry-specific]
8. Deliverables Expected
- Fidelity: [Wireframes / high-fidelity / both]
- Prototype: [Interactive prototype needed?]
- System: [Design-system components, documentation]
- Handoff: [Figma files, specs, developer support]
9. Questions for the Agency
- Who specifically will work on this project day to day?
- Walk us through your process on a comparable project.
- What's included in your quote—and what costs extra?
- What's your revision policy?
- Can you break the timeline down by phase?
- Can you share 2–3 references from similar-scope projects?
- How do you measure design success after launch?
- What will you need from us, weekly?
- What risks do you already see in this project?
- Why is this project a fit for you?
10. Evaluation & Timeline
- How we'll evaluate: [Your criteria and weighting]
- Proposal deadline: [Date — give 7–10 working days]
- Decision by: [Date]
- Expected kickoff: [Date]
How to Fill the Hard Parts
Most of the template is quick to complete. Three parts decide how useful your proposals come back—get these right and the rest takes care of itself.
Stating the budget
State a range. It's the single highest-leverage line in the document, and hiding it costs you more than it saves.
- ✅ "Our approved budget is €45,000–€65,000"
- ✅ "Budget is flexible around €50,000 depending on scope"
- ❌ "No budget constraints" (invites inflated quotes)
- ❌ "What's your best price?" (invites race-to-the-bottom work)
A stated range lets a professional agency scope honestly to your constraints—or tell you upfront that the fit isn't there, before either side sinks a week into it. The common fear, that agencies will simply pad their quote up to your ceiling, doesn't survive contact with reality: the ones worth hiring compete on value, and the ones who'd exploit an open budget are precisely the ones this screens out.
The no-spec-work rule
⚠️ Never ask for free spec work
"Do a quick design so we can see your ideas" is a red flag to exactly the agencies you want. Strong agencies decline spec work because it skips the strategy that makes design decisions defensible—so the ones who say yes are usually the ones reusing templates. If you want to test the working relationship, pay for a small discovery engagement (€2,000–€5,000) instead.
Questions that reveal the most
Section 9 of the template is where an agency's real character shows. Two questions predict the engagement better than any portfolio: "Who specifically will work on this day to day?" and "What's not included in the quote?"
The first flushes out the bait-and-switch, where a senior partner sells the work and a junior team delivers it. The second surfaces the exclusions—user research, testing, extra revision rounds—that quietly turn a tidy €48,000 quote into a real €61,000 one. Weak agencies answer both vaguely; strong ones answer both without flinching.
A Filled Example
Here's how sections 1–5 and 9–10 read once they're actually filled in. Meridian Fleet is invented—the company, the budget, and the metrics are all fictional—but the level of specificity is exactly what lets a strong agency quote accurately.
1. Company & Project Context. Meridian Fleet GmbH is a Berlin-based Series A B2B SaaS company, 25 people including 6 in-house developers. Its platform helps mid-sized logistics operators track vehicles, dispatch jobs, and schedule maintenance. The web app has grown feature by feature since launch and now feels bolted together; the redesign is driven by dispatchers being slow on it and churn creeping up as competitors ship cleaner tools.
2. Project Scope. A full redesign of the web app across desktop and mobile web—roughly 34 screens spanning four core flows: the live map, dispatch, maintenance scheduling, and driver communication. Native mobile apps are explicitly out of scope for this engagement.
3. Users & Context. Primary users are fleet dispatchers and operations managers working long shifts on desktop, with mobile as a secondary check-in. Meridian has six months of product analytics and eight recent dispatcher interviews to share. The UI ships in German and English.
4. Goals & Success Metrics. The objective is to make dispatchers measurably faster and cut the support load the current UI generates. Targets, measured against the current analytics baseline: dispatcher task time down 30%, support tickets down 20%, and product NPS from 31 to 45.
5. Timeline & Budget. Kickoff in about six weeks, running a 12-week engagement. The approved budget range is €45,000–€60,000.
9. Questions for the Agency. Who exactly will work on this day to day, and what's not included in the quote? How do you handle WCAG 2.1 AA and GDPR within a redesign like this?
10. Evaluation & Timeline. Relevant B2B SaaS experience and a clear process weigh most heavily. Proposals are due within ten working days, with Figma handoff and reusable design-system components expected at delivery.
Common RFP Mistakes
Five patterns account for most of the RFPs that agencies quietly move to the bottom of the pile:
Too vague to price. "We need better UX" gives an agency nothing to scope against—expect padded guesses, not real quotes.
No budget range. Hiding the number never gets you a lower price; it gets you proposals that can't be compared.
Sent to 20 agencies. A wide blast reads as a fishing expedition, and good agencies can tell when they're one of twenty.
Asking for free spec work. The agencies you most want will decline on principle, leaving you the ones who won't.
A 7-day deadline for everything. Too little time to scope forces guesswork—and signals to strong shops that the project isn't serious.
Timing and Logistics
Send the RFP on a Monday or Tuesday to five or six agencies—early in the week gives them room to read it and come back with questions before the weekend. Set the proposal deadline 7–10 working days out: shorter forces guesswork, much longer signals the project isn't a priority.
When questions come in, answer them to all bidders at once rather than only the agency that asked. It keeps the comparison fair and spares you from answering the same thing five times over. Pay attention to which questions get asked, too—the sharpest ones are free evaluation data. An agency that spots the gap in your analytics or the risk in your timeline before signing is showing you exactly how it runs projects.
RFP Timing TL;DR
- Send Monday or Tuesday to 5–6 agencies
- Give a 7–10 working-day proposal deadline
- Answer clarifying questions to all bidders at once
- Treat the quality of their questions as evaluation data
Time: 4–6 hours to write | Output: 5–6 comparable proposals
FAQ: Frequently Asked Questions
1. What's the difference between an RFP and a design brief? A brief describes the project—problem, users, goals, constraints. An RFP is a brief plus a procurement wrapper: budget range, evaluation criteria, questions for the agency, and a response deadline, sent to several agencies so their proposals arrive comparable. Under roughly €10,000–€15,000, a good brief alone is usually enough.
2. How many agencies should receive my RFP? Five or six. Fewer and you can't triangulate pricing; more and you can't give each response real attention—and good agencies can tell when they're one of twenty and deprioritize accordingly.
3. Should I state my budget in an RFP? Yes, as a range. 'Our approved budget is €45,000–€65,000' lets professional agencies scope honestly to your constraints or tell you upfront the fit isn't there. Hiding the number produces proposals from €20,000 to €150,000 that can't be compared—and it doesn't get you a lower price.
4. How long should agencies get to respond? 7–10 working days. Shorter forces guesswork; much longer signals the project isn't urgent. Send it Monday or Tuesday, answer clarifying questions during the week, and treat the quality of those questions as evaluation data—agencies that ask sharp questions tend to run sharp projects.
5. Do small projects need an RFP? No. For a landing page, an audit, or anything under about €10,000–€15,000, a structured brief sent to two or three agencies gets accurate quotes without the ceremony. Save the RFP for engagements where a mismatch is expensive.
Ready to Send It?
Short on time? Build your brief with the Brief Builder, grab the hiring toolkit, or follow the full 10-week hiring process.
Related Guides: