Market development funds for SaaS tech partnerships

Market development funds sound like something a cloud giant runs: a pool of money a partner can draw on to generate demand, with a portal, a claim form, and a team that approves banners. That is the version you meet in large channel partner programs. It is not the version a 20-person SaaS company should copy. For a small technology partnership, MDF is a small, named budget for a specific joint action, with proof that the money was spent on that action.

Used well, MDF buys a webinar, a joint landing page, or a field event neither side would run alone. Used badly, it becomes a vague marketing subsidy or a second discount on top of rev-share. This post defines MDF for SaaS tech partnerships, when a small company should offer it or ask for it, simple rules, and proof of spend. It sits next to the SaaS co-marketing playbook and partner incentives. MDF is neither of those. It is the budget line that funds a specific piece of joint demand.

The 60-second version

If you only read one section, read this one:

• MDF is a named budget for a named joint action, not a second discount and not a marketing retainer.
• A small company should rarely offer an open MDF pool. Fund one campaign at a time, with a cap, an owner, and a date.
• Request MDF only with a plan. Audience, action, cost, expected pipeline, and how you will prove spend. A blank ask gets a blank no.
• Pay on proof, not on promise. Invoice, screenshot, registration list, or placement confirmation. No artifact, no reimbursement.
• Keep MDF separate from rev-share and referral fees. Mixing them is how nobody can say what the partnership costs.
• Measure pipeline, not vanity. Registrations and sourced opportunities beat impressions you cannot audit.
• If you cannot operate the claim process, do not offer MDF. A messy fund trains partners that you do not mean the rest of the program either.

What MDF is, and what it is not

Market development funds are money one company sets aside so a partner can create demand for the joint offering. In large programs, the partner earns a pool (often as a percentage of trailing revenue) and draws it down against approved activities. Microsoft Partner Center documents this kind of program machinery in public; see Partner Center for how a scaled vendor thinks about partner operations. Amazon Web Services describes a similar partner-program shape at AWS Partners. You are not those companies. You do not need their portals.

For a SaaS tech partnership between peers, or between a startup and a larger platform, MDF usually means a campaign fund (reimburse a named webinar or event against receipts), a small co-op slice of last quarter's partner-sourced revenue, or a one-time launch budget for a new integration.

What MDF is not:

• A discount on the product. That is price.
• A referral fee or revenue share. That is partner incentives for selling, not for marketing.
• A retainer for the partner's marketing team. If you want to hire them, hire them.
• A way to buy a logo on a slide.

If the activity would not exist without the fund, and a customer could see it, you are in MDF territory. If the partner would sell you anyway, you are negotiating margin, not marketing.

When a small company should offer it

Offer MDF when three things are true: you can name the action, you can cap the spend, and you can review proof in under an hour. If any of those is false, do not offer a fund. Offer to split a specific invoice instead, or run the campaign yourself and invite the partner.

Good reasons to offer:

• A launch. The integration is live, you both have an audience, and a joint webinar or listing push will put the joint value proposition in front of buyers who already use one of the products.
• A field event where the partner's sellers will be in the room, and a small sponsorship gets you on the agenda rather than on a table of flyers.
• A partner who has already sourced pipeline, and you want them to repeat a motion that worked. Fund the second run of a campaign that produced meetings, not the first run of a theory.

Bad reasons to offer:

• They asked, and you wanted to sound serious.
• You are trying to win the partnership against a competitor by throwing budget. That is a bidding war, and you will lose to someone with a real pool.
• You hope MDF will make an inactive partner active. Money does not fix a missing motion. Enablement and a live integration do; see partner enablement.

Cap every offer. A useful starting shape (hypothetical, so you can do the arithmetic): a few thousand dollars against a named webinar, paid on the registration list plus the invoice from the webinar tool or venue. If the campaign works, you can fund the next one. If it does not, you lost a small, bounded amount and you learned.

Do not attach MDF to a partner who has not completed partner onboarding. Funding demand for a partner whose reps cannot tell the story is how you pay for confusion.

When a small company should request it

Larger platforms sometimes have MDF, co-op, or launch funds for ISVs and technology partners. Requesting them is reasonable. Requesting them with a blank email is a waste of both calendars.

A request that gets read has:

• The action (webinar, event, listing ads, regional meetup).
• The audience (who, how many, why they match both ICPs).
• The cost, itemized.
• What you are putting in (list, speakers, landing page, follow-up).
• The pipeline you will tag, and how.
• The proof you will file (invoice, screenshot, registration CSV, UTM report).
• A date, after which the ask expires.

