Skip to main content

Industrial outdoor storage

The IOS Yard Engine

Industrial outdoor storage went institutional inside five years, and the land that can legally hold a yard keeps shrinking as municipalities rezone it to higher uses. This pack is the screen nobody publishes: coverage measured on the assessor's own split between building value and land value, then owner resolution, a buy-box verdict, a first-pass underwrite, an IC memo and the outreach behind it.

Get the free packBook a call

Matthews sizes IOS at roughly $218B in its 2026 sector update, and the same report puts institutional capital behind a growing share of acquisitions. The method here is public records, not proprietary data.

See open times
Get the free packBook a call

Seven stages, one system

Two stages find and rank the yards. Five agents carry the ones worth working from the deed to the letter. The sample CSV is already the output of the first two, so you start at stage three.

  1. 01

    Filter the realm

    Every parcel in the county, then the ones the IOS mandate keeps: the industrial, warehouse and truck-terminal use codes with vacant industrial deliberately kept in, the acreage band, and an entity on the deed. A filter: what is in, and a counted reason for everything that is out.

  2. 02

    Rank by coverage and hold

    Coverage ratio on every survivor, lowest first, then longest hold. A sort: what is first. Stages one and two are what the sample CSV already holds, so you can audit them against the county rather than re-derive them.

  3. 03

    Resolve the owner

    A long-held yard almost always arrives as an entity on a deed, which is where most trails go cold. Supply the registry filings and it works the chain until two records agree on one person. Supply the CSV alone and it says so plainly: zero humans resolved, and here is the registry, the filing and the field pair that would name each one.

  4. 04

    Screen against the buy box

    Every parcel gets a verdict: KILL, WATCH, PURSUE or PRIORITY, with a fit score and the reason written on the row. Nothing leaves the pipeline without a counted reason.

  5. 05

    Underwrite the first pass

    A yard model shell quoted the way operators quote it, per acre per month. Every line is either sourced or tagged as an input to collect, never guessed, and the paving, fencing, drainage and lighting that make a low-coverage site usable are line items rather than an afterthought.

  6. 06

    Write the IC memo

    Eight sections where every fact carries the record it came from or its collect tag, plus a sources block, an open-items list, and an honest-ceiling section that states what the memo does not cover. Zoning and environmental status are named there as open questions, not answered ones.

  7. 07

    Draft the outreach

    A letter, an email and a call script that could only be about that yard, built from what the pipeline established and nothing else. No dollar figure in a first touch. The stage drafts; it never sends.

One lead agent runs all seven and owns the handoffs, so the screen, the underwrite and the memo read the same buy box and the same row, and the coverage number that ranked a parcel is the number the memo cites. Two gates stay human on purpose: one before the memo goes to IC, one before anything leaves your mailbox.

What is inside

One lead agent, five specialists, and everything they read.

Install guide

File tree plus install paths for a Claude Project, Claude Code, ChatGPT and Codex. Ten minutes from download to a running pipeline.

Implementation guide

The architecture end to end: what each of the seven stages reads, what it writes, and where the two human gates sit. The same architecture ships as a branded printable guide for the partner who will never open a markdown file.

The IOS buy box

One JSON file: use-code family, coverage threshold, acreage band with its separate infill tranche, hold period, entity-owner test and the signal weights. Written once, read by every agent downstream.

Stage contracts

Input and output columns per stage, plus the exclusion count each stage owes you. This is what keeps rows from vanishing between steps.

A fifty-row sample and a memo

A real public-county run at the property level with the value coverage and the physical footprint on every row, one IC memo generated from the top row, and the provenance note naming the portal, the pull date and the funnel counts.

Outreach templates

Owner letter, email and call script written for yard owners, with the property-specific slots the pipeline fills.

The two human gates

What a person checks before the memo goes to IC, and before anything is sent. Twenty minutes that keep a wrong-owner letter from going out with your name on it.

The lead agent and five specialists

Owner resolver, deal screener, underwriter, memo writer, outreach writer, and the acquisition lead that dispatches them. Paste-and-run, each one.

Worked example

The whole pipeline on the sample county, with the counts at every stage. How many parcels survive the use-code gate, then the coverage screen, then the acreage band, is the number nobody publishes.

The defining screen

Coverage is the screen. Value is the honest basis.

