Recent work

Six recent jobs, names withheld.

Here are the numbers. Ask about any of them and we will walk you through it.

Bulk scans · Texas operator

Four million pages of bulk scans, split and classified in 48 hours.

A scanning project produced roughly four million pages of bulk-scan PDFs, with dozens of instruments run together in each file. We split them into individual documents, keeping each instrument's pages and exhibits together and in order, classified each one, and delivered in two days. That operator has kept running work through us for the eighteen months since.

~4,000,000 pages48 hoursstill a customer 18 months on

Courthouse record · Midland Basin

A county's courthouse record, structured in 24 hours.

A private-equity-backed operator bought a county's full record: about 43,000 files and 1.15 million pages. The clock ran from the drive arriving to the CSV landing. We split it into individual instruments, classified them, extracted ten index fields from each (instrument type, parties, dates and recording references among them), and delivered one CSV their team loaded into their own database. Done by hand, that is a brokerage crew of thirty working for more than a month.

1.15M pages43,000 files24 hoursby hand: 30 landmen, a month

Data room · public E&P, post-close

A hundred thousand files, three land systems ago.

A public E&P had just closed a multi-billion-dollar acquisition and inherited a room of roughly 100,000 files, carrying agreement numbers from three generations of land systems, none of which matched. On the first tranche we resolved about half the unknown files on day one, from file names and folder paths alone, without opening a document. We then chained the old identifiers to the new ones through the company's own reference tables and linked each document to its leases and wells, in a table that loads straight into the land system.

~100,000 filesthree ID systems reconciledhalf the unknowns resolved on day one

Scan project · private operator

One box, pulled at random, checked for unrecorded instruments.

A land group midway through a scanning project asked us to take one box from about 800 completed scan boxes and find executed instruments never filed of record. We split and classified it against the team's list of recordable instrument types and flagged anything with no recording information. About twenty unrecorded leases and related instruments surfaced from roughly 1,500 pages, and the review shrank from every page to about a dozen per box.

~1,500 pages~20 unrecorded instrumentsreview: every page to about a dozen

Inherited portfolio · operator

Four sources, half a terabyte, 69 percent of it duplicate.

An operator inherited a portfolio spread across four sources in two states: 382,338 files and about half a terabyte, with the first share alone running fourteen folders deep. The inventory ran from metadata, before a person opened anything. On the first share put through classification, about 62,000 files collapsed to about 27,000 unique documents, which took roughly 30 percent off the classification bill before a model read a page. 862 duplicate groups were kept and flagged rather than removed, because they were standard forms that belong in every deal packet.

382,338 files69% duplicate~30% off the classification bill

Diligence · acquirer, thirty-day push

Six units checked against the seller's schedule in seven days.

An acquirer in a thirty-day diligence push sent the leases, amendments and agreements behind six units on a Monday. Seven days later they had each unit's working and net revenue interest by formation, reconciled against the seller's schedule, with the instruments of record behind every interest and a flag wherever the record did not close. Three units reconciled with no variance. Two differed from the schedule by fractions the record explained. One was about 476 net acres short in one formation, and the client's own title opinions corroborated it. We handed over the record. Their examiner made the call.

six unitsseven daysthree clean, two explained, one shortfall

Who else runs paper through this

The same four operations, on different paper.

Mineral and royalty packages.

Conveyances, division orders and addenda-heavy leases read across a package rather than a document at a time, for royalty terms, depths, and the fraction and legal description each instrument states, with the page beside each value, so net royalty acres are worked from the record rather than from memory. Owner mapping runs grantor to grantee through the conveyance chain on legal description and recording reference. Mineral packages have run through these operations; there is no headline job for one on this page yet.

Title and abstract firms.

A county's recorded instruments split, typed and indexed in a day, for your examiners to work from. We source recorded instruments you don't hold from the county, quoted exactly before anything retrieves. We do not render title opinions; your name goes on the work.

Right-of-way and surface files.

Easements, pipeline grants and surface use agreements, each grant chained through its partial assignments to today's holder, with width, crossing and consent language pulled beside it, delivered as a matrix your ROW team can act on. Route files have run through the same operations. Ask us for one.

A sensible next step

Run a sample on records you already know.

Pick a few thousand pages your team already knows: one folder from the room, a box of scans, a right-of-way file, a mineral package. We return them split, classified and linked, every value pointing to its page, with an inventory of the rest. Your team judges the output on their own documents before anyone talks about a project.

  • Instruments split and typed, exhibits kept with their parent, in order.
  • The fields that tie each one to a lease, tract, well or owner, each with its page.
  • A short inventory of the rest of the room, with a page count.
  • No obligation after it. Back inside a week.
  • Handled under the public MSA, or a mutual NDA if you prefer. Deleted when the sample is done unless you ask us to keep it; that is the platform's default.

If your team doesn't like what comes back, that's the end of it.

Tell us about the sample

Or email whit@infersoft.com. The Master Service Agreement is public.