1. The price of jaunting
Alfred Bester’s The Stars My Destination is about a man who discovers personal teleportation and uses it to reshape commerce and society. The book understands that a technology’s power is not in what it does but in what people will pay to use it for. Pricing and contracts are where that transformation becomes concrete. The desktop must turn orbital capability into offers that customers can say yes to.
Entry 298 covered early adopters and use cases. This entry focuses on pricing, contracts, and go-to-market.
2. Pricing models
The desktop can price its offerings in several ways:
- Slot lease: a fixed price for a payload slot over a mission life, paid upfront or periodically.
- Service fee: a price per unit of service, such as data volume, compute time, or image collected.
- Milestone payment: payments tied to integration, launch, commissioning, and operational milestones.
- Revenue share: the platform and the customer share revenue from data products or services.
- Demonstration fee: a lower price for early technology demonstration missions in exchange for risk tolerance and reference rights.
The right model depends on the customer, the use case, and the level of risk each party accepts.
3. What drives price
Prices must cover cost and leave margin, but they are also constrained by competition and customer value. Key drivers:
- Cost of the platform and launch. The price must eventually exceed the fully loaded cost.
- Customer alternative. What would the customer pay for a dedicated mission or another platform?
- Value created. Does the service save money, generate revenue, or enable something impossible?
- Risk premium. New platforms charge less because they carry more risk.
- Commitment length. Longer contracts can justify lower unit prices.
Early prices will likely be cost-plus or value-based discounts to win reference customers.
4. Contract structure
Contracts must allocate risk and define success. Typical terms include:
- Scope: what capacity, data, or service is provided.
- Schedule: integration, launch, commissioning, and service periods.
- Performance: technical specifications, availability, data quality.
- Price and payment: fees, milestones, and invoicing.
- Risk allocation: launch failure, on-orbit failure, liability, insurance.
- Termination: rights to end the contract and consequences.
- Intellectual property: who owns payload data, improvements, and background IP.
- Regulatory compliance: licenses, export control, and data handling.
A contract that is too favourable to one side will not survive negotiation or execution.
5. Go-to-market
Go-to-market is how the desktop finds, converts, and serves customers. A practical sequence:
- Reference missions: fly low-cost demonstrations for credible early adopters.
- Case studies: publish results to prove capability.
- Direct sales: engage government, research, and commercial prospects.
- Partnerships: work with launch providers, integrators, and distributors.
- Standard offerings: develop repeatable products with clear pricing.
- Scale: expand capacity and customer base as heritage grows.
The first sale is the hardest because there is no track record. After that, each sale becomes easier.
6. Sales before launch
A useful discipline is to sell capacity before the platform is built. Letters of intent, pre-booked slots, and paid deposits validate demand and help fund development. These commitments are not revenue yet, but they are evidence that the market exists.
What this changes
- Pricing models include slot lease, service fee, milestone payment, revenue share, and demonstration fee.
- Prices are driven by cost, alternatives, value, risk, and commitment length.
- Contracts must allocate scope, schedule, performance, price, risk, termination, IP, and compliance.
- Go-to-market starts with reference missions and builds toward repeatable offerings.
- Pre-launch commitments validate demand.
- The next entry will close the customers and markets arc with a contemplation.