How to Win RFPs: What Separates AE Firms That Win From Firms That Respond

Every AE principal has lived this cycle. An RFP shows up on a portal. It looks like a fit. The team drops billable work for two weeks, builds a proposal, hits the deadline, and waits. Six weeks later the letter arrives: thank you for your submittal, the committee has selected another firm.

Then you find out who won, and it's a firm no better than yours. Sometimes it's a firm you know is worse.

Here's the part nobody puts in that letter: the selection was mostly decided before the RFP was ever published. Not rigged. Decided. The winning firm had been in front of that owner for a year. They knew the project's history, the people scoring the submittals, and the problem keeping the capital projects director up at night. For them, the RFP was the last step in a long conversation. For you, it was the first.

That's the thesis of this entire article: winning happens before the RFP drops. Everything after release, the writing, the graphics, the page limits, is execution on a position you either built or didn't.

One note on the word itself. This article says RFP throughout because that's the term everyone searches, but on public work the same pursuit often arrives as an RFQ or a request for SOQs, and a federal Brooks Act selection isn't an RFP response at all: it's a SAM.gov synopsis answered with an SF330 qualifications package. The label changes. The mechanics don't.

Why Response-Only Firms Lose

An RFP is the end of the buyer's process, not the start of it. By the time a public agency, university, or institutional owner publishes an RFP for design services, the project has been through budgeting, programming, sometimes a feasibility study, and at least one board or council approval. Staff have talked to firms along the way. They've formed opinions about who understands the work.

So when your first contact with an owner is the proposal you submit, you're asking a selection committee to shortlist a stranger over firms they already know are qualified. Committees almost never do that. Not because procurement is corrupt, but because evaluators are people, and people score confidence. A familiar firm with relevant work feels like a safe recommendation. An unknown firm with a handsome proposal feels like a risk.

Response-only firms confuse activity with strategy. They set up SAM.gov alerts and state portal notifications, respond to whatever looks close, and call the resulting volume a pipeline. It isn't a pipeline. It's a lottery ticket, except worse, because in this lottery some of the other players got to meet the judges first.

The tell is where the effort goes. Response-only firms spend enormous energy after release: all-nighters, formatting marathons, boilerplate surgery. Winning firms spend their energy before release, when effort still moves the outcome.

What Evaluators Actually Score

Most public procurement of architecture and engineering services runs on qualifications-based selection. At the federal level that's the Brooks Act, which has required agencies to select A/E firms on qualifications rather than price since 1972, with fee negotiated afterward with the top-ranked firm. Most states have their own QBS statutes that work the same way for state and local projects. None of this is news to a principal who's sat through a few selections, but it's worth stating plainly, because so many proposals read like their authors forgot it.

QBS changes what a proposal is for. You're not competing on a number. You're competing on the committee's confidence that your team, specifically, will deliver this project, specifically. Look at the criteria in almost any A/E RFP, and at their federal cousins behind the SF330, and the same themes appear over and over: relevant project experience, key personnel, past performance, understanding of the project, management approach, capacity to perform.

Read that list again and notice what it rewards: specificity. Not "we have decades of combined experience" but "this proposed team delivered these three comparable projects." Not a generic approach section but one that names the actual constraints of the actual site, program, and delivery method. Evaluators read stacks of these things. Generic quals blur together. Specific quals get scored.

And here's the connection back to the thesis. Project understanding usually isn't the heaviest-weighted criterion on the scoring sheet; relevant experience and key personnel typically carry more points. But it's the most differentiable one. Every firm that survives the first cut has comparable projects and credible resumes. Understanding is where committees separate firms that look identical on paper, and it can't be faked from the RFP text. Everyone read the same RFP. The firm that scores highest on understanding is the firm that learned things the RFP doesn't say, in conversations that happened months before it existed.

One more thing the paper can't do alone. On most public selections the written submittal doesn't win the job; it gets you shortlisted. The decision usually happens at the interview, where the committee finally meets the people behind the resumes and finds out who actually understands the project. Pre-RFP work pays off twice here. It sharpens the submittal, and it's the difference between an interview that opens a relationship and an interview that continues one.

Capture Planning: The Work Before the Release

Capture planning is the unglamorous discipline of picking the projects you intend to win and doing deliberate work on them before there's anything to respond to.

Almost everything you need is public. Capital improvement plans, bond programs, facility master plans, board and council minutes, budget documents. Owners tell you years in advance what they intend to build. A firm that reads a county's five-year CIP knows what's coming, roughly when, and at roughly what budget, long before procurement writes a word.

The pre-RFP window is also when you're allowed to talk. Once an RFP is on the street, most agencies impose a quiet period and route every question through a procurement inbox. Before release, you can meet. Ask about the project's history. Learn what went wrong last time, where the internal pressure is coming from, which past consultant left a bad taste. None of this is gamesmanship. Owners generally want capable firms to understand their projects. It makes selection easier and outcomes better.

This is when teaming gets decided too. The strongest sub-consultants and partners commit early. If you start assembling a team the week the RFP drops, you're choosing from whoever's left, and there's a decent chance the partner you wanted is already on someone else's cover letter.

Do this well and the RFP becomes an assembly job instead of a research project. Your win themes already exist. Your team is committed. Your relevant projects are selected and written up. The response window goes into sharpening, not scrambling. That's the practical answer to how to win RFPs: make the proposal the last ten percent of the pursuit instead of the whole thing.

If nobody at your firm owns this work, that's not a character flaw. It's a structural gap, and it's the most common one in small and mid-sized firms. Principals are billable. Nobody owns the pre-RFP window, so nobody works it.

