Turn Overflow Leads Into an MSP-to-MSP Referral Channel
Ric Hall, CRO

Referral and partner-driven growth works best when you stop treating other MSPs as rivals and start treating the right ones as a channel. A formal referral agreement with a peer MSP turns a client outside your coverage area, vertical, or service scope from a lost deal or an uncompensated favor into tracked, recurring revenue on both sides.
Why aren't more MSPs formalizing referrals with other MSPs?
Most owners already know informal referrals happen between competitors who respect each other's work. What's missing is the structure to make that relationship pay. Only 19 percent of MSPs name exploring partnerships with other MSPs as a top priority for 2026, according to ScalePad's 2026 MSP Trends Report, even though word of mouth remains the most common client acquisition channel across MSPs of every size according to that same report.
That gap matters because the same report found that MSPs who grow through referrals and word of mouth tend to report lower client churn than those leaning on local events, SEO, or content marketing. You already trust referrals enough to let them drive new logos. Most owners just never built a version of that trust with the other MSPs sitting right next to them in a peer group, a vendor event, or a regional market.
Where overflow referrals actually come from
A handful of situations create the referral. A prospect sits outside your service area. A prospect needs a vertical specialty, like healthcare compliance or manufacturing floor systems, that you don't carry. A prospect is too small or too large for the tier of service you're built to deliver profitably. In every case, saying no loses the relationship completely unless you have somewhere specific to send it.
Peer networks already formalize this. The ASCII Group, a membership community for independent MSPs, launched a member portal in 2025 that "enables members to submit subcontracting requests, exchange vendor recommendations" across its network, according to ASCII's announcement of the portal. That network counts more than 1,300 member companies across North America, according to ASCII's own membership page. The infrastructure for MSP-to-MSP referrals already exists in the channel. What most individual MSPs skip is putting a commission and an attribution record behind the handoff instead of treating it as a one-time courtesy.
Not every MSP you meet at a vendor event or a peer group belongs in your referral list. Before you send a client's name anywhere, check how the partner actually services accounts in the vertical or region you're handing off, ask for a reference from an existing client of theirs, and get clear on how they handle security incidents and SLAs before the first referral moves. A referral agreement should also spell out what happens if the relationship doesn't work, including how either side exits and whether either party can solicit the client directly once the handoff is made. None of that needs to be complicated, but it does need to be written down rather than assumed.
What does it cost you to send a client to another MSP?
It costs you nothing if you structure it as a paid referral instead of a favor, and you get paid back the same way when a partner sends a client to you. Recurring commission structures already exist for MSPs to study and adapt. One partner network, for example, pays referral partners 10 percent of monthly recurring revenue in the first year and 5 percent in the second year, for up to 24 months per referral, according to EMPIST's partner network terms. Another agency-run referral program pays 5 percent of monthly contract value to non-clients and 7.5 percent to its own clients, with commission continuing every month the referred account stays active, according to Marketopia's referral partner program.
Some referral programs skip recurring commission entirely in favor of a flat bounty paid once. One cybersecurity vendor pays referral partners up to $1,000 for referring another MSP, distributed 90 days after the referred MSP's first purchase, with the amount tiered by the referred company's endpoint count, according to Blackpoint Cyber's partner referral terms. That structure works for a single-product introduction. It works less well for handing off an entire client relationship, where the revenue keeps running for years and a flat bounty undervalues what you gave up.
None of these rates is a universal number you should copy exactly. They show the range a reciprocal MSP referral agreement can occupy: a flat one-time bounty for a light-touch introduction, or a percentage of recurring revenue, paid monthly, for a defined window, when you're handing off an ongoing client relationship. That's the choice to make with a peer MSP before you ever send them a client, not after the first check is already overdue.
| Program | Commission | Duration |
|---|---|---|
| Marketopia (non-client referrer) | 5% of monthly contract value | Ongoing while account stays active |
| Marketopia (client referrer) | 7.5% of monthly contract value | Ongoing while account stays active |
| EMPIST Partner Network | 10% MRR year one, 5% MRR year two | Up to 24 months per referral |
| Blackpoint Cyber (one-time bounty) | Up to $1,000, tiered by endpoint count | Paid once, 90 days after first purchase |
How much is a reciprocal referral worth in practice?
Hypothetical example: say you refer a client worth $3,000 a month in recurring revenue to a partner MSP under a 10 percent first-year, 5 percent second-year structure modeled on the terms above. Year one pays you $300 a month, or $3,600 across 12 months. Year two drops to $150 a month, or $1,800 across the next 12 months, for a two-year total of $5,400 on a single handoff. Send four comparable referrals a year under the same terms and that reciprocal pipeline alone starts to look like a second small book of business, without adding a single technician headcount to service it.
The number changes with every deal. What doesn't change is the discipline behind it: write the percentage and the time window down before the first referral moves, not after.
Make the handoff work for your own stack, not just theirs
This is where owning a white-labeled tool stack changes the math on a referral you'd otherwise hand off for free. When you refer a client to a partner MSP, you can structure the agreement so you keep delivering a branded layer, like a client-facing scorecard or an onboarding tool, even after the partner takes over day-to-day service. That keeps your name on the account and a second revenue line running alongside the referral commission instead of walking away with a one-time check. Actiforge's MSP partner and referral program is built around formalizing exactly this kind of commission and retained-relationship structure for MSPs who refer and receive work from each other.
The same logic runs in reverse. When a peer MSP sends you an account outside their specialty, offering them continued visibility through a shared white-labeled tool, rather than cutting them out once the contract signs, is what turns a one-time referral into a repeat source instead of a single transaction you have to re-earn every time.
Track it like a channel, not a favor
A referral channel without attribution is just goodwill you can't report on. Tag every inbound and outbound MSP referral in your CRM the same way you'd tag a paid lead source, with the partner name, the commission terms, and the start date of the clock. Review that list quarterly alongside your other acquisition channels, not as a footnote in a relationship you're trusting to memory.
Put one person on the hook for the review, usually whoever owns growth or operations, and give them a standing agenda item rather than a reminder to bring it up if there's time. Ask what came in, what went out, and whether the commission actually got paid on schedule on both sides. A reciprocal agreement that only gets enforced when the other MSP happens to remember isn't a channel. It's a handshake you're hoping holds.
If you're mapping out which referral and partner channels are worth the structure versus which aren't, Actiforge's stack builder walks through the tradeoffs across your current tool set and growth channels in a few minutes. And if you haven't looked at what a white-labeled commission structure could add to a referral relationship you already have informally, the full Actiforge product catalog shows what's available to build into one.
Formalizing MSP-to-MSP referrals is a small operational lift against what owners already do informally every month. The difference is whether that goodwill shows up as a tracked line in your recurring revenue or disappears as an unpaid favor you can't repeat on purpose. See the full stack to find the pieces that make a reciprocal referral agreement worth signing.
