Legartis

What it is

Legartis is a Swiss AI contract review tool that reads incoming third-party paper against a playbook you define and returns a clause-by-clause position on it. The company is based in Zurich and was founded in 2017 by Michael Fetzer, David Alain Bloch, Marc von Samson Himmelstjerna and Don Tuggener. On 2026-04-20 it repackaged the review engine as the Legal AI Workspace — a Legal Agent for questions and drafting, a Contract Playbook Creator, and portfolio-level Contract Insights — and on 2026-05-28 it added Contract Management, which brings a repository with version history, status tracking, task assignment and DocuSign signing. The product it most resembles is LegalOn: playbook-driven review of counterparty drafts, sold to in-house teams, now extending sideways into lifecycle.

The load-bearing difference is where it runs and what language it reads. Legartis states that all servers sit in Switzerland and Europe, holds ISO 27001, and reviews across European languages rather than routing everything through English. Named customers are DACH industrials and institutions — Zürcher Kantonalbank, dormakaba, TÜV NORD, Emmi, Fiege, Framatome — which is the buyer profile the residency posture is built for.

Why it shows up in Legal Ops stacks

• It publishes prices, and almost nobody else here does. Spellbook withdrew its $99 and $179 tiers, LegalOn pulled the $550 Individual plan, and LegalFly has never had a pricing page at all. Legartis posts four tiers with real numbers on three of them. You can build a budget before you book a demo — true of one other vendor in this segment, Beck-Noxtua.
• German-language review is native, not a translation layer. The review, the playbook and the rationale all run in the contract’s own language. For a DACH team whose inbound volume is German vendor terms and DPAs, that removes the round-trip where an English-first reviewer loses the clause wording it was supposed to be matching.
• Playbook authoring is the product, not the onboarding tax. LawGeex died partly on four-to-eight-week rules encoding. The Contract Playbook Creator generates a first-pass playbook from standards you already have; Legartis puts that at hours rather than months, which is a vendor claim about its own tooling — test it during the free tier before it anchors your rollout plan.
• It stays in Word. The Legartis Word app covers Word 2019 and Office 365, so reviewers work where they already redline. An open REST API is the route for everything else.

Pricing

Four tiers, three of them public. Free is 1 seat and 2 contracts a month, restricted to NDA review against a pre-built playbook. Professional lists at CHF/€250 per user per month, or CHF/€2,500 per user per year on annual billing — €208 per user per month, about $223 — capped at 120 contracts a year with 3 custom playbooks. Team lists at CHF/€300 per user per month, CHF/€3,000 per user per year, behind a 5-seat floor, for 250 contracts and 5 playbooks plus custom insight dashboards. Enterprise is quoted, wants 10 seats and 500+ contracts, and adds unlimited playbooks, SSO, audit logs, advanced role management, priority support and a named CSM.

Price this per contract, not per seat, because the volume cap is the binding constraint rather than headcount. At the published caps Professional works out to €20.83 a contract and Team to €12. Two numbers to nail down on the order form: whether the volume cap is per seat or per account — at a 5-seat floor that is a 5x difference in what you actually bought — and the overage rate when you cross it, because the alternative to an overage rate is a tier bump.

Best for

In-house legal and procurement teams of roughly 5-25 people in DACH and the EU whose inbound volume is German, French or Italian vendor paper, NDAs and DPAs, and whose security review would stall on a US-hosted processor. The ROI band is 150-500 reviewed contracts a year: under that the seat price does not amortize against the caps, over it you are in Enterprise negotiation and should be pricing Legartis against a full CLM rather than against other reviewers.

It is the wrong buy for three groups. US-only teams pay a residency premium they never consume and get a thinner integration surface than Spellbook or Ivo. Teams whose bottleneck is drafting their own first-party paper rather than reviewing someone else’s want DraftWise or Spellbook instead. And teams whose contracts live in iManage, NetDocuments or SharePoint should stop at the integration list — Legartis names Word, DocuSign and a REST API, and nothing else.

Alternatives and when to pick them

LegalOn is the pick for multi-jurisdiction in-house work spanning the US and Japan as well as Europe, and for teams that want attorney-written standards shipped with the product instead of authoring playbooks. It costs more and quotes everything. Spellbook has the largest installed base in the segment and is the drafting-led choice for law firms working in English; see LegalOn vs Spellbook for that split. LegalFly is the fastest-growing entrant here — the Belgian vendor grew ARR more than 800% in 2025 with churn under 5%, has raised about €17M, and was preparing a Series B for 2026 — and it wins when you need on-premise anonymisation and a rollout across legal, procurement and compliance at once, if you can absorb enterprise-only quoting. Ivo matches the in-house review-and-playbook job when your agreements sit in one English-language jurisdiction. Noxtua is a different job entirely: German legal research over publisher-licensed content, not review throughput. If the constraint turns out to be lifecycle rather than review, Ironclad and Agiloft own that side.

Watch-outs

• Contract Management shipped 2026-05-28 and has not seen a renewal cycle. Guard: keep your current repository as system of record through the first full renewal season and run Legartis Contract Management alongside it, reconciling the two on renewal dates and party names before you cut over.
• Volume caps meter the product, and most teams do not know their real number. Guard: count reviewed third-party documents for one quarter before you sign, multiply by four, and buy to that figure with the overage rate written into the order form.
• Swiss hosting sits outside the EEA. Guard: the European Commission’s adequacy decision for Switzerland is the instrument that makes those transfers routine, but the sub-processor list is what decides your actual posture — request it, and have your DPO or counsel confirm the current instrument rather than treating “servers in Switzerland” as the finished answer. See GDPR for legal teams.
• The integration surface is Word, DocuSign and a REST API. Guard: if contracts live anywhere else, get the endpoint list and rate limits before signing and budget the connector work as part of year one, not as a later phase.
• Vendor scale is small and funding is undisclosed. Tracxn’s most recent public headcount figure is 35, as of July 2024. Guard: ask for a documented bulk-export path for contracts, playbooks and review history in a neutral format, and exercise it once during the trial rather than trusting that it exists.