When a hobbyist uses an extraction tool, the output is the end of the line — they read it, they use it, they move on. When a professional uses one, the output is the beginning of something they may have to defend. The number they pulled from the lease goes into a memo that goes to a client. The summary they generated informs a recommendation that someone acts on with real money. If the output is later questioned — by a counterparty, a reviewer, a regulator, or just a skeptical colleague — the professional has to be able to stand behind it. That changes what the output has to be. It’s not enough for it to be right. It has to be defensible.

Defensible means traceable to a source. When a professional puts an extracted figure into their work product, they need to be able to answer “where did this come from?” with something better than “the tool said so.” They need to point to the specific clause, the specific page, the specific sentence the value came from — and they need that pointer to survive the trip from the tool into their own document. An extraction that produces a clean value with no traceable provenance is, for this user, a liability they have to manually backfill by going to the source document and finding the value themselves. Which means the tool didn’t save the work; it just moved it.

This reframes the citation feature from a nice-to-have into the core of the product. For a casual user, a citation is reassurance they’ll probably never click. For a professional, the citation is the deliverable — it’s the thing that lets them adopt the output into work they’re accountable for. A tool that extracts accurately but doesn’t make its provenance portable and verifiable has built the easy half and skipped the half that determines whether a professional can actually use it. The accuracy gets them interested; the defensibility gets them to rely on it.

There’s a workflow dimension too. Defensible output has to leave the tool in a form that carries its provenance with it. If the value is traceable inside the tool’s own interface but becomes a bare number the moment it’s exported to a spreadsheet or pasted into a document, the defensibility evaporated at the boundary. The professional is back to maintaining the link between value and source by hand. Designing for defensibility means thinking past the tool’s own screen to the document the output will actually live in, and making sure the provenance travels.

The strategic point is that “defensible” is a higher bar than “accurate,” and it’s the bar that the highest-value users actually apply. Plenty of tools clear the accuracy bar. The ones that clear the defensibility bar — traceable, verifiable, provenance that survives export — are the ones a professional can build their own accountable work on top of. That’s a narrower target and a more demanding one, but it’s where the willingness to pay lives, because it’s the difference between a tool that’s impressive and a tool that’s load-bearing.