Application craft
How to explain why your innovation project needs a grant
Show grant assessors why public funding is needed, what would happen without it and how to evidence the difference without weakening your commercial case.
Start with the difference public funding would make
A commercially promising innovation can still have a weak grant application if the applicant cannot explain why public support is necessary. The question is not simply whether you would like help paying for development. It is what the grant would change compared with a credible plan without it. This is often described as additionality. Where a competition asks about the need for public funding, assessors want a reasoned explanation of that difference, supported by evidence rather than a general statement about limited cash.
First, check the competition’s scope, eligibility rules and assessment questions. Some calls ask directly about additionality; others explore it through project impact, value for money or the need for support. Use the wording of the live competition rather than a standard answer copied from another bid. The UK business grant directory of live competitions can help you identify opportunities to investigate. Grants are competitive awards, so meeting eligibility requirements alone does not establish that your project deserves funding.
Write a credible plan for proceeding without the grant
Before drafting the application, ask your founder, technical lead and finance lead to agree what the business would actually do if the grant were unavailable. Would it postpone the research, test fewer technical approaches, pursue a narrower product or prioritise existing customer work? Record the most likely course, not the most dramatic one. Check that it agrees with your budget, investor discussions and delivery commitments. A claim that nothing can proceed is difficult to defend if the same work is already funded and approved.
Write two short project descriptions side by side: the funded version and the version without support. Compare the technical questions investigated, testing undertaken, delivery timing and expected outputs. For example, a sensor developer might otherwise validate its design in one operating environment, while support would enable research into performance across more demanding conditions. That is an illustrative difference, not evidence in itself. You must explain why those additional investigations matter and show that they are not simply routine product expansion.
Explain the funding barrier without undermining viability
Next, identify why the business cannot reasonably finance the proposed research on the same scope and timetable through its available resources. Relevant barriers might include unresolved technical feasibility, an investment decision dependent on experimental results, or benefits that extend beyond what the company can capture commercially. Do not assume that technical risk automatically proves a need for subsidy. Explain the specific uncertainty, how it affects financing decisions and why the proposed grant would enable work that would otherwise be reduced, deferred or abandoned.
Describe the funding options you have genuinely considered and their limitations for this project. Investor correspondence, internal investment decisions or lender discussions can support the explanation where relevant and permitted. Do not claim that private finance is unavailable if you have not investigated it, and do not imply that borrowing must always be attempted before applying. Requirements vary. GrantUp’s guide to writing a grant application provides a broader framework for connecting this explanation with the rest of your bid.
Turn the argument into evidence assessors can follow
Create a working table with four columns: the claim, the supporting evidence, its source and where the application uses it. If you say the grant would bring forward testing, point to the resource assumptions and delivery dependencies behind that statement. If you say it enables a broader technical investigation, identify the experiments and uncertainties involved. Keep evidence proportionate: assessors need to understand the reasoning, not navigate a document dump. Only submit attachments allowed by the competition, and put essential explanations in the scored answers.
Then trace each proposed change through to a meaningful outcome. Additional testing may produce evidence needed for a customer trial; investigating a difficult operating condition may unlock a use case that the narrower project cannot address. Separate immediate project outputs from later commercial or wider benefits, and explain the dependencies between them. Avoid unsupported claims about jobs, exports or environmental savings. Where you include forecasts, show their assumptions and distinguish what you expect from what customer discussions or technical results already demonstrate.
Check for contradictions and weak public value
Read your funding explanation alongside the commercial case, budget and project plan. Common contradictions include saying the project cannot proceed without support while describing the same work as an unconditional customer commitment, or claiming faster delivery without showing additional delivery capacity. Another mistake is presenting the grant solely as a way to protect shareholder cash. Commercial benefits are legitimate, but the answer should also explain why the proposed use of public money meets the competition’s objectives and represents value for money.
Challenge every sentence that could appear in any applicant’s bid. Replace “the grant will accelerate innovation” with the specific activity enabled, its consequence and the evidence behind it. Ask a colleague unfamiliar with the project to explain back what changes if funding is awarded. If they cannot, simplify the argument. Also check that your preferred answer does not depend on costs or activities the competition excludes. An initial grant eligibility check can help identify questions to resolve before committing further writing time.
Where to go next
Bring the argument together in a short sequence: what you propose to investigate, what you would do without support, the barrier to funding the fuller project, the difference the grant enables and the resulting benefits. Keep the detail consistent with the competition’s word limits and questions. Have the technical lead verify the research differences and the finance lead verify the funding assumptions. Retain the underlying evidence so that your team can substantiate the account during any clarification or due diligence process.
If you want to test this reasoning before building a full application, book a 15-minute grant scope and eligibility assessment with GrantUp. Bring a short project summary, your intended technical work, an outline budget and an honest description of what happens without funding. The discussion can help identify eligibility questions, gaps in the public funding argument and the information needed to decide whether an application is worth pursuing. The aim is a defensible case, not a stronger-sounding version of an unsupported claim.
Ready to turn this into a funded proposal?
Book a free 30-minute consultation with a senior grant consultant. We will check your eligibility, match you to the right program, and map out your submission timeline.
Learn more about our approach