One question, five hundred contracts: review tables
Ask
Columns are questions, cells are answers
The idea is deliberately plain. You pick a set of contracts, a whole vendor category, everything expiring this quarter, or the entire estate. Then you add columns, and each column is a question in plain English. What is the liability cap? Is there an uplift cap, and at what percentage? What is the notice window for termination? Does this contract permit a benchmark reprice?
The agents read every contract and fill the grid, and crucially, each cell carries a citation back to the clause it came from. You are not trusting a summary. You are looking at an answer with a receipt, one click from the exact page and paragraph it was drawn from. A blank or a flagged cell is its own signal: this contract is silent on a protection the others have.
Scale is the whole point. Running one of these questions by hand does not really get harder as the estate grows, it just gets longer, until the honest answer to "have we checked all of them?" becomes "no, we checked the ones we had time for." A review table does not tire on the four hundredth contract. It reads the whole estate with the same attention it gave the first, which is precisely the part a human reviewer cannot promise at three in the afternoon.
app.isvcosell.com/review-tables
Columns are the questions, rows are the contracts, and every cell links back to the clause that answers it.
THE SAME JOB, TWICE
TODAY, BY HAND
The question arrives, which contracts are missing a price cap, and the answer lives in hundreds of PDFs across shared drives and inboxes.
A paralegal opens the documents one at a time, copying findings into a spreadsheet until the will runs out.
The honest answer to have we checked all of them becomes no, we checked the ones we had time for.
When the board asks about exposure, the reply is let us come back to you.
A week of somebody opening PDFs, per question
WITH ISVCOSELL
Open a review table and pick the contracts: a vendor category, everything expiring this quarter, or the whole estate.
Add columns as plain English questions: the liability cap, the uplift cap, the termination notice window, the mid term increase rights.
The agents read every contract and fill the grid, each cell cited one click back to the exact clause, with silent contracts flagged as gaps.
Sort and filter to the exceptions, and use document search underneath for the concept question you did not see coming.
A column added before lunch, answered across the whole estate
What changes: the week of PDF opening becomes a column you run in minutes, and the coverage goes from a sample to everything. A liability review across 500 contracts at even 20 minutes per contract is more than 160 hours of reading; the table does it with a citation in every cell, and the flagged gaps, the contracts silent on a cap, are exactly the exposures the sampled approach never found.
The shift is from reading contracts to interrogating them. A liability review that used to mean a paralegal opening files for a week becomes a column you add before lunch. And because the answer set is a table, you can sort it, filter it, and act on the exceptions instead of the whole pile.
"A contract you cannot query is a contract you are not really managing. It is just a file you hope you never need."
PART TWO
Grounded answers, not confident guesses
The danger with running AI over legal text is a fluent answer that is quietly wrong. On a contract, a hallucinated liability cap is not an inconvenience, it is a decision you will make badly. So review tables sit on the same rule as everything else here: no answer without a source. Every cell is grounded in a specific clause, and when a contract genuinely does not address a question, the honest output is a flagged gap, not an invented number.
Underneath the table is full document search across the estate, so you can also go the other way. Instead of asking a fixed column, you can search for a concept, indemnification, data residency, most favored nation, and see every contract that touches it, ranked and quoted. The table is for the questions you ask often. The search is for the one you did not see coming.
The two together turn the estate from a liability you hope about into one you can actually report on. When the board asks how exposed you are on a given risk, the answer stops being "let us come back to you" and becomes a filtered view you can share in the meeting, every figure in it traceable to the contract it came from.
app.isvcosell.com/document-search
Search a concept across every contract and get the exact passages back, quoted and linked. No answer without its source.
WORTH A COLUMN
The weekly licensing brief
Want to be updated when major licensing and pricing changes land? One analyst brief a week: the price rises, metric changes and audit campaigns that move software costs. Work email only.
Get the brief
Questions to ask your whole estate
1 Where are we uncapped? Liability caps and uplift caps, listed for every contract, with the silent ones flagged first. Missing protection is the exposure.
2 What renews without us? Auto renewal clauses and their notice windows across the estate, so no window passes because a PDF went unread.
3 Who can raise prices mid term? Contracts that permit in term increases, and on what terms, so a surprise invoice meets a clause you already found.
4 What did we already pay for? Swap rights, true down windows, price holds, and SLA credits, surfaced before they expire unused.
THE HONEST LIMIT
The table finds it, a person decides it
A review table does not give legal advice, and it does not close a gap on its own. What it does is end the excuse that the estate is too large to look at. It turns "we would have to check all of them" into a column you run in minutes, with every answer traceable to the paper it came from.
From there, the judgment is yours. But you are now making it with the whole board in front of you, exceptions sorted to the top, instead of a sample of the contracts someone had time to open. That is the difference between managing an estate and hoping about one.
About the author
Fredrik Filipsson, Cofounder, ISVCOSELL
Fredrik has spent more than twenty years in enterprise software, with time at Oracle, IBM, SAP, and Salesforce before moving to the buy side. He structured and priced the kind of large agreements most buyers only see once or twice in a career, which taught him where the leverage sits and how far a vendor will actually move. He started ISVCOSELL to hand that knowledge to every sourcing team.
More posts by FredrikConnect on LinkedIn →
See it in the product
How benchmarking works →Browse the use cases →Every feature →Calculate your time saved →
FREE TRIAL · FULL PLATFORM · NO CARD REQUIRED
Ask one question across every contract you hold.
The free trial opens the benchmarking database, 1,483 vendors deep, plus the negotiation guides, playbooks, and talking points for your own renewals. No card needed, a corporate email is all it takes.
Start your free trial →Or decode a contract free, no account
Free for 30 days, no card needed. Your data stays isolated at the database, and you can export or delete it any time.
Watch it in action
Nobody read the contractWhat changed in the new paper?One question, every agreement
Browse the full demo library →
THE ISVCOSELL AI BRIEF · WEEKLY
The week in enterprise software buying, in one email.
What shipped on the platform, and the pricing and licensing moves worth knowing before your next renewal. One email a week, to your work address. Unsubscribe any time.
Subscribe
Related reading
- Or decode a contract free, no account
- Start your free trial
- See what changed
- How benchmarking works
- ← All posts
- Every feature
- FF
- Calculate your time saved
- Browse the use cases
- Browse the full demo library
- What changed in the new paper?
- Nobody read the contract
- One question, every agreement
Pricing data and source text from the VendorBenchmark library. Co-sell reading is this site’s.