Why does an ESA GSTP proposal need national-delegation support?

A company preparing a General Support Technology Programme activity should treat national-delegation support as a distinct project dependency. A strong technical idea does not, by itself, establish that the relevant national support has been confirmed.

ESA's GSTP guidance says support for an activity must be confirmed through an official letter from the relevant national delegations. It points to esa-star for procurement information and notes an outline-proposal route through OSIP for Element 2 Make. These routes explain where to start; they do not replace the required support. How to work with GSTP The ESA C1–C4 procurement clause guide addresses how the actual tender allocates participation roles.

The practical implication is to prepare a concise proposition before investing in a full technical submission. Explain the technology, the uncertainty to be addressed, the intended commercial or programme relevance and the organisation that would deliver the work. The delegation needs enough information to discuss fit without receiving an unstructured product brochure. The light and full esa-star registration distinction separates proposal preparation from the registration needed at a later award stage.

Identify the legal entities involved. A project with partners in several countries can create separate support questions. A company should not assume that one partner's conversation resolves the position of every participant. The work allocation and budget should make each entity's contribution visible. The NAVISP Element 2 review connects the proposed navigation product with the programme's commercial purpose.

The technical plan should show a meaningful development step. Describe what is already demonstrated and what the proposed activity would establish. A broad ambition to enter the space market is less useful than a bounded question with a clear deliverable and evidence of progress.

Timing matters because technical review, national discussion and internal company approval can move at different speeds. Build the plan around those dependencies. If the scope changes substantially, check whether the existing support still covers the revised proposition.

Do not interpret a positive conversation as a formal letter. Record the actual status: initial discussion, information requested, support under consideration or written confirmation received. This prevents the team from presenting an incomplete funding position as settled.

The company's business case should remain visible throughout. A technology development activity may create an asset useful in later commercial work, but the path to that market needs additional decisions. Identify the expected next step and the evidence the project would provide without promising a future customer order.

For a consortium, establish who coordinates the support process and who owns each submission. Fragmented communication can produce inconsistent descriptions of the same project. A shared, controlled summary helps participants keep the technical scope and financing assumptions aligned.

The public GSTP guidance does not establish how quickly a delegation will respond, whether funding is available for a particular topic or whether a company qualifies. Those questions require the current programme documents and the relevant official national channel.

Why the national decision sits beside ESA's technical review

GSTP's structure explains why an applicant encounters two conversations. The engineering discussion concerns the usefulness and feasibility of a technology activity. The national discussion concerns support for that activity within the programme. Those decisions may use some of the same material, but they answer different questions. A delegation needs a recognisable industrial proposition: which national entity would undertake the work, which capability would remain with it and how the proposed budget connects to that contribution.

This becomes particularly important when a startup joins an established contractor. The startup may describe the activity as a new product, while the contractor describes it as qualification of a component for a wider system. Both descriptions can be accurate, yet the work packages must reveal who develops the reusable asset and who integrates it. Otherwise, a national discussion can proceed on the assumption that domestic development is substantial while the technical proposal allocates most engineering elsewhere. An agreed division of work makes that difference visible early.

The delegation letter therefore belongs to the proposed configuration of the project. Changes to the principal supplier, participating entities or development scope can affect the case that officials originally considered. The commercial implication is that partner selection is part of proposal preparation, rather than an administrative detail that can safely be deferred until contracting.

Make distinguishes several reasons for investing

ESA's description of GSTP Element 2 Make distinguishes market opportunities, strategic opportunities and national priorities. The first concerns a commercial prospect with identified customers; the strategic route can address entry into new markets, newcomers or technological obsolescence. National priorities add an explicitly national rationale. The programme excludes satellite telecommunications, for which ARTES provides the relevant ESA family.

These distinctions change the evidence an industrial team should emphasise. A component supplier responding to a known customer's requirement can explain the purchasing decision that depends on successful development. A newcomer transferring a terrestrial process into space may instead need to establish why the adaptation creates a credible position in a market where it has not yet sold. An established supplier addressing obsolescence has a different commercial problem again: preserving a viable product and its supply chain when a previous input can no longer support future production.

Consider a hypothetical optical-component company. If its prospective integrator has specified a performance gap in an existing product, the commercial story centres on closing that gap and completing evaluation. If the same company proposes an unfamiliar manufacturing process without an identified user, the project is asking a different question about industrial capability and market entry. Presenting both as a generic innovation project hides the basis on which the company is making its investment.

The programme's categories help a founder explain that basis without pretending that every development activity has an immediate purchase order behind it. They also expose a weak proposition: when neither a customer requirement nor a convincing strategic reason can be articulated, the missing work may be commercial investigation before proposal writing.

A useful development result must survive the project

For a hardware business, the durable result might include a qualified process, controlled production documentation and a component that can be manufactured consistently. For a software supplier, it might include a maintainable implementation, reproducible verification evidence and a clearly defined interface. Those assets have different owners, maintenance costs and routes into subsequent products. The proposal becomes more useful to the company when it identifies which of them is actually being created.

A practical distinction is between buying engineering effort and building a capability. External specialist work can accelerate an activity, but a company that intends to sell and support the result must retain enough knowledge to use it. Work allocation should therefore reflect the future operating model as well as the immediate development schedule. A subcontractor can deliver an excellent report while leaving the applicant dependent on that subcontractor for every subsequent modification.

The strongest national and technical narratives meet at this point. They explain what the activity establishes, which organisation can exploit that result and which subsequent commercial decision it enables. That is considerably more informative than a forecast of a large addressable market: it identifies the industrial consequence of funding this particular development step.

The useful planning principle is straightforward: build the technical case and the support case together. A letter is an identifiable milestone in that process, while an executed contract is a later commercial event. Keeping those stages distinct helps the company decide how much bid effort to commit and when it can responsibly plan delivery.