July 15, 2026
Patrick Allen
Keep the portal. Add the money layer.
Every PRM renewal now arrives with the same line item: an MDF module, bundled in, one more checkbox on the feature grid. And every channel leader gets the same question from the person signing the renewal: the portal already does MDF — why would we pay for anything else? It's a fair question, and it deserves a straight answer: because collecting a request is not running a program, and your PRM was never built to move money.
Give the PRM its due. A portal's MDF module does real things: it takes in a funding request, routes it to an approver, and stores the attachment. That's the front door of the program — and it's maybe the first 10% of the work.
Now list what "running MDF" actually means once the form is submitted: figuring out which budget the request draws from, tracking what's committed versus spent across regions and business units, validating proof that the activity happened, converting currencies, paying a partner in Warsaw or São Paulo, handling withholding tax, and producing a ledger finance will accept at quarter close. The module hands every one of those back to you — which is why the spreadsheets don't go away when the portal arrives. They multiply around it.
The utilization numbers say the quiet part out loud. Roughly 60% of allocated MDF goes unused every quarter, per Omdia research, and 43% of partners use less than half their allocation — by one estimate, around $15 billion in unspent marketing budget per year in the US alone. When Forrester polled channel leaders on why, the answers weren't "partners can't find the request form." They were cumbersome approval processes, painful claim and audit requirements, and red tape. The checkbox module digitized the request. It never touched the reasons the money doesn't move.
Follow one approved request past the form and watch where it lands.
None of that is portal work. All of it is the program.
This isn't a roadmap gap the next PRM release will close. PRMs are systems of engagement, and good ones earn their renewal: onboarding, content, training, deal registration — the relationship layer of the channel. Moving money is a different discipline with different bones: payment rails, FX, tax documentation, financial controls, liability when a payout goes wrong.
Your CRM doesn't run payroll. Your HR system doesn't close the books. Your PRM shouldn't move money. Ask a portal to be a payments platform and what you get is what most teams have today: a form bolted to a spreadsheet, with an inbox in between.
Here's the part the "portal vs. platform" framing gets wrong: this was never a rip-and-replace decision. Nobody should tear out a PRM they just spent two years driving partners into — and no partner wants another login.
The architecture buyers keep asking for is a layer, not a replacement. The PRM stays the front door — single sign-on, embedded in the pages partners already visit. The payments layer runs everything after "submit": multi-source budgets with live visibility, automated proof-of-execution review, approvals with the FX rate locked at the moment of approval, payouts on the right rails worldwide, and one audit trail underneath all of it — with results flowing back for ROI reporting.
A layer also changes the buying motion. You don't stand up a global replacement; you start with one region and one budget source, prove utilization and cycle time move, and expand from there. Renew the portal. It's good at its job. Just stop asking it to do a job it was never built for.
Relevize is the money layer for the channel — MDF, SPIFFs, rebates, and reimbursements on one platform that embeds in the PRM you already run: multi-source budgets with real-time visibility, AI-driven proof-of-execution review, FX locked at approval, payouts in 30+ currencies to 200+ countries, and a complete audit trail for every dollar.
