Verbatim or It Didn't Happen

Here are two CRM notes from the same discovery call.

The seller's version: "Customer has significant pain around alert triage inefficiency and is motivated to modernize their SOC workflows."

What the customer, a VP of Security Operations, actually said: "My analysts spend 22 minutes per alert to find the 4 percent that matter. I lose one L2 a quarter to burnout, and my board asked me — in writing — why detection costs doubled while coverage didn't."

The first version is a paraphrase. The second is evidence. And the distance between them is where deals die.

Paraphrase is not a compressed copy of what the customer said. It is a translation into the seller's language, weighted by the seller's hopes, and it decays a little more every time it is retold — to the manager, to the sales engineer, to the forecast call, to the proposal writer. By stage four, "the board asked me in writing" has become "leadership visibility," which means nothing, moves no one, and cannot be defended in a deal review. I call this what it is: seller fiction. Not lying — drift. But drift compounds, and your forecast is priced off the drifted version.

The rule that stops it is brutal and simple: verbatim or it didn't happen. If the deal file doesn't contain the customer's exact words, the deal doesn't contain the evidence.

Why the exact words are load-bearing

A verbatim quote does three jobs that no paraphrase can do.

It's falsifiable. "Customer is frustrated with manual processes" cannot be wrong, which is exactly why it is worthless — it would be equally true of every account in your territory. "22 minutes per alert to find the 4 percent that matter" can be checked, sourced, and dated. It has an author with a name and a title. When a deal reviewer asks "who said that, and when?", the verbatim quote has an answer. This is the entire logic of scoring MEDDPICC evidence 0 to 3: a paraphrase is a 1 — assumed — no matter how confident the seller sounds. A dated quote from a named stakeholder is what a 2 looks like. The same quote confirmed by a second stakeholder is a 3.

It carries the emotional payload. "I lose one L2 a quarter to burnout" is not information about attrition. It is a person telling you what keeps them up at night, in the phrasing their own mind uses. When you play that sentence back — in an exec summary, in a proposal — the customer doesn't hear your pitch. They hear themselves. No sentence you compose will ever be as persuasive to a customer as the sentence they already said.

It survives the meetings you're not in. Your champion is going to sell for you in rooms you will never enter. What do you want them carrying: your value proposition, in vendor dialect they'll mangle under pressure — or their own colleague's words, which they can repeat with total fluency because it's their native language? Enterprise deals are won in your absence. Verbatim quotes are the only asset that travels there intact.

The capture discipline

None of this works as a memory exercise. Verbatim capture is a mechanical habit with three parts.

Record, with consent, and mine the transcript within 24 hours. Conversation-intelligence tooling has made this nearly free. The discipline is not the recording — it's the extraction. Within a day of every discovery call, pull the three to five sentences that carry the deal: the pain statement, the number, the consequence, the aspiration. Quotation marks, speaker, title, date. If you can't record, the rule adapts: write the key sentences during the call, then confirm them — "You said something earlier I want to make sure I got exactly right..." Customers are never offended that you cared about their exact words. They are quietly offended when you replace them.

Log them where the deal is built. The 3 Whys Builder has a field for this by design: every Why — why anything, why now, why us — requires the answer in the customer's own words, with a named owner, a number, and the evidence behind it. Not the seller's summary of the customer's position. The words. The same standard runs through the Value Delta One-Pager, which opens with "the pain, in one sentence, in their words." If that field contains vendor language — "inefficiencies," "modernization," "digital transformation" — the field is empty. It just doesn't look empty, which is worse.

Confirm the big ones in writing. The most important sentence in any deal — the Economic Buyer's conditional commitment — should exist as a quote the EB has seen and confirmed. "If you hit the three criteria and Model Risk signs off, this is in my Q4 spend." Sent back in a follow-up email, confirmed with one reply. That sentence, verbatim and acknowledged, is worth more to your forecast than any stage field in your CRM.

Reuse: where the quotes pay rent

Captured quotes that sit in call notes are a diary. The system pays off in reuse — and there are three places the customer's exact language belongs, all the way to signature.

The executive summary. Open with their words: "In our discovery sessions, your team described the problem in these terms: 'analysts spend 22 minutes per alert to find the 4 percent that matter.'" An executive reading their own organization's voice at the top of your document doesn't evaluate your understanding — they experience it. And an executive who spots vendor boilerplate in paragraph one stops reading, correctly.

The POV success criteria. The criteria the customer signs before kickoff should be phrased in the language the customer used to describe the pain — "reduce time-to-verdict on the alert classes we named" — not your product's feature taxonomy. Criteria written in the customer's words are criteria the customer already believes in; they defend them internally as their own, because they are. Criteria written in vendor language invite renegotiation the first time an evaluator gets nervous.

The proposal and business case. Every value claim in your Business Value Assessment should trace to a quote: the before-state numbers came from someone's mouth, on a date, and the document should say so. When procurement pressure-tests the business case — and it will — a case built from the customer's own quoted inputs cannot be dismissed as vendor math. The customer would have to argue with themselves.

There is a compounding effect here that sellers consistently underrate: every time you accurately reuse a customer's words, you deepen their conviction that you listened — which earns you better raw material on the next call. Paraphrase spends trust. Verbatim compounds it.

The objection you're already forming

"This is stenography — I'm a seller, not a court reporter." No: it's evidence handling, and it takes minutes per call, not hours. Three to five sentences, properly attributed, per conversation. Your best sellers already do a version of this instinctively — listen to how they quote their customers in deal reviews, names and phrasing intact, while the middle of the team speaks entirely in summary. As with everything else in the operating system, the point is to take what the top decile does invisibly and make it the written standard.

"Customers ramble — their words are messy." Good. Messy is what true sounds like. You may trim a quote for length; you may never upgrade its vocabulary. The moment "we keep missing the ones that matter" becomes "suboptimal detection efficacy," you have replaced a human being's fear with a slide bullet, and slide bullets don't sign contracts.

Where to start Monday

Audit five active deals for a single quote. Open the deal files and look for one sentence in quotation marks with a name and a date attached. Most files will have zero. Each zero is a finding: that deal's pain is currently a seller's opinion, and its MEDDPICC Identified Pain score is a 1 wearing a 3's confidence.
Make the 3 Whys Builder quote-mandatory in your next review. For one deal, ask the seller to read the "in the customer's own words" fields aloud. Vendor language in the field gets sent back the way an empty field would. The team learns the standard in one meeting.
Rewrite one live exec summary to open with the customer's voice. Take a proposal going out this month and replace the first paragraph with a properly attributed verbatim pain statement. Then watch what the customer does with that document internally. It will travel further than anything you've sent them — because for the first time, it sounds like them.

Discovery ends when the deal file can speak in the customer's voice without you in the room. That is the real exit criterion — not a stage checkbox, but a file full of sentences with authors, numbers, and dates. Everything downstream — the criteria, the business case, the forecast category, the signature — stands on those sentences.

Capture them exactly, or accept that your deal is built on fiction with your name on it.

Go deeper. This essay draws on The Value Engine: How Elite Enterprise Sales Teams Turn Buyer Pain into Forecastable Revenue by Rudy M. Celekli — the complete operating system, demonstrated end-to-end on one $8.9M enterprise deal. Get the book, and download the free Field Toolkit — including the 3 Whys Builder and the Value Delta One-Pager — to put the customer's own words at the center of your next deal review.