Another day, another vendor presentation promising "unprecedented ROI" and "frictionless integration." Having sat through more of these than I care to admit, I've found the most critical tool isn't a fancy evaluation matrix, but a simple, persistent habit: flagging the *risk* in every single pricing and contract clause. The sales rep's job is to sell; your job is to not get sold a liability. This isn't about being difficult; it's about institutional memory and turning soft concerns into hard, trackable points.
I'm talking about a concrete process, not a vague feeling. When reviewing a vendor like Read AI, or any SaaS platform, I maintain a separate document—call it a "Risk Register"—parallel to the official proposal. Every time a red flag pops up in a pricing discussion, it gets logged there with a specific format. The goal is to move from "this seems expensive" to "this pricing model creates a measurable, ongoing financial exposure."
Here’s what a single entry in that register looks like. It's a template I force myself to fill out for every significant concern:
* **Risk Flag:** [A short, searchable label] e.g., "Metric Manipulation - User Count Definition"
* **Source:** [Where did this come from?] e.g., "Pricing Page Footnote 3", "Call with Sales Rep Adam, 10/24", "Section 4.2 of Draft MSA"
* **The Pitch:** [How the vendor is presenting it] e.g., "Per-user pricing provides simple, predictable scaling."
* **The Reality:** [The specific, exploitable ambiguity or burden] e.g., "Contract defines a 'user' as any registered individual, regardless of activity level. Inactive or occasional users from a large department will inflate costs with zero value. Vendor audit rights allow them to count these users annually."
* **Quantifiable Impact:** [The best guess at the financial or operational cost] e.g., "Our org has ~40% 'occasional' users in similar tools. At their $25/user/mo tier, a 100-seat deal could mean paying $12,000 annually for unused licenses, with annual true-up penalties."
* **Mitigation / Required Clarification:** [The exact contractual or process fix needed] e.g., "Require definition change to 'Active User' (logs in at least once in 30 days). Demand proration for true-ups and right to de-provision without penalty. Otherwise, push for site-wide license based on concurrent sessions."
Applying this to a tool like Read AI, you might immediately flag their "per meeting" or "per transcript" pricing. The risk isn't the price itself; it's the lack of control over the metric. What constitutes a "meeting"? A scheduled 60-minute call that gets canceled after 5 minutes? An automated system generating daily stand-up transcripts? The risk register forces you to articulate that *before* you're holding an invoice for 10,000 "meetings" you didn't anticipate.
The power of this walkthrough isn't in the template itself, but in its consistent application. It turns subjective gut feelings into a list of negotiation action items. When the vendor says, "Don't worry, we're flexible," you point to Flag #4 and say, "Great, then we can codify the 'Active User' definition here in Appendix B." It prevents the classic amnesia that sets in after a slick demo, where all those nagging concerns get drowned out by promises. You're left with a document that serves as both a negotiation guide and, if things go south, a sobering post-mortem on why they did.
Trust but verify.