Platform rent map
Practicum for Volume 2, Chapter 9, "Physical AI and Who Owns the Rails." Version: 2026-07. Time: 30-40 minutes. For professionals, managers, and business owners. Each stands on different rails.
Platform rent is a regular payment to an infrastructure owner for access to customers, tools, or computing. Examples include a marketplace commission, payment processing fee, model subscription, or the ad platform's share of customer acquisition cost. Each payment may look reasonable on its own. The problem is paying without looking at the total or asking what happens if the owner raises the price. This worksheet turns invisible rent into one number you can manage.
Step 1. List every toll
Use the online store in the chapter as a guide: marketplace commission, payment processing, marketplace ads, service subscriptions, delivery and returns, and per-request agent costs. Each looks small alone. Together, they are your margin.
| Toll | Who receives it | Monthly amount | % of revenue |
|---|---|---|---|
| Total platform rent | ₽ _______ | ____ % |
The point is not to leave every platform. It is to see your total rent as one number for the first time.
Step 2. Find your position on the rails
On any rails, from a marketplace to a company AI subscription, you occupy one of three positions. Mark your position as a professional and as a business.
| Position | How to recognize it | Move up |
|---|---|---|
| Owns a junction | Other people pay to access something you own: direct customer relationships, unique data, expertise with demand, or your own distribution | Deepen the moat through trust, context, and responsibility (Volume 1, Chapters 5-7) |
| Builds on someone else's rails with eyes open | You pay rent, know the total, keep a backup route, and own at least one junction | Move one asset from a platform into your ownership each year |
| Pays rent without looking | You do not know the total platform cost or what to do if prices double and access narrows | Start with this worksheet: list, add, and ask what you can replace or own |
My position now: ________________________ Move up that I will make: ___________
Step 3. Check all three roles
- Professional: whose platforms stand between you and your value, and what do you own besides an account?
This is your own ladder: finished work, people, and a name.
_______________ - Manager: whose models, clouds, and data support the process, and what happens to unit economics, the profit or cost of one unit,
if computing becomes three times more expensive and access terms change?
_______________ - Business owner: what is total rent as a percentage of revenue, and which one asset will you move into your ownership this year?
_______________
Step 4. Run the "what if the price rises?" test
Use rough but useful arithmetic. If the AI bill is 5% of unit cost, a threefold increase hurts but may not break the model. If half the process depends on one API, a price increase affects the design of the business, far beyond one expense line.
- AI and platform share of unit cost:
____ % - What breaks if prices become 3x higher tomorrow or access closes:
_____________________ - My backup route (multiple providers, portable data and prompts, open models, or local inference when justified):
_________________________________________
You probably do not need to build your own rails. For most people, the right answer is to use someone else's rails with open eyes. Know the toll, map the detour before the bridge closes, and own one junction that makes you useful on any route.
Next
The same mechanism affects careers: Who Owns Your Ladder? (Chapter 8). See the current map of rails and infrastructure spending in Who Owns the Rails?. Treat a backup route as a no-regret move with No-Regret Moves (Chapter 10).
Back: Volume 2 Workbook. Version: 2026-07.