How to Win More RFPs

Qualified companies lose RFPs they should win. Not because they lack the experience, the certifications, or the track record, but because writing a proposal and scoring a proposal are two different disciplines, and most teams only ever study the first one.

You know your work is good. Your team knows it. Your past clients know it. The problem is that none of those people are in the room when your proposal gets graded. The evaluator is. And the evaluator does not know what you know. They know what is on the page, in the order the rubric asks for it, at the depth the scoring criteria require. Everything you understand about your own quality has to survive the trip onto that page or it does not count.

That is the gap this guide closes. Lisa Rehurek developed The RFP Success^® Company’s approach across 30+ years on every side of the RFP table, responding to proposals, developing them, and sitting on the other side as an evaluator scoring them. From that cross table view, the reasons qualified teams lose stop looking like bad luck and start looking like patterns. The same handful of mistakes, over and over, on proposals that had every reason to win. The recurring ones are collected in common RFP mistakes and how to avoid them, with more RFP strategy articles on the blog.

The RFP Success^® Company works exclusively in SLED, the State, Local, and Education market. The principles below are written for service-based businesses competing for state, county, city, school district, and university contracts. The result of applying them is a 76%+ win rate across client portfolios against an industry average near 25%. If you are weighing which market to pursue, how SLED, federal, and commercial RFPs differ explains what changes in each one.

“IT IS NOT ABOUT YOU” means the evaluator does not care about your company. They care about their problem and whether you can solve it with the least risk. Winning proposals are written about the buyer’s outcome, not the bidder’s résumé.

Here is the most expensive habit in proposal writing. A team sits down to respond, and the first instinct is to talk about themselves. Our history. Our team. Our awards. Our process. Page after page of “look at us.”

The evaluator reading it has one question running on a loop: what does this do for me?

That is the whole reframe. The proposal is not your stage. It is the buyer’s decision document. Every paragraph either helps the evaluator picture a lower risk, higher value outcome for their agency, or it is taking up space that a competitor will use better. “IT IS NOT ABOUT YOU” is the principle that turns a capabilities brochure into a winning proposal.

Watch how it changes a single sentence. A capabilities first team writes: “We have 15 years of experience and a 24/7 support center.” An evaluator reads that and thinks, fine, so does the next vendor. The same fact, written from the buyer’s side, reads: “Your team reaches a live specialist in under two minutes, any hour, so a system outage never becomes a missed deadline for your residents.” Same capability. One version is about the bidder. The other is about the evaluator’s worst day and how you prevent.

This is the shift the Capability Dumper archetype has to make. Capability Dumpers are not unqualified. Their proposals read like a data dump because their subject matter experts know the technical answer cold and assume the value is obvious. It is not obvious to an evaluator who has never met them. The fix is not more content. It is the same content, rewritten so the evaluator does the least work to see the value.

“You’re not losing because you’re unqualified. You’re losing because you’re undisciplined.”

Founder, The RFP Success^® Company · 30+ years of RFP experience

Evaluators score against a rubric, section by section, often reading dozens of proposals in a compressed window. They are not hunting for the best company. They are checking whether each required answer is present, complete, and easy to find, then awarding points. Proposals that make scoring easy score higher. For a closer look at the scoring itself, see how RFP evaluators score proposals.

That reality changes how you write. Three things matter more than most teams realize.

A SLED evaluation panel is usually a few people who have day jobs, a stack of proposals, and a deadline. They score against a published rubric that assigns points to specific requirements. They read for what the rubric tells them to find, in the order it tells them to find it. When a required answer is buried, vague, or missing, the points are simply not awarded. There is no partial credit for “they probably meant this.”

Most teams have never seen the inside of an evaluation. So they write for an audience that does not exist: a careful reader with unlimited time who will infer your quality from context. The real audience is different.

