# Build vs. Buy for Intelligent Document Processing: Proven Pattern or Science Project

What you are actually buying, the checklist that separates a proven document-processing pattern from a demo, per-page economics at millions of pages, and the hybrid answer most institutions should choose.

Every institution with a document backlog faces the same fork: license a platform, or build on the pattern. The honest answer depends on what you are actually buying — and the market works hard to blur that. Vendors sell "AI document processing" as if it were one thing. It is at least three: an OCR engine, a processing pipeline, and an outcome (a prepared, citable record). They have different economics, different risks, and different build/buy answers.

## Price the outcome, at your volume

Per-page pricing looks trivial in a pilot and dominates at scale. Run the arithmetic at your real volume — an institution processing millions of pages a year should model the three-year cost of per-page licensing against the cost of running the pipeline on infrastructure it controls, where the marginal cost per page is compute, not licence. Neither answer is automatically right. But the decision made on pilot pricing is automatically wrong, because pilots are priced to be approved and production is priced to be renewed.

## The proven-pattern checklist

Whether you build or buy, demand the same evidence. A proven pattern has:

- **Provenance** — every extracted fact and summary claim linked to its source page, mechanically checkable.
- **Deduplication and classification** as first-class stages, not search-time patches.
- **Bilingual processing** measured per language, if your files are bilingual.
- **Measured accuracy** — field-level, on representative messy files, with a golden dataset you can inspect.
- **A human-in-the-loop design** — confidence routing, review queues, corrections captured as training data.
- **Privacy by architecture** — residency for processing as well as storage, no training on your data, full audit logs.
- **A deliverable you can cite** — searchable, bookmarked, hyperlinked, stably paginated output.

A science project has a demo on clean PDFs, an accuracy claim without a methodology, and a roadmap where your requirements live. The checklist is how you tell them apart in an evaluation, before the contract does it for you.

## What building really commits you to

Building on the pattern — OCR services or engines, a vector store, orchestration, your own QA discipline — buys control: residency is yours to guarantee, per-page costs collapse at volume, and the pipeline encodes your institution's taxonomy and standards. It commits you to operating it: model and engine upgrades, accuracy monitoring, the golden dataset's upkeep. Institutions with sustained volume and in-house (or partner) engineering depth usually find this trade favourable. Institutions with a one-time backlog usually do not.

## The hybrid most should choose

The pragmatic middle: buy the commodity layers — OCR engines are mature, competitive, and not where your institution's uniqueness lives — and build (or have built) the layers that encode your judgment: taxonomy, dedup rules, provenance discipline, QA workflow, deliverable standard. This keeps the differentiating parts under your control, keeps exit costs low because your index, metadata, and golden datasets are yours, and avoids paying licence rent on the parts of the system that constitute your institutional knowledge.

Whichever route you choose, write the checklist into the evaluation and the exit terms into the contract on day one. The pattern is proven. Make your vendor — or your own build — prove it again, on your files.
