Compare / Ivo
Sandstone vs Ivo: Contract Review or the Whole Legal Function?
Ivo does AI contract review for in-house teams: agentic redlining inside Microsoft Word, and a repository that answers questions across your contract library. Sandstone covers the work around the contract too — intake from Slack and email, triage, routing, and the business context behind each request. Here's a side-by-side.
Sandstone vs Ivo
| Capability | Sandstone |  Ivo |
|---|---|---|
| Primary focus | AI-native operating system for in-house legal work, from intake to resolution | AI contract review, redlining, and contract intelligence |
| Where the work happens | Inside Slack, email, and the business systems teams already use | Primarily a Microsoft Word add-in, plus the Ivo web platform |
| Intake and triage | Agents capture requests from existing channels, understand intent, and route to the right owner | Contract review begins once the agreement is in hand |
| Business context | Counterparty history, prior negotiations, relationships, and business signals attached to every request | Contract-level context via AiRE, its repository engine, which clusters agreements without manual tagging |
| Playbooks | AI playbooks built from your existing contracts and precedent, applied across workflows | Clause-level playbooks applied during review, with one recommendation per issue |
| Contract redlining | Playbook-driven redlining with the attorney in control | Agentic review, redlining, and comments; plain-language prompts inside Word |
| Repository and portfolio questions | Contracts sit alongside matters, obligations, and counterparties in one working surface | Repository with natural-language queries across the library; surfaces amendments and superseding agreements |
| Reporting | Cycle times, risk exposure, capacity, and deviation rates across all legal work | Negotiation patterns and risk insight drawn from the contract portfolio |
| Permissions across systems | Permissions mapped across every connected integration | Controls within the Ivo platform |
| Internal collaboration | Legal works a request together in the app or the plugins, with comments and drafts staying behind the scenes until you choose otherwise | Collaboration on contract review |
| Acting back in source systems | Replies and actions go back to Slack, procurement, and contract systems under a shared team identity, with permissions mapped across those integrations centrally | Word and platform |
| Best fit for | Teams where the bottleneck is everything around the contract, not only the contract | Teams whose primary bottleneck is high-volume contract review and redlining |
Based on publicly available information as of September 2026. Names and trademarks belong to their respective owners. If anything here is inaccurate or out of date, contact us and we'll update it.
Frequently asked questions
Sandstone handles the work before and around the contract — the request that arrives in Slack, the question that never becomes a document, the review that comes in as an email forward. It captures those, routes them with the counterparty history attached, and records how they were resolved. Review tools start once a contract is in front of you.
Sandstone is built for teams from roughly five to a hundred lawyers, and small teams tend to feel the context problem hardest because there's no one to absorb it. That said, if nearly all your load is reviewing contracts and little else, a focused review tool may be the better first purchase, and we'll say so.
Yes, playbook-driven and attorney-controlled, with playbooks built from your existing contracts and precedent rather than authored from scratch. Redlining is one capability inside the platform rather than the whole product.
In-house only. The workflows assume a legal department serving a business, not a firm serving external clients.
