Build on Land You Own

Every industry eventually hits its sovereignty moment. It's the point where the people doing the work look up and realize someone else owns the thing that makes the work valuable — and that they signed it away without noticing. Banking had it with the payment networks. Local news had it with the social platforms. Working businesses are having it right now, in the fine print of AI subscriptions, and most of them haven't looked up yet.

The survey at the top of this page is from 1793 — John Priggs laying out Charles Carroll Jr.'s tracts in what would become central Washington, D.C. A cadastral map does exactly one job, and it does it permanently: it fixes whose land is whose, so that everything built on a parcel from that day forward accrues to the name in the margin. Two centuries later, that's still the only question that decides whether something you build is an asset or a liability. A lot of businesses signing AI deals right now are pouring foundations without checking the survey.

The debate everyone thinks they're having

The conventional take goes like this: the AI tools work now, the early adopters are pulling ahead, and the only real question is how fast everyone else catches up.

Half right. The tools do work, and the productivity case is settled.

But adoption was never going to be the real fight. It never is. The real fight is over who owns the data that makes the tools work — and on that question, a lot of businesses are losing without knowing the score.

What the platforms figured out before you did

Here's the thing the software platforms understood early, and most of their customers still don't: the AI is not the asset. The data is.

A model that's read ten thousand real businesses — how actual firms price, schedule, and recover when a job goes sideways — is worth something no public dataset can touch. And the only people sitting on that are the businesses themselves. So it's rational for a platform to write the right to use your work into the terms of service of tools you already pay for. Your schedules, your costs, your estimates, your records — standard licensing language that grants broad usage rights can quietly turn all of it into training feedstock. It's worth reading the clause.

This isn't a conspiracy and the platforms aren't villains. Compounding data advantage is simply the best business in software: accumulate enough high-quality data and the product gets stickier, the moat gets deeper, and the customer gets more dependent every quarter. It's the same playbook the payment networks ran, the same one the ad platforms ran. It works. It's just a poor deal for whoever's on the other side of the clause.

Whatever you affix to the land

There's a doctrine in property law older than any of us: quicquid plantatur solo, solo cedit — whatever is affixed to the soil belongs to the soil. Build a barn on land you don't own and the barn isn't yours. It became a fixture. It belongs to whoever holds the dirt.

Anyone who's ever built anything understands this in their bones. You'd never pour a foundation on a lot you were renting month-to-month and call the building an asset. Software quietly imported the same doctrine, and almost nobody noticed. Run your operation on someone else's platform and your data is affixed to their land. You can stop paying. You can export a CSV. But the pattern you taught their model — the part with the real value — became a fixture the moment it trained. It belongs to the soil now, and the soil isn't yours.

Who wins, who's exposed

Read this the way you'd read any leverage contest, because that's what it is.

The platform wins. Every job its customers run can sharpen a model it owns. Then the sharper model gets sold back next quarter as a premium feature — and sold to the competitor bidding against you on the next job, and the one after that. The business supplied the raw material; the platform keeps the compounding asset.

The busiest business is the most exposed. The more work you run, the more valuable the signal you're handing over, and the more directly you're funding a tool that will be pointed at your own margin. You are not a customer in that arrangement. You're an unpaid supplier building equity in someone else's company, collecting one dividend: the privilege of renting back a commoditized version of your own expertise.

The tenant and the owner

Strip away the technology and there are only two positions in this market.

You can be a tenant — running your operation on someone else's platform, generating value that's affixed to their land, building a model you'll rent back at a markup. Convenient, fast to set up, and structurally a slow transfer of your hardest-won knowledge to a company that may sell it to your competitor.

Or you can be an owner. You build on land you own. The system runs on accounts in your name: the database is yours, the cloud accounts are yours, the relationship with the model provider is yours. Your records and their history stay yours. The AI works on your jobs, and your jobs never quietly become training feedstock, because there's no third party holding the land underneath your data.

That distinction is the whole game, and it's why an owned build is even possible: the major model providers will rent you the engine without taking the land. Anthropic, for one, does not use data submitted through its API to train its models. You rent the capability. You keep the data. Concretely, an owned system means the cloud accounts are provisioned in the customer's name, the estimates and records live in storage the customer controls, the model is called over that data rather than fed it, and leaving is a migration of your own stuff — not a negotiation with a vendor over an export.

It's more work than clicking "subscribe." It's also the difference between an asset and a liability dressed up as a convenience.

Why it's worth deciding up front

The reason to settle this early isn't legal. It's physical.

Mess is cheap to make and expensive to clean up. You can cancel a platform. You cannot reach into a trained model and pull your records back out. Once your pricing patterns are in the weights, they're in the weights — there's no "actually, please forget how we bid that work." Giving the data away took one click; getting it back isn't on the menu.

That asymmetry is why the decision is best made at the start, before you affix your work to someone else's land. Measure twice. Your data is the cut worth thinking hardest about.

The principle

Use AI. The productivity is real, and that debate is over.

But know what you're standing on while you do. If the value you generate compounds into a model you'll rent back at a markup, you're improving someone else's lot. If it compounds into a system you own, on accounts in your name, on land you hold the title to, you're building an asset. Same AI, same capability — an entirely different deal, decided by one question worth asking first.

Whose land is this built on?

Build on land you own.