Token classifier - reads layout, not numbering, and proposes where each clause starts and ends
Recension keeps a dated copy of your vendors' published terms and marks what changed
Every capture is hashed, split into clauses with permanent URLs, and diffed against the version before it. At renewal you can point at the clause that moved.
Two models do what numbering cannot: one reads layout, one proposes each clause's earlier version. Below a set confidence, a person rules before any diff ships.
€290
per watched vendor, per year
10 vendors
the minimum, too many for a small estate
2 business days
our target for clearing a held diff
Why a second line item
We already pay for a spend platform. This is a second line item for paperwork.
Judged on the job a spend platform does, it loses.
The order form comes with an MSA and an entitlements schedule, both PDFs. Neither links, and prior versions come on request.
Nobody can cite them, and each renewal starts from zero.
Vertice negotiates for you. It cannot show which clause moved.
Pricing
€290 per watched vendor, per year
Why it shows no saving
It produces no saving, so nothing pays for it.
Correct. A record has to exist before the week you need it.
Vertice claims 20% average savings, 7x ROI and 90-day payback.
Last year's version history cannot be bought at renewal.
Compare
Recension against Vertice, on the five criteria this reviewer weighs
Two go against us, and a procurement lead weighs those two most.
CriterionA rate before any callTerms you can link toPrior versionsSomeone to negotiateBenchmarks
Recension€290 per vendor a year, breaks publishedA permanent URL on every clause versionEvery capture kept, dated, hashed and resolvableNobody; we never talk to your vendorsNone held, none planned
VerticeThree tiers, no figureThe MSA is a 197KB PDF downloadAvailable on requestA Dedicated SaaS Buyer and a negotiating teamPricing data on 32,000+ vendors
Numbers
Figures from the rate card and the license
All terms or arithmetic; we publish no savings claim.
- 01€290per vendor a year, from 10 to 25 vendors
- 02€240per vendor a year, from 26 to 100 vendors
- 03€190the rate above 100 watched vendors
- 04€2,900the ten-vendor minimum, per year
- 05SHA-256the hash on every fetched file, delivered with it
- 0624 monthscited clause URLs keep resolving after the license
Why you can check our work
If your parse is wrong, I have cited a machine's mistake in a review memo.
Fair. Every extraction ships beside the file it came from, with its hash, headers and timestamp.
The open verification script lets you prove a mismatch without us.
Fixes ship as new versions with errata; old versions still resolve.
Setup
Week one, from vendor list to first drop
The slow part is day one, and it is on your side.
- 01Send the listSSO export or renewal tracker, duplicates included
- 02Coverage reportfree, before any contract; sorts vendors into web pages, files only, or nothing
- 03Name the watchlista day of asking around, then your sign-off
- 04Bucket and roleyour cloud team creates a bucket or Azure Blob container and our write role
- 05First dropafter the backfill, Parquet and JSONL land nightly, even when empty
The two models
Where a clause ends, and which clause it used to be
Numbering rules do most of it on a clean HTML page; the residue from a two-column PDF goes to two models.
Cross-version match - the embedding model proposes each clause's prior version, so 9.2 becoming 10.1 counts as moved
A fixed floor - score and similarity margin must both clear it, or no diff ships
The review queue - a reviewer confirms or corrects held pairs; the models retrain on them, never your watchlist
what you get
One clause, two versions, and the span that moved
What a diff looks like when the schedule underneath it was renumbered.
vendor terms · v11 to v12 · 4 Aug 2026
| clause | v11, 19 May 2026 | v12, 4 Aug 2026 |
|---|---|---|
| liability cap | 9.2, 12 months of fees | 10.1, 6 months of fees |
| notice period | 9.4, 60 days | 10.3, 60 days, unchanged |
| data location | 11.1, EEA only | 12.1, EEA and UK |
| sub-processors | 12.6, 30 days notice | 13.6, 30 days notice, unchanged |
| audit rights, 0.61 | 14.2, annual | held as unaligned, no diff published |
A drawn diff, not a real vendor. The last row scored under the floor, and a pair below it is withheld rather than published wrong.
What we chose
A low-confidence diff is withheld rather than published
The cost lands on you: on a heavily reformatted document the digest says something changed before it can say what.
Only pairs above the threshold are diffed and published.
A clause wrongly marked unchanged gets relied on at signature.
A diff that arrives two business days late does less harm.
Scope
Recension records what changed and leaves the judging to you
The first three are refusals; the first is a capability Vertice sells.
- in scope01Nightly capture of every vendor document, with headers, timestamp and SHA-256.
- in scope02Clause diffs marked unchanged, reworded, moved, new, removed or held as unaligned.
- in scope03A permanent URL and citation line on every clause version.
- we don't01We do not negotiate with your vendors or hold pricing benchmarks.
- we don't02We never see your signed contract; compare it with our text.
- we don't03We score no risk and flag no clause as unfavorable.
Ask for one clause record and its diff
Name and work email. Tell us the vendor when you reply to the confirmation.
We reply within one business day.