The Go/No-Go Discipline

Here's an uncomfortable observation from inside a lot of AE firms: the biggest proposal problem usually isn't quality. It's volume. Firms chase too much, qualify too little, and spread their best people across pursuits they were never going to win.

Every proposal has a real cost even when nobody invoices it. Senior time, production time, and the opportunity cost of the pursuit you starved because everyone was buried in the one you shouldn't have chased. A loss doesn't cost you nothing. It costs the fully loaded hours of everyone who touched it, and those hours came out of billable work or a better pursuit.

A workable go/no-go screen doesn't need software or a weighted scoring model. It needs a few honest questions, asked before anyone opens InDesign:

• Did we know this was coming before it published?
• Do we know the owner? Does the owner know us?
• Have we delivered this project type, at this scale, for this kind of client?
• Is the right team actually available, or are we proposing people we'd have to free up?
• Is there an incumbent, and is the owner happy with them?
• If we're honest: why us? What would make an evaluator rank us first?

If most of those answers are no, the pursuit is a donation. The hard part is that "no" has to be a real outcome, and declining feels like turning down revenue. It isn't. Revenue you were never going to win isn't revenue. Saying no to the wrong pursuits is what funds doing the right ones properly. The point of the discipline isn't to shrink ambition. It's to concentrate force.

Compliance Is Table Stakes

Now the boring part that kills proposals anyway. Before anyone evaluates your qualifications, someone checks whether your submittal follows the rules. Page limits. Required forms. Mandatory certifications. Tab structure. File naming, portal, deadline. In public procurement that check often happens before the evaluation committee sees anything, and a non-compliant submittal can be set aside without a single page being read. All that positioning, dead on a technicality.

The fix costs an afternoon: a compliance matrix. Go through the RFP line by line and pull out every "shall," "must," and "will provide," plus every form, certification, DBE commitment, insurance requirement, and portal rule. One row per requirement. Who owns it, where it's addressed, who verified it. Build it the day the RFP drops, not the night before submittal, and have someone other than the lead author run the final check, because by then the lead author has stopped seeing the document.

Two more habits that cost nothing. Follow the RFP's stated order even when your standard layout is prettier, because evaluators score against a checklist that mirrors the RFP, and every deviation makes their job harder. And answer the question that was asked, not the question your boilerplate answers.

Just understand what compliance buys you: nothing. It doesn't win a single point. It keeps you alive long enough to be scored. Plenty of firms polish compliant, professional, completely generic proposals and wonder why they keep finishing third. Compliant is the floor. Positioned is the ceiling.

Losing Well: The Debrief Habit

You'll lose RFPs. Everyone does, including firms that do everything in this article. The difference between firms that improve and firms that plateau is what a loss produces. For most firms it produces a shrug and a forwarded email. It should produce information.

Request a debrief every time you lose a shortlist or a selection. Most public agencies will provide one, or at least release scoring summaries, and the ask costs you an email. Go in with questions, not grievances: Where did we score weakest? What separated the winner? What would a stronger submittal from us have looked like? Procurement people talk to firms that lose gracefully. They remember the ones that argue.

Then look for patterns, because one loss is noise and five are a diagnosis:

• Losing on relevant experience again and again means your go/no-go screen is broken. You're chasing work you can't yet win.
• Losing on approach means your proposals are generic. Evaluators couldn't tell you'd thought about their project.
• Finishing second repeatedly usually means you're everyone's safe backup: qualified, but never the firm with the inside position. That's not a writing problem. That's a pre-RFP positioning problem.

Debrief your wins too. Knowing why you won is how you repeat it on purpose instead of by accident. And keep the internal version blameless. The first time a debrief turns into a trial, people stop telling you the truth, and the information stops flowing.

Build the Bench or Bring In Outside Muscle?

So who does all of this? Capture planning, go/no-go facilitation, proposal leadership, debrief tracking. It's a real workload, and in most small and mid-sized firms it lands on principals by default, in the margins around billable work. Which is exactly why it doesn't happen. Pre-RFP positioning is important but never urgent, and the urgent always wins.

A full-time BD director solves the ownership problem, and for firms with enough pursuit volume it's the right answer. But it's a serious salary, and at a 15 or 40 person firm the honest math often doesn't support it. So the role gets justified on hope, filled by someone too junior to sit across from owners, or skipped entirely.

The seller-doer model is the usual fallback, and it has a hard ceiling: every hour a principal spends on pursuit is an hour of the firm's most expensive technical capacity not being billed. And the work is inconsistent by design. When the backlog is full, pursuit stops, which guarantees a thin pipeline six months later.

There's a middle path: senior BD leadership at a fraction of the cost, owning the pre-RFP work as a function instead of a side project. That's the model we run at BD-AEC. You can read exactly what fractional BD is and how an engagement works elsewhere on this site. The short version: you need the discipline in this article to happen every week. You don't necessarily need a full-time salary to get it.

Whichever route you take, the principle holds. Someone has to own the work that happens before the RFP drops, because that's where the winning happens. When it's owned by "everyone," it's owned by no one.

Ready When You Are

If your firm is submitting steadily and winning rarely, the fix probably isn't a better template. It's a better process upstream of the template. A 30-minute conversation is usually enough to see where the gaps are: pipeline, positioning, go/no-go, or all three.

Book a discovery call. No deck, no pressure. Just a straight look at how your firm pursues work and what it would take to win more of it.

Scott Mann is the Founder and Lead BD Director of BD-AEC, a fractional business development practice for architecture and engineering firms, based in Florence, Kentucky and serving firms along the I-75 corridor.