The shadow SMEs who should be on every proposal invite
Three roles answer the hardest questions on most proposals and aren't titled as experts. How to identify them in your org and why they belong on the kickoff invite.
Every mature proposal shop has three or four people who answer the hardest questions on every bid and don’t show up on the official subject-matter-expert list. They aren’t titled as experts. They sit in adjacent functions. They get pulled in by name, off-channel, in Slack DMs that start “hey, quick question.”
We call them shadow SMEs. They are load-bearing and they are usually invisible to the proposal manager who didn’t grow up inside the company. Their absence from the official kickoff invite is one of the small reasons proposals run late — the proposal manager calls the named SME, the named SME doesn’t actually know, the named SME forwards the question to the shadow SME, and three days have passed.
This is a short field note on the three roles to look for and how to find them in your org.
Role 1 — The implementation engineer who deployed the customer’s analog
Every product has a customer that’s two years ahead of the bid you’re answering. Somebody on your implementation team — a CSM, a forward-deployed engineer, a senior solutions architect — was on the ground for that deployment. They know the workarounds, the failure modes, the things the marketing site can’t say.
When a buyer’s RFP asks “how do you handle [hard problem],” the official SME — usually the product manager for that area — gives the official answer. The shadow SME — the engineer who has actually run the workaround at three customers — gives the answer that wins the bid because it includes the operational truth.
How to find them: ask your customer success team who they call when an enterprise customer escalates. The names that come up twice are your shadow SMEs.
Role 2 — The pre-sales engineer who lost the deal that mattered
Sales engineers carry institutional memory about lost deals that nobody else carries. They know which competitor won, which feature they lost on, what the buyer said in the post-mortem call. They know the language the buyer’s evaluator used to describe their decision.
When a new RFP comes in from a similar buyer, the pre-sales engineer who lost that previous deal can predict — with surprising accuracy — which sentence in your draft will land badly with the evaluator. They are the closest thing your team has to a buyer-side reader.
How to find them: pull the last 10 lost deals in the segment of the current bid. Find the SE who supported each. Two or three names will recur. Those are your shadow SMEs for that vertical.
Role 3 — The customer support lead who reads every escalation
Support escalations are the leading indicator of every weakness a buyer’s evaluator will eventually surface. The lead support engineer or director of customer success has read the patterns. They know which features have unstable behavior under load, which integrations break in specific stack configurations, which compliance posture statements get questioned in deep diligence.
The official SME for any of these areas usually doesn’t read the support queue. The support lead does. When a DDQ asks “describe how you handle data corruption events,” the official answer is the disaster-recovery process. The shadow SME’s answer adds the actual lessons from the three corruption events the team handled last year — sometimes the latter is what an evaluator scores higher.
How to find them: ask the head of support which team members are in the room for every customer-facing escalation review. There is usually one or two.
Why they don’t show up
The named-SME list in most proposal shops is generated by org chart. Product managers for product areas. The legal team for legal questions. The CISO for security questions. The CFO for finance questions.
Shadow SMEs don’t show up on the org chart because their expertise is operational, not titled. The implementation engineer who deployed three customers is not the product manager. The SE who lost the deal is not the head of competitive intelligence. The support lead who reads every escalation is not the VP of Engineering.
The 48% SME-bottleneck stat from Qorus’s research — held steady for five years — has shadow SMEs as part of its denominator. The bottleneck isn’t just “the named SMEs are busy.” It’s also “the people who actually know the answer aren’t on the invite.”
Lohfeld’s research on proposal-process drag names the same effect from another angle: proposal managers spend more time chasing the right SME than they spend on strategy. Naming the shadow SMEs explicitly cuts the chase.
What to do
Three things, in order of effort.
Add them to the kickoff invite by default. A kickoff with one extra implementation engineer, one extra SE, and one extra support lead is barely larger than a kickoff without them, and the questions that hit them in the first hour are the questions that would otherwise blow up on Day 8.
Maintain a shadow-SME registry. A short list — name, role, segments they know best, last bid they contributed to. Updated quarterly. The proposal manager who joins next year inherits the list.
Credit the work. Shadow SMEs do this work in addition to their day job. They notice when nobody notices. A standing line item in proposal-cycle retros — “shadow SME contributions” — keeps the work visible to the people who would otherwise lose it.
The named SMEs are necessary. The shadow SMEs are the multipliers. Get them on the invite.