Why does 'up to 80% ESA co-funding' not equal 80% of a startup's cash needs?

An advertised co-funding percentage is one part of a project financing model. It does not tell a company the full amount of cash it must provide, the timing of payments or whether every planned expense is eligible. Those questions need to be calculated separately.

ESA's current BASS proof-of-concept and pilot table includes rates up to 80% for qualifying smaller businesses, subject to national authorisation. The Growth Projects page also expresses support as a share of eligible costs. The word “up to” and the eligible-cost basis both matter. BASS funding table and Growth Projects funding table The choice between ESA BASS proof of concept and pilot projects similarly depends on the customer evidence the work needs to produce.

Consider a hypothetical project with €200,000 of approved eligible costs and an authorised contribution of 80%. The calculated agency share would be €160,000, leaving €40,000 of those costs to be covered elsewhere. That arithmetic says nothing about additional expenditure outside the approved budget.

If the company also plans €30,000 of unrelated commercial work, its overall spending becomes €230,000. The same €160,000 contribution would cover less than 70% of that broader amount. The example illustrates why a programme percentage should not be applied to the company's entire growth plan.

Cash timing introduces another distinction. The company may incur salary or supplier costs before receiving a payment under the agreement. Even where the eventual contribution covers a large share of eligible costs, the company can need working capital during delivery. The actual payment schedule must come from the contract.

Create three linked views. The project budget identifies eligible activity and cost allocation. The financing plan identifies the sources covering each part. The cash forecast shows when money is paid and received. Keeping these views aligned is more useful than relying on one headline percentage.

For a consortium, check the position of each participant. Different entities may have different funding conditions or contributions. A blended project-level percentage can hide a substantial commitment for one partner. Work allocation and financing should be agreed before the consortium presents a consolidated budget.

Treat public support from another source carefully. The fact that money is available does not establish that it can be used for the same costs under the programme's rules. Record what each source funds and obtain clarification where the combination is uncertain. Do not assume that every remaining share can be filled by another grant.

The company should also test a lower contribution or delayed start. If the project is only viable at the maximum advertised rate, that dependency should be explicit in the internal approval. Management can then decide whether to reduce scope, seek other finance or wait for confirmation.

Calculate the contribution against the right cost base

The percentage in a funding table becomes useful only after the company has identified the costs to which it applies. A business-wide cash forecast can contain costs that sit outside the proposed activity, expenditure incurred at a different time and spending that the applicable documents do not treat as eligible. Applying a headline percentage to the entire forecast would therefore answer the wrong question.

ESA's proof-of-concept and pilot call page presents different baseline rates for the two activity types, with a higher ceiling for qualifying smaller enterprises subject to national authorisation. The page also distinguishes a participant's commercial interest when describing research-organisation contributions. A mixed team should not assume that every organisation receives the same rate or participates on the same basis.

Consider a hypothetical startup planning an activity with €500,000 of approved eligible cost. If the agreed ESA contribution were 80%, that contribution would be €400,000 and the remaining eligible-cost share €100,000. Now suppose the company also expects €70,000 of separate sales, support and unrelated product spending during the same period. The company's funding need would include that expenditure as well. The illustration is arithmetic, not an estimate of a particular applicant's eligibility or an offer of ESA support.

The team should also avoid confusing the total activity cost with the cost of one participating company. If several organisations have different roles and contribution rates, calculate each line under the relevant conditions before reconciling the overall budget. A maximum percentage cannot establish the final contribution without the approved scope and funding decision.

Model the largest temporary cash gap

Even an accurately calculated final contribution does not establish when cash reaches the company. A project can be viable over its full duration while encountering a shortage during an expensive development or customer-evaluation period. The useful management question is the largest temporary gap between cash leaving and confirmed cash arriving.

A monthly schedule should distinguish payroll, external invoices and other payments from the accounting recognition of costs. It should then show only the payment timing supported by the actual agreement or a clearly labelled planning assumption. If the contract has not been negotiated, alternative timing cases are more informative than presenting one assumed schedule as settled.

For example, a hypothetical team might expect to pay €45,000 each month for six months before a major customer evaluation. A delay in the evaluation could extend that spending period even if the eventual eligible-cost percentage remains unchanged. Management needs to understand which costs can be rescheduled, which people must remain available and what additional financing would be necessary. The calculation should not depend on an invented ESA payment schedule.

Customer and partner contributions require their own examination. A commitment to provide staff time may be valuable without supplying cash that can pay the startup's salaries. A promised purchase contingent on a successful evaluation is different from money available to finance that evaluation. Each contribution should retain its form, timing and conditions in the model.

Distinguish project affordability from product economics

A supported activity can be affordable while the resulting service remains commercially unattractive. Once development support ends, the business may still pay for data, hosting, customer acquisition and support. Those continuing costs belong in the product model even when they sit outside the supported activity's budget.

For a hypothetical space-enabled reporting service, a founder could calculate the cost of serving ten customers under ordinary commercial arrangements. The calculation would include recurring data access, staff time spent correcting exceptions and the support promised in the proposed subscription. A price that covers only automated processing would understate the resources needed to deliver the full service.

Growth creates another possibility: revenue rises while cash becomes tighter because new customers require onboarding before their first payment. The company should therefore examine both the contribution margin of an established customer and the cost of adding the next one. A development grant percentage supplies neither measure.

A useful board decision brings these views together without merging them. The approved project budget establishes the supported activity; the cash forecast shows whether the company can carry it; the product model asks whether the resulting business can continue. A high co-funding rate can improve the first two, but management still needs credible answers to all three before committing the company's resources.

The official tables provide a useful starting point, while the current tender documents, national authorisation and contract determine the actual arrangement. A sound decision uses the approved cost basis and realistic payment timing. That makes the supported project manageable without confusing a high contribution rate with a fully financed business plan. The ESA BASS proposal template review identifies the applicable application documents before a team prepares its submission.