Partner KPIs: The Metrics That Measure a Partnership

Turn this article into takeaways for your work.

Each assistant summarizes the article only for you and suggests best practices for your work.

A partner program produces a lot of numbers. Signed partners, trained staff, registered deals, closed revenue, portal logins, MDF claims. The hard part isn't collecting them. It's knowing which ones describe the health of a partnership, and which ones just describe activity.

This article is a reference catalogue. It groups partner KPIs by the stage of the partner lifecycle, gives a definition and a formula for each, and separates leading indicators from lagging ones. It then looks at how large vendor programs score their own partners, using their published documentation, and closes with the pitfalls that distort partner reporting. How to arrange these metrics into a one-page report is covered in partner scorecard, and how to credit revenue between partner and vendor is covered in partner attribution.

What a Partner KPI Is

A key performance indicator is a measurable value that shows how effectively an objective is being met. The general idea is covered in KPIs. A partner KPI applies that idea to the channel: it measures what partners do, what they produce, or what the relationship costs.

Partner metrics fall into three groups, and mixing them up is the most common reporting mistake:

  • Activity metrics count things partners do: trainings completed, leads submitted, portal logins.
  • Output metrics count what those activities create: pipeline, deals, revenue.
  • Economic metrics compare output with cost: return on MDF, cost of channel per dollar of revenue.

Activity metrics are cheap to collect and easy to inflate. Output and economic metrics are harder to measure and much harder to fake. A useful set includes all three, weighted toward the last two.

Partner KPIs by Lifecycle Stage

The sections below follow a partner from recruitment through to long-term economics. Every formula is a plain definition. Your own program may define a term slightly differently, and that's fine, as long as you write the definition down and apply it the same way every period.

Recruitment

Recruitment metrics tell you whether you're finding the right partners, not just more of them.

KPI Definition Formula
Qualified applicant rate Share of applicants or targets that meet your partner profile Qualified applicants / total applicants
Recruitment conversion Share of qualified prospects who sign Signed partners / qualified prospects
Time to sign Days from first conversation to signed agreement Signature date minus first-contact date
Fit mix Share of new partners in your target segments or types New partners in target profile / all new partners

Fit mix matters more than raw volume. Fifty signed partners outside your ideal profile will cost more in onboarding than five inside it.

Onboarding and Activation

Onboarding ends at a partner's first productive deal, so these metrics measure speed and conversion to that point. The process itself is described in partner onboarding.

KPI Definition Formula
Time to first deal Days from signed agreement to first closed or delivered deal First-deal date minus signature date
Activation rate Share of new partners that reach a first deal inside a fixed window Partners with a first deal within N days / partners signed in the cohort
Time to access Days from signature to working portal and product access Access-live date minus signature date
Dormant partner share Partners that finished onboarding but registered nothing in a period Partners with zero registered opportunities / onboarded partners

Fix the activation window (90 or 180 days, say) before you look at the data, and keep it the same across cohorts. Segment by partner type, because a referral partner and a systems integrator will never share a time to first deal.

Enablement and Certification

These metrics ask whether partners have the skills to represent the product. See partner enablement and partner certification for the programs behind them.

KPI Definition Formula
Certified individuals People at the partner holding a current credential Count of active certifications linked to the partner
Certification coverage Share of partners meeting your minimum credential bar Partners at or above the bar / active partners
Training completion Share of assigned courses finished Courses completed / courses assigned
Certification currency Share of credentials still valid Unexpired credentials / total credentials held

Certifications are an activity metric. They become more useful when you check them against output: do certified partners register and close more than uncertified ones in your own data? That's a comparison you can run internally, and it will tell you more than any published average.

Pipeline

Pipeline metrics sit between activity and revenue. They're leading indicators of revenue, with the usual caveat that pipeline is only worth what it converts to.

KPI Definition Formula
Partner-sourced pipeline Opportunity value the partner originated and brought to you Sum of open opportunity value where the partner originated the lead
Partner-influenced pipeline Opportunity value that originated elsewhere but where a partner played a defined role Sum of open opportunity value with a partner role, excluding sourced
Deal registration volume Opportunities partners register in a period Count of registrations submitted
Deal registration approval rate Share of registrations accepted Approved registrations / submitted registrations
Registration to close rate Share of approved registrations that become closed-won Closed-won registered deals / approved registrations
Pipeline per active partner Average pipeline contributed by each engaged partner Total partner pipeline / active partners

Registration data is one of the cleanest signals in the channel, because a partner who bothers to register a deal is putting a claim on it. How registration works is covered in deal registration. A low approval rate can mean partners misunderstand the rules, or that your rules are too restrictive, or that channel conflict is rejecting deals your direct team already touched. The number alone doesn't say which.

Revenue

Revenue metrics are the lagging indicators everyone cares about most.

