Comparison
Your landmen are good at the work that requires judgment: chain construction, abstractor's notes, curative recommendations, the call on whether an instrument controls. They aren't search-engine operators or PDF-naming clerks, and they shouldn't be. We do the records work first so they can spend their day on the chain.
The current state
If you run a land department of any size, this is the picture you already know. It's nobody's fault and everybody's working hard:
A new tract comes in. A landman opens a fresh Excel workbook and types column headers. Same headers as the last fifty workbooks, typed again, formatted again, sometimes a little differently than last time. The first hour of the job is administrative setup. The first day is records-stitching.
The county clerk online portal. The CAD's GIS viewer. The RRC well browser. The GLO survey index. Probate. District court. Each with its own login, its own search idiosyncrasies, its own download quirks. Each landman has their own bookmarked workflow, and trains every new hire from scratch.
The same deed, the same lease, the same release. Each landman who needs to look at it pays the per-page fee, downloads it again, names it their own way, drops it in their own folder. The exact same PDF lives, paid for, in fifty places on the file server. Nobody can find it from anyone else's name.
"Try 'Smith' with one R. Try 'Smyth.' Try just the first name. Try with the middle initial. Try the spouse." The same painstaking name-juggling on every record search, by every landman, across every county. The skill is real. The repetition is murderous.
SmithToJonesWD.pdf · smith-jones-wd-2003.pdf · WD_2003_Smith_Jones.pdf · Vol1822Pg443.pdf · scan_001.pdf · IMG_4471 (3).pdf. Five conventions on one file server, each landman convinced theirs is correct. Six months later nobody can find anything without asking the landman who downloaded it.
The same chain, run by three different landmen on three different transactions, produces three different runsheets. Slightly different normalization. Slightly different tags. Slightly different abstractor's notes. The institutional knowledge from runsheet #1 doesn't carry to runsheet #2. The thirtieth time someone abstracts that survey, it's still the first time.
None of this is a knock on your landmen. They're doing the only thing the workflow allows. The workflow is the problem.
The County.Land alternative
The shift is small to describe and enormous in practice. Instead of building a runsheet from scratch, your landman starts from a finished runsheet and removes what they don't need. Subtractive, not additive. The abstract is already built. The instruments are already pulled, OCR'd, normalized, named, tagged, indexed, and linked. Their job is judgment, not assembly.
Open the County Foundation. Filter to the abstract. The runsheet is already there: every recorded instrument, chronologically, normalized, with tags and abstractor's-note placeholders. Your landman scans, removes the rows that don't matter to this engagement, and writes the notes. Hours, not days.
Every PDF lives once. Named consistently. Indexed consistently. Linked from every row that references it. The fifteenth landman to look at a 1947 deed opens the same file as the first: same name, same hash, same OCR. No duplicate downloads, no duplicate fees, no duplicate folders.
Smith, Smyth, Smithe, Smith Jr., Smith II, the estate of W. M. Smith: all collapsed to a canonical entity ID, audit-trail intact. Search the canonical name; see every variant, every instrument, every transaction. The name-juggling is done once, by us, and never again, by anyone.
The RRC join your landman would have done by hand: done. The CAD parcel overlay they'd have built in QGIS: done. The GLO survey-to-abstract crosswalk: done. The mechanical joins ship with the workbook. Your landman walks into the file with everything already on the desk.
The thirtieth runsheet on a survey isn't the first time anymore. The abstractor's notes on previous engagements are visible (with permission), the curative threads, the flags from prior litigation, all attached to the abstract record. New landmen onboard onto a county that already remembers itself.
Your landman delivers the same work product (same craft, same judgment, same defensibility) in a fraction of the time. And because the records work is done correctly once, the runsheet is also tighter: fewer missed instruments, fewer normalization errors, fewer renamed-twice files.
Run the numbers
A single tract is the typical billable unit on an oil & gas leasing or HBP-defense file. A survey abstract may contain a hundred or more tracts. Move the sliders to fit your team and the work in front of you. Whole-county engagements are scoped separately as custom work, let's talk.
% of time on records-stitching
—
of every tract spent on search, pull, OCR, naming, normalizing — not judgment
$ wasted per tract · across team
—
team-wide cost per tract at the day rate above
Total wasted
—
across the whole team, at typical throughput
Numbers are honest typical ranges, not guarantees. Hot Permian abstracts run heavier, quiet East Texas abstracts run lighter. The shape of the savings holds.
| Per tract | From scratch | From a Foundation runsheet |
|---|---|---|
| Set up workbook | 30 min, open Excel, type headers, format | 0, workbook ships ready |
| Search county clerk index | 2 to 6 hrs across name variants, abstract searches, instrument-type passes | 0, already harvested, OCR'd, normalized |
| Pull and pay for PDFs | 1 to 4 hrs, per-page fees, individual downloads | 0, already in the document library, paid once |
| Name and file PDFs | 30 to 60 min, inconsistent across the team | 0, canonical naming convention, indexed |
| Type instruments into runsheet | 3 to 8 hrs depending on density | 0, pre-populated, normalized, tagged |
| Resolve party-name variants | 1 to 3 hrs by hand, every time | 0, entity resolution already run county-wide |
| Join wells, parcels, surveys | 1 to 4 hrs in QGIS or by joining spreadsheets | 0, already joined in the workbook |
| Read documents, write abstractor's notes | 2 to 6 hrs (judgment work) | 2 to 6 hrs (judgment work) |
| Chain construction & curative call | 1 to 3 hrs (judgment work) | 1 to 3 hrs (judgment work) |
| Total per tract | ~12 to 34 hrs | ~3 to 9 hrs, almost entirely judgment work |
The split
The records work is search, pull, OCR, normalize, name, file, index, join, dedupe. High-volume, low-judgment, identical across every engagement. It compounds when you do it once and reuse it everywhere. It bleeds you when each landman re-does it, slightly differently, every time.
The judgment work is the chain call, the abstractor's note, the curative recommendation, the conversation with the client. Low-volume, high-judgment, and where your landmen earn their keep. It can't be automated and we aren't trying to.
Hire us for the records work. Pay your landmen for the judgment. Both teams get to do what they're actually good at.
Common objections
Your landmen are good. That's the argument for County.Land. Every hour they spend on records-stitching and PDF-naming is an hour they don't spend on the work that requires their judgment. We're not replacing your bench. We're paying it back the hours it's currently losing to administrative work.
Probably. We aren't selling you those documents. We're selling the layer that makes them findable, named consistently, OCR'd, normalized, and linked into a runsheet. If you have a clean canonical corpus already, we'll integrate yours; most operators don't, and the dedup work alone usually pays for the engagement.
NDA-first. White-labeled if you need it. Your runsheets are your runsheets. We don't republish, share, or expose your engagement work to other clients. The standing county data we maintain is the public record; everything you build on top of it stays yours.
The landmen who lean into this become noticeably more productive and the work becomes more interesting. They spend their day on judgment, not transcription. The shops that have moved this direction don't lay off landmen. They take on more files with the same bench, and the bench is happier.