How to write a market development funds (MDF) request template

Before you write a single form field, decide the campaign types the template will accept. A loose template that lets partners write anything in a free text box produces a backlog of one off requests that cannot be benchmarked against each other and cannot be reviewed in bulk at quarter end. A tight template picks six to ten campaign types, defines each in one line, and forces every request to pick exactly one. Standard categories for B2B SaaS MDF are webinar or virtual event, in person event or dinner, trade show booth or sponsorship, paid digital campaign (search, social, programmatic), content asset (co-authored report, case study, guide), direct mail or ABM gift, telemarketing or outbound SDR sprint, and training or enablement event. Each type gets a named owner on your side (demand gen owns paid, field marketing owns events, content owns assets) so routing is automatic. Resist the pull to invent a 'custom' bucket; it becomes the dumping ground for everything the partner did not want to think about, and partner marketing ends up triaging it anyway.

• Pick six to ten campaign types that cover 90 percent of partner requests and write a one line scope for each
• Assign a named owner on your side per campaign type (demand gen, field marketing, content, enablement) so routing is automatic
• Build a minimum spend and maximum spend band per campaign type so partners self select realistic requests
• Publish the taxonomy inside the partner portal with one example request per type so partners see what good looks like

Co-branding is where MDF requests quietly fail audit, because the partner spent the money, ran the campaign, and used a stale logo or an off brand color palette, and partner marketing cannot cleanly tie the asset back to the brand standard. Build a co-branding plan section into the template that forces the partner to describe how both logos will appear, which lockup they will use, which approved assets they will draw from, and which creative they will submit for review before launch. Require a draft creative upload for anything above the auto approval threshold, so partner marketing can approve the creative in the same review as the budget. Standard practice at the enterprise end of the market is a 48 to 72 hour creative review service level agreement on anything in the manager approval tier and above, and partner programs that publish that service level agreement see MDF utilization rise because partners stop sandbagging requests they expect to drag. Forrester channel research is consistent on this: the number one reason partners stop submitting MDF requests is not denial, it is unpredictable turnaround.

• Require a one paragraph co-branding plan: which logos appear, which lockup, which color palette, which voice
• Require a creative draft upload for any request above the auto approval threshold, reviewed on a named service level agreement (48 to 72 hours is standard)
• Link the brand kit, logo lockup gallery, and approved asset library directly from the form so partners do not have to hunt
• Flag any request that proposes partner only branding with no co-brand element, and route it to a stricter review path

An MDF request without target metrics is a budget transfer, not a marketing investment. Build a target metrics section that forces the partner to commit, in writing, to the pipeline sourced and the deals they expect the campaign to produce. The two numbers that matter are pipeline sourced (dollar value of opportunities created and attributed to the campaign inside a defined window, typically 90 days post campaign) and deals closed (number and dollar value of deals won inside a defined window, typically 180 days post campaign). A webinar might target 40 registrations, 20 attendees, 8 sourced opportunities, and 2 closed deals inside 180 days. A trade show booth might target 200 badge scans, 50 qualified conversations, 15 sourced opportunities, and 4 closed deals. Resist vanity metrics (impressions, reach, likes) as the only commitment; they are fine as supporting indicators but they are not the primary unit of accountability. 2112 Group channel research shows programs that require sourced pipeline commitments on every MDF request see 50 to 80 percent higher return on MDF than programs that accept vanity metrics, because partners self select higher intent campaigns when they know they will be measured on pipeline.

• Require two primary target metrics on every request: pipeline sourced (dollar value, 90 day window) and deals closed (count and dollar value, 180 day window)
• Allow secondary supporting metrics (registrations, attendees, badge scans, downloads) but mark them as supporting, not primary
• Pre populate benchmark ranges per campaign type (for example, 'webinars in this program typically source 5 to 12 opportunities') so partners submit realistic targets
• Build the metrics into the CRM MDF request record so the quarterly review joins target to actual automatically

Timeline is where MDF requests slip into a reimbursement fight. Build three date fields into the template and make all three required: submission date, campaign launch date, and proof of execution due date. The gap between submission and launch has to be long enough for the approval tier it falls into, which is why the taxonomy and the approval tiers interlock with timeline. Standard practice is a 10 business day minimum lead time for anything under the auto approval threshold, 20 business days for manager tier, and 30 business days for executive tier, because the executive tier typically includes a creative review, a legal review, and a budget sign off that cannot be rushed. The proof of execution due date is the second half of the timeline nobody writes down, and it is where receipts disappear. Set it as the campaign end date plus 30 days, make it a required field, and build a system reminder from the CRM to the partner contact on day 15 and day 25 after campaign end. Partner marketing programs that enforce a proof of execution due date see audit survival rates jump materially at year end, because the receipts arrive while the campaign is still fresh in everyone's inbox.

