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 the part numbering cannot. One reads page layout instead of clause numbers, the other proposes which earlier clause a new one matches. Both propose and a person decides, and below a set confidence we publish no diff at all.
No card. The rate is on this page.
€290
per watched vendor, per year
10 watched vendors
the minimum watchlist, and the reason a small estate should not buy this
2 business days
the target for a diff held in review, and not a guarantee
Why a second line item
We already pay for a spend platform. This is a second line item for paperwork.
Put that way it should lose. Against the job that platform does, it does lose.
The order form arrives with a Master Services Agreement as a PDF, and a second PDF setting out what the subscription entitles you to. Both download. Neither links. Prior versions come on request.
So the review runs on a document nobody can cite, and at renewal the reconstruction runs again from zero.
Vertice's pricing FAQ says its team leads negotiations as an extension of your procurement function, against benchmarking data for more than 32,000 vendors.
None of that answers which clause moved. We do not negotiate and we hold no benchmarks. We hold the text, dated and hashed, with the changes marked.
Pricing
Why it shows no saving
It produces no saving, so nothing pays for it.
Correct. Read one more paragraph before deciding that settles it.
Vertice's pricing page claims 20% average savings, 7x ROI and 90 days payback. Its figures, not ours.
This is a record, not a saving, and a record has to exist before the week you need it. Nobody buys last year's version history at renewal.
Compare
Recension against Vertice, on the five criteria this reviewer weighs
Two of them go against us, and they are the two a procurement lead cares about most.
Numbers
Figures this page is willing to stand behind
Each one is a term of the product or the arithmetic of your own exposure. None of them is a result.
- 01€290per watched vendor per year, at 10 to 25 vendors
- 02€2,900the floor, being the ten-vendor minimum at the published rate
- 03€190the rate above 100 watched vendors
- 04SHA-256hashed on the response body nightly, and kept on the source file we deliver
- 052 business daysthe target for a diff withheld in review, stated as a target
- 0624 monthshow long a cited clause URL keeps resolving after the license ends
Why you can check our work
If your parse is wrong, I have cited a machine's mistake in a review memo.
That is the right objection. It is also the one the product is built around.
The source file as fetched ships beside our extraction, with its hash, headers and timestamp. The verification script recomputes the chain: if the two disagree, you can prove it without us.
A version is never edited. A correction ships as a new one with an errata note, and the superseded version stays resolvable.
Setup
Week one, in the order it actually happens
The slow part is day one, and it is on your side.
- 01Send the listthe SSO application export or the renewal tracker, arriving with trading names, duplicates and entities acquired two years ago still in it
- 02Coverage reportrun before any contract, sorting your list three ways: vendors publishing at a stable URL, vendors publishing downloadable files only, and vendors publishing nothing we can find
- 03Name the watchlistsomeone on your side signs off which vendors are on it, a decision nobody has had to make explicitly before, and it takes a day of asking around
- 04Bucket and roleyour cloud team creates the delivery bucket and the role we assume to write into it, which is a ticket in a different queue from the one legal is working
- 05First dropthe backfill runs, then a Parquet partition and a JSONL file land the next night, empty partition and manifest if nothing moved
what you get
One clause, two versions, and the span that moved
What a diff looks like when the schedule underneath it was renumbered.
| 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.
A model proposes clause matches across versions and a similarity score ranks them. Above threshold the pair is diffed span by span; below it, nothing ships.
Clause 9.2 reported unchanged when it moved gets pasted into a review ticket and relied on at signature. A wrong diff is worse than a late one, and late costs us up to two business days.
Scope
What we refuse, and what the license actually buys
The first three are refusals. One of them is a capability you may want more than anything here.
- in scope01Nightly capture of every document each watched vendor publishes, kept with its response headers, its fetch timestamp and its source SHA-256.
- in scope02Clause-level diffs against the previous captured version, marked unchanged, reworded, moved, new or removed, or held back as unaligned.
- in scope03A permanent URL and a citation line on every clause version: vendor, document, effective date, capture date, clause path and source hash.
- we don't01We do not negotiate with your vendors and we hold no pricing benchmarks. Vertice's team leads negotiations as an extension of your procurement function, against benchmarking data for more than 32,000 vendors. That is a real capability we do not have.
- we don't02We do not take, store or diff your executed contract. Your signed MSA against the vendor's current published one is a comparison you run yourself, against our text.
- we don't03We do not score risk. No red, amber and green, no playbook fit, no flag calling a clause unfavorable. Whether a change matters stays the reviewer's call.
Ask for one clause record and its diff
Name and work email. Tell us the vendor when you reply to the confirmation.
We'll come back within one business day with a straight yes or no.