The anatomy of a stalled deal: 8 questions your rep couldn't answer fast enough

Table of contents

• The moment a deal dies
• Question 1: "How do you handle our data in the EU?"
• Question 2: "Are you SOC 2 compliant?"
• Question 3: "How does this integrate with our Salesforce setup?"
• Question 4: "What happens if your system goes down?"
• Question 5: "Can you support our enterprise SSO?"
• Question 6: "How does pricing work at our scale?"
• Question 7: "Who else in our industry uses this?"
• Question 8: "Can you answer our security questionnaire?"
• The pattern behind all eight
• What actually fixes this

---

The moment a deal dies

It rarely happens with a hard "no." It happens with "let me check on that and get back to you."

Your rep is on a live call. The prospect asks something specific — data residency, uptime guarantees, enterprise pricing. Your rep doesn't know the answer cold. They say they'll follow up. The prospect nods. The call ends.

Then the deal goes quiet.

That follow-up email takes 48 hours because it needs three Slack threads, a Confluence search that returns nothing useful, and a ping to an engineer who's mid-sprint. By the time the answer lands in the prospect's inbox, their attention is elsewhere. A competitor who answered on the spot is now the front-runner.

Deals stall for a lot of reasons. This one is preventable.

Here are the eight questions that kill more B2B deals than almost anything else — and why your reps keep getting caught flat-footed on them.

---

Question 1: "How do you handle our data in the EU?"

This comes up in nearly every enterprise deal involving a European buyer or a company with EU customers. It sounds simple. It isn't.

A real answer requires knowing your data residency options, your sub-processor list, your DPA terms, and whether your infrastructure supports region-specific storage. Most reps know the headline — "yes, we're GDPR compliant" — but not the specifics procurement actually needs.

When the prospect's legal team pushes for details and your rep says "I'll confirm," the deal enters a holding pattern it may never leave.

---

Question 2: "Are you SOC 2 compliant?"

Every rep knows to say yes. The problem is the follow-up: "What type? What period does your report cover? Which trust services criteria?"

SOC 2 Type I and Type II are not the same thing, and a savvy buyer knows the difference. If your rep hesitates or goes vague, it signals that your security posture isn't as solid as you claimed. That's a credibility hit at exactly the wrong moment.

---

Question 3: "How does this integrate with our Salesforce setup?"

Not "do you integrate with Salesforce" — they already know the answer is yes. The real question is about their specific setup: custom objects, workflow rules, data sync frequency, field mapping.

Your rep can't answer this without either knowing the product deeply or having someone nearby who does. On a live call, neither option is fast enough. The rep hedges. The prospect notices.

---

Question 4: "What happens if your system goes down?"

This is a reliability and SLA question dressed up as a casual concern. The prospect wants to know your uptime commitment, your incident response process, and what remedies exist if you miss it.

Vague answers invite skepticism. Specific ones close the credibility gap fast — "99.9% uptime SLA with credits for breaches, documented in section 4 of our MSA" is a very different response than "we have a great track record."

The specific answer exists somewhere in your documentation. Getting to it on a live call is the problem.

---

Question 5: "Can you support our enterprise SSO?"

The question sounds technical. The answer is usually yes. But the follow-ups are where reps get stuck: which identity providers, SAML or OIDC, how provisioning works, what role mapping looks like.

Your rep knows you support Okta. They don't know the implementation details. So they say "yes, definitely" and then have to walk it back when IT gets involved. That backtrack costs credibility.

---

Question 6: "How does pricing work at our scale?"

Pricing questions mid-deal are delicate. The prospect isn't just asking about cost — they're testing whether you've thought about their situation specifically.

A rep who says "I'll have to get you a custom quote" when the prospect expected a direct answer creates friction. Not because custom quotes are wrong, but because the hesitation signals the rep doesn't know the product well enough to have an intelligent conversation about value at scale.

---

Question 7: "Who else in our industry uses this?"

Reference questions feel easy. They're not. The prospect wants a specific name, a specific use case, and ideally a contact they can call.

If your rep can't name a relevant customer on the spot, the social proof moment is gone. If they name one and get the details wrong, it's worse. The answer requires knowing which customers are referenceable, what their use case was, and what results they saw.

That information lives in Salesforce, in Gong call notes, in a Confluence page someone updated six months ago. It doesn't live in your rep's head.

---

Question 8: "Can you answer our security questionnaire?"

This one doesn't come up on a call. It arrives as an email attachment — a 400-row Excel file with merged cells, broken formulas, and questions buried in instruction tabs. The prospect needs it back in five business days.

Your rep forwards it to the solutions team. The solutions team forwards it to engineering. Engineering puts it in the queue. Two weeks later, the prospect has moved on or gone with whoever responded first.

Security questionnaires kill deals quietly. They're the follow-up version of every question above, formalized into a document that exposes every gap in your sales knowledge operation.

---

The pattern behind all eight

None of those questions are trick questions. None of them are unreasonable. Every single one has a correct, specific answer that exists somewhere in your company.

The problem isn't that your reps are unprepared. The problem is that the answers live in places reps can't reach fast enough — Confluence pages, security docs, engineering specs, legal templates, Gong recordings from six months ago.

So reps improvise, hedge, or punt to an SME. The SME is mid-sprint. The answer takes two days. The deal goes cold.

This is what SME bottlenecks actually cost your pipeline — not just engineering time, but deal velocity. Every hour between question and answer is an hour the prospect spends reconsidering.

The tools your team already uses don't solve this. Guru and Highspot help with content management, but they don't surface the right answer in under two seconds on a live call. Confluence is a great repository for people who know what to search for. Your reps don't always know what to search for, and they don't have time to search during a demo.

---

What actually fixes this

The answer isn't better onboarding. It isn't more battlecards. It isn't telling reps to study the knowledge base harder.

It's giving reps instant access to the right answer — in your voice, with citations — in the time it takes to unmute.

AnswerPath connects to your existing documents, policies, and knowledge base. When a rep asks "how do we handle EU data residency," they get a source-backed, cited, on-brand answer in under two seconds. Not a search result. Not a Slack thread. Not a ticket.

The same system handles security questionnaires. Drop in the Excel file, get back a completed first-pass draft in minutes — pulled from your approved documentation, matched to your voice, formatted for the prospect.

It's not magic. It's just your knowledge base made accessible at the speed a deal actually moves.

Your best engineers are already losing deals every time a rep pings them for an answer that's already written down somewhere. That stops when reps can self-serve.

Your corporate knowledge goes in. Source-backed, cited, on-brand answers come out.

Book a demo at answerpath.com