A UK hardware company can pursue space work through national grants, ESA programmes or a contract in another company’s supply chain. Start by identifying who will buy or fund the work, what instrument they use and which application stage is available. Then define the hardware responsibility, delivery milestone and evidence your engineering team can own.
This is the route-selection hub for Arc’s space funding and bids guides. Programme status was checked on 8 September 2026. The new UK Space Strategy is a useful signal of priorities; its investment announcement is not a single open competition. UK Space Strategy announcement
Which route fits our first project?
| Route | What to establish | Engineering preparation |
|---|---|---|
| UKSA national grant | The named call, eligible applicant, match funding and application stage. C-LEO Call 3 and NSIP have separate rules. | A credible R&D scope, maturity gap, funded tasks and measurable outputs. |
| ESA programme route | Programme participation, the opportunity’s conditions and any national support process. C-LEO Call 2 uses ARTES. | Technical proposal, product definition and the work/evidence required by that route. |
| Procurement | A current invitation to tender, the buying organisation and contractual deliverables. An award notice records past purchasing. | Response to the actual statement of work, acceptance criteria and invoked standards. |
| Consortium or subcontract | The lead’s stage, your proposed scope and whether changes or new partners are permitted. | Interfaces, supplied items, test access, handover evidence and acceptance owner. |
ESA describes participation in its technology procurement and the use of esa-star for Invitations to Tender. Registration is an access step, not proof that a company is eligible for every opportunity. Read the conditions of the specific programme and tender. About ESA technology programmes For practical ESA submission mechanics, use the first ESA contract guide.
Where did the September 2026 calls stand?
C-LEO Call 3 is closed to new Stage One submissions: that deadline was 7 September 2026. Invited Stage Two applicants face a published deadline of 11 November 2026 at midday GMT. C-LEO Call 3: national applicant guide NSIP Call 3’s outline stage has also closed; the full-proposal deadline is 12 November 2026 at 23:59 for invited applicants. NSIP Call 3 announcement of opportunity Neither later deadline is a new entry point for an unsubmitted lead proposal.
Existing C-LEO Call 2 applicants should check the separate ARTES process: the UKSA guide lists an indicative full-proposal checkpoint on 25 September, followed by ESA submission on 5 October. Its exact timezone wording and programme instructions need checking before submission. C-LEO Call 2: ARTES applicant guide The C-LEO proposal guide explains the route split; the NSIP full-proposal guide explains the engineering pack.
Which route does the mechanism supplier choose?
Fictional example: a 30-person mechanism company has a laboratory tool-changing breadboard. Its engineering lead can own the mechanical and electrical interfaces, but the company cannot yet commit to a complete in-orbit mission. No funding award or test result is implied by this example.
The team first writes a one-page scope: supplied mechanism, assumed host interfaces, current configuration, evidence available, missing environmental work and the next decision. It considers a national R&D grant only against the relevant call’s eligibility and stage. In parallel, it evaluates a supplier package for a mission lead. That package excludes spacecraft operations and states who must provide the host simulator.
The useful output is a bounded offer: “We propose to deliver a representative mechanism and agreed interface test evidence; host loads and test access require agreement.” The unresolved load envelope goes into the risk and clarification records. A bid owner confirms route eligibility; a systems lead confirms scope; a verification lead estimates the evidence work. This role split is Arc’s recommended preparation method.
What belongs in our first evidence pack?
Use the workbook to connect each claim to its source or current result, the proposed work package, the missing evidence and an owner. Keep “we have demonstrated” separate from “we will demonstrate”. A customer letter may support demand; it does not establish performance. A laboratory report may support one function; it does not establish the whole product’s readiness.
Continue with TRL evidence, ECSS obligations before bidding and the C-LEO supplier handover checklist. For mission-specific preparation, use ISAM demonstration planning or SDA sensor contribution mapping. The 2026 strategy guide explains the funding context without turning allocations into open calls.
Review a first supplier package in Arc
Connect the proposed supplier deliverable to the customer requirement, interface question, available evidence and person who can resolve the allocation. A first-contract review should expose what the team can commit to and what still depends on the lead organisation. Arc’s connected programme model can organise that context; engineers retain the technical and approval decisions.
Frequently asked questions
Is UK space funding the same as a contract?
No. A grant supports an eligible project under funding conditions. Procurement buys defined work, goods or services. A supplier contract is an agreement with the customer or prime. Check the instrument in the actual notice.
Can a small hardware company join without leading a grant?
A supplier or consortium role may fit better. C-LEO Call 3 guidance permits consortium or subcontractor participation, subject to the call rules and the lead’s proposal. Agree a specific deliverable and evidence handover.
Which guide should an existing applicant read first?
Read the relevant C-LEO or NSIP guide for its current stage, then build a requirements-to-evidence record for one work package. Programme-issued instructions remain the submission authority.
Connect one bid commitment to its engineering evidence.
Try a work package in Arc: organise its requirements, interfaces, risks, verification work and evidence so your team can review the next decision.