• Require three dates on every request: submission date, campaign launch date, proof of execution due date
• Enforce minimum lead times by tier: 10 business days (auto), 20 business days (manager), 30 business days (executive)
• Set proof of execution due date automatically to campaign end plus 30 days, and send a day 15 and day 25 reminder from the CRM
• Reject any request where submission to launch is shorter than the minimum lead time for its tier, and route the partner to a conversation about pre planning

Approval tiers are the structural backbone of the template, and they are the single field that most programs get wrong by making the thresholds too narrow or too wide. Build a three tier approval structure keyed to the dollar amount of the request. The tiers used by most mid market and enterprise B2B SaaS channel programs are, as industry standard examples, under 5,000 USD for auto approval (routed to the named Partner Marketing manager for a 48 hour review and almost always approved if the template is complete), 5,000 to 25,000 USD for manager tier (routed to the Partner Marketing lead and the campaign type owner for a 5 business day review that includes creative and metrics review), and above 25,000 USD for executive tier (routed to the VP of Partnerships and VP of Marketing for a 10 business day review that typically includes a creative review, a legal and brand review, and a finance sign off on fund source). Publish the tiers inside the template so partners self select which bucket their request falls into, and build a confirmation step that forces them to acknowledge the lead time attached to the tier they picked. These dollar bands are industry standard examples for an MDF program design conversation; they are not Strkr pricing.

• Define three approval tiers by dollar amount with a named approver and a named service level agreement per tier
• Make the tier auto select from the amount field so partners cannot route a 20,000 USD request to the auto approval path
• Require a confirmation checkbox that the partner has read the lead time for the tier they picked and the proof of execution requirements
• Build a quarterly review of the tier thresholds so they do not drift out of calibration as program budgets grow

Proof of execution is where MDF budgets either survive audit or disappear into a receivables chase. Build a proof of execution section into the template that spells out exactly what the partner has to submit, by when, and in what format. Standard proof of execution components are itemized receipts (invoices from the vendor, not credit card statements), creative samples (final creative as it ran, not the draft that was approved), outcome metrics (actual registrations, attendees, scans, downloads, and the opportunities sourced in the CRM linked by campaign code), and a short written retrospective from the partner on what worked and what did not. Make the retrospective short (150 to 300 words) and structured (one paragraph on what worked, one on what did not, one on what they would change), because a structured retrospective produces training data for the quarterly program review that free form text does not. Sales Enablement PRO research shows programs that collect structured retrospectives on every MDF request can tell you the top three highest return campaign types inside a year of launch, and the programs that do not cannot.

• Require four proof of execution components: itemized receipts, creative samples as they ran, outcome metrics joined to CRM campaign code, structured retrospective
• Reject credit card statements and screenshots as sole proof of spend; require the vendor invoice
• Require the partner to tag opportunities in deal registration with the MDF campaign code so pipeline sourced attribution runs automatically
• Store proof of execution against the MDF request record in the CRM or PRM so finance can pull it in bulk at year end

A template that ships and never gets reviewed decays into the same free text form every program has already failed with. Set a fixed quarterly MDF review on the Partnerships and Partner Marketing calendar, and treat it as non negotiable. Each quarter, pull the full MDF request record set from the CRM and review four things: utilization by tier (how much of the budget by partner tier was requested, approved, and spent), return on MDF by campaign type (pipeline sourced and deals closed divided by dollars spent, broken out by campaign type), approval cycle time per tier (did auto hit 48 hours, did manager hit 5 days, did executive hit 10 days), and proof of execution survival rate (what percent of approved requests delivered receipts on time with full attribution). Use the review to tune the template itself: raise or lower the auto approval threshold if traffic is bunching, retire a campaign type that keeps underperforming, add a benchmark range to a type whose targets keep missing, and update the brand kit links if partners keep flagging stale assets. Canalys partner research shows the top quartile of partner programs tune their MDF template every quarter and the bottom quartile tune it once a year, and the gap in return on MDF between the two cohorts is roughly 3x over three years.

• Set a fixed quarterly MDF review on the Partnerships and Partner Marketing calendar, 60 to 75 minutes long
• Pull four reports: utilization by tier, return on MDF by campaign type, approval cycle time per tier, proof of execution survival rate
• Capture two to four changes to the template per quarter (thresholds, campaign types, benchmark ranges, brand kit links) and ship them in a dated version
• Share the review summary with the partner community at a quarterly partner council so partners see the template evolve on their feedback