Cold outreach to funders on LinkedIn: a practical playbook
Most founders treat a grant application the way they treat a job application: write something polished, submit it into a void, and wait. The ones who consistently get funded treat it more like a sales process. They identify the person on the other side of the queue, build a thin but genuine relationship before the window opens, and arrive at submission with context the application form cannot provide. That asymmetry is what this post is about.
LinkedIn is the most practical place to do this. Programme officers are professionals with public profiles, and a short, well-targeted message from a credible founder is one of the less annoying things in their inbox. Done right, it is not pestering. Done badly, it is memorable in the wrong way.
Who to actually approach
The instinct is often to go as senior as possible. Resist it. A director or VP at a large funder (say, UKRI or the European Innovation Council) is unlikely to be the person who reads your application, attends scoring panels, or can tell you anything useful about programme specifics. They are also less likely to respond to a cold message because their inboxes are genuinely unmanageable.
Programme officers are the right target. They are named on many programme pages (SBRI Healthcare publishes named contacts, as do most Innovate UK competitions). They attend the briefing webinars. They write the guidance documents. They know which eligibility edge cases get waved through and which ones sink applications. They also tend to be more reachable precisely because most applicants never think to contact them directly.
The comms or marketing team is worth knowing about but not worth cold messaging for substantive questions. They handle press and announcements; they will not give you a view on scoring criteria.
If you cannot identify a programme officer by name, look for the briefing event recording. Speakers are often the people who run the programme. The Q&A sections are also useful: the person answering technical questions about eligibility is usually the one you want.
The first message
Short. Specific. Evidence-based. One ask.
Short means under 100 words in the message body. Specific means referencing the programme by its actual name, not "your sustainability funding work". Evidence-based means one sentence that shows you have read the guidance: quote a criterion, mention the stated priority area, or name the outcome the programme is trying to achieve. The ask should be either a 15-minute call or a question they can answer in writing without needing to do any work.
A structure that works:
Hi [Name], I came across the [Programme Name] guidance and noticed it prioritises [specific criterion]. We're working on [one-sentence description] and sit in a grey area around [specific eligibility question]. Would a 15-minute call next week be useful, or can I put the question in writing instead? Happy with either.
That is it. No deck. No company history. No revenue figures. The message signals that you have done the reading and are asking a specific, answerable question. It also gives them a low-friction opt-out (answering in writing) if they do not want a call.
Do not use the connection request note to pitch. Connect first with a neutral note if you need to, then message after they accept.
The follow-up cadence
Two follow-ups. Two weeks apart each. Then stop.
The first follow-up is a single-sentence nudge: "Wanted to make sure this didn't slip through. Happy to put the question in writing instead if that's easier." Nothing else.
The second follow-up, two weeks later, is your last. Keep it brief and gracious: "Following up one final time before the [Programme Name] window closes. Totally understand if the timing isn't right." Then leave it.
Three total touches is the outer limit. Beyond that, you are creating an adverse impression before you have even submitted. Programme officers talk to each other. A reputation for pestering spreads within a funder's team.
If they have not responded after three messages, submit your application and move on. The outreach did not fail; it just did not land. That happens. The goal is not a guaranteed conversation; it is a marginally higher probability of one.
What to ask if they say yes
If you get the call, do not spend it explaining your company. They do not need the pitch. What they can give you that no guidance document contains:
What do applications that get rejected early usually get wrong? This surfaces the threshold issues that the scoring rubric does not explicitly flag. Common answers: the problem statement is not localised to the funder's mandate, the team section is thin, the letters of support are generic.
Are there specific scoring criteria that carry more weight in practice than the guidance implies? Funders often weight criteria in ways that are not obvious from the published percentages. Knowing that "route to market" is a hard filter at SBRI Healthcare, or that Horizon Europe reviewers weight "excellence" more heavily than "impact" in early-stage calls, shapes what you put in Section 2 versus Section 4.
Is there anything in the next call's direction that you can share publicly? Some programme officers will tell you. A surprising number will not, but asking signals you are thinking about the long game rather than just the current round.
What does a strong letter of support look like for this programme? This question is underused and almost always useful. The answer is usually very specific.
Take notes. Send a brief thank-you the same day. Refer to the conversation when you submit: "Following a scoping call with [Name] at [Funder], we have addressed the eligibility question around [X] in Section 3."
What not to do
Do not pitch your company in the opening message. The message is an access request, not a demo.
Do not send the deck unprompted. If they ask to see more before agreeing to a call, send a two-page brief (problem, solution, team, the specific ask), not a 20-slide investor deck with a valuation slide.
Do not ask for "any feedback on our idea". This is too open-ended to be useful and signals that you have not done enough independent work. Specific questions get specific answers. Vague questions get polite deflections.
Do not connect with multiple people at the same funder simultaneously. Pick one contact. If the programme officer does not respond, you can try a different person after the cadence above completes, not during it.
Do not follow up the day after submission to say you submitted. They know. They will see it.
After the application lands
Submit, then go quiet for at least three weeks unless the funder has published an explicit review timeline. During assessment, messages read as pressure.
If the programme has a published timeline and that date passes without communication, a single brief message is fine: "I wanted to check whether there is any update on the [Programme Name] assessment timeline. We submitted on [date]."
If you are rejected, a short note asking for feedback is legitimate and sometimes productive. Frame it as a request for the next round, not a challenge to the outcome: "We'd welcome any steer on where our application fell short so we can address it before the next window." Not all funders will respond. The ones that do are usually telling you something you can actually use.
If you are funded, update them on milestones without being asked. Programme officers manage portfolios over years. A brief quarterly note saying the project is on track costs nothing and builds the relationship that makes the renewal conversation easier.
Use this in Raise Lens
On /funders, each funder profile lists the programmes they run and, where available, named decision-team members surfaced from public sources: that list is a direct shortlist for your outreach, saving the time you would otherwise spend digging through programme pages and webinar recordings.
Before you send the first message, save the funder to your Watchlist. You will get notified when they open a new programme, which gives you a natural, non-awkward reason to follow up even if the initial outreach went cold.
Use /draft to put together a tight pre-application enquiry, then cut it aggressively before you send it. The discipline of drafting in full and then trimming to under 100 words is much easier than trying to write short from scratch.
The relationship you build before an application window opens is not a shortcut around good work. It is an investment in making sure the good work gets read properly. Start with /funders to find the right person, then use the playbook above to reach them.