Grant strategy
AI charging optimisation: build a grant case before scaling
A GrantUp client needed to prove AI-driven charging and routing optimisation before scaling. Learn how to turn that funding need into a focused grant case.
The client lesson: fund the proof before the scale-up
A lean team developing AI-driven charging and routing optimisation needed early non-dilutive capital to prove its approach before scaling. That is the central fact in this GrantUp client result. It gives other applicants a useful starting point: the immediate funding case was about establishing whether the technology worked, rather than financing every part of a growing business. The distinction matters because it creates a specific question for a grant-funded project to answer.
The supplied result does not identify the award, funding amount, assessment feedback or experiments undertaken. We cannot reconstruct a winning application from those details alone. What we can draw out is the transferable logic of the case: a small team, an unproven technical proposition and a need for evidence before expansion. The recommendations below explain how another applicant could build around that logic, rather than claiming to describe this client's submitted proposal.
Define what must be proved, not just what will be built
Charging and routing optimisation describes an area of work, but it does not yet define a research project. An applicant needs to explain what remains uncertain and why resolving it matters. For a comparable project, questions might concern performance when charging availability changes, the interaction between route choices and energy requirements, or whether an approach works beyond its initial test conditions. These are illustrative questions, not reported features of the client's technology.
The practical lesson is to replace a broad ambition, such as building an AI platform, with a bounded proposition that can be tested. State what the approach is expected to achieve, what evidence would support that expectation and what result would challenge it. Our guide to writing a grant application can help structure that explanation. Keep the technical uncertainty visible throughout, rather than letting a list of product features become the project rationale.
Make the next funding step proportionate to the evidence gap
The phrase 'before scaling' is important. It separates the decision the team needed to make next from its longer-term commercial ambition. For other applicants, that means asking which uncertainty must be reduced before committing to wider deployment. A focused proof project should produce evidence that changes a decision. It should not simply bring forward routine development work or absorb operating costs that have little connection to the technical question being investigated.
Competition selection should follow that project definition, rather than reshape the business around an available award. Use the UK business grant directory of live competitions to identify options, then check their published scope, applicant requirements and eligible activities. Grants are competitive awards, so eligibility alone does not establish a strong case. A relevant opportunity must also give the team enough room to carry out meaningful testing without expanding the project beyond what it can deliver.
Show how a lean team will generate credible evidence
A lean team needs a delivery argument that reflects its capacity. The supplied client result does not tell us its staffing, partners or facilities, so none should be assumed. For a comparable application, explain who will design the tests, prepare the inputs, run the work and interpret the results. Where specialist capability is missing, identify how it will be obtained. Naming responsibilities is more useful than describing the team as experienced without connecting that experience to delivery.
Evidence also needs a credible comparison. Depending on the proposed research, an applicant might compare its approach with an existing method under defined conditions, then examine where performance improves or deteriorates. Those choices must follow the actual technical question. Agree the evaluation method before writing claims about impact, and explain any limits in the available data or testing environment. A proposal becomes easier to assess when the reader can distinguish intended performance from performance already demonstrated.
Connect technical proof to a commercial decision
The client needed to prove its approach before scaling, which makes the link between research and commercial action central to the lesson. Other applicants should explain what successful proof would enable them to decide next. That might be whether to pursue a wider trial, refine the target use case or invest in further development. These are possible decision points, not outcomes reported for this client. The application should identify the decision relevant to its own business.
Keep the forecast separate from the evidence. A technical result can support a commercial plan without proving customer demand, deployment readiness or future revenue. Explain which assumptions the funded work will test and which will remain afterwards. When reviewing client case studies and funded projects, look for that connection between the immediate research question and the next business step. Borrow the structure of the reasoning, not another company's claims or anticipated results.
Where to go next
Start with a short project brief that identifies the technical proposition, the evidence gap, the proposed tests and the decision the results will support. Add the people and resources needed to complete that work, together with any constraints that could affect delivery. This is a more useful starting point than a polished pitch deck alone. It helps expose whether you have a defined research project or a collection of development activities still needing a clearer purpose.
If you are seeking funding to prove a technology before scaling, book a 15-minute grant scope and eligibility assessment with GrantUp. Bring your project brief and distinguish what you already know from what still needs testing. The discussion can help clarify the proposed scope and the eligibility questions to check against relevant competitions. The lesson from this client result is practical: make the next proof step clear before asking a funder to support the wider ambition.
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