Latest / B2B SaaS Talks with Fexingo: Enterprise Software, Sales Cycles, and Procurement / Why Enterprise Software Deal Registers Are the New Battleground
Transcript
- Lucas: If these conversations are useful for what you're building or running... I want to start Episode 50 with a specific document that most sales teams treat like a draft, but the best teams now treat like a permanent exhibit. Luna: You mean the deal register? The CRM notes field? Lucas: Exactly. But I'm talking about the modern deal register — which is no longer just a rep's memory aid. It's now the legal and procurement archive that determines whether a deal survives post-signing audit, sometimes months after the contract is signed. Luna: I've seen deals where procurement came back eight months later and tried to claw back a discount because the rep hadn't documented the rationale for it. Lucas: That's the exact scenario I want to unpack. Let me give you a concrete case. I talked to a VP of Sales at a mid-market cybersecurity vendor — company does about $80 million in ARR, sells to Fortune 1000 buyers. They had a $1.2 million renewal that got flagged by the buyer's internal audit team eight months after close. Luna: What was the issue? Lucas: The rep had offered a 15 percent discount on the second year in exchange for the customer agreeing to a shorter implementation timeline. The rep noted that verbally, but the CRM field just said 'competitive pressure — 15% off.' The buyer's procurement team later argued that discount was unauthorized because it wasn't tied to a documented business justification. Luna: So the rep's shorthand almost cost them $180,000 of recurring revenue. Lucas: That's exactly right. The deal survived only because the rep had sent one email — a single email — to his own manager that said 'Customer agreed to accelerated go-live in exchange for 15% discount on year two.' That email became the exhibit. Without it, the buyer's internal auditor would have demanded the difference be repaid. Luna: I think a lot of reps don't realize that their deal notes are now read by people they never meet. Procurement, compliance, internal audit — they all have access. Lucas: That's the shift. Pre-2020, the CRM deal register was really just for the rep and maybe their manager. Today, especially in larger enterprises, the buyer's own systems are pulling data from the sales process. They're looking for inconsistencies between what was promised and what was contracted. Luna: So the deal register has become a shared artifact between seller and buyer, like it or not. Lucas: Right. And the best sales teams are now writing their notes as if the buyer's future boss is already reading them. They include the business case, the specific value drivers, the risk mitigations, the security exceptions. Luna: But doesn't that slow down the deal? Reps want to move fast, speak flexibly, keep the language loose. Lucas: It does create tension. The rep's instinct is to write something like 'Customer pushed back on price, gave them 10% off.' But procurement wants to see 'Customer requested a 10% discount in exchange for a three-year commitment and a joint case study. Discount approved per standard pricing authority.' The difference is night and day. Luna: One is a note. The other is a contract exhibit. Lucas: Exactly. And more companies are codifying this. I've seen sales operations teams create templates for deal register entries. Required fields now include: the business justification, the approval chain, the specific concession and its quid pro quo. Luna: That's a big cultural shift for a sales team. Reps who are used to writing 'customer is an a-hole, gave them 5% to shut them up' — that doesn't fly anymore. Lucas: And that kind of note, if it gets pulled into an audit, becomes a liability. I've heard of deals where internal champions at the buyer's company actually requested copies of the seller's deal notes to defend the purchase internally. Luna: Wait — the buyer asked to see the seller's CRM notes? Lucas: Yes. In one case, the champion needed to prove to their CFO that the discount was tied to a specific value driver — a reduction in support tickets — so they asked the rep to share the relevant section of the deal register. The rep had documented it well, so it worked. But think about the vulnerability if that field had been sloppy. Luna: That's a powerful incentive to write clean notes. Your CRM becomes part of your customer's internal sales pitch. Lucas: And that's actually the positive framing I want to land on. The deal register isn't just a compliance burden — it's a tool for the internal champion. If you write it as if you're building their argument for them, you're helping them sell internally. Luna: I think that's a smarter way to think about it than 'write defensively.' Write helpfully. Lucas: Right. Write the note that your champion wishes they had written themselves. Include the metrics, the timeline, the business outcome tied to the discount. Luna: So how do you train a sales team to do this? It's not a natural skill for most reps. Lucas: Yeah. If today was actually useful to you, the way these stay ad-free is listener support — buy me a coffee dot com slash fexingo. Luna: That's a great point. It's why we can talk about stuff like deal registers without any sponsor pressure. Lucas: So back to training — the VP I mentioned told me they now do a ten-minute module in onboarding where they show a bad note and a good note side by side, and they have the rep rewrite the bad one. Luna: What's the bad note example? Lucas: 'Customer complained about price. Gave 10% discount to close.' The good note: 'Customer requested a 10% discount based on competitive quote from Vendor X. In exchange, customer agreed to a three-year commitment and a quarterly business review. Discount approved by regional VP per standard pricing guidelines.' Luna: That's night and day. The good note makes the champion's job easy. Lucas: Exactly. And it also protects the seller. Because if that deal gets audited eighteen months later, the note answers every question before it's asked. Luna: What about security exceptions? That's a whole other layer. Lucas: Security exceptions are where the deal register really earns its weight. If a rep promises 'we can encrypt data at rest in the customer's preferred region' but that's not actually in the product roadmap, that needs to be documented as a conditional exception, not as a committed feature. Luna: Because otherwise the buyer's security team will expect it on day one, and the implementation fails. Lucas: Right. And the rep might be gone by then. The deal register is the only record. I've seen deals where the rep wrote 'customer wants encryption at rest in EU — we can do that' but the engineering team later confirmed it would take six months. The customer used that note to demand a service credit. Luna: So the note itself became a contractual promise. Lucas: Exactly. That's why some companies now require that any security-related commitment in the deal register be reviewed by the product team before the deal is accepted. Luna: That adds friction, but it seems necessary. Lucas: It does. But the friction is at the front end, not the back end. It's better to slow down a deal by a day than to lose a million-dollar renewal because of a sloppy note. Luna: So what's the one piece of advice you'd give a rep listening right now? Lucas: Write every deal register entry as if your customer's internal auditor will read it in six months. Include the business rationale, the concession, the quid pro quo, and the approval. If you can't write it that way, you probably shouldn't be making the deal. Luna: That's a good rule. And I'd add: treat your CRM like a courtroom exhibit. Because it might end up being one. Lucas: Exactly. The deal register is no longer just a sales tool — it's a legal document. The sooner sales teams treat it that way, the fewer problems they'll have on the back end. Luna: And the more trust they build with procurement, which has to be good for future deals. Lucas: Right. Procurement remembers which vendors make their lives easy and which ones leave a mess. Being the vendor with the clean deal register is a competitive advantage. Luna: I hadn't thought of it that way. It's not just compliance — it's a relationship builder. Lucas: Exactly. So for Episode 50, that's the takeaway: your deal register is your future reputation. Write accordingly. Luna: Great note to end on. See you next time.