Horizon

The Garden and the Ground — Who Gets to Build the Business

A platform that runs apps inside a device and this structure look alike from outside, but the shape of the business is reversed. There, one party — the one that owns the device — makes the business, and growth is measured in units shipped. Here, the people who own domains each make their own, and growth is measured in domains. "You can build it yourself without knowing IT or AI" was never about convenience; it was about ownership changing hands.

By makemind · Aug 21, 2026

The previous piece said two different things resemble this. This one takes the first — a platform that runs apps inside a device — and says what separates us.

What separates us is not technical. It is the shape of the business.

Inside the fence, the business is born

Automotive infotainment, a smart-TV operating system, a home hub — the structure is the same shape.

Whoever makes the device puts a runtime on it, hands out authoring tools, and opens a store. Developers build apps, submit them, and if they pass review the app lands on that device. It works. It has worked for over twenty years, with hundreds of millions of units underneath it.

In that structure there is one party making the business: the one that owns the device. It opens the store, sets the review criteria, sets the cut. Whoever wrote the app does business inside that.

And the unit of growth is units shipped. How many of that device sell is how big that ecosystem is. Sell well and it grows; sell badly and it doesn't. However many apps you gather, none of them leave that device.

A walled garden. The garden is well kept. There is one gardener.

A workshop shelf of hand tools
A workshop shelf of hand tools

Here there are many owners

There is no slot in this structure for opening a store. More precisely, we do not hold that slot.

Whoever made the device describes their own device's screen. The player receives that description and draws it. The player does not know what it will draw and does not need to. So the party making the business stands separately in each domain.

The company that builds control panels for special-purpose vehicles mounts it on their panel and sells to their customers. So does the company that builds greenhouse equipment, and the one that builds weighing systems. There is no seat between them and their customer where we review or take a cut.

Then the unit of growth stops being units and becomes domains. Not how many of that device sell, but how many domains get on.

Ground. Ground is less tended than a garden. It has many owners.

So that number is not our ceiling

You can look at a similar company's revenue and read it as "so this market is about this big". That is not accurate.

That number is the size of one category. Automotive is automotive; TV is TV. It is what that position, worked for a long time inside that category, produces.

The size of a connective layer is measured on a different axis — not one category, but how many categories it crosses. Taking their number as our ceiling is picking the wrong ruler. Not a claim that ours is bigger — a claim that the same ruler does not reach.

It was never convenience. It was ownership.

One sentence has repeated in this magazine since it started.

Without knowing IT or AI, a domain expert stands up the system that fits their own domain.

We have been explaining that sentence as convenience — something hard became easy. That was wrong.

Standing it up yourself means becoming the owner of that business. You decide your equipment's screen, you meet your customers through it, and the revenue is yours. There is no seat in between that reviews, and none that takes a share.

It is not that building got easy — it did not, you have to know the specification — it is that whose it is changed.

Where one becomes two

What this looks like in practice is already in this magazine.

There is a sample where one person runs two cafés. The bundle is one — not two copies but the same folder. Yet each shop opens with different items, different prices, different hours. The only thing that differs is one configuration file.

Its verification carries a rule: if a shop's name appears inside the app, the run fails. The app must not know which shop it is. The moment it knows, every new shop means editing the app — and then you are back inside a fence.

Two shops become three, then twenty, and the app stays as it is. And the owners of those shops are each their own.

Next

Which leaves a question. The fence is already on hundreds of millions of units. How does the ground get there?

Not by fighting. That is the next piece.


makemind.dev "Horizon" — One bundle becoming two shops is exactly what the sample confirms.

Twitter