Differentiation in an AEC proposal is evidence, not adjectives. Every firm claims to be responsive, collaborative, and quality-focused. An evaluator reading six SOQs in a row sees the same six adjectives — they cancel out. Real differentiation is the specific project, the specific engineer, the specific outcome a competitor cannot also truthfully claim.
"We're Different" Is Not a Differentiator
Pick up ten AEC qualifications statements from the last year. Read the executive summaries back to back. The vocabulary repeats almost word for word: responsive, collaborative, client-focused, quality-driven, on time and on budget, integrity, partnership, deep bench, local presence, national resources, technical excellence.
Every claim is true. None of it is useful. If your direct competitor can write the same sentence about themselves without it becoming a lie, the sentence is not a differentiator. It's table stakes — the price of being considered.
This is the problem evaluators run into the moment they sit down to score. Three or five proposals deep, the adjectives blur together. Selection committees end up scoring something else — past performance, key personnel, fit with the scope — because the qualitative claims read identically across the stack. The firms that win are the ones whose proposals gave the evaluator something specific to remember.
The Three Sources of Evidence-Based Differentiation
Real differentiation in an AEC proposal comes from three places. None of them are adjectives.
Project evidence. Not project types — outcomes. Saying you've done "30 wastewater treatment plants" puts you in the same bucket as every other regional civil firm. Saying you delivered a 12-MGD plant expansion under a 14-month consent decree without missing a state milestone is evidence. The first claim is a category. The second is a story an evaluator can score.
People evidence. Not titles — demonstrated experience. "Our PM has 25 years of bridge experience" is the same sentence every bridge firm submits. "Our PM ran the structural analysis on three of the four longest movable-span bridges in the Midwest" is specific enough that the next firm in the stack cannot say the same thing without lying.
Process evidence. Not "our proven approach" — a process that visibly differs from what others do. If your QC review actually catches design conflicts before construction because you run it differently, the evaluator should be able to see how, not just that you "value quality." Demonstrated, not asserted.
| Claimed adjective | Evidence-based version |
|---|---|
| "Responsive" | "Average 4-hour turnaround on RFI responses across the last 14 projects, documented in the project log" |
| "Local presence" | "Our PM has lived in the watershed for 22 years and chaired the county's stormwater advisory committee from 2018–2022" |
| "Collaborative" | "Co-located staff with the agency for 6 months during preliminary engineering — three full-time engineers in the agency office" |
| "Deep bench" | "Eight licensed engineers in this specific discipline within the office serving this contract, named in Section E" |
| "Quality-focused" | "Independent QC review by an unrelated office; conflict log from the last five projects available on request" |
The pattern: every left-hand entry is a category every competitor can also claim. Every right-hand entry is something a competitor would have to be willing to lie about to copy.
Why Most Firms Have Real Differentiators But Can't Surface Them
Here is the part that makes this hard for most AEC firms: the differentiators exist. They're sitting inside the firm's project record. They just can't be retrieved fast enough to show up in a submittal.
The 12-MGD plant under a consent decree is in someone's old project sheet, in a format that doesn't fit the current client's template. The PM with the movable-span résumé has three versions of his bio floating around the shared drive, none of which list the specific bridges by name. The conflict log from the QC process exists as PDFs scattered across five project folders. None of it is impossible to find. It's all just slower to find than the proposal deadline allows.
So the proposal team does what every proposal team under time pressure does. They reach for the closest existing language. They drop in "responsive, collaborative, quality-driven" because those sentences are pre-written, pre-approved, and don't require chasing a PM for the actual numbers. Differentiation dies in the retrieval gap — not in the strategy meeting.
This is the same reason client research often fails to show up in the document. The intel exists. The team learned the hot button, knows who the right three projects are, identified the right four people to put forward. Then assembly time runs out and the team ships the generic version because the specific version takes longer to produce.
RFPM.ai is built to close that gap. When project records and staff profiles live as structured data — outcomes tagged, named personnel mapped to specific demonstrated experience, project histories filterable by client type, regulatory environment, and scope — "feature these three projects and these four people, told this way" becomes a filter and a format choice. Not a week of rebuilding.
How to Find Your Firm's Real Differentiators
If you've never done this exercise honestly, the first pass takes a day. The maintenance is much smaller than that, once the structure exists.
-
Run honest win/loss debriefs. Within a week of every selection — won or lost — write down why. Three bullets, not a memo: what the client said they were buying, what we offered that competitors didn't, where we were vulnerable. Six months of disciplined debriefs surface the patterns. The firm starts to see what it actually wins on, which is rarely what its marketing materials say it wins on. The same debriefs sharpen the go/no-go decision on the next pursuit.
-
Tag projects by outcome, not by type. Most AEC firms organize past performance by sector — water, transportation, vertical, environmental. That structure is fine for filing. It hides differentiators. Re-tag the same projects by outcome: completed under a consent decree, delivered ahead of a federal funding deadline, navigated a major design change without a schedule slip, came in 8 percent under budget. Outcomes are evidence. Sectors are categories.
-
Map personnel by demonstrated experience. Not by job title, not by years of experience, not by license alone. By the specific things people actually did — the agencies they worked with, the regulatory environments they navigated, the unusual projects they led. This is the version of a staff resume an evaluator can score; the title-and-years version is not.
-
Write the honest "why not them." For your three biggest competitors, write the case the client should pick you instead — specific evidence, not adjectives. If the case relies on words a competitor could also use about themselves, the case is not made. This exercise forces the firm to find the parts of its record that are actually different.
-
Pressure-test against six recent SOQs. Pull six executive summaries from the last twelve months. Strike every sentence a direct competitor could write about themselves without it being a lie. If more than half the document falls out, the firm's positioning is running on adjectives.
The point of this work is not a marketing exercise. It's a proposal-operations one. The output is a usable inventory — projects, people, and process evidence the proposal team can reach for the next time the assembly clock starts.
Where Evidenced Differentiation Goes in the Proposal
Once the inventory exists, the question is where it lands in a submittal. Adjective claims tend to drift toward the cover letter and the boilerplate. Evidence lives somewhere specific.
Section H / executive summary. Lead with one sharp, evidenced claim — not five vague ones. The executive summary's job is to give the evaluator a reason to read the rest of the submittal specifically.
Sections E and F (SF330). This is where most evidence-based differentiation actually scores. Section E key personnel and Section F project examples are evaluated against the selection criteria one line at a time. A resume that says "principal designer on the 12-MGD expansion delivered under a consent decree" earns a point. "25 years of water/wastewater experience" doesn't. The most common SF330 mistakes that cost shortlist points are all variations of the same failure — adjective claims instead of evidenced specifics in Sections E and F.
Win themes. A win theme is an evidenced answer to the question "why should the client pick you." Two or three themes, each backed by a specific project or person, beat ten generic ones. The theme should be repeatable across every section — and every section should reinforce it with evidence the evaluator can verify.
Past performance and references. Pick references who can speak to the specific differentiators you're claiming. A reference who confirms "they were responsive" is unhelpful — every competitor's references say that. A reference who confirms "they kept us on the consent-decree milestones despite a major design change in month six" is exactly the corroboration the evaluator needs.
The shape of an evidence-led proposal is recognizable from the first page. Every claim ties back to a specific project, a specific person, or a specific demonstrated process. Evaluators don't have to take anything on faith.
Frequently Asked Questions
What is differentiation in an AEC proposal?
Differentiation in an AEC proposal is the evidence — specific projects, specific personnel, specific demonstrated processes — that a competitor cannot also truthfully claim. Adjectives like "responsive" or "collaborative" are not differentiators because every competitor uses the same words. Real differentiation is something an evaluator can score on the page.
Why do AEC firms all sound the same in proposals?
Because proposal teams reach for pre-approved language under deadline pressure, and pre-approved language tends to be generic. The firm's real differentiators usually exist — buried in old project files, unfiled win/loss debriefs, or one PM's head. The retrieval problem makes the generic version faster to produce than the specific one, so the generic version ships.
How do you find what makes an engineering firm different?
Start with honest win/loss debriefs and a re-tagging exercise. Pull twelve months of pursuits, write down the specific reasons each was won or lost, and re-tag projects by outcome rather than by sector. The patterns are usually visible within a few months. The firm's actual strengths rarely match its marketing language exactly.
What's the difference between win themes and differentiators?
A differentiator is an underlying fact about your firm — a project, a person, a process. A win theme is the message you build around it for a specific pursuit. Differentiators are stable across pursuits; win themes are tailored to each one. Both fail if the underlying evidence isn't specific.
Can a smaller AEC firm differentiate against a larger competitor?
Yes — and the path is the same regardless of size. Larger firms generally rely on the same generic adjectives smaller firms do; their bench is bigger, but their qualifications language is rarely sharper. A 30-person firm with a specific, evidenced answer to "why us on this pursuit" can outscore a national firm running on category claims, because the evaluator can verify the evidence.