What evidence does an ESA Growth Project need beyond a successful first market?

A company considering an ESA Growth Project should explain both what has already worked and what must change for the next market. Commercial success in one setting is valuable evidence, but it does not automatically establish that the same service can be sold elsewhere without adaptation.

ESA describes Growth Projects as support for space-enabled solutions with demonstrable commercial success in a primary market, aimed at secondary-market opportunities. The scope includes new service elements, integration, testing and larger pilots. Optional support can help develop relevant business partnerships. ESA Growth Projects The choice between ESA BASS proof of concept and pilot projects similarly depends on the customer evidence the work needs to produce.

The first task is to define the primary-market evidence precisely. Revenue, repeat purchases and sustained use establish different things from a completed research project or an unpaid demonstration. Explain which customer segment has validated the offering and under what commercial conditions.

Then define the secondary market. “International expansion” is too broad to guide a project. A company should identify the buyer type, the problem, the route to purchase and the product changes required. A different geography may also involve a different industry, partner model or service expectation. The esa-match partner search guide focuses on evidence of complementary capability rather than profile visibility alone.

For an environmental analytics company, the first market might buy an annual report while the next expects a recurring software service with integration and support. The underlying data may be similar, but the delivery economics and customer relationship are different. The growth plan should expose those changes.

Separate adaptation from routine sales activity. A project that develops a new service element should explain why the work is needed for the target market and how it will be evaluated. A general desire to attend more conferences does not establish the product or service development case.

Partners should have defined roles. A data provider, distribution partner and customer-domain specialist solve different problems. Identify the contribution required before approaching organisations, and confirm interest before relying on their participation. Optional programme networking does not guarantee that a commercial partnership will materialise.

Build a market-specific cost model. Support effort, local integration, data rights and customer acquisition can change the economics that worked in the first market. A higher potential customer count does not necessarily compensate for a more expensive delivery model.

The project should produce evidence for a go-to-market decision. Define what would justify a larger commercial commitment and what result would lead to revision or withdrawal. This makes the supported activity useful even if the original expansion hypothesis changes.

Keep funding assumptions separate from growth forecasts. ESA's public page describes co-funding subject to the applicable conditions; it does not promise that every applicant will receive the maximum rate or that the target market will purchase the service. Check official tender documents and national requirements before finalising the financing plan. The ESA BIC space connection question concerns the business's connection to space, as well as local incubation conditions.

Explain what carries over from the first market

An expansion proposal should distinguish the assets that transfer to the next market from the work that must be repeated. The existing software, data relationships and delivery experience may provide a valuable foundation. They do not establish that another customer group has the same buying process, service expectations or willingness to pay.

ESA's Growth Projects framework makes prior commercial success central to the route and describes work aimed at secondary markets. The programme's optional partner support is also relevant: access to a market can depend on distributors, data providers or other organisations beyond the developer. An introduction can help investigate that dependency, but the company still needs a commercially workable relationship.

A hypothetical company might already sell a satellite-enabled reporting service to agricultural advisers and want to enter the insurance market. Some data processing could transfer, but an insurer might require a different reporting frequency, documentation standard and integration with internal review processes. The applicant should describe which parts of the existing product remain useful and which assumptions need new evidence.

The first-market results should be presented at a level that supports this comparison. A total number of trial users says little about recurring revenue or delivery cost. The company could instead distinguish paid customers, repeated use, renewal experience and the resources needed to serve an established account. Where figures are commercially sensitive, the submission process and applicable confidentiality arrangements should guide what is shared.

Test whether the second market improves the business

A larger potential customer base does not automatically make expansion attractive. The new segment may require longer sales cycles, more expensive implementation or support responsibilities that the company has not previously carried. The relevant question is whether the additional revenue can support those changes without undermining the existing service.

For illustration, suppose the hypothetical first-market product earns €12,000 per customer annually and requires five staff-days of onboarding. A proposed second-market offer might command a higher price but require thirty days of bespoke integration before use begins. The comparison would need to include the cost of that work, the likely contract duration and whether the integration can be reused. These invented figures illustrate the decision; they are not an ESA benchmark or a forecast for a particular business.

The company should also examine concentration. A second market dominated by a few large customers may create attractive contract values while increasing dependence on individual accounts. Conversely, a fragmented market can reduce concentration but raise the cost of distribution and support. The expansion case should explain why the company's existing capabilities fit the chosen structure.

A pilot should address those commercial uncertainties as well as product performance. Useful evidence could concern the work required to onboard a customer, the clarity of the commercial offer and whether the prospective buyer can use the result within its existing process. A favourable technical demonstration without a plausible purchasing route would leave much of the market-entry question unanswered.

Decide which partner relationship is actually missing

Different partners solve different expansion problems. A distributor may bring established customer relationships. A systems integrator may make the service usable within a larger offering. A data supplier may provide an input without which the company cannot deliver the proposed product. An investor may finance the expansion but contribute none of those operating functions.

A proposal should therefore identify the missing contribution before asking for general access to a network. It should explain what the partner receives, what the company retains and which responsibilities sit with each organisation. A relationship that depends on permanently unpriced support or ambiguous ownership of customer accounts may make expansion harder to sustain.

The negotiation should also consider what happens after the supported activity. Who renews the customer agreement, handles changes and carries the cost of maintaining the integration? If the company plans to enter several countries, it should examine whether the same arrangement can operate in each one or whether local partners require a different division of work.

The strongest expansion case connects existing commercial evidence with a specific new market and a limited set of remaining uncertainties. It does not need to claim that the company can serve every adjacent sector. A well-chosen secondary market is one where the existing product offers a real advantage, the adaptation can be defined and the company can explain how the resulting service will be sold and supported after the project ends.

A credible Growth Project starts with a real commercial base and a specific next-market challenge. The company should be able to show which assumptions are already supported, which remain open and how the proposed work will resolve them. That is the bridge between a successful first market and a repeatable expansion strategy.