MDF explained

Market development funds

MDF, explained. Spent properly. Proven properly.

Market development funds are one of the most useful budgets in the technology channel, and one of the most wasted. This is how MDF actually works, the rules that trip people up, and how vendors, distributors and resellers get real return from it.

The basics

What MDF is. And what it isn’t.

Market development funds are money a technology vendor sets aside for its channel partners to spend on marketing and demand generation. The goal is simple. Help partners create pipeline for the vendor’s products that they couldn’t fund on their own.

MDF is usually discretionary. The vendor, or the distributor acting for it, decides who gets funds, how much and for what. Partners normally have to propose an activity, get it approved before they spend, run it, and then prove it happened before they are paid back.

It is not a discount, a rebate or free money. It is an investment the vendor expects to see a return on, and every rand is tied to an approved plan.

MDF and co-op are not the same thing. Most people use the terms interchangeably.

MDF

  • Allocated at the vendor’s discretion, often per quarter or per campaign
  • Tied to specific activities that must be approved up front
  • Usually aimed at new pipeline, new markets or a product launch
  • Paid out once proof of execution is accepted

Co-op funds

  • Earned by the partner, usually as a percentage of past sales
  • Builds up in an accrual the partner can draw on
  • Often more flexible in what it can be used for
  • Still claimed against proof, and still expires if unused
How it works

The MDF cycle. Six steps, every time.

  1. 01

    Allocation

    The vendor sets a budget for the period and decides which partners, regions or campaigns receive it. In South Africa this often flows through a distributor.

  2. 02

    Proposal

    The partner submits a plan: the activity, the audience, the cost, the expected outcome and the dates.

  3. 03

    Pre-approval

    The vendor or distributor approves the activity before any money is spent. Spend without approval is almost never reimbursed.

  4. 04

    Execution

    The activity runs as approved. Changes in date, format or cost usually need to be approved again.

  5. 05

    Proof of execution

    The partner submits evidence that the activity happened and what it produced, within a fixed window.

  6. 06

    Claim and payment

    Once the proof is accepted, the claim is paid, usually as a credit note or a payment against invoice.

The rules

The rules that apply almost everywhere. Programmes differ. These don’t.

1

Get approval first

If it wasn’t approved before it ran, assume it won’t be paid.

2

Use it or lose it

MDF is tied to a period. Unspent funds don’t roll over, and the next allocation is often smaller.

3

Claim windows are short

Proof of execution is typically due within 30 to 60 days of the activity. Miss the window and the claim can be rejected.

4

Brand the vendor properly

Logos, messaging and product focus must follow the vendor’s guidelines. Competitor products usually can’t feature.

5

Spend on demand, not overheads

Salaries, general running costs and internal events rarely qualify. Activity aimed at customers does.

6

Report outcomes, not just activity

Attendance and impressions get a claim paid. Pipeline and revenue get next quarter’s budget approved.

What qualifies

What usually qualifies. And what usually doesn’t.

✓Do

  • Customer events, roundtables, breakfasts and webinars
  • Targeted digital campaigns and account-based marketing
  • Thought leadership and content aimed at buyers
  • Lead generation and appointment setting
  • Trade media and sponsored editorial
  • Sales and technical enablement tied to a campaign

✕Don’t

  • Staff salaries and general overheads
  • Gifts or incentives with no business purpose
  • Activity that promotes competing products
  • Internal team events
  • Anything that ran before it was approved
  • Spend without invoices and proof
Where it goes wrong

Why MDF claims fail. It’s rarely the idea.

Late or missing proof

The activity ran, but nobody collected the evidence in time.

Scope drift

The date, format or cost changed and nobody went back for approval.

Weak evidence

Photos and a guest list, but no attendee data, no leads and no outcomes.

Wrong branding

Vendor logos missing, outdated or used incorrectly.

No link to pipeline

The activity happened, but nothing shows what it did for sales.

Last-minute spend

Funds approved months ago, rushed into anything that can run before the deadline.

Where we come in

Turn MDF into pipeline. And prove it.

Publishared plans and runs MDF-funded activity for vendors, distributors and resellers across South Africa. We work with the country’s IT distributors every week, so we know what gets approved and what gets paid.

We handle the room, the audience and the reporting. That includes senior decision-makers from TechCentral’s audience, and proof of execution that stands up to a vendor audit.

Questions

MDF questions. Answered.

What does MDF stand for?

Market development funds. It is a budget technology vendors give their channel partners to spend on marketing and demand generation for the vendor’s products.

Who controls MDF in South Africa?

The vendor owns the budget. In many programmes a distributor manages allocation, approvals and claims for its reseller base.

Can MDF pay for events?

Yes. Customer events, roundtables, breakfasts and webinars are among the most common MDF activities, as long as they are approved up front and aimed at the right audience.

What is proof of execution?

The evidence that an approved activity ran as agreed. It usually includes invoices, attendee or lead data, photos or screenshots, and a short results report.

What happens to unspent MDF?

In most programmes it is lost at the end of the period. Consistent underspending can also shrink future allocations.

How do you measure MDF ROI?

Track the pipeline and revenue created by the activity, not just attendance or clicks. Agree the measures before the activity runs so they can be reported on afterwards.