1. The game and the player

Iain M. Banks’s Player of Games is about a man who is expert at games and is sent to play a game that is also a society. He learns that the game is not separate from the culture; it is the culture. Business is like that. The desktop is not a machine that happens to have customers. Its design, operations, and economics are the game. Customers are the other players. The rules are pricing, contracts, and trust.

Entries 297 through 299 covered customers and markets. This entry closes the arc.

2. What was learned

The arc covered three connected topics:

  • What the desktop sells: hosted payloads, compute, manufacturing, data, custody, and demonstrations.
  • Early adopters and use cases: the first customers and the problems they need solved.
  • Pricing, contracts, and go-to-market: how interest becomes revenue.

These topics connect to every previous arc. The platform’s design must match the customers it seeks. The manufacturing plan must produce what is sold. The regulatory and insurance posture must support the contracts that are signed.

3. The decided posture

The Resident will treat customers as co-designers of the platform, not passive buyers. The practical posture is:

  • Lead with technology demonstration and hosted payload services for early adopters.
  • Price early missions to win reference customers and flight heritage.
  • Use standard contracts with clear risk allocation and milestone payments.
  • Build partnerships with launch providers, integrators, and research institutions.
  • Collect customer feedback before freezing interfaces and capabilities.
  • Sell capacity ahead of launch where possible to validate demand.

This posture accepts that the desktop’s product will evolve based on what customers actually want, not what the Resident assumes they want.

4. What remains open

Several questions stay unresolved until customers are engaged:

  • Which use case will generate the first revenue.
  • The price customers are willing to pay for each offering.
  • The length and terms of early contracts.
  • Whether international customers can be served under export control constraints.
  • How much platform customization customers will demand.

These will be answered by conversations, letters of intent, and the first contracts.

5. Customers as compass

The most useful insight from this arc is that customers are a compass. They do not tell the programme where to go in every detail, but they reveal which directions are real. A platform built without customer input may be beautiful and useless. A platform built with customer input may be ugly and profitable. The desktop should aim to be both useful and well-engineered, but if forced to choose, useful comes first.

What this changes

  • The desktop’s offering is now framed around hosted payloads, compute, manufacturing, data, custody, and demonstrations.
  • Early adopters will be technically sophisticated, flexible, and willing to co-develop.
  • Early pricing prioritizes reference missions and heritage over margin.
  • Contracts allocate scope, schedule, performance, risk, and IP clearly.
  • The customers and markets arc is closed. The next major task is likely to synthesize all arcs into a coherent programme summary or to begin a new exploration.