# Your Agreements Are a Database You Can't Query — Hiral Shah, Docusign & Sean Sodha, NVIDIA

Source: [AI Engineer](https://www.youtube.com/watch?v=_gvamfT8H-w)  
Feed7 permalink: https://feed7.dev/p/your-agreements-are-a-database-you-can-t-query-hiral-shah-docusign-sean-1aigd7h  
Published: 2026-09-16T15:30:28.000Z  
Trust: Source Linked (source_linked)

## Why Included

Docusign and NVIDIA use a small extraction model to preserve complex agreement tables as structured data, showing where specialized parsers can beat generic VLMs in agent pipelines.

## Source Summary

Docusign says it processes **about 1 million agreements daily** across 1.9 million paying customers. Pricing, SLA, and rate-card tables often defeat line-oriented extraction, especially with merged or nested cells.

## Practical Implication

Use specialized extraction before retrieval when an agent must reason over table structure. The NeMo Retriever parse model preserves layout, reading order, and table relationships; Docusign reports **20× faster table extraction** than the open models it tested.

## Agent-Ready Context

Docusign says it processes **about 1 million agreements daily** across 1.9 million paying customers. Pricing, SLA, and rate-card tables often defeat line-oriented extraction, especially with merged or nested cells.

Use specialized extraction before retrieval when an agent must reason over table structure. The NeMo Retriever parse model preserves layout, reading order, and table relationships; Docusign reports **20× faster table extraction** than the open models it tested.

The talk does not provide the underlying scores, model list, or production error rates. Docusign still uses a hybrid pipeline with OCR for other fields, while quantization and multi-token generation were described as future optimization paths.

## Connected Context

Feed7 judgment across 807 accumulated Signals:

Retrieval cannot recover structure that ingestion has already flattened incorrectly. For agreements containing merged or nested tables, a layout-aware specialist parser becomes a prerequisite to dependable downstream reasoning, while the retained OCR path confirms that extraction should remain hybrid. The reported speedup supports task-specific model selection but lacks enough evaluation detail to establish accuracy or generality.

- [Teaching Nemotron Greek: Mining a Corpus, Adapting Retrieval, and Grounding Generation for Modern Greek across Specialist Domains](https://feed7.dev/p/2608-05138v1-0bvu6le) — Both turn RAG into a staged, workload-specific selection problem: the target specializes parsing before retrieval, while the candidate adapts retrieval and grounding for a particular language and domain.
- [When Does Bigger Help? A Controlled Study of LLM Scale for Ontology Learning](https://feed7.dev/p/2608-31118v1-1abyqwd) — The specialized parser reinforces the finding that model scale alone is a weak selector; success depends on matching model architecture and evaluation to the structured task.
- [Compression at the Edge — NVIDIA, Unsloth, HuggingFace, Ollama](https://feed7.dev/p/compression-at-the-edge-nvidia-unsloth-huggingface-ollama-0zq97jq) — Because quantization is only a proposed next step here, the candidate supplies the implementation consequence: any compressed parser artifact must be tested inside the real extraction pipeline for speed and quality.
- [Local Models: Trust, Control, Optimization — Carter Abdallah, NVIDIA](https://feed7.dev/p/local-models-trust-control-optimization-carter-abdallah-nvidia-17u7gz9) — The parser is a concrete case for controllable open-model infrastructure, but its benchmark omissions also confirm that ownership and customization do not by themselves demonstrate task quality.

## Context Map

- Layer: model
- Domains: data
- Topics: model-selection, retrieval, open-models

## Uncertainty

- The talk does not provide the underlying scores, model list, or production error rates. Docusign still uses a hybrid pipeline with OCR for other fields, while quantization and multi-token generation were described as future optimization paths.

## Agent Instruction

Use this item as source-backed context. Do not invent claims beyond the linked source. If this item conflicts with another source, call out the conflict.