The evaluator’s scorecard, the rubric, is the most important document in the whole process, and it is the one most teams skim. It tells you exactly where the points are and how they are weighted. The D.A.R.E. Method covers both the explicit items the scorecard spells out and the silent items it does not, the unwritten things an evaluator rewards even when no line item names them.

Evaluators score section by section. If the rubric asks question seven and your answer to question seven is woven into a paragraph under a different heading, you have made the evaluator hunt. Tired evaluators do not hunt. They score what they can find. Answer in the order asked, label it clearly, and make the points impossible to miss.

By their 20th proposal, an evaluator is not savoring your prose. They are scanning. Long, formal paragraphs that “sound professional” lose points to the same content presented in short paragraphs, clear headings, and scannable structure. Clarity reads as competence. Density reads as risk.

This is the lens The RFP Success^® Company team applies in an RFP Success^® Mastery Audit, scoring up to three of a client’s past proposals the way a panel would, to surface exactly where points were left on the table.

A win theme is a short, repeated message that connects what you do to what the evaluator most needs, backed by proof. You build one by reading the rubric for what the agency values most, then attaching a provable outcome to it and threading it through every relevant section.

Win themes get named on every RFP advice page on the internet. Almost none of them tell you how to build one an evaluator can actually score, so here it is.

A win theme is not a slogan. It is a claim the evaluator can give you points for. It has three parts: the thing the agency cares about most, the specific way you deliver it, and the proof that you have delivered it before. Miss any of the three and it stops being a win theme and becomes marketing.

Start from the rubric, not from your strengths. Read the evaluation criteria and the weighting. What is the agency most afraid of going wrong? What gets the most points? That is where your win theme lives, because a theme aimed at what you are proud of instead of what they are scoring does not improve your score.

Then attach proof. A theme of “reliable delivery” is empty. A theme of “your deadline holds because we have hit 97% on time delivery across 14 state agency contracts” is scorable, because the evaluator can see the evidence and award points for low risk. Evidence is what separates a theme an evaluator believes from one they discount.

Keep it to what you can prove everywhere. Two or three themes you can substantiate in every relevant section beat a long list you mention once. Proof density beats promise density, every time.

Then repeat it. A win theme stated once in the executive summary and never again does not register. The same theme, surfaced in every section where it is relevant and proven each time, builds across the whole proposal until it is the thing the evaluator remembers when they tally the score.

You stand out by making your difference visible, not inferable. Every shortlisted competitor is qualified, so the evaluator is choosing among capable options. The proposal that clearly shows why it is the lowest risk, highest value choice wins; the one that assumes its quality is obvious blends in.

By the time a SLED evaluation reaches scoring, the unqualified bidders are usually gone. The panel is choosing between qualified and more qualified. That means your technical competence is the price of entry, not the differentiator. Everyone in the room can do the work. The question the evaluator is really answering is: who is the safest, strongest choice?

The mistake qualified teams make is assuming the evaluator will see the difference. They will not, not on their 30th read of the week, not unless you make it impossible to miss. Distinction has to be visible on the page, stated plainly, and tied to the evaluator’s outcome. “We are different because we care more” is not visible. “We are the only bidder proposing a 30 day transition plan that keeps your current system live until cutover, so your residents never lose access” is visible, specific, and scorable.

The most expensive version of this problem is the team that waits for the RFP to start thinking about how to win. By the time the solicitation hits the street, the agency’s priorities, problem definition, and preferred outcomes are already taking shape. Strong qualifications and a well-written proposal can keep you competitive, but they cannot fully make up for a strategy that began at release. Winning starts before the RFP with relationships, intelligence, positioning, and a clear reason the agency should choose you over every other capable bidder.

Differentiation also is not about trashing competitors or overclaiming. SLED evaluators are experienced. Overpromising reads as risk, and risk loses points. The strongest distinction is quiet and specific: a concrete commitment, a relevant proof point, a clearly lower risk approach, repeated where it counts.

“Anyone can help you submit a proposal. Very few can help you win one. We don’t measure success by submission. We measure it by win rate.”

