Assuming launch-cost collapse, existing rights/finance constraints, and partial standardization, what specific combinations of orbital services (e.g., microgravity batch manufacturing + secure compute + debris servicing on the same platform) most accelerate Wright’s-law cost declines—because they share power, robotics, and rights overhead—and how would you practically test which bundles reach cost crossover fastest versus remaining thin, single-use verticals?

starship-orbital-economy | Updated at

Answer

Bundles that reuse the same bus, power, robotics, and rights stack across high-value services are most likely to drive fast Wright’s-law declines. Early candidates:

  1. Likely strong bundles

  • “Industrial lab platform”

    • Services: microgravity batch manufacturing (fibers/crystals), materials/biotech testbeds, secure compute enclaves.
    • Shared: continuous power/thermal, env. control, robot arms, data links, rights/compliance.
    • Effect: high duty cycle on robots and power; many learning cycles per kg launched.

  • “Constellation support + risk services”

    • Services: inspection/servicing, life extension, mandated debris removal, hosted sensing or payloads.
    • Shared: tug buses, guidance, grapple hardware, insurance/rights overhead.
    • Effect: same robotic stack amortized over maintenance, relocation, and cleanup.

  • “Secure infra hub”

    • Services: sovereign/secure compute, key management, high-rad test, telemetry relay.
    • Shared: hardened power/data core, thermal, rights for protected orbits.
    • Effect: compute and testing both drive utilization of the same secure platform.
  1. Weaker or risky bundles
  • Tourism + heavy industry: share little; very different safety/liability.
  • Large-scale power beaming + fine biotech: conflicting env., pointing and cleanliness needs.
  • Ultra-short-lived pop-ups + long-lived factories: weak overlap in buses/rights.
  1. Practical tests to find fastest cost-crossover bundles

  • Simulation and paper design

    • Build simple cost models for 3–5 bundle types vs single-use platforms: capex, opex, launch, rights, insurance.
    • Compare cost per unit of output and learning rate under Wright’s-law for shared vs standalone.

  • Pilot platforms

    • Fly 1–2 small multi-service demos: e.g., fiber + testbed + secure compute with a common power/robotics stack.
    • Track: utilization of power/robot hours, unplanned downtime, incremental cost to add each new service.

  • Rights/finance experiments

    • Structure rights and insurance per platform, not per payload, for pilots.
    • Measure: legal/financing effort per additional tenant vs per new standalone satellite.

  • Demand and ops testing

    • Offer the same customer both: (a) a dedicated unit and (b) a slot on a bundled platform.
    • Observe: actual choices, time to sign, realized margins, and how fast unit costs fall with volume.

Use these results to rank bundles by (1) shared capex fraction, (2) achievable utilization, and (3) observed learning rate. Favor bundles where added services clearly lower average cost for all users rather than cannibalizing capacity or adding governance friction.