Funding

Grant Writing for Business

Prepare business grant applications with a funder logic, not only a company narrative.

Why this matters now

Grants are an undervalued line of capital for companies. They sit between equity and debt, do not dilute the cap table, and — used well — fund exactly the parts of the roadmap that are hardest to defend to investors: regional expansion, dual-use R&D, sustainability transition, market access. We write applications for companies that already have a real product, real customers, and real management — and that need the capital and the credibility a structured grant brings.

What this includes

Programme fit

Reverse-engineering the call: scoring criteria, evaluator profile, recent winners, the actual decision logic — before any writing begins.

Storyline and theory of change

One coherent narrative across the application, the budget, the work packages, and the impact logic. No two pages contradict.

Budget and partner architecture

A budget that survives audit, partners with the right complementarity, and a delivery plan that matches what the team can really run.

Submission and follow-through

Document hygiene, last-mile compliance, and the clarification questions you should answer before the evaluator sends them.

What you receive

Pre-decision memo

Two to four pages: do we apply, with what story, against which evaluator profile — written before any writing begins.

Application file

Application form, technical annex, work packages, budget, partner letters, CVs in funder format, all internally consistent.

Evaluator-side QA

A simulated scoring pass on our own draft against the call's criteria, with the weakest sections rewritten before submission.

Pipeline plan

If a window closes, where the same story should go next — programme, deadline, partner gap to close.

How we work

Triage

One week. Shortlisting calls, selecting one or two with a real chance, deciding what we will *not* apply to.

Architecture

Two weeks. Theory of change, work packages, partner map, budget skeleton, internal go/no-go.

Drafting

Three to five weeks. Iterative drafting with the technical lead, finance, and partners — under one editor.

Submission and follow-through

One week before deadline plus post-submission. Compliance check, submission, and the file ready for ethical clarifications and audit.

Indicators of success

Win rate

Selective application list with documented scoring logic — and a higher win rate than open-call averages.

Capital secured

Non-dilutive capital that funds the part of the roadmap which is hardest to defend to equity investors.

Reputation upgrade

Grants are evaluator-validated. A win is a third-party signal that strengthens the next bank, equity, or customer conversation.

Internal capability

Your team finishes the engagement with a written method, not a folder of files.

Common questions

How long before we know if it is worth applying?

Within ten working days. The pre-decision memo is binary — apply with a serious shot, or don't, and here is where the same story should go instead.

Who actually does the writing?

A senior writer with sector knowledge, supported by a budget lead, a compliance reviewer, and the editor — your team contributes the technical content.

What do we keep after the engagement?

The application file, the evaluator-style QA report, and the written method — so the next application is faster and built on the same architecture.

Discuss the next step

Describe the task, deadline and context. We will suggest the first practical route.