The most expensive mistake in a website redesign isn’t what you build, it’s how you buy it. Most web design RFPs are written to procure deliverables (40 pages, 6 templates, a CMS) and invite agencies to compete on price for work AI is making cheap. Then the buyer is surprised when the site looks fine in stakeholder presentations but produces nothing six months after launch.
Key Takeaways
A web design RFP that gets results defines business objectives before deliverables, evaluates process over portfolio, and asks how success will be measured post-launch. Skip page counts. Ask what the agency needs to know about your buyers, how they’ll validate assumptions during discovery, and what changes if conversion rates stay flat three months after go-live. The agencies that can answer those questions are the ones worth talking to.
Why Most Web Design RFPs Attract the Wrong Agencies
A typical web design RFP reads like a procurement document for office furniture. It lists pages, templates, integrations, and launch dates. Agencies respond with polished decks, beautiful portfolios, and line-item pricing. The selection committee picks the prettiest work at the best price, everyone shakes hands, and nine months later the site launches to crickets.
The problem is structural, not incompetence. When you ask agencies to bid on deliverables, you get agencies optimized to deliver pages fast and cheap. When you ask them to compete on portfolio aesthetics, you get agencies optimized to win awards, not drive pipeline.
Get the Toolkit
How to Create an RFP That Gets You a Website That Works
The RFP itself shapes who responds and what they optimize for. If your RFP specs 40 pages and six templates, you’ll attract agencies built to deliver exactly that and nothing more. If it asks how the agency validates buyer intent or measures content performance, you’ll attract different firms entirely.
The stakes are higher than they used to be, because the site is now doing most of the selling. 6sense’s 2025 Buyer Experience Report, based on a global study of nearly 4,000 B2B buyers, found that buyers make first contact with a vendor roughly 61% of the way through their buying journey, and that 95% of the time the eventual winner was already on the buying group’s day-one shortlist. Four out of five deals go to the vendor the buyer already favored before any conversation happened. Your website is not a brochure that supports the sales conversation. It is the thing that decides whether the sales conversation happens at all. An RFP that treats it as a design deliverable is mis-scoping the asset.
What to Actually Ask For in a Web Design RFP
Start with business objectives, not page counts. What needs to change about how your site performs? More qualified leads? Faster deal cycles? Better close rates from organic traffic? Lower cost per acquisition? If you can’t articulate what success looks like in business terms, the agency can’t design toward it.
Define the problem you’re solving, not the solution you think you need. “Our site doesn’t reflect where the business is going” is useful. “We need a rebrand and 50-page site refresh” is premature. The best agencies will challenge your assumptions during discovery; the worst will build exactly what you asked for and collect their check when it doesn’t work.
Ask what the agency needs to understand before they can propose a solution. Buyer personas? Conversion funnel data? Competitive positioning? Content audit findings? Win/loss interview insights? If an agency can propose a site architecture without asking those questions, they’re guessing. A discovery-led web design process should generate more questions in week one than answers.
Include evaluation criteria that predict performance, not just aesthetics. How will the agency validate that the new information architecture matches how buyers actually navigate decisions? What does their QA process look like? How do they handle post-launch performance tracking? What happens if organic traffic or conversions drop after launch?
Ask specifically about search and AI visibility. A redesign that changes URLs without a redirect map can erase years of accumulated ranking equity in a single deploy, and that is one of the most common ways a “successful” redesign quietly destroys value. Ask who owns the redirect map, who audits it post-launch, and how the agency approaches SEO and answer engine optimization as part of the build rather than as a phase-two add-on.
The Questions That Separate Strategic Partners from Page Factories
The best signal of whether an agency will deliver results or deliverables is how they respond to open-ended questions about process and measurement. Include these in your RFP and evaluate answers carefully.
How do you approach discovery, and what do you need from us to do it well? Weak answer: “We’ll run stakeholder interviews and a content audit.” Strong answer: “We’ll need access to your CRM data, win/loss insights, GA4 behavioral flow reports, and at least three customer interviews. We can’t design a site that converts without understanding why deals close or stall.”
What assumptions are you making about our buyers, and how will you validate them? Weak answer: “We’ll create personas based on your input.” Strong answer: “We’re assuming your buyers research independently before they talk to sales, but we’ll validate that by analyzing entry pages, time-on-page for key content, and whether demo requests come from first-time visitors or return traffic.”
How do you define success for this project, and how will you measure it post-launch? Weak answer: “A site that reflects your brand and is easy to update.” Strong answer: “Three months post-launch, we’ll compare organic traffic, conversion rate, and cost per lead to pre-launch baseline. If any of those metrics decline, we’ll have a punch list ready to address it.”
What happens if the site performs worse after launch than before? This question reveals whether the agency views the project as a handoff or a partnership. Weak answer: silence or deflection. Strong answer: “We include 90 days of post-launch optimization in every engagement. If traffic or conversions drop, we’ll prioritize diagnosing why and fixing it before we consider the project complete.”
How will you protect our existing search rankings during migration? Weak answer: “We’ll set up redirects.” Strong answer: “We’ll crawl the current site, map every ranking URL to its new destination, build a one-to-one redirect map with no chains, and monitor Search Console for coverage errors and ranking drops for at least 60 days post-launch.”
When 7Factor Software needed to position as a strategic consulting partner rather than an order-taking vendor, Blennd restructured their site around buyer evaluation patterns and rebuilt case studies as a proof engine, which drove form submissions up 467% and moved average ranking position from 23 to 10.6.
How to Structure Your Web Design RFP for Better Responses
Organize the RFP in three sections: context, objectives, and evaluation criteria. Context explains where the business is, where it’s going, and why the current site no longer supports that. Objectives define what needs to change in measurable terms. Evaluation criteria explain how you’ll compare responses.
Context section: include company overview, target audience, competitive landscape, current site performance (traffic, conversions, bounce rate, top entry/exit pages), and why you’re considering a redesign now. The more context you provide, the better the proposals will be. Agencies that ask clarifying questions during the RFP period are signaling they actually read it.
Objectives section: define success in business outcomes, not deliverables. “Increase qualified leads from organic search by 40% within six months of launch” is an objective. “Build a mobile-responsive site with 50 pages and a blog” is a deliverable. You can have both, but lead with outcomes. If you don’t know what good looks like numerically, say that and ask agencies to help you set benchmarks during discovery.
Evaluation criteria section: explain how you’ll score responses. Will you weight process and approach over portfolio? Strategy over price? Post-launch support over speed to launch? Be explicit. If cost is a major factor, say so upfront so agencies can propose phased approaches or scaled-down scopes. If you care more about strategic fit than speed, make that clear so agencies invest in thoughtful responses instead of fast ones.
Include a section on what you will NOT evaluate on, which helps filter out mismatched agencies early. Example: “We will not select based solely on portfolio aesthetics, lowest cost, or fastest delivery timeline. We will prioritize agencies with a documented discovery process, post-launch optimization commitment, and experience working with B2B brands in [your industry or growth stage].”
Step-by-Step: Writing a Web Design RFP That Gets Strategic Responses
Step 1: Define what needs to change and why. Start by auditing your current site’s performance. Which pages drive conversions? Which drive traffic but no pipeline? Where do visitors drop off? What’s your bounce rate on key landing pages? Use GA4, heatmaps, and CRM data to build a factual picture of what’s working and what isn’t. If you don’t have this data, say so in the RFP and ask agencies how they’d gather it during discovery.
Step 2: Write objectives in terms of business outcomes. Translate site problems into business goals. If your bounce rate on service pages is 75%, the objective isn’t “redesign service pages.” It’s “reduce service page bounce rate to under 50% and increase contact form submissions from service pages by 30% within 90 days post-launch.” Specific, measurable, time-bound.
Step 3: Specify what you need from the agency, not what you think the solution is. Instead of “We need 50 pages, 6 templates, and a blog,” write “We need a site architecture that helps buyers self-identify their needs, a content strategy that supports organic discovery for [specific topics], and a CMS our team can manage without developer support.” This gives agencies room to propose better solutions than you’d spec on your own.
Step 4: Include open-ended strategy questions in the RFP. Ask how they approach discovery, what data they need, how they validate assumptions, and how they measure success post-launch. Evaluate the quality of these answers as heavily as you evaluate portfolio work. An agency with average design work and a rigorous process will outperform an agency with a beautiful portfolio and no discovery rigor.
Step 5: Define your evaluation criteria and weighting upfront. If strategic fit is worth 40% of your decision, process rigor is 30%, cost is 20%, and portfolio is 10%, say that in the RFP. Transparency attracts better-matched responses. Agencies that know you prioritize process over price will invest in explaining their approach instead of just sending a deck.
Step 6: Set a realistic timeline and budget range (if possible). Agencies can propose better solutions if they know whether you’re working with a $50K budget or a $250K one. If you can’t share budget, at least share timeline and scope constraints. A six-month timeline with a discovery phase will attract different firms than a six-week “refresh and launch” project.
Step 7: Ask for a migration and measurement plan, not just a build plan. Require every respondent to describe how they will preserve existing rankings, what analytics and attribution they will implement, and what they will monitor for the first 90 days after launch. This single requirement filters out more page factories than any other question in the RFP.
Red Flags in Agency Responses to Your Web Design RFP
Some responses reveal misalignment before you ever get on a call. Watch for these warning signs.
Proposals that skip discovery entirely. If an agency can propose a full site architecture, page count, and design direction without asking follow-up questions, they’re guessing. Good agencies will request a discovery kickoff or list the questions they need answered before they can propose a solution confidently.
Responses that compete primarily on speed or cost. “We can deliver this in half the time for 30% less” often means “We’ll reuse templates, skip research, and hand you a site that looks fine and converts poorly.” Faster and cheaper is occasionally legitimate (if scope is genuinely smaller), but if it’s the lead selling point, be skeptical.
Portfolios with no performance data. Beautiful screenshots prove design capability, not business impact. If an agency’s case studies don’t mention traffic, conversion rate, lead volume, or revenue outcomes, you have no evidence the sites they built actually work. Ask for performance data during the evaluation process.
Vague answers to process questions. If you ask “How do you validate buyer intent?” and the answer is “We run user testing,” that’s not an answer. What kind of testing? With whom? What hypotheses are you testing? How do findings change the design? Vague answers suggest the agency doesn’t have a real process, just buzzwords.
No mention of post-launch support or optimization. If the proposal ends at launch with no discussion of monitoring, performance tracking, or iteration, the agency views this as a project, not a partnership. The best agencies know that launch is the beginning of performance work, not the end. Ask whether they offer ongoing maintenance and support and what it actually covers.
When KIOSK Information Systems shifted toward a product-led sales model, Blennd rebuilt their site with an eCommerce-like browsing experience and stronger conversion paths, lifting SQL quality so that 50% of leads became sales-qualified and the company hit 157% of its SQL goal for the year.
How to Evaluate Competing Proposals Fairly
Create a scoring rubric before you read responses. Weight each evaluation criterion (strategic fit, process rigor, cost, timeline, portfolio quality, post-launch support) and score each proposal numerically. This reduces bias and prevents the prettiest deck from winning by default.
Compare agency responses to your open-ended questions side by side. Which agencies asked clarifying questions during the RFP period? Which proposed discovery phases before committing to solutions? Which included measurable success criteria in their proposals? These process signals often matter more than portfolio aesthetics.
Request case studies with performance data, not just screenshots. Ask: what were the business goals? How did the agency measure success? What changed post-launch in terms of traffic, conversions, or revenue? If the agency can’t provide this for past work, they likely won’t do it for yours.
Interview finalists about scenarios, not just credentials. Present a real challenge your site faces (for example, “Our service pages rank well but convert poorly; how would you diagnose that?”) and evaluate how they think through the problem. Agencies that ask follow-up questions before proposing solutions are demonstrating the curiosity you want in a partner.
Check references, but ask better questions than “Were you happy with the work?” Ask: Did the site perform better post-launch than before? Did the agency deliver on time and budget? What surprised you (good or bad) about working with them? Would you hire them again for a different project? These questions reveal more than generic satisfaction ratings.
What to Leave Out of Your Web Design RFP
Don’t spec deliverables you’re not confident you need. If you’re not sure whether you need 40 pages or 60, don’t lock in a number. Let the agency propose what’s appropriate based on your goals and content. Locking in deliverables prematurely often leads to bloated sites with pages that exist to meet contract terms, not user needs.
Don’t ask for creative concepts in the initial RFP response. Agencies that invest in speculative design work before understanding your business are either desperate for work or bad at scoping. The best agencies will propose a process to get to creative direction (discovery, stakeholder alignment, moodboarding), not show up with unsolicited mockups.
Don’t require references from your exact industry unless domain expertise is genuinely critical. A great agency that’s worked with SaaS companies can likely serve a fintech company well, even if they haven’t done fintech specifically. Overweighting industry experience often eliminates stronger generalist agencies. That said, some verticals genuinely do have distinct buyer behavior and compliance constraints, which is why we maintain dedicated practices in areas like fitness and wellness and functional medicine rather than pretending every industry is the same.
Don’t make cost the tiebreaker unless budget is genuinely the constraint. If two agencies score equally on strategy, process, and fit, and one is 15% cheaper, the cheaper one isn’t automatically better. Ask why the cost differs; it might be less discovery, fewer revisions, or no post-launch support.
If you want the strategic case for why redesign budgets should be aimed at positioning and measurement rather than page production, we made it here: B2B Website Redesign: Stop Solving the Wrong Problem.
Frequently Asked Questions
Should I include our budget range in the web design RFP?
Yes, if possible. Sharing a realistic budget range helps agencies propose solutions that fit your constraints and eliminates mismatched responses. If you’re working with $75K, you don’t want proposals for $200K enterprise builds or $20K template sites. If you can’t share an exact number, share a range or at least scope constraints (for example, “We’re a mid-market B2B company; we’re not looking for enterprise-scale solutions but we’re also not looking for the lowest-cost option”).
How do I evaluate agencies if I don’t have technical expertise?
Focus on process and communication, not technical jargon. A good agency will explain their approach in business terms you understand. If an agency hides behind technical complexity or can’t explain why their CMS recommendation matters for your goals, that’s a red flag. You don’t need to understand React vs. WordPress; you need to understand how the platform choice affects cost, flexibility, and your team’s ability to manage content post-launch.
What’s a reasonable timeline for a web design RFP process?
Two to four weeks for RFP responses, one to two weeks for evaluation, one week for finalist interviews, and one week for final selection. Shorter timelines favor agencies with templated responses; longer timelines attract more thoughtful proposals. If you’re asking for custom strategy in responses, give agencies time to deliver it.
How much should I weight portfolio quality versus process rigor?
For most B2B companies, process rigor should outweigh portfolio aesthetics. A beautiful portfolio proves design capability but not business impact. Process rigor (how the agency approaches discovery, validates assumptions, measures success) predicts whether the site will perform. If you’re in a visually-driven industry (consumer brand, hospitality, luxury), weight portfolio higher, but even then process matters more than most buyers realize.
Can I use this same approach for other marketing RFPs?
Yes. The principles (define outcomes before deliverables, evaluate process over portfolio, ask how success will be measured) apply to SEO, paid media, content strategy, and demand generation RFPs. The specific questions will differ, but the structure (context, objectives, evaluation criteria, open-ended process questions) works across disciplines.
What if no agencies respond with strong answers to the strategy questions?
That’s a signal the RFP attracted the wrong pool, not that good agencies don’t exist. Revisit where you distributed the RFP, whether the timeline or budget was realistic, and whether the evaluation criteria favored process-driven firms. You may need to extend the timeline, adjust scope, or go directly to agencies with proven track records in your space rather than relying on open RFPs.
Sources
- The B2B Buyer Experience Report 2025. 6sense, 2025. (Global study of nearly 4,000 B2B buyers; point of first contact at 61% of the journey, 95% of winners on the day-one shortlist.)
Planning a website redesign and need a partner who asks the right questions first?
Blennd’s web design process starts with discovery, not deliverables. We work with B2B brands to build sites that support pipeline, not just traffic. If you’re evaluating agencies or writing an RFP, we can help you ask better questions and avoid the assumptions that predict disappointing outcomes.
