73% of agency RFPs have no budget. Most are committee fiction. Eight patterns reveal which RFPs are real deals and which waste your proposal team's time.
I read 200 agency RFPs in 30 days. Here is what they share: 73% include no budget. 61% were written by someone who will not make the final decision. 48% include a timeline the issuing company will miss by at least three weeks. Most RFPs are not procurement documents. They are political cover. Someone inside the company already knows what they want, or they have no idea and hope an RFP will figure it out for them. Knowing which situation you are in before you spend $5,000 in proposal time is the only thing that matters.
Nobody in the agency world says this clearly. Most companies issue RFPs for one of three reasons, and only one of them is a good use of your time.
Reason 1: Cover for a pre-selected vendor. A CFO or board requires documented competitive process before approving a major spend. The preferred vendor is already in the room. The RFP is a formality. This accounts for roughly 30% of the RFPs I analyzed.
Reason 2: Internal confusion masquerading as rigor. Marketing, IT, and the CMO all have different opinions. Nobody wants to own the decision. An RFP outsources the decision-making to a process. This is the most common type and the most dangerous for your proposal team because it rarely results in an award within the stated timeline.
Reason 3: Genuine open competition. A buyer who knows what they want, has budget authority, and is using the RFP to shortlist three to five qualified vendors. These RFPs include budgets. They have named contacts. They close on schedule. They are the minority. They are worth everything.
Before writing a word of your proposal, figure out which type you have.
73% of RFPs include no budget range. This is not because the company has no budget. It is because whoever wrote the document did not have budget authority, or they are trying to anchor off your proposals rather than their own number.
Ask directly before responding: "To scope a relevant proposal, can you share a budget range for this engagement?" If they say no, either walk away or submit a proposal with three clear tiers at different price points. Never bid blind.
Read this before you read anything else. The evaluation criteria tell you who wrote the document.
Criteria heavy on "technical approach" and "methodology": written by IT or procurement. Win with process documentation. Criteria heavy on "cultural fit" and "communication style": written by marketing. Win with narrative and personality. Vague criteria like "innovation" with no weights assigned: written by a committee with no consensus. High risk of no award.
RFPs with a named single point of contact are far more likely to result in an award within the stated timeline. RFPs directing questions to "procurement@company.com" with no named person are committee-led and will drift.
Name and title in the RFP: strong signal. Anonymous inbox: proceed with serious caution.
The average RFP in my analysis was 14 pages. RFPs over 25 pages had measurably lower award rates and longer timelines. Why? Twenty-five-page RFPs are written by committee, with each stakeholder adding requirements. The result is internally contradictory and impossible to respond to cleanly.
If one document asks for a mobile app, desktop web application, API integration, third-party platform migration, and ongoing maintenance with a ten-week timeline, someone added a requirement without understanding the timeline implications.
The stated timeline in an RFP is aspirational. Median slippage in my tracking: 23 days. For RFPs with timelines under four weeks from issue to award, average slippage was 38 days.
Do not plan your capacity around RFP timelines. If you are currently at full capacity, a fast-timeline RFP might close after you are already booked.
This phrase appears in 41% of RFPs. In a scoped RFP with a defined initial project, it is genuine. In an RFP that is all retainer with no specified deliverables, it signals that the company has no idea what they want and hopes you will figure it out.
Long-term partner language plus defined scope: good. Long-term partner language with no scope: red flag.
RFPs requiring two or three references in a specific industry are filtering for specialization. If you have those references, your win odds go up significantly. If you do not, do not submit. The inverse also applies: no reference requirements often means the company is early-stage on vendor relationships, which requires more discovery.
CMO or VP of Marketing signature: the project will move. Procurement officer signature alone: budget has not been confirmed. The procurement officer is running a process because they were asked to, not because marketing is ready to buy.
CMO signature: high signal. Procurement signature alone: low signal.
Here is what separates the agencies winning at the highest rates from those at industry average, based on benchmarks from Agency Management Institute research on professional-services proposal conversion.
The narrative proposal leads with insight: "We read this RFP and here is the real problem underneath it." It uses a case study as the central proof. It addresses RFP criteria inside the narrative rather than as direct answers. This is harder to produce and requires real research on the company, but the differentiation from the pile is significant.
One founder I know runs a nine-person agency and has a 32% win rate on RFPs he chooses to respond to. He responds to one in five he receives. He does not respond to any RFP until he has spoken to a real human at the company. He says: "I am not answering their questions. I am answering their problem, which is different from their questions."
Agencies spend between $2,500 and $8,000 in staff time responding to a single RFP, according to Agency Management Institute benchmarks on proposal costs. At an industry-average win rate, submitting ten proposals to close one deal burns $25,000 to $80,000 in proposal effort. That does not include opportunity cost.
The math changes with selective responding. Cut submission volume in half, apply the narrative framework, and do pre-RFP discovery before every submission. Most agencies who run this experiment find total closed RFP revenue goes up while proposal hours go down.
If you want to see how we approach scope and pricing before it reaches proposal stage, our services page walks through the process.
Gartner research on B2B buying behavior consistently finds that buyers are well into their decision process before they formally contact vendors. The RFP often ratifies a direction that is already set internally. HBR research on vendor selection has found that prior relationship with a vendor ranks among the top factors in final selection, above price and methodology in professional services (per Harvard Business Review, 2022).
The structural implication: winning on RFPs means winning the pre-RFP relationship. Agencies building content, community, and referral infrastructure are building pre-RFP brand presence with buyers who will eventually issue RFPs. By the time the document lands in your inbox, you are already the preferred vendor.
Reading 200 RFPs taught me more about how companies fail to buy than how agencies fail to sell. Most RFPs are broken documents issued by organizations in the middle of an internal argument about what they need.
Agencies succeeding on RFPs are not better at responding to RFPs. They are better at pre-qualifying which RFPs are real, pre-positioning before the RFP is issued, and pre-building the relationship that makes the formal process a formality.
Run the numbers on your last 20 RFPs. Win rate, staff hours per proposal, average deal size, actual award date versus stated date. Most agencies who do this exercise cut submission volume by 40% and improve total closed revenue from the channel.
More submissions is not the answer. Better selection is.
Industry win rates for agency RFP responses are typically in the low double digits for agencies without pre-existing relationships with the issuing company. Top-performing agencies that pre-qualify heavily and submit narrative proposals achieve win rates of 25% to 35% on their responded RFPs. The key variable is not response quality alone but selectivity: agencies with strict pre-qualification criteria win a higher proportion of the smaller pool they choose to answer. Submitting to every RFP you receive is a reliable path to low win rates.
Usually because whoever wrote the RFP did not have budget authority, or the company wants to anchor off agency proposals rather than their own number. In a 200-RFP analysis, 73% included no stated budget. The workaround: ask directly for a range before investing proposal time. Most buyers will provide a range when asked. Those who refuse are either genuinely confused about their budget or running a process where your proposal is meant to set their pricing anchor.
Between $2,500 and $8,000 in staff time per response, based on Agency Management Institute benchmarks on proposal production costs. This includes reading the RFP, asking clarifying questions, writing the proposal, sourcing case studies, creating custom materials, and coordinating approvals. At a low win rate, an agency submitting ten proposals to close one deal is spending $25,000 to $80,000 in cost of sales per closed deal. Selective pre-qualification significantly improves this math.
Narrative structure over point-by-point template matching. Winning proposals lead with insight about the company's actual underlying problem, use a single strong case study as the central proof, and address RFP criteria inside the narrative rather than as direct answers. They tend to run 30% shorter than template proposals while being more persuasive. The key is research on the company before writing. Better templates are not the solution.
Three positive signals: a named human point of contact, any visible budget range, and a timeline under eight weeks from issue to award on a scoped project. Three red flags: no budget and refusal to provide a range, more than 12 unweighted evaluation criteria, and scope that includes incompatible deliverables without timeline acknowledgment. Any two red flags in one RFP is a strong signal to pass regardless of deal size.
No. RFP response is a high-cost, low-conversion acquisition channel for most agencies. Research consistently shows that buyers in B2B professional services rank prior relationship with the vendor as a top selection factor. Agencies building inbound through content, community, and referrals create pre-RFP brand presence with future buyers. When those buyers eventually issue an RFP, the agency with the prior relationship wins at far higher rates. RFPs work best as a supplement to a strong inbound base.
Founder & CEO of Striveloom. Software engineer and Harvard graduate student researching software engineering, e-commerce platforms, and customer experience. Builds the agency that ships like software — one team, one pipeline, one platform. Writes on AI agencies, web development, paid advertising, and conversion optimization.
Median agency hourly rate in 2026: $185. Our 87-founder survey breaks down rates by service type, team size, and niche versus generalist positioning.
We broke down the full tech stack of a $10M digital agency. Base bill: $1,847/month before AI tools. Most of it is HubSpot. Here is where every dollar goes.
Operator communities like Hampton now route more inbound deals than email outbound for agencies inside them. Here is the data, the economics, and the playbook.
Book a free 30-minute call to scope your project. Fixed pricing, transparent timelines.
| Approach | Template Response | Narrative Response |
|---|
| Structure | Point-by-point RFP answer | Story-first with criteria addressed inside |
| Length | Matches RFP page count | 30% shorter |
| Tone | Formal, third-person | Direct, first-person |
| Differentiation | Listed in bullets | Woven into case studies |
| Win rate | Industry average | Roughly 2x industry average |
