Software procurement
Intake-to-decision for new software suppliers, run by an AI legal agent, with a human verifier as the gate before anything is approved.
The software-procurement module takes a request to buy a SaaS product from first submission through to an auditable approve or reject decision. An AI agent, clmAI Procurement, captures the supplier’s terms, reviews them with the skills expected of a SaaS-specialist legal counsel, and recommends a decision. A human Verifier then audits that work and is the only party who can approve.
What it does
- Captures the real terms, including terms incorporated by reference from a URL, version-matched to the date they would apply. See Online terms capture.
- Reviews them against your policy, producing a structured, evidence-grounded legal review with a recommendation and a gap analysis. See clmAI Procurement legal review.
- Drafts remediation: a mitigation rider for the gaps found and a plain-language summary agreement. See Rider & summary agreement.
- Enforces a human gate: a Verifier confirms the review and makes the decision, subject to firm diligence gates.
The lifecycle
Each request moves through these states:
- Submitted: the requestor has filed the request.
- Documents ready: supplier documents have been uploaded to the request’s folder.
- Terms captured: online terms incorporated by reference have been fetched and version-matched.
- Under legal review: clmAI Procurement is running its review.
- Review complete: the review and recommendation are ready for the Verifier.
- Summary generated / negotiating: optional downstream states while remediation is drafted and negotiated.
- Approved / rejected / onboarded: the terminal decision.
Principles
Evidence over assertion
Every finding in a review is grounded in a quote from the supplier’s own documents or captured terms. Where the agent cannot find support for a point, it marks the item Unverified rather than guessing, and a human clears it before approval.
Honesty under uncertainty
clmSpace is used by enterprises that rely on its output. The agent is built to say “I could not establish this” rather than fabricate a comforting answer. This is most visible in online-terms version-matching, where an unconfirmable version is reported as such.
Auditability
State changes, the review, the recommendation, the Verifier’s confirmation and any approver waiver are all recorded. Generated artifacts (review, gap analysis, rider, summary agreement, supplier dossier) are stored and downloadable.
Prerequisites
Bind a Procurement folder once in Settings » Document sources. clmSpace auto-creates a per-supplier sub-folder for each request and stores uploads and generated artifacts there.