Ivo

Ivo's strongest design decision is refusing to build another editor. Redlines land in Microsoft Word or Google Docs, so your reviewers keep their track-changes habits and outside counsel keeps receiving files it can open. The value sits underneath: each clause is checked against two things most tools treat as an afterthought — your own playbooks and historical contracts, and live deal context like contract value and urgency. Benchmarking is the differentiator worth testing first. Ivo compares clause positions against your executed contracts segmented by governing law, contract type, party role, and industry, then shows how those executed contracts deviate from your standard positions. That is a data question, not a drafting question, and it depends on you actually having a repository and playbooks to work from. A team with ten NDAs and no precedent pool will get generic-feeling output from a tool priced for volume. Assistant covers the mid-negotiation questions that eat senior lawyer time: how a draft differs from what you previously accepted, what a change in the law means for your positions, and what a regulation requires before you flag shortfall terms in an agreement. Intelligence is the query layer — plain-English questions across contracts wherever they live, plus a unified term timeline showing a base agreement and all its amendments in one view. No tagging or field mapping to maintain is the claim, and it is the right claim: contract metadata projects die on maintenance. Collaborate, launched September 1, 2026, is the biggest change since the seed data was written. It runs every deal through one place from intake to signature: intake reads the agreement, turns it into a list of open issues, routes each to the right stakeholder, and follows plain-English workflows per agreement type (NDAs, DPAs, MSAs each with their own steps, playbook, and policy). Low-risk agreements move straight to signature; anything needing judgment routes to a reviewer. Intake can start in Salesforce, redline in Word, approve in Slack, with changes syncing back to the same deal with version history. It also reports which provisions you negotiate most, where deals stall, and which positions and approvers add turns to cycle times — the kind of negotiation telemetry legal ops has wanted for years. Where it does not fit: if you want one system that also owns signature and workflow orchestration end to end, Ivo is explicitly the review-and-insight layer beside your CLM, not a replacement for it. If your team works in neither Word nor Docs, the core surface is wasted. Pricing is quote-based for in-house legal teams, so budget approval has to go through a procurement cycle before you can test value — plan for that. Certification coverage (SOC 2, ISO 27001, GDPR, CCPA, no training on customer data) is stated and worth verifying against your own security review.