KPI Definition Formula
Partner-sourced revenue Closed revenue from deals the partner originated Sum of closed-won value, partner-sourced
Partner-influenced revenue Closed revenue where a partner contributed but didn't originate Sum of closed-won value, partner-influenced
Partner revenue share Partner contribution as a share of total revenue Partner-sourced (or total partner-touched) revenue / total revenue
Win rate vs direct Partner deal win rate compared with direct deals Partner closed-won / partner opportunities, against the same ratio for direct
Deal size vs direct Average partner deal against average direct deal Average partner closed-won value / average direct closed-won value
Sales cycle vs direct Partner cycle length against direct cycle length Median days to close, partner vs direct

Always state which revenue base you divide by. "Partners drive 30% of revenue" means different things if the numerator is sourced revenue or all partner-touched revenue, and the two should never be quoted interchangeably.

The three comparisons against direct are where partner reporting becomes honest. A partner channel with a lower win rate, smaller deals and a longer cycle than direct may still be worth running, but it costs more per dollar, and you should know that. Compare like with like: same segment, same product, same period. For the broader revenue-metric family, see RevOps metrics.

Retention and Customer Outcomes

Partner-sold customers can churn faster or slower than direct ones. Nobody knows until they measure it.

KPI Definition Formula
Gross revenue retention (partner book) Recurring revenue kept from partner-sold customers, excluding expansion (Starting recurring revenue minus churn and contraction) / starting recurring revenue
Net revenue retention (partner book) Same, including expansion (Starting recurring revenue plus expansion minus churn and contraction) / starting recurring revenue
Logo retention Share of partner-sold customers still active Retained customers / starting customers
Customer satisfaction on partner-led accounts Survey score for customers served by the partner Average score for partner-led accounts, compared with direct
Partner renewal rate Share of partners that stay in the program Partners renewing / partners up for renewal

Retention of the customers a partner brings is a quality check on the partner, not just the deal. A partner that closes quickly and churns heavily is leaking money you've already paid commission on. Some vendor programs build exactly this into tier criteria, as the next section shows.

Engagement

Engagement metrics describe how present a partner is in the relationship.

KPI Definition Formula
Active partner rate Share of partners with a recent qualifying action Partners with a registration, closed deal or completed training in the last N days / all partners
Joint plan attainment Progress against targets agreed in the joint business plan Actual result / planned result
Review attendance Share of scheduled business reviews held Reviews held / reviews scheduled
Response time How fast the vendor answers partner requests Median hours from partner request to first response

Define "active" by an output, not a login. A partner who opens the portal weekly and never registers a deal is not active in any sense that matters. And note that response time is a vendor-side metric: partners disengage when the vendor is slow, and that deserves its own line on the report.

Program Economics

This group answers whether the channel pays for itself. See market development funds and partner incentives for what the spend consists of.

KPI Definition Formula
MDF return Revenue or pipeline generated per fund dollar spent Partner revenue attributed to funded activity / MDF spent
MDF claim rate Share of allocated funds actually used MDF claimed / MDF allocated
Partner margin and incentive cost Total payout as a share of partner revenue (Margins + rebates + SPIFFs + MDF) / partner revenue
Cost of channel Full cost of running the program per revenue dollar (Incentives + program team + tools + enablement) / partner revenue
Payback on partner Time to recover the cost of recruiting and onboarding a partner Acquisition and onboarding cost / monthly margin from that partner

Cost of channel is the number executives most often want and teams most often leave out. Include salaries and tooling, not only payouts. A channel that looks cheap because the partner team's time isn't counted is cheap on paper only.

Leading vs Lagging Indicators

Some of these metrics tell you what's coming and some tell you what already happened. You need both, and you need to know which is which.

Type What it tells you Examples from the catalogue
Leading Where results are heading Activation rate, time to first deal, certification coverage, registration volume, partner-sourced pipeline, joint plan attainment, active partner rate
Lagging What has already happened Partner-sourced revenue, partner revenue share, win rate vs direct, retention of partner-sold customers, MDF return, cost of channel

Leading indicators give you time to act. A falling activation rate this quarter predicts weaker revenue in two or three quarters, depending on your sales cycle. Lagging indicators confirm whether the leading ones were pointing the right way, and they're the ones you can defend in front of a finance team.

A practical rule: review leading indicators monthly and lagging ones quarterly. Check each year whether your leading indicators actually predicted your lagging ones. If registration volume rose for three quarters and revenue didn't move, registration volume isn't predicting anything for your program, and it needs a rethink.

How Vendor Programs Measure Their Partners

Large vendors publish how they score partners. These documents are useful reference points because they show which metrics a mature program chooses to weight, even if you'd never copy the thresholds.

Microsoft: Partner Capability Score

Microsoft's Partner Capability Score documentation describes a composite score across three categories: performance, skilling and customer success. Each of six solution areas carries a maximum of 100 points. Metrics within each category have weights and thresholds, and a partner earns partial points for partial progress.

