The indirect-cost line that kills deeptech grant budgets

I have watched strong deeptech projects lose months because the budget was the weakest part of the application. Not because the numbers were too high, but because the story behind the numbers was missing. Auditors and evaluators do not trust a budget they cannot reconstruct.

The most common failure is personnel. Founders list a percentage of a founder's time without explaining which work packages that time feeds into, or what happens to the project if that founder is pulled back into technical firefighting. A grant budget is a project plan expressed in money. If the plan is unclear, the money looks invented.

Direct costs must map to work packages

Every direct cost needs a home. Equipment belongs to a specific work package and a specific milestone. Materials need a quantity and a unit cost grounded in a quote or a recent purchase. Travel needs a purpose: which partner, which event, which customer visit. When an evaluator can trace each line back to the technical description, the budget becomes credible.

Founders often underestimate consumables and maintenance. A piece of equipment without the budget to run it is a shelf ornament. A pilot without travel money to visit the site is a PowerPoint slide. Build the real cost of doing the work, not the cost of buying the headline item.

Indirect costs are where audits live

Indirect costs, overheads, or flat-rate percentages vary by programme. Some schemes allow a real-cost calculation. Others force a flat rate. The mistake is applying the wrong method or mixing methods within the same budget. Read the call. Then read the financial guidelines. Then ask the national contact point if you are unsure.

If you are using a flat rate, know exactly what it covers and what it does not. If you are claiming real indirect costs, have the accounting system to support it before the first euro is spent. Retrofitting documentation during an audit is expensive and sometimes impossible.

Partner contributions have to be real

Consortium proposals often include in-kind contributions that look generous on paper and evaporate in practice. A university partner offering access to a cleanroom is valuable only if the access is documented, scheduled, and priced at a rate the auditor accepts. A corporate partner offering data is valuable only if the data exists, can be shared legally, and has been priced.

The test is simple: would this contribution still be made if the grant were not approved? If the answer is no, it is probably not a real in-kind contribution. Do not promise things your partners have not signed off on.

Build the budget before you write the narrative

The strongest applications I see are written backwards from a defendable budget. The founders know what they need to spend, why they need to spend it, and when the spending produces a measurable output. The narrative then explains the thinking. Weak applications write the story first and invent numbers to match.

Grant money is patient capital, but the administration is not patient. Build the budget like a project manager, not like a scientist asking for resources. If the budget is clean, the rest of the application is easier to defend.

For companies we work with, the grant application sits alongside the commercial plan. Here is how SLSCRW helps founders align the two.