How to Write an MDF Proposal That Gets Approved

Why the proposal matters more than you think

An MDF proposal is not paperwork — it is the moment a partner turns available funds into approved funds, and the quality of the proposal decides whether that happens quickly, slowly, or not at all. A vague request creates friction, delays, and often a rejection. A specific, well-structured one gets approved fast, builds credibility for the next request, and — because it already contains the plan and the measurement — makes the eventual claim far easier.

This guide sets out the structure of a proposal that gets approved, whether you are a partner writing one or a vendor deciding what to ask for. It pairs with our pillar guide on how to run an MDF programme, where the approval workflow is one of the five decisions that make or break a programme.

The proposal structure (a request template)

Most vendors provide their own MDF request form, and you should always use it. But the underlying structure is consistent across programmes, and following it — even when the form is minimal — is what separates an approvable proposal from a declined one. A complete MDF proposal covers six things:

1. Objective — the business outcome the activity serves.
2. Audience — exactly who you are targeting.
3. Activity plan — what you will do, and when.
4. Budget — the cost, broken down.
5. Expected pipeline — the outcome you expect to generate.
6. Measurement plan — how you will track and evidence results.

Think of these six headings as the request template. The sections below explain what each should contain and where partners most often fall short.

Objective and audience

Objective.Open by tying the activity to a business outcome the vendor cares about — ideally the one the programme is funding this cycle. “Generate new-business pipeline for [product] in the mid-market” is an objective; “run some marketing” is not. If the vendor has published a priority (a launch, a vertical, a market), align your objective to it explicitly. Approvers fund proposals that advance their goals, not generic activity.

Audience.Name the audience precisely: industry, company size, role, geography, and — for account-based activity — the actual account list. A specific audience signals a real plan and makes the expected outcome credible. “IT decision-makers at UK manufacturers with 250–1,000 employees” earns trust; “prospective customers” does not.

Activity plan and budget

Activity plan. Describe what you will actually do and when. Specify the channels and tactics — a webinar, a paid-social campaign, a telemarketing sprint — the key dates, and how the pieces fit together. Make sure every element is eligible under the programme rules; a proposal built on ineligible activity is dead on arrival (our guide to MDF-eligible activities is the reference to check against). Where you can, sequence the activity into a simple campaign rather than a one-off — vendors favour plans with a coherent path from awareness to lead.

Budget. Break the cost down by line item — media, agency fees, platform, content — rather than presenting a single lump sum. A transparent breakdown is easier to approve, easier to claim against later, and demonstrates you have actually costed the plan. Note any co-investment you are making yourself; partner skin in the game strengthens a request.

Expected pipeline and measurement

Expected pipeline. State the outcome you expect — number of leads, meetings, or pipeline value — and show your working. You are not committing to a guaranteed result; you are demonstrating that the activity is sized to produce a return worth the funding. Reasonable, explained estimates beat either silence or wildly optimistic numbers.

Measurement plan. This is the section partners most often omit, and the one that increasingly makes the difference. Describe how you will track results: the campaign identifier or tag you will apply, how leads will be captured against it, and how you will report outcomes back. A proposal that explains how it will be measured is far easier to approve — and, crucially, it pre-builds the evidence you will need at claim time. The method is set out in how to measure MDF ROI, and the MDF Intelligence Platform makes the tagging and attribution automatic.

A short worked example

To see the difference specificity makes, compare two versions of the same request. The weak version: “We'd like £8,000 of MDF to raise awareness of [product] and generate some leads through digital marketing this quarter.” There is no audience, no measurable outcome, no plan, and nothing to claim against later — an approver has no basis to say yes.

The strong version says the same thing with substance: “Objective: generate new-business pipeline for [product] among IT directors at UK financial-services firms of 500–2,000 staff. Activity: a four-week LinkedIn and paid-search campaign driving to a co-branded landing page and a live webinar on [topic], running weeks three to six of the quarter. Budget: £8,000 — £5,000 media, £2,000 webinar production, £1,000 content, with £4,000 partner co-investment. Expected outcome: around 60 registrations, 25 attendees, and 8–10 qualified opportunities. Measurement: all traffic tagged to a single campaign code, leads captured in our CRM against that code and reported back monthly.” Same budget, same idea — but the second is approvable on sight and effectively writes its own claim.

Common rejection reasons

Most rejections trace back to a short list of avoidable errors:

• Vagueness — no specific audience, no measurable outcome, no clear plan.
• Ineligible activity — costs that fall outside the programme rules.
• Objective mismatch — activity that doesn't serve the vendor's stated priority.
• No measurement — no way to tell whether the funds worked.
• Unexplained budget — a lump sum with no breakdown or rationale.
• Late submission — proposed after the activity window makes execution impossible.

Notice that most of these are about specificity, not ambition. Approvers rarely reject a modest, well-defined plan; they reject requests they can't evaluate.

After approval: set yourself up to claim

A proposal isn't finished when it's approved — it's the blueprint for the claim. Because a good proposal already names the activity, the audience, the budget, and the measurement, executing against it and then claiming becomes straightforward: you evidence what you said you would do. Keep proof of execution as you go rather than reconstructing it later, and you avoid the reimbursement delays covered in MDF claims and proof of execution.

One more discipline separates partners who get funded repeatedly: they submit early. A proposal that lands well before the activity window opens gives the approver room to come back with questions rather than a flat rejection, leaves time to adjust the plan, and makes execution comfortable rather than rushed. Proposals filed at the last minute force a hurried yes-or-no and often miss the window entirely — one of the most avoidable routes to unspent MDF.

If you are a vendor and your partners struggle to write fundable proposals, that is usually a sign the process or the enablement needs work — and it is a major cause of unspent MDF. Fixing both the proposal experience and the measurement behind it is the heart of our MDF programme optimisation service.