The categories map neatly onto the lifecycle above:

  • Performance uses net customer adds: eligible customers added in the trailing 12 months, with lost customers subtracted from new ones.
  • Skilling counts intermediate and advanced certifications held by people linked to the partner's organization.
  • Customer success uses usage growth and deployments.

To qualify for a Solutions Partner designation, a partner needs a score of at least 70 points in the solution area, and every metric in that area must be above zero. That second rule is the interesting one: it stops a partner from reaching the bar on a single strength, since all three categories have to show something. The same page says performance and customer success data are typically refreshed by the 20th of each month, and skilling data within 10 days of a certification being completed.

The design lesson is that Microsoft blends output (customer adds), capability (certifications) and outcomes (usage and deployments) into one score, rather than relying on any one of them.

AWS: Services Partner Tiers

AWS's Services Partner tier criteria combine knowledge requirements with experience requirements. On the knowledge side, the Select, Advanced and Premier tiers ask for four, eight and twenty accredited individuals respectively, split evenly between technical and business roles, plus foundational and technical certified staff. On the experience side, the tiers require launched opportunities with a minimum total monthly recurring revenue: three opportunities and at least $1,500 for Select, twenty and at least $10,000 for Advanced, and fifty and at least $50,000 for Premier.

The page also lists additional requirements for Premier, including a formal business plan, an executive business review and sustained attainment of the criteria for more than six months. In effect, AWS pairs a certification metric (coverage) with a pipeline-to-revenue metric (launched opportunities and MRR), then adds a relationship requirement at the top tier.

HubSpot: Points and Retention

HubSpot's partner tier page shows a points-based model. Sourced points are earned by sourcing and closing deals with customers, at 5 points per $100 of MRR in non-growth markets and 10 in growth markets. Total points are the sum of sourced, assisted and managed points, which separates originating a deal from helping on one or managing the account afterwards. The page also states that Elite partners must hold at least 80% average gross revenue retention over the trailing 12 months, and Diamond partners at least 75%.

So HubSpot explicitly separates sourced from assisted contribution and puts a retention floor on its top tiers. That's the same logic as the retention section above, built into the program rules.

Across the three, the pattern is consistent: a revenue or pipeline measure, a skills measure, and (in two of the three) a quality or customer-outcome measure. None of them rely on activity metrics alone.

Pitfalls in Partner Measurement

Key Facts: Partner KPIs

  • Microsoft's Partner Capability Score gives each solution area a maximum of 100 points across performance, skilling and customer success, and a partner needs at least 70 points with every metric above zero to qualify (Microsoft Learn).
  • AWS's Premier Services Partner tier requires 50 launched opportunities with total MRR of at least $50,000, against 3 and $1,500 for Select (AWS).
  • HubSpot requires Elite partners to hold at least 80% average gross revenue retention over the trailing 12 months, and Diamond partners at least 75% (HubSpot).
  • HubSpot awards sourced points for sourcing and closing deals, and counts assisted and managed points separately in the total (HubSpot).
  • Partner metrics fall into three groups: activity, output and economics. Reliable reporting weights output and economics most heavily.

Vanity Metrics

Signed partners, portal logins, courses completed and leads submitted all rise easily and say little about revenue. They're fine as diagnostics. They're a problem when they become targets, because partner managers will then optimize for them. If a team is rewarded for partners signed, expect a long tail of partners that never sell.

Double Counting Sourced and Influenced

Sourced and influenced pipeline are different claims, and adding them together overstates partner contribution. A deal can be sourced by one partner and influenced by two more, and a single deal can show up three times in a naive total. Keep the categories separate, count each deal once under a single primary role, and report totals only for a defined, non-overlapping set. The crediting rules are the subject of partner attribution.

Mixing Revenue Bases

A partner revenue share built from sourced revenue in one quarter and partner-touched revenue in the next will move for reasons that have nothing to do with partners. Pick the definition, write it into the scorecard and leave it alone.

No Direct Comparison

Reporting partner win rate without direct win rate in the same segment gives you a number with no meaning. The same goes for deal size and sales cycle. Without the comparison, a good number and a bad number look identical.

Averaging Across Partner Types

A blended activation rate across referral partners, resellers and integrators hides what's happening in each. Segment every metric by partner type at least, and by tier or region where volumes allow.

Measuring Activity That Partners Control Cheaply

Registration volume can be gamed by submitting speculative deals. Pair it with approval rate and registration-to-close rate so volume without quality shows up.

Ignoring Vendor-Side Metrics

Partner results depend on what the vendor provides. Slow access, slow deal-registration decisions and slow support all show up as weak partner performance. Track your own response times next to the partners'.

About the author

Brian Tr

Brian Tr

Co-Founder & COO

Brian Tr is Co-Founder and COO of Rework, with 12+ years in B2B go-to-market and operations. Brian scaled Rework from 0 to 10,000+ B2B customers across CRM and productivity tools. Brian writes for founders and owner-CEOs: startup fundamentals, founder-led and family businesses, partnerships, and how SaaS, marketplace, AI and EdTech companies grow.