The Document Agent finishes as an application | VendorBenchmark Blog
V VendorBenchmark
Benchmarking Use cases Features Security Integrations Pricing About Blog Log in Start free trial
← All posts
PRODUCT UPDATE · FROM THE ANALYST DESK

The Document Agent finishes as an application: one command table, undo, a search language, and a desk that talks beside the clause

We shipped the finished shape of the Document Agent. One command table behind every menu, real Undo, a token search language, and comments that sit beside the clause they concern.

By , Cofounder
September 11, 2026 · 9 minute read · LinkedIn
Product Update Document Agent

Most buyers do not lose negotiations on price. They lose the thread. A clause you flagged three weeks ago is now buried under a redline nobody labelled, the comment you left is stranded in an email, and the version you approved is one of six PDFs with the same filename. The Document Agent was already the place you read archived contracts without leaving the app. What shipped this week is its finished shape as an application, and the point of it is to stop the thread going cold. If you have followed the Document Desk, this is where it grows a spine.

PART ONE

One command table behind every surface

Every menu, the toolbar, the right click, and Ctrl K now read the same command table. That sounds like plumbing, and it is, but the effect on a buyer is direct. The action you find by right clicking a clause is the exact action you find in the menu and the exact action Ctrl K surfaces when you type its name. There is no drift between how you reached a command and what it does. When you train a colleague, you train one vocabulary, not three.

The Edit menu now carries Undo and Redo, Ctrl Z and Ctrl Y, for every reversible move. Reorder a set of clauses, retag a position, fold a pane, and you can walk it back without hunting for the previous state. This matters most when you are working fast under a deadline and need the freedom to try a structure, see it, and reverse it. The cost of a wrong move drops to nothing, which is the condition under which people actually explore.

app.vendorbenchmark.com/doc-search
The Document Agent search interface showing tokenised query filters for vendor, date, and clause type
The question line turns typed prefixes into search tokens as you type.
THE SAME JOB, TWICE
TODAY, BY HAND
Open the shared drive and scroll the folder of signed PDFs looking for the right counterparty and date
Search each file separately for the limitation of liability language, copying passages into a spreadsheet
Trawl your inbox for the comment thread where legal raised the uplift concern
Draft a summary memo from scratch, reconciling which version everyone actually approved
Roughly 9 hours, spread across a week
WITH VERA
Type vendor: and the counterparty name, then before: a date, and clause: liability into the question line
Read the matching clauses on the page with comments sitting beside each one
Open the brief, which edits in place, and check the version timeline for the approved state
Send the composed note from the desk, which mentions the papers and clauses by reference
About 20 minutes of your attention
What changes: 9 hours of file archaeology becomes 20 minutes of directed reading. For a buyer running, say, eight of these reviews a month, that is roughly 70 hours a month reclaimed, close to two working weeks that go back into the negotiation itself rather than the hunt for the paper.
PART TWO

The question line learned a language

The biggest change for daily use is the search language. As you type, vendor:, signed:, before:, after:, and clause: become tokens, and a quoted phrase becomes a token too. So vendor: Acme after: 2023-01-01 clause: indemnity finds you exactly that, and "most favoured nation" pulls every document carrying the phrase. You are no longer describing what you want to a box that guesses. You are constructing a filter that means one thing. Buyers who work across a large estate will recognise the difference between a search that is fuzzy and a search that is deterministic. This one is deterministic.

"The cost of a wrong move drops to nothing, which is the condition under which people actually explore."

The foot of the window is now a status bar of doors, so the places you move to are always visible at the edge. The rail and the evidence pane fold to strips when you want the clause to have the room, and unfold when you want the context back. The ledger and the Library carry a Columns chooser with grips and groups, so you decide which fields sit where and in what order. The question tabs drag, which means the way you arrange your open queries is yours to set. None of this is decoration. It is the difference between a tool you bend to your work and a tool you bend your work around.

PART THREE

A desk that talks beside the clause

Comments now sit beside the clause they concern, not in a separate thread you have to correlate by memory. When your legal reviewer questions an uplift, the question lives next to the words it questions. The desk composer mentions papers and clauses directly, so a note you send carries its references rather than a paraphrase of them. The titlebar shows who else is in the window, which removes the small but real risk of two people editing the same brief blind to each other.

app.vendorbenchmark.com/clause-library
The clause library showing positions and comments anchored to individual clauses
Comments and positions attach to the clause, not a detached thread.

The cap line prices the uplift above the cap you hold out for, so you can see, in the moment, what a proposed increase costs relative to the ceiling you set. That connects the reading directly to the position, which is the part buyers usually have to do in a second spreadsheet. If you want the arithmetic of switching costs alongside it, that pairs naturally with measuring lock-in before the vendor prices it for you. The brief edits in place, and every version of a brief sits on a timeline, so the history of a position is visible rather than reconstructed from filenames. Help walks you through the window when you need it, which lowers the cost of handing this to someone new.

1
One vocabulary, everywhere. Menu, toolbar, right click, and Ctrl K read one command table, so the action is the same wherever you reach it.
2
Undo on every reversible move. Ctrl Z and Ctrl Y cover reordering, retagging, and folding, so exploring a structure carries no cost.
3
A search you can trust to mean one thing. vendor:, signed:, before:, after:, clause:, and quoted phrases become tokens as you type, giving you deterministic filters instead of guesses.
4
A window you arrange, not one that arranges you. Panes fold to strips, columns choose and group, and question tabs drag into the order you want.
5
Comments and cap arithmetic beside the clause. Reviewers talk next to the words, the cap line prices the uplift, and the brief keeps every version on a timeline.
PART FOUR

Where it fits, and where it does not

This sits at the reading and drafting end of the deal. It does not approve anything, and it is not the sign off chain. When a brief is ready for signatures, that hands to the sign off chain, which carries approvals before signature with a brief for every approver. The Document Agent gets the brief right. The chain gets it signed. Keep the two jobs separate in your head and the workflow stays clean.

Be clear about the limits. The search language is exact, which is its strength and also its edge. If a document uses different words for the same idea, a clause: filter finds the tagged clause, not every synonym in the prose, so quoted phrase search remains your fallback for language you know is there but is not classified. The cap line prices the uplift against the cap you set, and it is only as good as the cap you set, so a poorly chosen ceiling produces a confident but wrong number. Undo covers reversible moves, and a few actions, sending a note from the desk among them, leave the window and are not reversible from the Edit menu. And presence in the titlebar tells you who else is in the window, not what they are about to change, so coordination on a shared brief is still a conversation, not a lock. Used with those limits in mind, this is the fastest path we have shipped from a folder of PDFs to a brief you can defend.

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.

About the author
, Cofounder, VendorBenchmark

Morten brings two decades of enterprise and software procurement, with stints across Oracle, IBM, SAP, and Salesforce shaping how he reads a deal. He has led sourcing through hundreds of renewals, from mid market order forms to nine figure global agreements, and learned that the buyers who win are the ones who walk in knowing the market. He built VendorBenchmark to make that pattern recognition repeatable.

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

Read your contract estate the way you already think about it

The free trial opens the benchmarking database, 1,483 vendors and their product lines, 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
Vera AI: the three minute demo Vera AI: the three minute demo What discount should we expect? What discount should we expect? One question, every agreement One question, every agreement
Browse the full demo library →
V VendorBenchmark
A VendorBenchmark product · © 2026