Blog

David Martinez•July 22, 2020·October 14, 2025•6 min read

Philosophy Books That Change Worldviews

Security and compliance: Ask for current SOC 2 Type II or ISO 27001; if not available, require a roadmap and interim controls. Data residency should match regulatory exposure; EU PII may require EU data centers and SCCs. Breach notification within 72 hours is standard; for regulated data, 24 hours may be warranted. Require annual pen tests and the right to review summaries. These terms reduce downstream audit costs and incident risk.

Liability and IP: Vendors propose total liability capped at 12 months of fees and exclude consequential damages. For data loss, PII exposure, and IP infringement, push for a higher cap (2–3x fees for those categories) and carve-outs that allow recovery of direct remediation costs. Termination for convenience is rare on multi-year terms, but you can secure a termination for cause with cure periods, plus pro-rata refunds for chronic SLA breaches (e.g., three misses in any rolling 12 months).

Numbers To Watch

1. The Sense of an Ending — Julian Barnes Memory is slippery; this slim novel shows how one small omission can rewrite a life.
2. Of Mice and Men — John Steinbeck A spare, devastating tale of friendship, dreams, and the cost of mercy.
3. The Metamorphosis — Franz Kafka Wake up as a bug, discover how quickly love becomes logistics.
4. We Have Always Lived in the Castle — Shirley Jackson A gothic whisper that turns into a scream about family, fear, and outsiders.
5. The Old Man and the Sea — Ernest Hemingway A lone fisherman, a stubborn marlin, and the dignity of losing well.

Auto-renewal windows are often 30 days; request 90–120 days and require email notice to a legal inbox. Data portability: mandate exports in non-proprietary formats (CSV/Parquet plus JSON for metadata) at no extra cost, and define a data deletion timeline (e.g., 30 days post-termination) with certification. Audit logs: minimum 12 months online retention or export capability. Small changes here can save weeks of scramble during audits or migrations.

• A short book that changed your mind: ______
• A novella you finished in one sitting: ______
• A slim classic you expected to hate but loved: ______
• The best under-250-pages for a book club: ______
• A tiny book with a huge last line: ______

Sequence Negotiations To Maximize Leverage

Run pricing and legal in parallel but stagger commitments. Get a written commercial proposal with line items before deep legal redlines; then use legal risk to trade for price or term concessions. Maintain a credible BATNA: a competitor quote or a validated build-in-house cost baseline. If there’s no true competitor, create option value with scoped pilots or phased deployments tied to clear acceptance criteria.

Time matters. Quarter- and year-end can unlock 5–10 additional percentage points, but only if you have approvals ready. Build a mutual close plan with the vendor: dates for security review, legal draft turnover, and executive approvals. Exploding offers are a red flag; counter with a price-lock letter valid for 30 days while reviews complete. If the vendor insists on a fast close, ask for a concession that expires with it (e.g., extra sandbox, migration services).

Negotiate give-gets explicitly. Examples: you offer a two-year term and a public reference case; they freeze price for the full term and include two integrations at no charge. You agree to a case study; they increase liability cap to 2x fees for data breaches. Document these in a side letter if they are operational commitments not suited for the MSA.

A Practical Timeline

Week 1–2: baseline usage and define KPIs. Week 3: issue a concise requirements brief (one page) to shortlisted vendors. Week 4: obtain comparable proposals; request line-item pricing and meter disclosures. Week 5–6: security review and pilot. Week 7: finalize license design, negotiate price, and draft legal redlines. Week 8: executive approvals and signature. Compressing this to four weeks increases price risk and the chance of missed controls.

Real-World Pitfalls And How To Avoid Them

Module creep: vendors bundle “advanced analytics” or “AI assistants” that add 10–20% cost. If KPIs don’t depend on them in the first 90 days, exclude or negotiate a no-cost trial with opt-in pricing later. Evidence is mixed on immediate ROI from generic AI features; collect your own before committing.

Consumption traps: generous free tiers on API calls can flip to punitive overages after growth. Ask for soft caps with notifications at 50/75/90%, and a 90-day grace period to re-tier. Model worst-case: at 2x forecast volume, ensure overage charges don’t exceed the next tier’s effective rate. If they do, force a right to retroactively re-tier.

Renewal shock: uplifts compound. A 7% annual increase makes a $300k contract cost ~$343k in year two and ~$367k in year three, adding ~$110k over three years versus 0% uplift. Insert a cap, tie increases to a public index, or bake in step-down pricing as your volume rises. Calendar reminders 180 and 120 days before renewal prevent auto-renew traps.

A Note On Vendor Behavior

Some vendors will withhold best pricing until late. Keep one alternative warm until signature. If a rep offers a steep end-of-quarter cut, ask them to translate it into a sustainable rate (no backloading, no forced module adds). If they cite “global policy,” request the policy in writing or ask for an executive override meeting; both moves clarify whether the constraint is real.

Conclusion

Treat SaaS buying as an engineering problem: define the objective, measure the baseline, isolate variables, and lock in guardrails. Design the license mix from observed usage, force line-item transparency, cap uplifts, and trade legal risk for commercial value with explicit give-gets. If you can’t explain your total three-year cost and your exit path in two sentences, you’re not done negotiating.