To win more agency RFPs, respond to fewer of them. Score every RFP against a written qualification scorecard within 24 hours, bid only on the ones that clear it, structure the response around the buyer's priorities instead of the question order, price transparently against your target margin, and debrief every outcome. Most of the gain comes from the bids you decline.
Some agencies swear off RFPs entirely; others build their pipeline around them. In practice, most RFPs are poor fits, a few are excellent opportunities, and a disciplined process is what tells them apart.
Key takeaways:
- Qualify every RFP with a written scorecard; responding to everything spreads senior time across bids you cannot win
- Make the bid decision in one short meeting with at least two senior people
- Some RFPs are written around a preferred vendor; learn the signals and invest accordingly
- Transparent pricing with stated assumptions is easier for evaluators to compare and trust than vague ranges
- Debrief every win and loss, and track your own win rate by qualification score
This guide gives you a complete RFP response framework: how to qualify, how to structure the response, how to price, and how to debrief whether you win or lose. It is written for agencies in the 5 to 100 person range that respond to anywhere from 6 to 60 RFPs per year.
The first question: Should you even respond?
The biggest leak in most agencies' new business process is responding to RFPs they had no realistic chance of winning. A full response can easily take dozens of hours of senior time. For example, 80 hours at a loaded senior cost of $120 an hour is $9,600 of time, before any travel for presentations. Spend that on the wrong opportunity and you have starved a winnable one.
Build a written qualification scorecard. Run every RFP through it within 24 hours of receipt. The scorecard should include:
- Budget fit (0 to 5). Is the budget disclosed or estimable? Does it match your minimum engagement size? Score 0 if budget is undisclosed and the project sounds like it could be under your floor.
- Capability match (0 to 5). Have you delivered this exact type of work three or more times? If not, you are competing against agencies that have, and they will write more credibly.
- Relationship signal (0 to 5). Have you talked to anyone at the company before the RFP arrived? Have you been through their procurement before? A cold RFP scores 1 or 2.
- Decision process clarity (0 to 5). Do you know who the decision maker is, what the timeline is, and how the evaluation will be scored?
- Strategic value (0 to 5). Would this client unlock a new vertical, geography, or case study you have been chasing?
- Competitive position (0 to 5). How many other agencies are invited? Six or fewer is workable; twelve plus usually is not.
If your total is under 18 out of 30, do not respond. If it is 18 to 22, respond only if you have idle senior capacity. Above 22, treat it as a priority pursuit.
Spotting the pre-wired RFP
Some RFPs are issued with a preferred vendor already in mind, and the process exists to satisfy procurement rules. In Forrester's 2024 Buyers' Journey Survey, 41% of B2B buyers already had a single preferred vendor before formal evaluation began (Digital Commerce 360, 2025). Common signals include:
- The questions read like they were written by someone deeply familiar with one specific agency's services
- Required certifications or partnerships are extremely narrow
- The timeline for response is unusually short (under 7 business days)
- The buyer refuses or limits clarifying questions
- The scope is described in oddly specific tooling or workflow terms
When you see two or more of these signals, your odds drop sharply. That does not always mean walk away, but it should change how you invest. Submit a strong but lean response, do not fly the team out, and do not spend 120 hours on it.
The 90-minute bid decision meeting
Once an RFP clears the scorecard, schedule a 90-minute bid decision meeting within 48 hours. Required attendees: the senior account or business development lead, a senior craft lead (creative director, head of strategy, or technical lead), and someone with finance authority. The agenda:
- Read the RFP aloud together (20 minutes). This forces alignment and surfaces ambiguity.
- Score against the qualification framework (15 minutes).
- Identify the three things this RFP is really about (20 minutes). Buyers rarely tell you their actual priorities. Read between the lines.
- Decide pricing posture (20 minutes). Premium, market, or aggressive?
- Confirm bid or no-bid and assign owners (15 minutes).
The output is a one-page bid plan with the win theme, owner, hours budget, and submission deadline.
Structuring the response
Many RFP responses fail because they answer the questions in order rather than telling a coherent story. Buyers reviewing a stack of responses skim. They look at the cover letter, the executive summary, the team page, the case studies, and the price. Everything else is reference material.
Structure your response in this order:
1. Cover letter (1 page)
Address it to the named decision maker. Open with a single sentence that names the buyer's most important business outcome. Reference one specific detail from the RFP that proves you read it. Sign it from a partner or principal, not the new business coordinator.
2. Executive summary (2 pages)
State the buyer's challenge as you understand it. State your recommended approach in three to five bullets. State the expected outcomes. State your investment range. This is the only page some evaluators will read.
3. Strategic approach (4 to 8 pages)
This is where you demonstrate thinking, not just experience. Walk through how you would approach the work in three or four phases. For each phase, name the activities, the deliverables, the team involved, and the timeline. Include one diagram or framework. Avoid jargon.
4. Case studies (3 to 5 examples)
Pick case studies that match the buyer's industry, scale, or challenge type. Each case study gets one page: client, challenge, approach, results with hard numbers, and a quote. Do not include 14 case studies; it dilutes signal.
5. Team and capabilities (2 to 3 pages)
Name the actual humans who will work on the account, not stock bios. Include their last three relevant projects and a sentence on why they fit. Buyers want to know who they will be on a Tuesday afternoon call with.
6. Investment (2 pages)
Pricing transparency wins more often than vague ranges. Show fee structure, what is included, what is excluded, and assumptions. If you offer options (good, better, best), keep it to three.
7. Process, tools, and governance (1 to 2 pages)
How you collaborate matters. Describe your project management cadence, communication rhythm, reporting, and tools. If you use a client portal or structured client reporting system, name it.
8. References and appendix
Three references with permission to be contacted. Optional appendix with detailed bios, security policies, or insurance certificates.
If the RFP sets a page or word limit, follow it exactly. If it doesn't, keep the core response tight (often 15 to 30 pages for larger engagements) and move supporting material to the appendix. Evaluators reward clarity, not volume.
Pricing strategy in RFPs
Pricing is where many agencies underperform. The instinct is to price low to win, but evaluators often read a price far below the others as a sign of inexperience, a misunderstood scope or change orders to come.
Three pricing approaches that work:
Anchored fixed fee. Best when the scope is well defined. State the total, name the assumptions, and detail what is and is not included. This fits most RFPs with a clear scope.
Phased with go/no-go gates. Best for complex or strategic work. Phase 1 is a discovery or strategy sprint at a defined fee. Subsequent phases are scoped and priced after Phase 1 deliverables. This reduces buyer risk and surfaces scope realities early.
Retainer plus project. Best when the engagement is partly ongoing. Define the retainer scope precisely and bill projects against it. Read more on retainer vs project pricing.
Use the project pricing calculator and the profit margin calculator to sanity-check your pricing against your target margins before submission. A common mistake is pricing the work without checking it still meets your target project margin after fully loaded delivery costs.
The oral presentation
Many RFPs include a shortlist presentation, and this is often where the decision is made.
Rules that consistently work:
- Present with the team that will do the work. Not just the partners. Buyers want to meet the actual senior practitioners.
- Spend the first half on the buyer. Recap what you have learned about their business. Ask three sharp questions. Show you have done homework.
- Show work, not slides. Bring a short worked example, a draft strategy, or a live walk-through of something relevant.
- End with the team they will work with on a Tuesday. Not the org chart, the actual humans.
- Time the presentation to the time allotted. Going over by 4 minutes signals you cannot manage scope.
The debrief: Win or lose
Most agencies skip the debrief. This is the single highest-leverage thing you can do to improve win rate.
If you win, ask the buyer in writing: what made the difference, what almost cost you the deal, and which of the other agencies came closest. Capture this in your CRM.
If you lose, request a 20-minute call. Ask: who won, why, what would have changed your odds, and how the response compared to others. Ask within a week, while the evaluation is fresh; many buyers will give a candid answer if you make it easy.
Track the patterns. Over 12 months, you will see which qualification signals were most predictive, which case studies actually moved buyers, and which pricing structures won.
Building an RFP response function
If you are responding to more than 20 RFPs per year, build a small function to support it:
- A maintained library of case studies, bios, security documents, and reusable response sections
- A scoring template stored in your CRM
- A central repository of past responses (win and loss) tagged by industry and scope
- A standing 30-minute Friday review of in-flight RFPs
- Quarterly analysis of win rate by qualification score, industry, and pricing structure
Treat RFPs as a portfolio, not a stream of one-off responses. The compounding effect of qualification discipline, response quality, and structured debriefs will move your win rate further than any single response innovation.
When to walk away
Three situations should prompt a no-bid even if the scorecard is favorable:
- The procurement process explicitly forbids any pre-RFP contact and the response window is under 7 business days
- The buyer requires you to pay a fee to participate or assigns onerous IP terms before contract
- The scope is unclear and the buyer refuses to clarify in writing
Walking away costs nothing. Bidding on a poor-fit RFP costs senior time, team morale, and the focus you needed for a winnable opportunity.
Bringing it together
A high-functioning RFP function looks like this: every RFP scored within 24 hours, bid decisions made in 90-minute meetings, responses structured around buyer priorities, pricing anchored to target margins, oral presentations led by the team who will do the work, and debriefs captured for every outcome. Agencies that work this way spend less time on bids they were never going to win and more on the ones they can.
To build this alongside your broader pipeline, see the agency new business process guide. For writing proposals outside RFPs, see AI proposal generation for agencies.
Frequently asked questions
What is a typical RFP win rate for an agency?
There is no reliable public benchmark for agency RFP win rates. Across industries, Loopio's RFP benchmarks (2026) put the average win rate at 45% for 2019 to 2026, but that figure covers proposal teams in every industry, not agencies specifically. Track your own: win rate by qualification score, industry and pricing approach. A low win rate usually points to weak qualification (responding to RFPs you cannot win) before it points to weak writing. A very high win rate on RFPs can mean you are declining too many good ones, or only bidding where you were already the favorite.
Should agencies always respond to RFPs?
No. Disqualify any RFP where you don't know the buyer, the incumbent has a clear advantage, the budget is unrealistic, or the timeline doesn't match your capacity. A full response takes dozens of hours of senior time; chasing unwinnable RFPs is one of the most expensive mistakes in new business.
How long should an RFP response be?
Match the page count or word count the RFP specifies. If it is unspecified, keep the core response short enough to read in one sitting (often 15 to 30 pages for large engagements, less for smaller ones) and put supporting material in an appendix. Lead with an executive summary that addresses their stated priorities directly.
How do you price an RFP without giving away too much?
Provide ranges or fixed prices for the requested scope, and clearly state assumptions and exclusions. Avoid giving detailed hourly breakdowns; clients use those to negotiate or reverse-engineer your team rates. Anchor pricing to outcomes, not effort.
Should agencies attend RFP debriefs?
Always request a debrief regardless of outcome. Wins teach you what worked; losses teach you what to fix. Not every buyer will agree, so ask early and keep it short, then track patterns across debriefs to find the changes that matter.
Want your pipeline and proposals in one place? AgencyPro's leads pipeline and Documents (quotes, proposals and contracts with e-signatures) are on the Pro plan and above. See plans or book a demo.