Partner program template
Most partner programs are a signed agreement, a shared drive and a promise that someone will register deals. The parts that decide whether the program produces revenue are the ones nobody writes down: what a tier requires in practice, who owns the customer in each motion, how long a registration protects a partner, and what happens when a partner and a direct rep land on the same account. This template puts those decisions in one document, with tiers, margin by motion, deal-registration rules, an onboarding sequence, MDF approvals and a quarterly scorecard you can fill in from your CRM.
Download it
PDF and CSV, plus the full web version. The template is free. One short form unlocks it and the rest of the library for this browser.
What you get
- A tier table with entry requirements, commitments, margin and benefits per tier
- Deal-registration rules: what qualifies, how long protection lasts, who approves, and the SLA
- A margin and incentive table by motion, covering referral, reseller, MSP and co-sell
- Rules of engagement for channel conflict, account overlap and existing customers
- A 60-day partner onboarding checklist, from agreement signed to first registered deal
- An MDF and co-marketing request table with proof-of-performance requirements
- A quarterly partner scorecard: registered deals, partner-sourced pipeline, win rate and certifications
Who it's for
- Partnership leads launching or rebuilding a channel program
- RevOps teams configuring deal registration and partner sourcing in the CRM
- Sales leaders who need partner and direct territories to stop colliding
What's inside
10 sections, each listed with its own size. The first is previewed below; the remaining 9 come with the download, with blank rows ready to fill in.
| Section | Size | Previewed |
|---|---|---|
| Partner tiers | 6 columns, 4 worked example rows | Below |
| Program basics | 7 fields to complete | In the download |
| Deal registration rules | 5 columns, 7 worked example rows | In the download |
| Margin and incentives | 7 columns, 4 worked example rows | In the download |
| Sourcing definitions | 6 fields to complete | In the download |
| Partner onboarding, first 60 days | 14-point checklist | In the download |
| MDF and co-marketing requests | 8 columns, 2 worked example rows | In the download |
| Quarterly partner scorecard | 10 columns, 1 worked example rows | In the download |
| Rules of engagement | 6 fields to complete | In the download |
| Why registration decides the program | Guidance notes | In the download |
Preview of section 1
Partner tiers
One table per motion. The thresholds below are an example: set yours from your own trailing four quarters of partner-sourced revenue and registration counts, so that the entry tier covers partners who are already selling and the top tier is reachable by more than one.
| Tier | Entry requirements | Annual commitment | Margin or fee | Benefits | Review cadence |
|---|---|---|---|---|---|
| Registered | Signed agreement, 1 certified rep | None | Referral fee on approved registrations | Portal access, standard collateral, deal registration | Annual |
| Select | 4 registered deals and 1 closed-won in trailing 4 quarters, 2 certified reps | Stated revenue target, no penalty | Base reseller discount | Named partner manager, joint account mapping, co-marketing eligibility | Quarterly |
How to use it
1. Pick the motions before the tiers
Decide which partner types you sell with today: referral partners who hand over a name, resellers who transact, MSPs who own the customer relationship, and technology or co-sell partners who bring overlap. Each motion has a different margin, a different owner of the customer record, and a different definition of a qualified lead. Tiers only make sense inside one motion, so a referral tier and a reseller tier are two tables, not one.
2. Set requirements the CRM can report
Write every entry requirement as something your CRM or LMS can report: registered deals in the trailing four quarters, certified individuals, partner-sourced closed-won revenue, a signed annual commitment. Requirements like "actively engaged" or "strategic alignment" cannot be reviewed, so tier moves become negotiations and the top tier fills with partners who stopped selling two years ago.
3. Make deal registration the whole contract
Registration is the one mechanic that decides whether partners trust the program. State what qualifies a registration, how long protection runs, what happens at expiry, what happens if a direct rep is already on the account, and who decides. Give the approval an SLA in business hours, because a partner who waits three days to find out whether a deal is theirs will stop registering and start selling something else.
4. Price margin per motion, not per partner
Put the referral fee, the reseller discount and the co-sell arrangement in the table once, and route exceptions through the same approvers who sign off direct discounts. A program where margin is negotiated partner by partner produces a spreadsheet nobody can audit and a renewal conversation with every partner at once.
5. Run the onboarding checklist in order
Work the 60-day checklist in order: agreement and tax details, portal and CRM records created, named contacts on both sides, certification booked, first joint account mapping session, first registered deal. The milestone that matters is the first registered deal, not the kickoff call. Track days-to-first-registration per partner and treat anything past 60 days as a recruitment problem rather than a partner problem.
6. Score the program every quarter
Fill the scorecard from the CRM each quarter: registered deals, partner-sourced pipeline and closed-won, win rate against direct, certified reps, and the date of the last business review. Partners with no registration in two consecutive quarters go to an inactive status with a written path back. Without that step, tier benefits accumulate against partners who no longer sell, and the margin table stops meaning anything.
Frequently asked questions
What should a partner program include?
At a minimum: the motions you sell through, a tier structure with measurable entry requirements, margin or referral fees per motion, deal-registration rules with an approval SLA, rules of engagement for channel conflict, an onboarding sequence, and a quarterly scorecard. The registration rules and the sourcing definitions matter most, because they decide whether partners trust the program and whether its revenue can be reported.
How do partner tiers work?
A tier trades a commitment for a benefit. The partner meets stated requirements, usually registered deals, certified people and partner-sourced revenue over a trailing period, and gets better margin plus support such as a named manager or MDF eligibility. Tiers only work when every requirement is something your CRM can report, and when there is an inactive status that partners can fall into.
What is deal registration?
A partner submits an account they are working on, and once approved, that account is protected from your direct team and from other partners for a stated period. The mechanic needs four written answers: what qualifies, how long protection lasts, what happens at expiry, and what happens when a direct rep is already on the account. An approval SLA in business days belongs in the agreement, not only in the process doc.
What is the difference between partner-sourced and partner-influenced?
Partner-sourced means the partner brought the account: an approved registration existed before any logged activity of yours. Partner-influenced means you sourced it and the partner materially helped, evidenced by a dated joint meeting, a proof of concept or implementation scope. Compensation should follow sourcing only, and the flag should be set at registration approval and locked at close.
How much margin should partners get?
It depends on the work the partner does and your gross margin, which is why the margin table in this template is left blank rather than pre-filled. The structural rule is to set rates per motion rather than per partner, and to route exceptions through the same approvers who sign off direct discounts. A program with partner-by-partner margin cannot be audited or renegotiated at scale.
How do you avoid channel conflict?
Pay direct reps on partner-sourced deals in their territory, remove registered accounts from direct prospecting lists for the protection period, name an owner on both sides at registration approval, and publish a two-step escalation path with a decision deadline. Conflict is almost always a compensation problem wearing a process costume.
When is a partner program worth building?
When you can name the motion, name the first five partners, and name the person who will own registrations and the scorecard. A program without an owner becomes an agreement template and a shared drive. Start with one motion, usually referral or reseller, and add a second only after the first produces registered deals on a predictable cadence.