RFP-expert Lisa Rehurek

Founder, The RFP Success^® Company · 30+ years of RFP experience

The D.A.R.E. Method is the tactical writing system inside the Content pillar of the 4×4 Framework™. It stands for Distinction, Answer the Questions for Impact, Readability, and Evidence & Authority, the four places proposals most often win or lose points with an evaluator.

Everything above, the evaluator’s lens, win themes, differentiation, lives inside one tactical system. The D.A.R.E. Method is how The RFP Success^® Company turns “write for the evaluator” from a slogan into a checklist a team can apply to a real draft. It addresses both the explicit items the scorecard spells out and the silent items it does not.

Chasing every RFP spreads your team thin and lowers the quality of each response, which lowers your win rate. Winning more starts with a disciplined go/no go process so your best effort goes only to the pursuits you can actually win.

This is the counterintuitive part, and it is where the Scrambler archetype lives. Scramblers treat every RFP as a fire drill, respond to everything, and burn out producing rushed proposals that almost win. The math works against them. Splitting one team’s capacity across eight pursuits produces eight average proposals. Concentrating it on three produces three strong ones, and strong proposals win.

A go/no go decision is not about pessimism. It is about putting your strongest work where it can actually convert. Before committing a team, the questions worth answering are honest ones: Do we have the people and time to do this well, not just to submit? Do the terms work for us? Is this the kind of work we want more of? Do we have a real, provable reason to win this one over the incumbents and the field?

When the honest answer is no, walking away is the win. Every hour not spent on an unwinnable pursuit is an hour your team spends making a winnable one excellent. This is the discipline behind the 92% down select rate, qualified pursuit, then disciplined execution.

The 4×4 Framework™ is The RFP Success^® Company’s proprietary methodology: four pillars, Strategy, Content, People, and Process, each with four sub components. Everything in this guide maps to one of those pillars, which is how the framework turns scattered tips into a repeatable system for winning more RFPs.

The advice in this guide is not a loose collection of tips. It is organized, and the organizing structure is the 4×4 Framework™, developed by Lisa Rehurek from 30+ years on every side of the RFP table. Four pillars, each with four sub components, covering the 16 places proposals consistently break down.

Is the win theme, the positioning, the read on what the agency actually values, the intelligence beyond the document itself.

Is where the D.A.R.E. Method lives, Distinction, Answer the Questions for Impact, Readability, Evidence & Authority. Most of this guide sits here, because content is where evaluators score.

Are the right roles in the right seats, your subject matter experts feeding the technical truth, a reviewer reading like an evaluator, leadership weighing in where it counts.

Is the go/no go discipline, the development workflow, the review cycles, and submission readiness that keep quality from slipping under deadline pressure.

Winning more RFPs is not one move. It is these four working together. A great win theme (Strategy) written as a data dump (weak Content) still loses. Perfect content (Content) on a pursuit you should have walked away from (weak Process) still loses. The framework exists so nothing important gets dropped while the deadline closes in.

Each Win Strategist service applies the framework to a different part of the problem. Start with the two-minute RFP Assessment.

The free, two-minute RFP Assessment is the starting point. It helps our team point you to the right service.

The RFP Success^® Mastery Audit applied the D.A.R.E. Method, the Content pillar, across multiple recent proposals, scoring them the way a panel would. The diagnostic surfaced one specific pattern: RTA Fleet’s technical competence was clear, but their win themes were buried under required response structure. Distinction was breaking down. Evaluators could not easily find what made RTA Fleet the right choice.

The audit delivered a prioritized roadmap focused on Distinction, with Readability and Evidence & Authority as secondary fixes. RTA Fleet applied it in their next proposal cycle. Their finalist rate climbed from 50% to 80%, and revenue is on pace to 2 to 3x the prior year, all from one focused diagnostic on the single pillar driving their losses.

RTA Fleet