Start with the government mission
A satellite service for a government customer starts with a question about the work. Does the team need secure communications, observations of Earth, or a way to carry an instrument into orbit? SpaceX describes Starshield around those three areas. The achievement is a government-focused offering built on capabilities SpaceX developed for its broadband and launch businesses. The public record supports a comparison of the product’s purpose and architecture. Individual deployments should be judged through the evidence the customer is authorized to examine.
The company’s June 2026 prospectus describes Starshield as a separate network for national security applications, built on technology and infrastructure that also support Starlink. It identifies manufacturing and launch as part of that base. This is an example of product reuse at the platform level. A customer buys a mission capability, with requirements that can change which equipment, access, and operating procedures the customer needs.
Define the required result for each mission
- Communications. Define where operators need to connect and what the connection must support. Agree who administers equipment, who can authorize a change, and what happens if the service is interrupted. Have the technical and operational owners verify a complete exchange in an approved exercise.
- Earth observation. Define what information a decision maker needs, the timing that makes it useful, and who will interpret it. Put a named owner on requesting a collection and another on checking whether the delivered data answers the original question.
- Hosted payloads. A hosted payload is an instrument or other equipment carried on a spacecraft platform. Establish who owns the interface between instrument and spacecraft, who can command it, and how the team verifies the data received on the ground.
These are different acceptance problems. A working communications terminal illustrates a communications result. It supplies little evidence about the quality or timing of an observation from another system. Tie each claim to its mission and define the environment in which it was tested. Keep product descriptions, contracted deliverables, and operational evidence separately identifiable so a reviewer can see what each establishes.
Put responsibilities in writing before the work starts
For a fictional example, suppose an agency needs to move approved information between two remote teams when a terrestrial connection is unavailable. The program manager owns the mission, the security owner defines access and data handling, and the network operator owns activation and recovery. Ask the supplier to identify its escalation contact and describe what support is available during the test window. Agree on a fallback the agency can control if the alternate link fails. Use authorized test material and record the sequence through successful delivery and return to the normal path.
The staffing implication is concrete. A program may need a systems integrator who can translate the mission into interface tests, a security specialist who can validate the operating boundaries, and an operator who can run the procedure during an interruption. Evaluate each candidate against the work they will perform. Handle any formal access requirements through the authorized process. Starshield shows what can happen when a commercial technology base is adapted for a specialized buyer. The buyer still owns the decision about which mission it can trust the service to perform.