Domain Context

Why this chapter

You won't be expected to be a domain expert. You will be expected to engage credibly — ask good questions, recognize vocabulary, understand what the customer actually cares about. This chapter is enough to do that.

CLM history in 90 seconds

Contract Lifecycle Management software has gone through three generations:

1. Gen 1 — Document repositories (early 2000s). Where the contract PDFs sit. Workflow for approvals and signatures. Examples: SpringCM, ContractWorks.
2. Gen 2 — Workflow CLM (2010s). Drafting tools, e-signature, approval chains, basic clause libraries. Examples: Ironclad, DocuSign CLM, Conga, Icertis, Agiloft.
3. Gen 3 — Contract intelligence (mid-2020s). Extracting structured data from contracts (and invoices, POs, supplier catalogs) for analytics, compliance, and spend optimization. This is the category contract-intelligence platforms compete in.

The differentiator vs Gen 2: Gen 2 is workflow-centric (where contracts live, who signs them); Gen 3 is data-centric (what's in the contracts and what it implies). Both can coexist; large enterprises often have both.

Vocabulary you'll hear

Document types

• MSA (Master Service Agreement) — the parent agreement establishing the relationship terms; SOWs hang off it.
• SOW (Statement of Work) — specifies a particular engagement under an MSA.
• NDA (Non-Disclosure Agreement) — confidentiality.
• DPA (Data Processing Agreement) — GDPR-required for vendors processing personal data.
• BAA (Business Associate Agreement) — HIPAA-required for vendors handling protected health info.
• EULA — end-user license agreement.
• Amendment / Addendum — modifies an existing agreement.
• PO (Purchase Order) — the buyer's purchase commitment.
• Invoice — the seller's bill.
• 3-way match — comparing PO + receipt + invoice before paying. Standard procurement control.

Clause vocabulary

• Indemnification — who covers losses if things go wrong. Legal cares.
• Limitation of liability — caps on what the vendor will pay if they cause damage.
• Termination for convenience — can the customer cancel without cause? Usually requires notice.
• Termination for cause — can the customer cancel if vendor breaches? Always present.
• Renewal terms — auto-renew vs not, notice period required, renewal-term length.
• MFN (Most Favored Nation) — vendor commits to give this customer the best price they give anyone.
• Service Level Agreement (SLA) — performance commitments (uptime, response time, accuracy).
• SOC 2 / ISO 27001 — security certifications referenced in security exhibits.

Procurement vocabulary

• P2P (Procure-to-Pay) — the end-to-end flow from need-identification through payment.
• S2P (Source-to-Pay) — broader; includes supplier sourcing and contracting before P2P.
• S2C (Source-to-Contract) — just the sourcing + contracting phase, before procurement.
• Spend analytics — analyzing what's being purchased, from whom, at what price.
• Direct vs indirect spend — direct = inputs to product (raw materials, COGS); indirect = everything else (IT, services, office).
• Maverick spend — purchases made outside the procurement process (off-contract).
• Tail spend — many small purchases that are individually inconsequential but collectively material.
• Supplier rationalization / consolidation — reducing the number of suppliers a company uses for a given category.
• Category — a grouping of purchases (IT services, professional services, raw materials).
• 3-way match exception — when PO, receipt, and invoice don't reconcile; finance investigates.

Finance vocabulary

• Accrual — recognizing an expense before cash leaves. Important for month-end close.
• Accounts payable (AP) — owed to suppliers but unpaid.
• GL (General Ledger) — the master accounting record.
• Cost center — internal organizational unit that owns budget.
• FY (Fiscal year) — the customer's accounting year, often not calendar year.
• Period-end close — month-end / quarter-end accounting wrap-up.

Personas you'll meet

• Chief Procurement Officer (CPO) — owns the procurement function. Cares about supplier consolidation, spend reduction, contract compliance.
• VP / Director of Procurement — typical buyer of contract-intelligence platforms. Has a hard target: "X% cost reduction this year."
• Category Manager — owns a specific spend category (IT, services, MRO). Wants visibility into their suppliers' contract terms and spend patterns.
• Procurement Analyst — does the daily work. Will use the platform UI and the dashboards. Your most frequent customer-side contact.
• General Counsel / VP Legal — wants risk visibility (indemnification, liability caps, regulatory clauses). Often a co-buyer.
• Paralegal / Contract Analyst — legal's analog to procurement analyst.
• Controller / VP Finance — co-buyer when the pitch includes accruals, payables, audit prep.
• IT lead — owns integrations, security review, identity. Gatekeeper of access.
• Data engineering / analytics lead — your peer-level partner. Will own the deployment with you.

Key processes the platform touches

Renewal management

The single highest-ROI use case for many customers. Auto-renew clauses with missed notice windows lock customers into agreements they wanted to renegotiate. Platform surfaces upcoming renewals with notice deadlines so the customer's procurement team can act in time.

Off-contract spend reduction

15–30% of enterprise spend is typically "off-contract" — purchases from suppliers without an active agreement, or outside the negotiated terms. Surfacing this lets the customer route spend back onto contracts (better pricing, better terms).

Supplier consolidation

Enterprises have 3000–10000 suppliers; many are duplicates (Acme Cloud vs Acme Cloud Services), and consolidation to ~10% of that gives volume discounts and operational simplification. The platform's entity-resolution layer enables this.

Audit and compliance prep

When auditors arrive, finance / legal needs to produce evidence of contract terms, spend reconciliation, and policy adherence. Platform output is the artifact.

Contract risk surfacing

Find agreements with unusual indemnification, missing data processing addenda, or non-standard liability caps. Legal cares about this.

Negotiation prep

Before renewing or renegotiating, the procurement team wants every term across every agreement with this supplier. Platform produces it.

Where the platform's revenue comes from

Useful to know for the founder / GM round.

• Customers are typically Fortune 1000. Annual contract values of $250k–$2M+ depending on scope.
• Land-and-expand. Initial deployment is one division or business unit; expansion is to other parts of the enterprise.
• Pricing is usually a mix of platform license + document volume + integration scope. Sometimes a percentage of validated savings.
• Renewal is contract-anniversary. Net revenue retention is the headline metric — are customers expanding within their contract or shrinking?
• FDE deployments are often time-bound in cost (you can't have FDEs at every customer indefinitely). Platform improves to reduce per-customer FDE hours over time.

The implication for the role: your job is to make deployments succeed in less time over time. Patterns and reusable artifacts you build at one customer should reduce the next deployment's hours. That's the senior FDE muscle.

Interview probes