You are not entitled to MDF because you listed an app. You are proposing a small investment with a return they can see. If the platform's program requires a portal claim, use the portal. Do not invent a side process.

Be honest about scale. A startup asking a hyperscaler for a six-figure fund for an unproven listing will be ignored. A startup asking for a few thousand against a dated campaign with a named field sponsor has a chance. Read the program's own rules first; Partner Center and AWS Partners are examples of how public those rules can be.

If there is no program, you can still ask a partner manager for a split on a specific invoice. That is often faster than waiting for a fund to exist.

Simple rules, and proof of spend

Five rules keep MDF from turning into a second set of books.

Rule 1: one action, one cap, one owner. Name the person who approves, on your side. Name the person who runs it, on theirs (or yours).

Rule 2: pre-approve the activity, reimburse the proof. Do not pay a pool up front to a partner you have not run a campaign with. Exception: a platform's standard program that pays on their terms, which you either join or skip.

Rule 3: eligible costs are external and receipted. Media, venue, tools, design from a named vendor. Not their internal salaries, not "estimated time," not a round number.

Rule 4: keep MDF off the commercial exhibit for rev-share. Put it in a short MDF addendum or a campaign brief. Mixing funds with the share schedule is how finance loses the plot and how you accidentally discount twice.

Rule 5: tag the pipeline. Every campaign gets a UTM, a campaign ID in the CRM, and a "partner MDF" source. If you cannot tag it, you cannot learn.

Proof of spend is a small packet, filed before money moves:

Review proof in the partner QBR for any fund that repeats. A campaign that cannot show meetings should not get a second check. A campaign that can should get a larger cap, still against proof.

Finance will ask two questions: did we get what we paid for, and is this a discount in disguise. The packet above answers both. If you cannot produce it, do not run MDF.

Common mistakes, and the fix

Offering an open pool with no claim process. The fix: one campaign, one cap, pay on receipts. Add a pool when you have a person whose job includes approving claims.

Using MDF as a second discount to win the partner. The fix: negotiate the commercial model on its own. MDF buys a visible action, not a better mood.

Paying on a slide that says the event went well. The fix: invoice, plus a registration list or a dated placement screenshot. No artifact, no reimbursement.

Requesting platform MDF with no plan. The fix: audience, action, cost, pipeline tag, proof, date. That email is the whole skill.

Skipping the CRM tag because "we will know." The fix: you will not know in 90 days. Campaign ID on every opportunity, or the fund has no learning.

FAQ

How much MDF should a startup budget? As little as funds one real action you can staff. Increase only after a campaign produces tagged pipeline.

Is MDF taxable, a COGS item, or marketing spend? Treat it as marketing unless your finance team says otherwise, and keep it out of the rev-share true-up. This is not tax advice. Do not bury it inside margin.

Can MDF pay the partner's sales spiffs? No. Spiffs are partner incentives. MDF pays for demand the market can see. Mixing them hides both.

What if the partner wants the cash and will "figure out the campaign later"? That is a discount request. Decline, or convert it to a split on a named invoice with a date.

Should MDF sit in the partnership agreement? A short addendum that says funds are discretionary, capped, and paid on proof is enough. Do not promise an annual pool you have not budgeted.

Do we need a portal? Not until claim volume hurts. A shared folder of briefs, invoices, and registration lists is a program.

What activities are a poor use of MDF? Swag with no event, generic brand ads with no joint offer, and content nobody will promote. Fund actions with a list, a date, and a follow-up owner.

When should we stop offering MDF to a partner? When two funded actions produce no tagged opportunities, when proof is late or fictional, or when the partner is inactive in every other motion. Stop in writing, at the QBR.

Further reading

• Channel partners: where MDF comes from as a channel tool, before you copy a giant's pool.
• Microsoft Partner Center: an example of scaled partner operations, including how large vendors think about programs and funds.
• AWS Partners: another public example of a large technology partner program, useful as a contrast to a one-campaign fund.

The short version

MDF is a named budget for a named joint action, paid on proof. A small SaaS team should fund one campaign at a time, cap it, tag the pipeline, and keep the money off the rev-share schedule. Offer it to partners who already have a motion. Request it with a plan, not a hope.

If you cannot review a receipt and a registration list, you cannot operate MDF. Split a specific invoice instead, or run the campaign yourself. Proof of spend is how finance stays on your side and how partners learn that the fund is real.

If you want help deciding whether MDF belongs in your partner motion at all, that is exactly what a Partner Audit is for.