IOS is a low-coverage asset: the value sits in the dirt, not the building. The obvious way to measure that is a footprint ratio, building area over land area, and this pack deliberately does not screen on it. County building area is heated square feet, which excludes the unheated structures a yard is actually improved with, and measured on the county a large distribution warehouse sails through the footprint gate. The assessor's own split between building value and land value does not lie about where the value sits, so that is what the screen runs on.

The screen

value_coverage = building_value / assessed_value

Keep at or below 0.30. Both figures are published on every row of the sample, so you recompute the screen from the row instead of taking our word for it.

Published, never the screen

footprint = building_sqft / (acres * 43560)

The physical ratio ships on every row as well, because you should be able to see the parcel the way the tax roll describes it. It is transparency, not the filter, and the large distribution warehouses that clear it are why.

What the records compute

  • Value coverage, from the assessor's own building and total figures on the same row, with the physical acreage and building area printed beside it so you can hold both readings of the parcel at once.
  • The acreage band: two to twenty acres for the core screen, with half an acre to three run as a separate infill tranche because infill trades on different economics.
  • The use-code family: industrial, warehouse, truck terminal, and vacant industrial kept in on purpose, because unimproved land is a legitimate yard target rather than noise.
  • Hold period and owner type: a deed more than a decade old held by an entity is the classic profile of a seller with a low basis and no broker relationship.

What you verify off the records

  • Zoning and whether outdoor storage is a permitted use. Assessor codes record how a parcel is used for tax, not what the municipality allows, so a yard operating today can be a legacy non-conforming use that cannot be re-let or expanded. The pack sends you to the zoning map and the ordinance text every time.
  • Whether the yard is paved, fenced, secured, and how much of it is actually usable. That is aerial imagery and a site visit, not a data field.
  • Environmental status. A Phase I is a real gate on this asset class and no records query substitutes for it.
  • In-place tenancy and rent. The pack does not screen on it, because the buy-box research is explicit that the common institutional criteria do not turn on tenancy.

The screen produces candidates, not qualified sites, and the pack says so in every file that touches it. A ranked row means the records are consistent with a yard. Whether that yard can legally keep being a yard is a question for the municipality, and it is the one claim that would embarrass you in front of a seller.

The sample run

Fifty rows you can run today

The pack ships with a real run so you can watch the pipeline work before you have your own data. Here is exactly what those rows are, and what they are not.

What the rows are

  • One public county: Mecklenburg County, North Carolina.
  • Property level: parcel id, address block, asset type, acres, building area, building value and total assessed value, the value coverage computed from those last two, and last sale year.
  • The owner entity exactly as recorded on the deed, plus the signals that fired, the buy-box fit and the rank.
  • Every row badged SAMPLE, so no row can be mistaken for live deal flow.

What the rows are not

  • No zoning verdict. Nothing in the sample says a parcel may legally be used as a yard.
  • No owner contact data of any kind, and no resolved human names. The entity string on the deed is where the free sample stops.
  • No phone numbers, no email addresses, no mailing addresses.
  • Not a client run. Public county records only, never rows from work we did for someone else.

Owner contacts are not in this download. What ships is the method and the public property-level trail. Resolving an entity to a reachable human is a separate engagement with its own verification work, which is why a free zip does not hand you the people.

Want it built and run on your markets?

We build it on your counties, your buy box and your data, and hand back the working system.

Book a 20-min call

Get the pack

Free, and it installs in the tool you already use. It is a first-pass system, not straight-through processing: it ranks candidates, you verify zoning, and the IC call stays human.

Download the pack

Want the system, not just the files?

Get the full pack once, then use the walkthrough below to see exactly what is inside and how to run it.

Get The IOS Yard Engine Pack

Enter your details and the full pack downloads right away. No cost.

We will email you occasionally about real estate AI. Unsubscribe anytime.

Have us build it for you

Twenty minutes. Bring your target markets and we will walk the coverage screen on your own counties.

Loading calendar

Questions real estate teams ask

What is the IOS Yard Engine?

It is a free pack that installs one acquisition lead agent and five specialists into Claude, aimed at industrial outdoor storage: laydown yards, trailer and container storage, fleet parking, truck terminals and contractor yards. The lead runs seven stages. Stages one and two filter a county parcel table to the industrial-family use codes and rank what is left by coverage ratio and hold period. Stages three to seven are the specialists: the owner resolver works the entity on the deed toward a named human through the public trail, the screener scores each parcel against your IOS buy box, the underwriter builds a first-pass shell in dollars per acre per month, the memo writer produces an investment committee memo where every fact carries the record it came from, and the outreach writer drafts the letter. Two human gates sit in the flow, one before the memo goes to IC and one before anything leaves your mailbox.

