A grant strategy built on project need, funding options and affordability

A small business grant strategy needs five decisions: what project matters, which funding routes are viable, what evidence supports the application, how the company will deliver and when it should walk away.

What to take away

• A grant strategy needs five decisions covering project need, funding options, evidence, delivery and when to walk away.
• Compare a possible grant with business as usual, a smaller project and at least one commercial route.
• Map every material claim to a record and change the narrative if evidence contradicts it.
• Test affordability including ineligible cost, application time, reporting cost and the period before payment.
• Use gates with named decision makers rather than an average score that hides one decisive failure.

1. Define the project

Write the problem, baseline, intended outcome, delivery period and minimum viable scope. Keep the purchase separate from the outcome. Equipment, software or training may enable change, but none proves that the change will happen.

Use current management information where possible. Label estimates and explain missing data.

2. Generate funding options

Compare grant support with business as usual, a smaller project and at least one commercial route. The Business.gov.uk funding guide sets out broad features of grants, loans, equity and self-funding.

For each option, record cash timing, ownership effects, obligations, decision time and the downside if the project underperforms. Do not compare a possible grant with a loan as though both were certain and available on the same date.

3. Set a grant search specification

List the applicant structure, English location, sector, business size, project activity, dates, costs and available contribution. Search the government finance and support finder, then validate every opportunity on the funder's own page.

Use a pass, question or fail status for each critical condition. A "question" requires written clarification or further evidence before the application proceeds.

4. Build an evidence file

Map every material claim to a record. The file may contain accounts, forecasts, quotations, research, technical work, ownership details and prior-funding declarations. Give each item an owner and version date.

If evidence contradicts the proposed narrative, change the narrative. Do not remove inconvenient figures or present a forecast as an observed result.

5. Test affordability

Calculate eligible cost, grant contribution, business contribution, ineligible cost, application time, reporting cost and the period before payment. Add a downside case for lower funding, delay or cost increase.

Business.gov.uk's application preparation guidance describes the role of business plans and cash-flow forecasts. Use the company's actual payment terms and tax treatment.

6. Plan delivery and control

Set milestones, owners, supplier decisions, approval points, evidence requirements and claim dates. The plan should say who may approve a variation and when the funder must be consulted.

Create the project record before spending begins. Keep quotes, purchase approvals, contracts, invoices, payment records and proof of delivery together.

7. Apply a stop rule

Stop or pause when the project has no clear business case, a critical rule fails, match funding is unsafe, the timetable is unrealistic or the application would require an unsupported statement. Record the reason.

Use gates, not an average score

Review the project at discovery, shortlist, submission, award and first-spend stages. Each gate should have a named decision maker and a small number of conditions. A high total score must not hide one decisive failure such as an excluded location or an unaffordable cash requirement.

Classify assumptions by how much damage they could cause. A minor estimate can be updated during planning. A critical assumption, such as permission to start work before an offer, needs written confirmation before the business acts.

Review after the decision

If the application succeeds, compare the offer with the submitted scope and budget. Conditions may change the commercial case. If it fails, record any feedback, then reassess the project independently of the grant. Do not resubmit automatically or rewrite facts merely to fit another call.

Give the framework an owner and review date. A dormant opportunity list filled with expired schemes is not a strategy.

The framework is successful when it improves the funding decision, including a decision not to apply. It does not predict or guarantee an award. This draft has no live internal links and remains on editorial hold.

Before you act

• Define the problem, baseline, outcome, delivery period and minimum viable scope.
• Record cash timing, ownership effects and obligations for each funding option.
• Validate every opportunity on the funder's own page.
• Map every material claim to a record with an owner and version date.
• Calculate eligible cost, grant contribution and business contribution.
• Apply the stop rule when a critical condition fails.

Common questions

How should a business compare grant support with other funding routes?

Compare grant support with business as usual, a smaller project and at least one commercial route. For each option, record cash timing, ownership effects, obligations, decision time and the downside if the project underperforms. Do not treat a possible grant and a loan as equally certain and available on the same date.

What should happen if evidence contradicts the proposed narrative?

Change the narrative. Do not remove inconvenient figures or present a forecast as an observed result. The evidence file may contain accounts, forecasts, quotations, research, technical work, ownership details and prior-funding declarations, and each item needs an owner and version date.

When should a business stop or pause a grant application?

Stop or pause when the project has no clear business case, a critical rule fails, match funding is unsafe, the timetable is unrealistic or the application would need an unsupported statement. Record the reason. Review the project at discovery, shortlist, submission, award and first-spend stages, each with a named decision maker.