Walking Down the Tail
If the tail is the product and honest declines mark its edge, then the work is a slow walk down the tail — turning each declined document into a handled one. That walk is what compounds into a tool nobody can catch.
If the tail is the product and honest declines mark its edge, then the work is a slow walk down the tail — turning each declined document into a handled one. That walk is what compounds into a tool nobody can catch.
Users don't carefully audit every field a tool extracts. They skim. A tool that assumes a thorough review gets one that doesn't happen — so the output has to be built for the glance, not the audit.
A user reviewing a tool's output has a small, fixed amount of attention to spend. The tool's real job at the review stage is to spend that budget where it changes outcomes — not to hope there's more of it than there is.
The dangerous extraction error isn't the one that looks broken — the user catches that. It's the one that looks exactly like a right answer and sails straight through the quick review.
If the last mile is getting output into the user's workflow, the first mile is getting the document in. The friction at the start of the task quietly decides whether the tool gets used at all.
A document tool's job isn't done when it produces a correct result on its own screen. It's done when that result is sitting in the format and place the user actually works in. The gap between those is where tools quietly fail.
The highest compliment a workflow tool can earn isn't 'I love using it.' It's that the user stops noticing it — because it fits the work so well it stopped being a separate step.
The extraction engine is increasingly a commodity. What's left as the durable product is the domain knowledge encoded around it — and that's the part a generic competitor can't copy.
Aggregate accuracy treats every field as equally important. The user doesn't. Where a tool spends its reliability should follow the cost of being wrong, not the count of fields.
The instinct is to extract every field a document contains. The more useful discipline is deciding which fields the tool should refuse to extract — and saying so.