Introduction
Launch-company acquisitions combine aerospace engineering, regulated operations, government procurement and project-like cash flow. The buyer is purchasing a system that must manufacture a vehicle, secure a site and range window, integrate a payload, obtain approval, launch safely, place the payload into the contracted orbit and collect cash. Weakness in any stage can defer revenue, absorb capital and damage the target's access to customers or regulators.
The valuation question is therefore narrower than the addressable market for access to space. It asks how much cash a specific target can produce from missions it can lawfully, technically and operationally deliver. The answer requires evidence for cadence, mission reliability, backlog quality, unit economics, remaining development and the buyer's ability to control risk after closing.
1. Define the acquisition thesis
The transaction team should write the acquisition thesis as a set of measurable claims. Examples include acquiring an operational launch service, securing sovereign launch access, integrating launch with spacecraft manufacturing, obtaining propulsion or avionics intellectual property, entering a government procurement channel or accelerating a buyer's vehicle programme. Each claim needs a value mechanism, evidence standard, owner and failure case.
The thesis should identify which cash flows belong to the target on a stand-alone basis and which arise only after integration. Customer revenue, contract margin and working capital belong in the operating case when supported by target evidence. Procurement savings, shared range infrastructure, constellation demand and cross-selling are buyer synergies. Separating them prevents the seller from being paid twice for value created by the buyer.
2. Separate company value from programme value
A launch company can contain an operating vehicle, a vehicle in development, propulsion assets, test facilities, launch-site rights, mission software, payload-integration capability and government qualifications. These assets mature at different rates and should not be valued through one revenue multiple. The operating service can be valued from accepted missions and cash generation. A development programme requires completion cost, schedule and probability adjustments.
Technology option value should be tied to an identified future decision. A reusable stage, larger vehicle or responsive-launch capability can create value if the technical path, customer requirement, funding plan and expected economics are credible. An idea without those components remains an opportunity narrative. The buyer should preserve options through staged funding and governance instead of capitalizing the full forecast at closing.
3. Reconstruct verified flight history
The diligence team should rebuild every attempted mission from primary evidence. Record vehicle configuration, licence, launch site, scheduled window, actual time, payload, target orbit, achieved orbit, anomaly, customer acceptance and corrective action. The FAA's commercial-space data and operator-licence resources provide a public starting point, while mission records, telemetry, customer certificates and regulator correspondence support transaction-level verification. [1][2]
Flights should be grouped by configuration. A success using an earlier engine, stage, avionics stack or launch site may provide limited evidence for the configuration being acquired. The same discipline applies to partial successes and test flights. Reliability statistics should state the population and avoid combining materially different systems merely to improve the headline rate.
4. Measure cadence as repeatable throughput
Cadence is the number of completed and accepted missions the full operating system can sustain. It depends on vehicle production, engine supply, test capacity, payload readiness, range access, licensing, launch-site operations, weather, mission engineering and customer decisions. A launch calendar that ignores these constraints is a sales plan rather than a capacity model.
Measure scheduled-to-actual variance, turnaround time, work in process, manufacturing cycle, engine-test throughput, launch-site occupancy and causes of delay. Separate target-controlled delay from customer, range and weather delay. Both affect cash timing, while remediation differs. Cadence receives valuation credit after repeated delivery across representative missions, sites and operating conditions.
5. Underwrite reliability and learning
Mission reliability is both a technical probability and a commercial condition. Customers may require vehicle certification, mission assurance, insurance, specific flight heritage or additional oversight. NASA's Launch Services Program describes its role in selecting vehicles and supporting mission success, while its performance site warns that mission-unique requirements can alter advertised capability. [11][12]
The buyer should inspect failure-mode analysis, qualification evidence, non-conformance records, telemetry, supplier escapes and closure of corrective actions. Learning has economic value when it produces fewer defects, less rework, shorter cycle times or better mission performance. Experience measured only as elapsed calendar time or cumulative engineering hours should not receive the same credit.
6. Classify backlog by enforceability
Backlog should be reconstructed contract by contract. Record signed value, funded amount, customer options, deposits, termination rights, refund rights, launch windows, price escalation, performance conditions, cancellation payments, assignment restrictions and change-of-control consent. The buyer should reconcile this schedule with the general ledger, deferred revenue, invoices, cash receipts and customer confirmations.
Rocket Lab states that its backlog includes contracts and purchase orders entered into by customers, excludes unexercised options, and can contain termination rights exercisable on notice with specified fees. Its filing also separates launch-services backlog from space-systems backlog. The disclosure illustrates the level of definition a buyer should demand from a private target. [16][17]
7. Verify government backlog
Government opportunity can range from an awarded procurement vehicle to a funded task order for a named mission. The acquisition team should obtain the base contract, modifications, orders, funding notices, statements of work, delivery schedules, award-fee provisions, termination clauses and performance assessments. Public award announcements and USAspending records help corroborate the documents, but the executed contract controls. [15]
Government backlog also carries programme, appropriations, certification, security and political dependencies. Revenue recognition may differ from billing and cash. The buyer should distinguish minimum guaranteed amounts, obligated funds, unfunded options and maximum ceiling. Customer concentration should be assessed at agency, programme and mission level because nominally separate awards can depend on one budget or architecture.
8. Distinguish IDIQ ceilings from funded orders
An indefinite-delivery, indefinite-quantity contract establishes a mechanism for future orders within stated limits. The Federal Acquisition Regulation states that the government is committed to the contract's minimum quantity and places orders for individual requirements; the maximum is not a promise to purchase that amount. Orders must identify scope, quantity, price and schedule. [13][14]
NASA's VADR contract demonstrates this distinction. NASA selected a pool of providers under a fixed-price IDIQ vehicle with a collective maximum value and issues firm-fixed-price task orders as missions are needed. A provider's admission to the pool can be strategically important, while transaction value should follow task orders, qualification, competitiveness and the provider's ability to deliver. [10]
9. Test commercial customer quality
Commercial customers vary in credit, mission readiness and financing. A launch contract with a funded satellite programme and completed payload can have greater conversion probability than an agreement with an early-stage constellation still raising capital. Diligence should examine the customer's financing, spacecraft production, regulatory approvals, spectrum position, insurance and launch dependency.
The contract schedule should include customer deposits, milestones and cancellation behaviour. Customer interviews can test launch-date priority, switching alternatives and willingness to accept a different vehicle or window. Revenue scenarios should avoid assuming every customer is ready when the target is ready. A launch company can appear supply-constrained while a material portion of its manifest remains customer-constrained.
10. Map deposits and cancellation rights
Deposits provide evidence of commitment only after their legal and accounting treatment is understood. The buyer should identify whether each amount is refundable, credited against launch price, forfeitable after a date, secured, held in escrow or subject to performance conditions. Cash already spent on vehicle production can create a future delivery obligation without providing future liquidity.
Cancellation clauses should be modelled under customer delay, target delay, mission failure, licensing delay and force majeure. The economic result may include refund, termination fee, replacement flight, priority rebooking or damages cap. These outcomes affect both backlog value and working capital. The quality of a manifest is partly the quality of its cancellation economics.
11. Normalize pricing and mission mix
Headline price per launch can obscure mission-specific services. Price may include payload processing, range support, mission design, separation systems, special studies, schedule priority, responsive-launch capability, insurance or orbital transfer. Normalize each mission to a standard configuration and separately value mission-unique work.
Rocket Lab's 2025 annual report explains that revenue per launch varies with orbit, insertion requirements, payload handling, launch location, time sensitivity, revenue recognition and other factors. Its disclosed launch-services revenue, cadence, revenue per launch and cost per launch provide a useful public example of how operating evidence can be connected. [16][17]
12. Build per-launch unit economics
The buyer should construct cost per accepted mission from bill of material, engine and stage production, direct labour, test, consumables, freight, integration, launch-site operations, range charges, mission-unique engineering, insurance, allocated support and expected rework. Separate recurring cost, fixed operating cost and programme development.
Margin should be reconciled at mission and cohort level. A target may report improving unit cost while shifting development labour, overhead or launch-site expense elsewhere. The model should compare management's standard cost with purchase orders, payroll, inventory movements and actual mission closeouts. Cash contribution matters because revenue recognition can precede or follow mission delivery.
13. Model fixed-cost absorption
Launch businesses carry facilities, engineering, range, safety and programme-management costs that do not move proportionally with missions. Higher cadence can improve absorption if the additional flights use available capacity and do not require another site, factory or shift structure. The model should therefore represent capacity in steps rather than assume a smooth cost curve.
At each cadence level, identify headcount, engine-test slots, stage flow, integration bays, pad occupancy, maintenance windows and supporting capital. A ten-mission plan that needs a second production line should include its completion cost and ramp loss. Fixed-cost absorption creates value after the system passes its next bottleneck.
14. Underwrite engine and vehicle supply
Supply diligence should trace propulsion, structures, avionics, valves, tanks, composite materials, separation systems and controlled components to qualified sources. Record lead times, minimum orders, sole-source exposure, export classification, quality history, tooling ownership, intellectual-property rights and change-of-control provisions.
The buyer should test whether the forecast cadence can be supported by released purchase orders and supplier capacity. A target can hold a large manifest while lacking engines or long-lead components for the scheduled year. Supplier substitution can require redesign, qualification and regulator engagement. Inventory should be assessed for configuration obsolescence and recoverability after programme changes.
15. Assess launch-site and range access
Range access is a capacity right, operating relationship and schedule dependency. The buyer should inspect site agreements, permitted vehicle configurations, pad capacity, shared infrastructure, maintenance, emergency response, environmental conditions, range fees and priority rules. The operating plan should include weather, public-safety constraints and conflicts with other users.
GAO reported that commercial launches at federal sites had more than quadrupled since 2021 and identified strained infrastructure, cost-recovery issues and limited scheduling insight for payload processing. These findings support a specific diligence question: whether forecast cadence fits the actual range and processing system. [7]
16. Review manufacturing capacity
Factory capacity should be demonstrated through routing, cycle time, yield and work-in-process. The buyer should walk the production line and reconcile serial numbers, material status, non-conformance, labour bookings and stage completion. Prototype facilities often require different controls to support repeatable production.
Capacity should be modelled at the constraint, which may be engine test, tank production, avionics acceptance, final integration or site logistics. Overall floor area provides limited evidence. The buyer should require a funded debottlenecking plan, supplier commitment and quality controls before valuing the higher cadence case.
17. Test schedule realism
An integrated master schedule should connect engineering release, supplier delivery, manufacturing, qualification, licensing, site readiness, payload availability, range windows and customer milestones. Each critical path needs an accountable owner and evidence of duration. Schedule reserve should reflect maturity and historical variance.
The transaction model should preserve date-specific cash effects. A launch delayed across a fiscal period can change revenue recognition, milestone receipts, working capital and covenant compliance. Multiple missions relying on the same unresolved qualification test should be treated as correlated rather than independent.
18. Evaluate licences and regulatory approvals
The FAA licenses commercial launch and re-entry operations and transitioned current operators to Part 450. Part 450 can support a portfolio of operations, configurations, mission profiles and sites within the approved basis. The buyer must still determine which exact operations the target can conduct and which modifications require review. [2][4][5]
The legal data room should contain current licences, applications, safety analyses, waivers, environmental records, financial-responsibility evidence, reporting history and regulator correspondence. Change-of-control consequences, key personnel and foreign-ownership issues require counsel. A valuation case should avoid assuming that a licence automatically transfers or covers a future vehicle.
19. Review mishaps and corrective actions
Mishap diligence should cover flight failures, test incidents, pad events, near misses and serious quality escapes. The FAA's mishap framework and public investigation information establish the regulatory context, while the transaction team needs underlying telemetry, causal analysis, corrective-action verification and return-to-flight conditions. [3]
A closed report does not by itself establish economic closure. The buyer should identify configuration changes, supplier remediation, additional inspection, schedule effects and recurring cost. If a corrective action reduces performance or increases labour, the unit economics and mission commitments must be updated.
20. Address national-security procurement
National Security Space Launch Phase 3 uses a dual-lane approach. Lane 1 broadens competition for missions with defined requirements and on-ramp opportunities. Lane 2 supports more demanding missions and includes certification and mission-assurance requirements. Public contract values and provider allocations should be interpreted within their contract form and ordered missions. [7][8][9]
An acquirer should test whether the target's eligibility, certification plan, security posture and programme relationships survive closing. Government relationships are valuable through lawful, transferable capabilities and performance. They should not be valued as personal influence. Integration planning must protect cleared work, controlled information, approved systems and required organisational separation.
21. Review foreign-investment and export controls
Launch vehicles, propulsion, guidance, technical data and defence-related services can be subject to the International Traffic in Arms Regulations or the Export Administration Regulations. Transaction parties should classify assets and data, identify foreign persons, review licences and technical-assistance agreements, and design clean teams before sensitive diligence begins. [25][26]
The Committee on Foreign Investment in the United States can review covered transactions involving critical technology, critical infrastructure, sensitive personal data and control or certain non-controlling rights. Treasury regulations and annual reports provide the governing framework and enforcement context. Counsel should determine filing, mandatory-declaration and mitigation requirements for the actual ownership structure. [23][24]
22. Assess intellectual-property control
The buyer should map patents, trade secrets, source code, design files, test data, manufacturing know-how, government rights, university licences, employee assignments and supplier licences. Ownership of a vehicle design can be less valuable if the target lacks rights to essential tooling, software or technical data.
Government funding can introduce data-rights regimes that differ by contract. Open-source components and commercial software require licence review. The integration plan should protect restricted data while allowing the buyer to operate, improve and support the acquired system. Technology value should be reduced where rights are incomplete, disputed or dependent on a departing individual.
23. Test insurance and liability
The insurance workstream should distinguish statutory financial responsibility, launch liability, property, business interruption, product liability, directors and officers cover, cyber cover and customer requirements. Policy limits, exclusions, deductibles, named insureds and claims history matter. A launch failure can create replacement obligations even when third-party liability is insured.
The valuation model should include expected loss, premium changes after an incident and the cash needed to build a replacement vehicle. The buyer should assess whether contract caps align with insurance and whether government indemnification or cross-waivers apply. Insurance can transfer selected loss; it does not replace operating resilience.
24. Model working capital and cash conversion
Cash conversion depends on deposits, milestone billing, long-lead purchases, inventory build, payroll, customer acceptance and refund exposure. The buyer should construct a mission-level cash curve from signing through launch and final acceptance. Aggregate annual EBITDA can hide a liquidity trough before a high-cadence period.
Deferred revenue should be reconciled with delivery obligations. Customer cash spent on development may leave the buyer responsible for future launches. Payables extended beyond supplier terms can flatter liquidity and threaten supply. Completion funding belongs in the purchase-price bridge or committed financing plan.
25. Fund remaining development and completion
Remaining development capital should be estimated through an engineering-based cost-to-complete, not a percentage of historic spend. Work packages should cover design closure, hardware, testing, qualification, software, sites, licences, mission assurance, contingency and working capital. The estimate should identify dependencies and schedule confidence.
GAO's Technology Readiness Assessment Guide and NASA's Systems Engineering Handbook provide useful structures for evaluating maturity, evidence and system integration. They do not determine transaction value. The acquirer should connect maturity gaps to specific spend, milestone, probability and commercial consequence. [19][20]
26. Value government relationships carefully
Government access can create durable demand, qualification barriers and reference value. The buyer should value awarded work, transferable qualifications, performance records and demonstrated ability to compete. Unfunded pipeline, programme ceilings and anticipated policy support should remain separately probability-weighted.
The commercial model should identify bid cost, mission-assurance burden, cybersecurity, reporting, audits, domestic-content requirements and payment timing. Government revenue can provide visibility while carrying compliance cost and customer concentration. Value follows net cash after those obligations.
27. Value technology options separately
A target may offer options in reusability, medium-lift vehicles, in-space transport, hypersonics, defence responsiveness, manufacturing services or propulsion sales. Each option should be framed as a staged decision with remaining spend, time, technical evidence, customer evidence and strategic fit.
The buyer can use a probability-weighted present value or real-options framework. Both require disciplined assumptions. Base enterprise value should not include a full forecast for every concept. Consideration can be linked to qualification, flight, funded order or margin milestones so that seller proceeds rise as evidence improves.
28. Apply evidence-weighted valuation
The valuation should triangulate mission contribution, discounted cash flow, comparable companies, precedent transactions, replacement cost and strategic option value. Multiples require normalization for vehicle maturity, service mix, backlog definition, capital intensity, government concentration and accounting policy. A space-systems company with launch operations is not directly comparable to a pure launch provider.
Fair-value and impairment standards provide general principles for market-participant assumptions, cash-generating units and identifiable intangibles. Transaction teams should apply the relevant accounting framework with advisers and auditors. [28][29][30]
29. Construct the hypothetical transaction
The hypothetical target reports sixteen missions and USD 480 million of stated backlog. Contract review identifies USD 180 million of funded firm orders, USD 140 million of framework or ceiling capacity, USD 90 million of options and USD 70 million of letters of intent or unsupported pipeline. Evidence weights of 85, 20, 35 and 10 percent produce USD 219.5 million of risk-adjusted economic backlog before fulfilment cost.
The target completed five missions in the last year and plans ten within four years. Fully absorbed cost per launch falls from USD 34 million to USD 24 million as yield and utilization improve. The case assumes USD 620 million of unadjusted present value, less USD 140 million of remaining completion capital and USD 110 million of execution, concentration and compliance risk, plus USD 70 million of buyer-specific synergies and USD 40 million of probability-weighted option value. The resulting illustrative enterprise value is USD 480 million. These figures are hypothetical.
30. Stress cadence cost and backlog
The model should combine downside variables because launch risks are correlated. A qualification delay can defer missions, postpone deposits, extend payroll and reduce customer confidence. A failure can interrupt cadence, increase testing, raise insurance cost and trigger customer remedies. Scenario design should reflect these pathways.
At minimum, test launch count, average price, mission mix, cost per vehicle, supplier inflation, site charges, customer delay, cancellation, development overrun, return-to-flight duration, funding availability and terminal value. Liquidity should remain visible monthly through the trough. A transaction that produces acceptable value only under the full manifest and fastest cadence requires stronger price protection.
31. Structure consideration and protection
Closing consideration can reflect verified operating assets and funded backlog. Deferred consideration can follow named milestones such as licence approval, successful flight, required reliability, funded order, customer acceptance or gross margin. Milestones should be objective, within defined control and protected against deliberate diversion of resources.
Representations should address backlog, contracts, licences, export controls, security, intellectual property, product performance, incidents and financial records. Escrow, indemnity, warranty insurance and specific covenants can allocate identified risk. The buyer should also reserve sufficient capital to complete the plan; reducing price without funding completion can still destroy the asset.
32. Plan integration before signing
Integration planning should protect mission delivery from Day One. The buyer should define authority for flight safety, engineering change, customer commitments, government communication, supplier release, cash control and incident response. Critical personnel and cleared teams need retention and governance that preserves lawful independence where required.
The integration plan should sequence systems, finance, procurement and commercial changes around launches. Disrupting configuration control or supplier approvals near a mission can create disproportionate risk. Synergies should have owners, costs, timing and customer safeguards. The first objective is continuity of safe contracted service.
33. Define the acquisition decision
The investment committee should receive a concise decision record. It should state the acquisition thesis, verified flight and cadence evidence, risk-adjusted backlog, unit economics, completion capital, regulatory conditions, downside liquidity, transaction protections, integration readiness and value range. Open matters should have owners and closing conditions.
Approval should specify which claims are accepted and which remain conditional. The decision can distinguish closing value, milestone value and strategic option value. This structure preserves upside while preventing aspirational manifest and technology narratives from entering the base price without evidence.
Conclusion
Launch-company valuation becomes tractable when the transaction team follows the evidence chain from customer mission to accepted launch and collected cash. Cadence requires a repeatable production, regulatory and range system. Reliability requires configuration-specific flight and corrective-action evidence. Government backlog requires funded orders and executable scope. Technology options require staged capital and explicit probability.
The proposed framework converts those principles into a diligence schedule, unit-economic model, downside case and transaction structure. Buyers can use price, milestones, escrow, indemnities and committed completion capital to align consideration with evidence. Sellers can increase value by producing a clean flight record, enforceable backlog schedule, reconciled mission economics and a credible path through the next operating constraint.
The most useful diligence output is a common evidence model used by engineers, commercial teams, finance, legal advisers and the investment committee. It should preserve the provenance of every material assumption and show how a change in mission readiness, licensing, cadence, reliability or customer funding affects cash and value. This discipline supports faster decisions because disagreements become specific and testable. It also gives the post-closing team a practical control system for capital allocation, customer commitments and integration. A launch transaction can then be priced around what the system has demonstrated, funded around what remains to be completed and protected against the events that could interrupt safe delivery.
Appendix A. Flight and cadence checklist
Reconstruct every mission by configuration, site, scheduled window, actual date, payload, target orbit, achieved result, customer acceptance and anomaly. Reconcile the operating forecast with vehicle work in process, engine-test capacity, supplier releases, site windows, licence scope and payload readiness.
The schedule should show the source and review date for each fact. Flight evidence should distinguish regulatory outcome, customer outcome and internal engineering outcome because the three can differ. A payload can reach an orbit outside its original tolerance, a vehicle can complete a test objective without completing a customer mission, and a regulator can require additional action after an event. Record each conclusion in the terms used by the responsible authority or customer. For cadence, calculate the interval between completed missions, planned-to-actual variance, pad occupancy, rework and the proportion of delay controlled by the target. Reconcile the next twelve months of missions with serialized hardware and customer payload status.
Appendix B. Backlog checklist
For every agreement, record funded amount, contract ceiling, minimum guarantee, task order, option, deposit, cancellation right, launch window, price escalation, change-of-control consent, customer readiness and expected gross margin. Confirm material balances with customers and accounting records.
The contract schedule should connect legal rights to accounting and cash. For each line, include recognized revenue, deferred revenue, billed receivable, collected cash, remaining performance obligation and estimated fulfilment cost. Identify agreements that share one customer financing event, satellite factory or regulatory approval because apparent diversification may be illusory. Government entries should show appropriation, obligation and issued order separately. Commercial entries should record the customer's payload, financing, licence and launch-alternative status. The buyer should require written explanations for every difference among stated backlog, accounting backlog, funded order value and the risk-adjusted economic schedule.
Appendix C. Technical and regulatory checklist
Review configuration control, qualification, telemetry, failure analysis, corrective actions, software, cyber security, intellectual property, export classification, licences, environmental approvals, site agreements, insurance and government security. Link each issue to cost, schedule and transaction protection.
Configuration control should establish which drawings, software, materials and processes produced each flight article. The qualification matrix should distinguish analysis, component test, subsystem test, integrated test and flight evidence. For each open waiver or deviation, identify approving authority, affected missions and expiry. The regulatory schedule should show current approval, pending action, responsible counsel and the operating consequence of delay. Export-control diligence should limit access before sensitive data enters the deal room. Cyber review should cover development environments, mission systems, supplier access and incident response. Every red item should result in a priced remediation, a closing condition, a covenant or a specific decision to accept the exposure.
Appendix D. Financial checklist
Build mission-level revenue, cash collection, recurring cost, fixed cost, development spend, working capital and replacement obligations. Reconcile management forecasts with source records. Present base, downside and severe-downside liquidity with committed funding.
The model should preserve both calendar timing and vehicle cohort. Revenue and cash should follow contract milestones, including refunds and replacement-flight obligations. Cost should follow purchase orders, labour routing, test slots and site activity. Development work should be separated from recurring production even when the same engineers perform both. Forecast improvements require a named mechanism such as yield, labour learning, supplier pricing or asset utilization. Each mechanism should have a starting observation, target, implementation cost and accountable owner. The acquisition bridge should show debt, cash, leases, customer deposits, provisions and cost to complete. Liquidity should include minimum operating cash and covenant headroom rather than only ending cash.
Appendix E. Transaction checklist
Separate stand-alone value, buyer synergy and technology option value. Define closing conditions, regulatory filings, representations, escrow, indemnities, milestone consideration, retention and integration governance. Assign each material risk to a contract term or funded operating response.
The definitive agreement should identify the evidence date for backlog and major operational representations. Between signing and closing, ordinary-course covenants should govern new launch contracts, price concessions, customer refunds, supplier commitments, engineering changes, incidents and regulator communication. The buyer should decide how milestone consideration is treated when a customer or regulator delays an event outside seller control. Integration governance should name the authority for flight safety and engineering release, preserving technical independence from short-term financial pressure. Retention should focus on roles and documented knowledge transfer. A closing checklist should confirm that committed completion funding, insurance and operating liquidity are available on Day One.
The board paper should include a one-page claim register. Each material value claim should point to its contract, flight record, cost schedule or independent confirmation. The register should state who verified the claim, when it was verified, what remains open and which valuation line depends on it. This makes the acquisition decision auditable and helps the integration team preserve the assumptions that justified the price.
Appendix F. Decision figures and tables
Proposed transaction framework; higher levels require stronger verification.
| Category | Required evidence | Base-case treatment |
|---|---|---|
| Funded firm order | executed order, funding and mission scope | include with delivery probability and margin |
| IDIQ or framework ceiling | base vehicle and minimum guarantee | include only minimum and issued orders |
| Customer option | exercisable terms and customer readiness | scenario probability outside contracted base |
| Letter of intent | non-binding expression and conditions | pipeline only |
| Internal forecast | sales estimate without customer obligation | exclude from backlog |
Proposed evidence treatment.
Wholly hypothetical; USD million.
| Instrument | What it proves | What it does not prove |
|---|---|---|
| Base IDIQ award | eligibility and ordering mechanism | future orders up to the ceiling |
| Minimum guarantee | binding minimum obligation | full programme share |
| Funded task order | defined scope and obligated funding | automatic follow-on work |
| Option | contractual right to order | exercise or appropriation |
| Public announcement | agency intent and context | executed terms and collected cash |
Proposed contract review.
Wholly hypothetical annual missions and USD million fully absorbed cost per launch.
| Cost component | Year 1 | Year 4 | Evidence |
|---|---|---|---|
| Vehicle hardware and engines | 18.0 | 14.0 | purchase orders and build records |
| Direct labour and test | 6.0 | 4.0 | payroll and routing |
| Range and launch operations | 4.0 | 3.0 | site and service agreements |
| Mission engineering and integration | 3.0 | 1.8 | mission closeout |
| Allocated fixed support | 3.0 | 1.2 | capacity and cost ledger |
Hypothetical cost build for diligence.
Wholly hypothetical missions per year by principal operating constraint.
| Area | Principal question | Evidence |
|---|---|---|
| FAA licence | which configurations sites and missions are covered | licence basis and correspondence |
| Mishap history | are corrective actions verified and costed | investigation and return-to-flight record |
| Export control | who may access hardware software and data | classification and licences |
| CFIUS | does ownership trigger filing or mitigation | counsel analysis and filing record |
| Security | can cleared programmes continue after closing | facility and personnel approvals |
Proposed workstream.
Wholly hypothetical; USD million.
| Uncertainty | Structure | Verification event |
|---|---|---|
| Licence scope | closing condition | approved configuration and site |
| Development completion | milestone consideration | qualification and successful flight |
| Backlog conversion | earnout | funded order and collected cash |
| Reliability | escrow or milestone | defined mission-success record |
| Compliance | representation and indemnity | clean regulatory and export review |
Proposed allocation of evidence risk.
Wholly hypothetical cumulative cash after acquisition in USD million.
| Criterion | Investable evidence | Red flag |
|---|---|---|
| Cadence | repeat missions supported by capacity | calendar without bottleneck proof |
| Reliability | configuration-specific flight and closure | pooled or incomplete success record |
| Backlog | funded executable orders | ceilings and letters presented as revenue |
| Economics | reconciled mission cash contribution | unsupported cost curve |
| Completion | funded work packages and schedule | percentage uplift without engineering basis |
| Control | licences security and integration plan | unresolved change-of-control dependency |
Proposed approval framework.
| Decision item | Required conclusion | Owner |
|---|---|---|
| Strategic thesis | defined stand-alone and synergy value | deal sponsor |
| Technical evidence | accepted configuration and maturity | chief engineer |
| Commercial evidence | risk-adjusted backlog and customer readiness | commercial lead |
| Financial case | value range completion funding and downside liquidity | chief financial officer |
| Regulatory clearance | FAA export control CFIUS and security path | general counsel |
| Integration | Day-One continuity and milestone governance | integration lead |
Proposed board output.
Sources
- Federal Aviation Administration, Commercial Space Data. Read the primary source
- Federal Aviation Administration, Vehicle Operator Licenses. Read the primary source
- Federal Aviation Administration, Commercial Space Mishap Investigations. Read the primary source
- Electronic Code of Federal Regulations, 14 CFR Part 450 Launch and Reentry License Requirements. Read the primary source
- Federal Aviation Administration, FAA Streamlines Commercial Space License Approvals. Read the primary source
- Federal Aviation Administration, Aerospace Forecast Fiscal Years 2025 to 2045. Read the primary source
- United States Government Accountability Office, National Security Space Launch Increased Commercial Use of Ranges Underscores Need for Improved Cost Recovery. Read the primary source
- Space Systems Command, National Security Space Launch Phase 3 Lane 1 On-Ramp Awards. Read the primary source
- United States Space Force, National Security Space Launch Phase 3 Lane 2 Contracts. Read the primary source
- National Aeronautics and Space Administration, Venture-Class Acquisition of Dedicated and Rideshare Launch Services. Read the primary source
- National Aeronautics and Space Administration, Launch Services. Read the primary source
- National Aeronautics and Space Administration, Launch Vehicle Performance Website. Read the primary source
- Federal Acquisition Regulation, 16.504 Indefinite-Quantity Contracts. Read the primary source
- Federal Acquisition Regulation, 16.505 Ordering. Read the primary source
- United States Government, USAspending Contract Data. Read the primary source
- United States Securities and Exchange Commission, Rocket Lab 2025 Form 10-K. Read the primary source
- United States Securities and Exchange Commission, Rocket Lab 2025 Annual Report to Stockholders. Read the primary source
- United States Securities and Exchange Commission, Rocket Lab 2025 Results Exhibit. Read the primary source
- United States Government Accountability Office, Technology Readiness Assessment Guide GAO-20-48G. Read the primary source
- National Aeronautics and Space Administration, Systems Engineering Handbook. Read the primary source
- United States Department of Justice and Federal Trade Commission, 2023 Merger Guidelines. Read the primary source
- Federal Trade Commission, Hart-Scott-Rodino Act and Premerger Notification Program. Read the primary source
- United States Department of the Treasury, CFIUS Annual Reports. Read the primary source
- Electronic Code of Federal Regulations, 31 CFR Part 800 Regulations Pertaining to Certain Investments in the United States by Foreign Persons. Read the primary source
- Electronic Code of Federal Regulations, 22 CFR Part 121 United States Munitions List. Read the primary source
- Bureau of Industry and Security, Export Administration Regulations. Read the primary source
- National Institute of Standards and Technology, SP 800-161r1 Cybersecurity Supply Chain Risk Management Practices. Read the primary source
- IFRS Foundation, IFRS 13 Fair Value Measurement. Read the primary source
- IFRS Foundation, IAS 36 Impairment of Assets. Read the primary source
- IFRS Foundation, IAS 38 Intangible Assets. Read the primary source
