Launch Services
Zero-failure programs where certification, partners, and supply chains must execute against gated evidence.
This interactive experience is the shipped product itself — the same application code customers run in production, mounted read-only in your browser over a real sample journey. Not a video, not a mockup: because the demo and the product are one codebase, it can never drift from the real thing.
Inside this journey
-
Pre-Sales
Qualify and diagnose mission requirements, risks, and schedule before committing to detailed planning.
-
Qualification
Confirm budget window, schedule constraints, decision-makers, insurance/governance requirements, and mission critical timelines before full discovery.
Qualification Questions
Mission fit and critical timing
- So we make the best use of your time, what is the mission's target launch window or earliest required on-orbit date?
- Are any dates mission-critical and not permitted to slip? If yes, briefly state which.
Commercial readiness and budget
- Is there an allocated budget range for launch services today?
- Who signs the launch services agreement and who else materially influences the decision?
Insurance, compliance, and governance
- Do specific insurance limits, indemnity terms, export controls, or government approvals apply?
- If any of the above apply, please briefly state the required insurance limits, approvals, or compliance notes.
Readiness for discovery and next steps
- Who from your team should join a focused discovery call (roles and best availability)?
- From your perspective, is this opportunity ready for a focused discovery conversation now?
-
Mission Discovery
Map mission objectives, payload constraints, required orbit accuracy, manifest flexibility needs, and stakeholder roles for technical due diligence.
Discovery Questions
Mapping your mission and timeline
- Tell me briefly what your mission must achieve on orbit and why the launch date matters to your program
- When does your first satellite or payload need to be operational on orbit, and how firm is that date
- Which orbital regime and approximate altitude are you targeting for this launch
- How many satellites or discrete payloads are you planning to fly on this mission
- Describe the primary payload form factors, typical mass per unit, and any nonstandard or hazardous components
- Who will be the named mission director or day-to-day integration owner on your side for decisions and approvals
- Share an example of a late requirement change on a past mission and how your team managed schedule or cost impacts
Where schedule and money really bite
- If this launch slips by six months, what immediate program costs or operational impacts would you face
- How often have multi-month schedule slips occurred across your last three launches, and what caused them
- Who ultimately bears the cost of satellite storage or delayed operations under your current procurement model
- Which contractual mechanism do you rely on today to recover costs from a delayed or failed launch
- Explain the orbit insertion error (km or percent of delta-v) that would still allow your mission to meet its operational objectives
- Estimate how much your insurance premium or underwriting requirements would change after a major schedule slip or anomaly
- Name the single contractual or technical failure that would make you walk away from this launch option immediately
Nailing the technical numbers for mission assurance
- Imagine your required orbit accuracy shifted by 50 kilometers or an order of magnitude in pointing, how would that change launch viability
- List the avionics, sensors, and propulsion margins your payloads require for post-separation phasing and on-orbit commissioning
- How many discrete separation events and deployment windows must the vehicle perform to meet your manifest sequencing needs
- Provide the mechanical, thermal, and vibration limits for your payload interfaces during processing and ascent
- Identify the telemetry, tracking, and command endpoints you need during the launch campaign and whether access will be continuous
- Name the single unresolved technical question that, if not settled before integration, would force you to delay or cancel the launch
Practical readiness, facilities, and approvals that gate work
- Suppose your payload needed a custom separation system, can your schedule and budget absorb an additional 6–10 weeks for design, analysis, and test
- Are your payload shipping windows, receiving inspection slots, and integration bay reservations already secured
- Count the number of engineers and technicians you can commit to hands-on integration and campaign support during the launch window
- List export controls, licenses, or facility approvals that could gate payload handover or on-site work
- Identify any ground facility access constraints or range access conflicts that will require external coordination
- Name the single missing approval, test result, or resource that would prevent you from meeting your target integration start date
The other options on your table
- Assuming keeping your incumbent or solving launch internally is possible, what must be true for you to choose not to move to a new provider
- Select the alternative approaches you are actively evaluating right now
- List the commercial or internal decision criteria that would keep you with the current approach instead of changing
- Name internal roles or teams that have proposed an in-house launch or significant program change
- Describe any reference checks, flight histories, or actuarial analyses you require before switching to a new launch provider
- Which single condition about a competitor or internal fix would convince you to delay selecting a new launch option
What will make you sign and what will stop you
- Outline the top three acceptance criteria your procurement and insurance teams require to move from evaluation to contract
- Rate how important each of the following decision factors is for your final award: reliability, schedule certainty, cost per kg, manifest flexibility, indemnification terms
- State any absolute non-negotiables in contract language or insurance terms that would veto a deal
- If a short pilot or demonstration mission proved the performance claims, what would prevent your team from signing within two weeks
- Predict the internal approval path and typical timeline from mutual technical agreement to signed contract in your organization
- Describe the single governance or budget gate that will most likely delay or stop award on your side
Final practical next steps and immediate blockers
- Clarify the immediate documents, data, or test reports you can share within the next 7 days to accelerate technical review
- Choose the preferred cadence and audience for decision meetings over the next month
- List any internal calendar windows, travel freezes, or blackout dates that would block integration or campaign activities
- Confirm whether an underwriter or technical advisor will attend a joint technical review and provide their availability
- Name the one next step we should complete together that would most accelerate a decision on your side
-
-
Solution Walkthrough
Walk through how available vehicle classes, integration flows, and timelines deliver the buyer's mission outcomes using the customer's context.
Solution Experience
- Solution Walkthrough Session
- Confirm the current state and its cost to your program
- You confirm the recommended vehicle class and integration approach meet your payload mass, orbit accuracy, and manifest flexibility needs.
- Deliver a mission mapping report that pairs each payload and orbit requirement to recommended vehicle classes, expected insertion accuracy ranges, and cost/schedule tradeoffs.
- You acknowledge the quantified schedule risk and accept the proposed mitigation path or request specific alternatives.
- Match vehicle classes to your mission scenarios
- Provide a timeline with hard dates for payload shipping, integration milestones, and contingency windows, and identify the manifest decision cutoff dates.
- You identify the remaining evidence required before a commercial decision, such as reference flight data, insertion accuracy statistics, or underwriter inputs.
- Walk the end-to-end integration flow and risk points
- Share final payload mass properties and mechanical interface drawings for each payload slot to allow final verification of fit and separation sequencing.
- Timeline overlay and decision cutoffs
- Confirm named decision-maker(s) and their approval criteria for schedule commitments and launch acceptance.
- Validate alignment
- Solution Walkthrough Session
- Solution Walkthrough Deck
- Solution Brief
- meeting
- slides
- document
-
Mission Scope
Define the launch configuration, manifest sloting, payload integration tasks, verification requirements, responsibilities, and measurable acceptance criteria.
Scope Configuration
- Receive and Inspect Payload Hardware
- Cleanroom Stowage and Environmental Control
- Mass Properties and Center-of-Gravity Measurement
- Mechanical and Electrical Integration to Dispenser/Adapter
- Install Separation and Deployment Mechanisms
- Encapsulate Payload within Launch Vehicle Fairing
- Propellant Loading and Cryogenic/Hypergolic Fueling
- Vehicle Final Assembly and Payload Mating
- Execute Vibration, Shock, and Thermal Test Campaign
- Provide Real-Time Launch Telemetry Feed
- On-Orbit Deployment Confirmation and Orbit Determination
- Provide Rideshare Slot Integration and Interface Delivery
Scope Questions
Receive and Inspect Payload Hardware
- Provide your payload shipping manifest and associated tracking numbers (airway bill, container IDs) for the expected incoming consignment.
- When will your payload arrive at the integration facility (estimated arrival date and time) and what is the inbound carrier?
- Indicate the sealed-package environmental requirements during transport you expect us to verify on receipt (temperature range, relative humidity, shock thresholds).
- What measurable acceptance criteria will confirm payload receipt inspection is passed (examples: dimensional tolerance within drawing X, no visible damage, functional power-on test results)?
- Who on your team will provide the packing list and witness the receipt inspection and sign the packing acceptance certificate?
- Specify any hazardous material (HAZMAT) declarations, battery state of charge, or radioactive sources included in the payload manifest that require special handling on receipt.
Cleanroom Stowage and Environmental Control
- Select the cleanroom class you require for payload stowage and integration tasks.
- Describe any continuous environmental monitoring or data-logger trace you require while the payload is in stowage (temperature, humidity, particulate counts).
- Identify the ESD (electrostatic discharge) controls and contamination control fixtures your hardware requires (for example wrist straps, ionizers, filtered toolkits).
- Who will provide the payload contamination control plan or special handling instructions in the payload interface control document (ICD)?
- Specify required access restrictions or PPE (personal protective equipment) for your team during cleanroom operations (gowning level, visitor rules).
- Estimate the total cumulative cleanroom stowage time your payload needs before integration (days).
Mass Properties and Center-of-Gravity Measurement
- Provide your latest mass properties package including mass, center-of-gravity (CG) coordinates, and inertial moments from your structural analysis or prior test reports.
- Which measurement deliverable do you require from our facility: raw measurement data, calibrated CG report with uncertainty, or both?
- Indicate the tolerance band for CG and total mass that you accept without requiring redesign or additional integration (e.g., ±1 kg, ±10 mm).
- Who on your engineering team will approve the final mass properties report and sign the mass-and-balance certificate?
- What measurement fixtures or handling attachments from your hardware drawing (for example, balance interface points or datum references) must be used during the CG test?
- What acceptance evidence will validate that mass properties measurement is complete and acceptable for launch integration (for example signed mass-and-balance certificate, measurement uncertainty <= X%)?
Mechanical and Electrical Integration to Dispenser/Adapter
- Attach or describe the payload interface control document (ICD) for mechanical and electrical mating to the dispenser or adapter, including connector pinouts and mechanical datum drawings.
- Select the mechanical interface type you require for mounting to the dispenser/adapter.
- Which electrical interfaces must be routed during integration (power, low-voltage telemetry, separation pyro initiator circuit, separation switch)?
- Who will supply flight harnesses, separation switch assemblies, and connector backshells: your team or our integration hardware pool?
- List any electrical functional checks you require prior to mechanical mating (e.g., continuity checks, basic power-up, bus health telemetry snapshot).
- When must final connector pin-mapping and harness drawings be locked for harness fabrication (weeks before integration)?
Install Separation and Deployment Mechanisms
- Provide the part number and qualification status of the separation system or deployment mechanism called out in your ICD.
- Specify required shock and pyrotechnic initiation tests or witness points for the separation hardware (for example shock pulse level, initiation current).
- Who will certify the separation system acceptance test results and provide the certificate of conformity?
- Which functional checks must be performed after installation (for example, mechanical stroke verification, latch continuity, redundant switch state)?
- Identify the separation sequencing constraints for your payload (separation time relative to T+ seconds, desired delta-V vector, any spin or tumble requirements).
- Estimate whether any specialized tooling or test articles for the separation mechanism must be provided by you for integration or functional verification.
Encapsulate Payload within Launch Vehicle Fairing
- Provide your payload mechanical envelope drawing and the fairing interface drawing to confirm fit-check dimensions.
- Select any environmental constraints during encapsulation you require us to control (for example maximum particulate counts, maximum relative humidity).
- Which fairing access and purge requirements does your hardware need during encapsulation (nitrogen purge, continuous purge flow rate in L/min)?
- Who will approve the final fit-check and sign the fairing interface clearance form?
- When must final mass and CG be locked relative to the scheduled encapsulation date (weeks prior)?
- Identify any off-axis protrusions or deployment appendages that require special fairing tooling or altered separation clearances.
Propellant Loading and Cryogenic/Hypergolic Fueling
- State whether your payload requires any on-pad fueling or propellant conditioning (for example pressurant recharge, cold-gas topping, hydrazine filling).
- If fueling is required, specify propellant types and maximum filled mass (for example: monomethylhydrazine (MMH) 5 kg, hydrazine 2 kg, liquid oxygen cryogenics).
- Identify required safety approvals and authorizations for propellant handling that you will provide (Material Safety Data Sheets, certified venting plans).
- Who on your side is the designated hazardous operations point of contact for fueling rehearsals and fueling execution?
- Specify any cryogenic conditioning timelines or thermal soak requirements for your hardware prior to fueling (hours at temperature).
- Do you require witness access or remote telemetry access during propellant operations (for example live pressure/temperature telemetry)?
Vehicle Final Assembly and Payload Mating
- Provide the latest vehicle-to-payload interface drawing and the scheduled date for mechanical mating at the integration facility.
- Which final electrical and mechanical sign-offs do you require at mating (for example torque witness, connector pincheck, harness strain-relief verification)?
- Who will provide final flight software version and telemetry configuration to be loaded prior to mating, if applicable?
- When must your team deliver the approved flight acceptance paperwork required before vehicle mating (for example flight heritage reports, waivers, Certificate of Flight Readiness)?
- Specify any mechanical or thermal constraints during mating (for example allowable bolt torque, maximum allowable handling acceleration in g).
- List the named owners from your organization who will sign the final mating acceptance form (name and role).
Execute Vibration, Shock, and Thermal Test Campaign
- Provide your environmental test levels and profiles for vibration, shock, and thermal vacuum that we should run (reference the test specification by number or include envelope values).
- Which test artifacts must you have retained or witnessed (for example flight hardware on the shaker, load path invoices, witness video)?
- Identify any flight acceptance thresholds or functional test pass/fail criteria that must be demonstrated post-environmental test (for example telemetry bit error rate, checksum integrity).
- Who will approve the environmental test final report and associated nonconformance dispositions?
- Estimate the number of hours of test and instrument calibration we should reserve for your campaign (approximate total).
- Do you require vibration fixture modifications or a full custom test rig built from your mechanical drawing?
Provide Real-Time Launch Telemetry Feed
- Specify the telemetry channels and data rates you require in the real-time feed (for example bus voltage, separation switch status, payload temperature, sample rate in Hz).
- Which telemetry transport do you prefer for real-time delivery (secure VPN stream, dedicated IP multicast, encrypted API endpoint)?
- Who on your operations team will receive the real-time feed and act as the telemetry operations lead during launch?
- When do you require access to the pre-launch test telemetry (hours before T-0) to perform final checkouts?
- List any telemetry security or encryption requirements (for example TLS 1.2+, dedicated keys, IP allowlist).
- If real-time telemetry is interrupted, what backup evidence will you accept to confirm separation (for example separation event timestamps in on-board log, post-launch TLE confirmation)?
-
Mutual Commit
Resolve commercial and contractual terms, insurance and indemnification arrangements, schedule commitments, and launch acceptance criteria.
Agreement Modules
- Master Launch Services Agreement (MLSA)
- Mission Statement of Work (SOW)
- Launch Order & Order Form
- Insurance Certificate & Policy Schedule
- Indemnity and Liability Exhibit
- Launch Schedule Commitment & Delay Remedies Addendum
- Launch Acceptance Criteria & Flight Readiness Acceptance
- Technical Interface Agreement (TIA)
- Change Order & Contract Variation Agreement
- Export Control & Regulatory Compliance Addendum
-
Deployment
Operationalize the launch campaign with readiness checks, integration, and go/no-go validation.
-
Pre-Deployment Readiness
Capture concrete readiness facts — payload shipping dates, facility access, fueling authorizations, range coordination and named owners required before integration.
Pre-Deployment Questions
Environment and site access
- Which integration site(s) or launch facility will receive the payload? (List site name(s) as used in your organization — needed to allocate facility slots.)
- For each site listed above, what is the first-available date for payload intake? (This date sets the baseline for inbound scheduling and storage.)
Logistics and shipping
- What is the confirmed payload shipping window—earliest inbound date and latest acceptable arrival? (So we can book transport and storage hold points.)
- Who is arranging commercial transport and customs clearance for the payload? (Select the party responsible; if a third party or buyer broker is used, the DeploymentConfig will capture contact details.)
- Does the payload contain hazardous items requiring special handling or permits (batteries, pressurized systems, propellant, etc.)? If yes, has the authorization been submitted to the facility/range?
Technical integration readiness
- Has the mechanical and electrical integration baseline been locked (fit-checks, separation interface, telemetry endpoints)? (We need a 'Locked' state to freeze integration drawings and dates.)
- Are required verification tests and witness plans finalized and booked (vibration/thermal/EMC, witness roles)? If booked, provide the target test completion date in DeploymentConfig.
People and ownership
- Who is the buyer's named owner for payload inbound coordination (name and role)? (This single point will accept custody at intake and coordinate facility handover.)
- Who is the named owner responsible for range coordination and launch window approvals (name and role)? (This person must be enabled to approve range interfaces and schedule decisions.)
- Are there any blackout dates or fixed constraints (facility outages, regulatory windows, insurance embargoes) that must be avoided during integration or campaign execution? (If yes, note that dates/details belong in DeploymentConfig.)
-
Integration Configuration
Lock technical integration values and operational parameters the team will use — mechanical/thermal limits, telemetry endpoints, separation sequencing, and test sign-offs.
Configuration Details
Integration Configuration — Environments & Endpoints
- Integration instance name (enter the single name used in all configs; format: lowercase alphanumeric and hyphen, Default: mission-integration)
- Integration environment stage (which environment do these values apply to? Default: Production)
- Telemetry ingestion endpoint URL (format: https://... — enter the endpoint the seller will push integration telemetry to)
- Telemetry authentication method (Default: mTLS — pick how telemetry is authenticated; if choosing token, you will be asked only for the token IDENTIFIER, not the secret)
Mechanical & Thermal Limits
- Primary mechanical interface standard for the payload adapter (Default: Clamping ring)
- Maximum allowable payload mechanical load during integration (peak g, integer — Default: 3)
- Minimum allowable payload temperature during integration (°C — Default: 0)
- Maximum allowable payload temperature during integration (°C — Default: 40)
Separation, Sequencing & Confirmation
- Separation sequencing mode (Default: Timed sequencing)
- Separation delay after ignition cutoff (seconds — numeric; Default: 120)
- Primary telemetry endpoint for separation confirmation (enter topic name or URL used to publish confirmation; format example: telemetry://separation/status or https://host/path)
Verification & Test Sign-offs
- Required integration test sign-off types (select all that will be required before flight integration)
-
Launch Campaign Execution
Plan and execute the launch campaign with a sequenced Gantt, owners for integration tasks, range windows, and real-time launch operations coordination.
-
Launch Readiness & Go/No-Go
Formalize final pre-launch checks, stakeholder sign-offs, and the official go/no-go decision with named owners and acceptance criteria.
Checklist items
- Receive signed Go/No-Go decision document
- Obtain written range clearance and NOTAM release
- Fueling authorization and LOTO verification completed
- Flight Termination System (FTS) acceptance and arming authorization
- Final payload acceptance certificate received from payload owner
- Telemetry and command link end-to-end verification completed
- Signed flight readiness review (FRR) closure with all open actions closed
- Required insurance certificates and indemnification docs validated
- Final integration configuration baseline signed
- Abort/standdown and contingency plan approval recorded
-
-
Success
Confirm orbital insertion outcomes, share telemetry and orbit determination, capture lessons learned, and maintain a shared channel for issues and enhancements.
Success Reviews
- Post-separation Health Check
- First Measurement Review
- Formal Acceptance Gate — Orbit Determination Decision
- Lessons Learned and Anomaly Closure
- Quarterly On-orbit Review
Issues & Enhancements
- Publish the lessons-learned report and the updated runbook to the shared channel.
- Restate Mission Scope acceptance criteria and numeric targets
- Produce a documented pass or fail decision against each Mission Scope acceptance criterion and capture the formal acceptance record.
- If any criterion is unmet, commit to a remediation plan with milestones and an agreed final resolution timeline.
- Publish the signed acceptance decision and supporting evidence to the shared workspace.
- If conditional acceptance or failure occurred, publish the remediation plan with milestone dates and verification criteria.
- Update the mission risk register to reflect acceptance outcomes and any residual risks.
- Consolidated telemetry and anomaly summary
- Close or assign resolution dates for all remaining anomalies and confirm the projected closure timeline.
- Agree a concise set of operational improvements and update the runbook and integration checklist accordingly.
- Re-confirm success criteria and responsibilities
- Complete the telemetry archive and verify accessibility for both parties.
- Close all anomaly tickets that meet closure criteria and update the anomaly tracker with planned residual items.
- On-orbit health and telemetry uptime review
- Confirm the asset continues to meet on-orbit health expectations and identify any trending issues requiring attention.
- Ensure the backlog of enhancements and persistent issues has prioritized next steps and resolution timelines.
- Publish the quarterly on-orbit health scorecard including telemetry uptime and mean time to anomaly detection.
- Update and publish the prioritized enhancement and defect backlog with estimated delivery windows.
- Validate the shared channel escalation contacts and publish any changes to the communications plan.
- Confirm each payload recorded a completed separation event and initial telemetry was received or document exceptions.
- Produce an immediate issue list with remediation tasks and target resolution windows.
- Publish the initial telemetry packet archive and separation timeline to the shared channel for review.
- Log all immediate anomalies in the shared issue tracker with remediation tasks and target dates.
- Schedule technical detailed review sessions for any items blocking payload commissioning.
- Present first orbit determination and telemetry completeness
- Determine whether orbital insertion error and beacon acquisition time are trending toward Mission Scope targets and identify any remaining risks.
- Agree a remediation plan with specific tasks and dates that addresses any gaps prior to the acceptance gate.
- Deliver an updated orbit determination report and telemetry completeness summary to the shared channel.
- Log and prioritize telemetry frame gaps and provide a re-ingest timeline for missing data.
- Publish the evidence package checklist required for the Mission Scope acceptance gate.
- Separation event and timeline verification
- Root cause and corrective action effectiveness review
- Present consolidated outcomes against each criterion
- Compare measurements against Mission Scope targets
- Incident and anomaly trend review
- Enhancement and defect backlog review
- Record pass/fail decision per criterion and capture signatory
- Operational and process improvements
- Root cause analysis for any insertion or telemetry gaps
- Initial telemetry and beacon acquisition check
- Early functional checks and mode confirmation
- Shared channel and escalation process validation
- Archive telemetry and lessons to the shared channel
- If conditional or failed, agree remediation plan and timeline
- Agree corrective actions and timeline to acceptance
- Open issues triage and immediate remediation actions
- Agree next quarter actions and schedule next review
- Confirm data and evidence package for the acceptance gate