What is the coverage ratio and how is it computed?

Coverage means how little of a parcel's value sits in the building rather than the land, and the screen runs on the assessor's own split: building value divided by total assessed value, kept at 0.30 and below. Both figures are published on every row of the sample so you can recompute the screen from the row. The physical footprint, building square feet over acres times 43,560, ships beside it as transparency and is deliberately not the filter. County building area is heated square feet, so it excludes the unheated structures a yard is actually improved with, and measured on this county a large distribution warehouse passes the footprint gate. The value split does not lie about where the value sits.

Does it tell me whether a parcel is zoned for outdoor storage?

No, and it is written so that it never pretends to. Assessor land use codes describe how a parcel is used for tax purposes, not what the municipality legally permits, so a yard operating today can be a legacy non-conforming use that cannot be re-let or expanded. Zoning is a collect item in every file that touches it: the pack tells you to pull the municipal zoning map and the ordinance text and verify permitted use with the jurisdiction. The screen finds candidates, not qualified sites, and it says so inside the pack.

What does this pack not do?

It does not close deals and it is not straight-through processing. It does not screen in-place tenancy or rent: the buy-box research is explicit that the common institutional criteria do not turn on tenancy, and inventing a tenancy screen would be inventing a claim. It does not judge environmental status either, which is a Phase I question, not a records question. The underwrite is a first pass on public records, sharper when you supply documents, and from records alone it returns a shell of named inputs to collect rather than finished numbers. The memo is a draft whose honest-ceiling section states what it does not cover, and the IC call stays human. It ships no data pipeline: you bring the parcel rows, from your own export or from a county portal.

Does the pack include owner contact data?

No. The pack teaches the resolution and gives you the agents that run it, and the sample stops at the property. What ships is the method and public property-level records. Resolving owners to reachable people is a separate engagement with its own verification work, which is why no contact data is in the download.

What is in the fifty-row sample?

Fifty ranked rows from one public county, Mecklenburg County in North Carolina, at the property level: parcel id, address block, asset type, acres, building square feet, building value and total assessed value, the value coverage computed from those last two, last sale year, the owner entity exactly as recorded on the deed, the signals that fired, the buy-box fit and the rank. Every row carries a sample note. There are no resolved human names, no zoning verdicts, no phone numbers, no email addresses and no mailing addresses in it.

Which markets does it work in?

The three records the method runs on, the county assessor, the state business registry and the county recorder, exist in all fifty states. What varies is depth. The coverage screen needs acreage and building area, and counties that publish one without the other are why the value proxy exists. Land-use code legends differ county by county, so the worked example shows which use codes were kept and which were excluded, and the provenance note names the portal and the pull date so you can redo the same filter on your own market.

How is this different from the AI Acquisition Infrastructure?

Same seven stages and the same contracts between them. The difference is the buy box and the screen. The AI Acquisition Infrastructure ships a general CRE mandate; this one ships an IOS mandate: the industrial use-code family as a gate, coverage as the ranking signal, an acreage band with a separate infill tranche, and an underwriter that quotes rent per acre per month instead of per square foot. Install either. They install the same way, and the agents are interchangeable once the buy box is set.

Where AI changes the answer

The IOS screen is one ratio the county already gives you, and it is a value ratio rather than a footprint one: how much of the assessed value is the building. What stops most teams is not the arithmetic, it is carrying that ratio through owner resolution, underwriting and a memo without retyping the row. A stage contract between agents means the coverage number that ranked the parcel is the same number the memo cites, and the fields the records cannot answer, zoning above all, stay marked as things to collect instead of quietly becoming claims.

See how we build this →

Related resources

Want the system, not just the files?

Two ways to go further with NextAutomation.

Work with us

Have us build the sourcing-to-reporting pipeline these files only hint at. Custom AI systems for your firm.

Apply to work with us

Join the community

Live builds, the template library, and a room of operators using AI on real deals. from $49/mo.

Join the community

From free pack to full system

Solution

AI Deal Sourcing for Off-Market Pipeline

How the front of this pipeline runs in production: screening a county, tracing owners, and routing targets before deals reach the open market.

Learn More
Solution

The AI Underwriting Copilot

Want the underwriting and memo half run on your own deal flow? We build it on your documents and your underwriting standards.

Learn More