# PartnerImpact — full machine-readable overview > PartnerImpact — B2B SaaS partnerships advisory. Field notes on partner program design, co-sell, tiering, attribution, and the operating model behind partnerships that compound. ## Identity - Organization: PartnerImpact - Canonical URL: https://www.partnerimpact.net/ - Founder / principal advisor: Bart Dirksen - Contact: partnerimpact@outlook.com - Registered address: Kweldam 1, 6678DK Oosterhout, Netherlands - Specialisation: B2B SaaS partnerships — program design, co-sell execution, tiering and scoring, partner attribution, partner operating model - Audience: Heads of Partnerships, CROs, and founders building or fixing a B2B SaaS partner program - Two entry intents served: (1) "I know I need partnership help" → advisory conversation; (2) "I need to understand what is wrong with my partner program" → Partner Program Maturity Assessment ## Methodology — Partner Program Maturity Model The assessment at https://www.partnerimpact.net/partner-maturity-assessment scores a partner program across 12 sections and 48 dimensions. Each dimension is rated on a five-level maturity scale, and each carries a named intervention for the lowest levels. Section and dimension names below are the authoritative list, taken from the running application. ### Ecosystem Design & Strategy Does the company know what kind of partner program it - Strategic direction and partner rationale - Partner type definition and prioritisation - Whitespace and build/buy/partner framework - Investment thesis and board narrative ### Commercial Model Design Can the program generate, structure, and defend partner economics? - Revenue type definition (sourced vs. influenced) - Incentive structure and tier alignment - Partner economics modelling - MSA and hyperscaler transaction terms ### Partner Organization Design Is the team structured to scale the program rather than just manage it? - Role differentiation and specialisation - Coverage model and PAM ratios - Regional pod structure and specialist overlays - Reporting line and headcount planning ### Partner Program Design Is the program designed to produce behaviour, not just sign agreements? - Tier structure and outcome-based criteria - Benefit stack (funded and deliverable) - Program economics and NPS - Partner experience and program differentiation ### Partner Enablement Can partners sell and implement independently? - Onboarding structure and milestones - Sales playbook and ICP enablement - Technical enablement and certification - Self-service portal and enablement independence ### Partner Marketing Is the partner channel generating its own demand, or just riding the direct sales motion? - Co-marketing budget and programme - Partner-generated lead tracking - ABM campaigns with partners - Digital presence and partner-led demand generation ### Co-Sell & GTM Execution Are partners integrated into the sales motion, or working in parallel to it? - Rules of Engagement and deal registration - Account mapping overlap - MEDDICC × partner plays by type - Co-sell pipeline visibility and win rate ### Partner Process & Operations Are the operational mechanics of the partner program reliable and scalable? - Core operational infrastructure (PRM/CRM) - Deal registration and agreement workflow - PRM/CRM integration and automation - Operational resilience and process documentation ### Data & Attribution Does the company know what partners are contributing and how to prove it? - Attribution methodology - CRM data quality and partner tagging - Partner reporting infrastructure - Predictive analytics and automated alerts ### Partner Performance Measurement Are partners held accountable to outcomes, and does the program reward what it intends to? - Core KPI suite per partner tier - Active vs. signed partner ratio management - Leading indicators and partner health scoring - Benchmarking and program improvement loop ### Governance & Cadence Is the program systematically managed, or does it run on memory and urgency? - Partner-facing QBR cadence - Internal partner review cadence - Action tracking and accountability - Partner Advisory Board (PAB) ### Partner-First Culture Does the rest of the company enable the partner program, or resist it? - Executive sponsorship and CRO trust - AE incentive alignment - Cross-functional integration (Product, Marketing, Finance) - External recognition and partner-first identity ## Insight library (full text) ### The partner base is about to split in two URL: https://www.partnerimpact.net/insights/ai-agents-reshaping-partner-base Author: Bart Dirksen · Published: 2026-04-24 · Category: Ecosystem Strategy AI agents are taking over the work that used to give many services partners their margin. Onboarding. Basic setup. Provisioning. Small-business rollout templates. This is the routine middle of services work, and it is being automated faster than most partner programs have updated their training. Big enterprise change work still needs people. The work below that is moving to software. The new space is above it: designing how AI gets deployed, owning the result, coordinating many parties, and managing adoption over time. This work is harder, and for now it pays more. The clearest sign is in the hyperscaler marketplaces. Co-sell deals that include AI deployment work close at much higher value than software-only deals. The programs that handle this well make an honest call about their current partners. The useful test is not what a partner can do on paper. It is whether the partner has already put their own money into AI deployment talent. That one signal separates the partners who will lead from the ones still waiting for the vendor to pay for it. Many programs still run the same model across every partner and hope the partners will upgrade on their own. That worked when software margins paid for the patience. It does not work now. The partner base is starting to split. Some firms move up into AI deployment work. Some get bought by larger integrators built for this motion. A long tail drifts into low-margin, self-serve marketplace work. And new AI-native firms arrive from outside the usual channel. Programs that made the call early already know which partners sit where. Everyone else is running quarterly reviews trying to work it out. --- ### A co-sell SPIFF is a bet on behavior, not a reward for revenue URL: https://www.partnerimpact.net/insights/co-sell-spiff-behavior-design Author: Bart Dirksen · Published: 2026-04-23 · Category: Co-Sell & GTM A co-sell SPIFF is not a reward for revenue. Your AEs already have quota for that. It is a bet on one behavior: getting AEs to actually bring partners into deals, instead of just having partners available. That difference should shape how you build it. Most SPIFFs fail because they are built like recognition programs. The money is there, but the behavior you want is vague. "Partner involvement" ends up meaning whatever the rep says it means. You do not get more co-selling out of it; you get reps tagging partners onto deals to claim the payout. The real design question is not how much to pay. It is what you are trying to change. Which behavior is lower than it should be? What does real partner involvement look like, versus a partner just getting credit? Who checks that it happened? Without clear answers to those three, the SPIFF gives you a leaderboard, not a motion. The harder truth: a SPIFF cannot fix the real reasons AEs avoid partners. If quota credit is unclear, if routing is broken, or if partners do not make deals better, the SPIFF buys you compliance for one quarter, and then things go back to how they were. It buys you time, but it does not fix the underlying design. --- ### Co-sell that actually closes URL: https://www.partnerimpact.net/insights/cosell-that-actually-closes Author: Bart Dirksen · Published: 2026-05-20 · Category: Co-Sell & GTM Co-sell is the most over-announced and under-engineered motion in B2B SaaS. Every partnerships team says they do it. Very few can point to a repeatable path from partner-sourced meeting to closed revenue. ## Three failure modes - The handoff is undefined. Partner passes a lead, seller does not know what to do with it, opportunity dies. - Compensation is misaligned. The seller carries a quota that treats partner deals the same as direct deals, or worse. - The cadence is missing. Nobody meets weekly to unstick the deals in flight. ## What good looks like A single-page handoff spec. A compensation accelerator on partner-sourced ARR. A weekly deal desk between partnerships and the AEs who own the accounts. Not complicated, but rarely in place. --- ### Why multi-agent deals break partner attribution URL: https://www.partnerimpact.net/insights/multi-agent-attribution-governance Author: Bart Dirksen · Published: 2026-04-24 · Category: Operating Model & Attribution The attribution problem in co-sell is not new. What is new is that deals now run through many partners and AI agents at once, and that breaks the old way of tracking who did what. Picture one deal. An AI agent finds the account. A technology partner adds the integration context. A services partner builds the business case. The direct rep closes it. Now try to label that deal "sourced" or "influenced." The old model was never built for credit spread this thin. The first instinct is to fix it with better tools: more tracking, automatic logging, cleaner PRM data. That improves your data quality, but it does not touch the real problem, which is governance. Most companies have no clear, leadership-backed way to settle a contested deal. They rely on informal habits, quiet deals between managers, and the odd escalation. AI-led selling will create more contested deals, and faster. The companies that agree on clear attribution rules now, with sales leadership behind them, will spend less time arguing and more time selling. --- ### Most programs enable partners too early URL: https://www.partnerimpact.net/insights/partner-activation-sequence Author: Bart Dirksen · Published: 2026-04-23 · Category: Co-Sell & GTM Most partner programs track their activation rate. Very few look at what happens before activation. The usual approach: sign the full legal agreement, run a big certification program, hold an account mapping session, launch co-marketing. All of it done first, before the two sides have earned a single dollar together. Training a partner before there is a live deal is preparing for a future that may never come. Account mapping before there is trust is just two sides swapping wish lists. Negotiating a full agreement before you share any real context is arguing about SLAs that do not exist yet. Each of these has a right moment. That moment is after the first deal closes. Once a deal closes, everything changes. The partner has proof. You have proof they can deliver. Now both sides have something real to build on. The heavy program work finally has solid ground under it. Most programs lose partners in the gap between signing them and activating them, because they try to finish everything before there is any momentum. The better question to ask in every recruiting conversation: who is the first client we will work on together? --- ### Building partner attribution in HubSpot URL: https://www.partnerimpact.net/insights/partner-attribution-in-hubspot Author: Bart Dirksen · Published: 2026-08-15 · Category: Operating Model & Attribution HubSpot ships without a partner attribution module. The pieces are all there: deal properties, UTM capture, workflows, reporting. You assemble them yourself, and where you assemble them wrong is where the partner number stops surviving a finance review. This is the build, layer by layer, followed by the two places the native model gives out: multiple partners on one deal, and attribution at the level of the individual partner rep. For the argument behind why these definitions matter more than the tooling, see the pillar: [partner attribution is an operating-model decision, not a reporting task](/insights/partner-attribution-operating-model). ## Part 1: HubSpot referral attribution Partner attribution in HubSpot is assembled from four layers: deal properties (primary tracking), contact properties (UTM capture), workflows (propagation logic), and report builder (revenue reporting). There is no single "partner module" to activate. Each layer is configured deliberately. The approach differs based on whether you are tracking inbound referrals (a partner sends a contact to you), co-sell assists (a partner is active inside a deal already in pipeline), or both. ### Step 1: Deal properties Go to **Settings > Properties > Deal Properties** and create the following custom fields: | Property | Type | Notes | | --- | --- | --- | | Referring Partner | Dropdown or single-line text | Use dropdown if the partner list is fixed and known | | Partner Source Type | Dropdown | Options: Referral, Co-sell, Influenced, Reseller | | Partner Deal Registration Date | Date | For programs with formal deal registration | | Attribution Confirmed | Checkbox | Manual sign-off step before reporting | > **Configuration note.** Set Referring Partner and Partner Source Type as required fields on the deal creation form, at the pipeline stage where partner deals enter. Required fields enforced at stage entry are the most effective way to prevent blank attribution records accumulating over time. ### Step 2: Pipeline structure If partner-sourced deals follow a different qualification or approval path (deal registration review, co-sell approval), create a dedicated pipeline under **Settings > Deals > Pipelines**. This produces clean pipeline reporting by source without relying on saved filters, and keeps partner deals from mixing with direct inbound in forecast views. If deal volume does not yet justify a separate pipeline, set a required Lead Source property to "Partner Referral" and segment using list filters. This is the right starting point for programs with fewer than 20 active partners. ### Step 3: UTM tracking for digital referrals For partners who send traffic to your website, generate unique UTM links per partner using this structure: | Parameter | Value | | --- | --- | | utm_source | partner | | utm_medium | referral | | utm_campaign | [partner-name] | HubSpot captures UTM parameters on contact records automatically when a form is submitted or a tracking cookie is set. Map utm_campaign to a persistent contact property ("Referring Partner") on first conversion using a contact-based workflow. > **Known limitation.** UTM data is contact-level, not deal-level. A workflow is required to copy the value from the contact record to the associated deal. See Step 4. ### Step 4: Propagation workflow Create a deal-based workflow to move attribution data from contact to deal: - **Trigger:** Deal is created and the associated contact has the "Referring Partner" contact property populated. - **Action:** Copy the contact property value to the deal property "Referring Partner". This is the bridge between UTM capture (which lives on the contact) and revenue reporting (which lives on the deal). Without this workflow, UTM attribution is invisible in deal-level reports. ### Step 5: Reporting on partner-attributed revenue In **Report Builder**, configure a deal-based report as follows: - **Data source:** Deals - **Filter:** Referring Partner is known, or Referring Partner equals [partner name] - **Metrics:** Deal Amount, Deal Count, Close Date, Pipeline Stage Save these to a Partner Attribution Dashboard and share it with the partner team on a monthly cadence. > **Scope note.** HubSpot's built-in Attribution Reports (Marketing Hub Professional and above) are designed for ad and content attribution. They do not cover deal-level partner attribution. Do not use them for partner revenue tracking. ### Common gaps to avoid 1. **Not distinguishing sourced from influenced.** A partner who introduced the deal is different from one who supported a deal already in pipeline. Both are valuable, but combining them makes the metric untrustworthy. Capture both Partner Source Type values and report them separately. 2. **Manual entry without field enforcement.** Required properties at stage entry are the most reliable enforcement mechanism. Relying on training and goodwill produces inconsistent data within one quarter. 3. **Losing UTM data on return visits.** UTM parameters are not set on a contact's second visit if they arrive without them. The contact property capturing the first-touch value must be set to "never overwrite" to preserve the original referral source. 4. **Counting influenced deals as sourced.** This inflates partner revenue figures and erodes trust with Finance and the CRO. Define attribution rules in writing before building reports, and have RevOps agree them before they go into any leadership deck. ### Minimum viable configuration For teams starting from scratch, this is sufficient for programs with fewer than 20 active partners and takes one day to implement: 1. Add "Referring Partner" as a required deal property (dropdown). 2. Add "Partner Source Type" as a required deal property (dropdown: Referral, Co-sell, Influenced). 3. Train the team to populate both at deal creation. 4. Build one custom report filtering closed-won deals by Referring Partner. 5. Review against total closed-won ARR monthly. This needs no integrations or workflows. It needs process discipline. Introduce UTMs and workflow propagation in the next phase, once the attribution data is clean. ## Part 2: Multi-partner attribution HubSpot's default property model assumes one partner per deal. When several partners are involved, you build the data model deliberately. Three options, in rising order of complexity. ### The problem A single deal can involve more than one partner. A referral partner opens the door. A solutions partner runs implementation scoping. A technology partner's integration is the reason the prospect evaluated you at all. Each contributed something. The question is how to record it without either losing the data or making reporting unusable. HubSpot has no native multi-partner attribution. The three options below differ in complexity, reporting quality, and the HubSpot tier required. ### Option 1: Sequential deal properties Add a fixed set of partner attribution property pairs to the deal object: | Property | Type | | --- | --- | | Partner 1 Name | Dropdown | | Partner 1 Attribution Type | Dropdown: Sourced / Influenced / Technical / Delivery | | Partner 2 Name | Dropdown | | Partner 2 Attribution Type | Dropdown: Sourced / Influenced / Technical / Delivery | | Partner 3 Name | Dropdown | | Partner 3 Attribution Type | Dropdown: Sourced / Influenced / Technical / Delivery | > **Limitation.** Reporting on "all deals where [Partner X] appears in any attribution slot" requires filtering across three properties with OR logic. It is buildable in HubSpot's report builder but must be replicated by hand for each partner. It does not scale cleanly beyond three partners or 15 active partners. ### Option 2: Partner Attribution custom object (Enterprise) HubSpot Sales Hub Enterprise supports custom objects. Create a Partner Attribution custom object with these fields: - Associated Deal (lookup) - Partner Name (dropdown) - Attribution Type (dropdown: Sourced / Influenced / Technical / Delivery) - Attribution Weight % (number, 0 to 100), optional, for programs that split credit Each deal can have multiple Partner Attribution records associated to it, one per partner involved. This is the cleanest data model: reporting by partner is accurate regardless of which slot the partner occupied, with no arbitrary three-partner cap. Requirement: HubSpot Sales Hub Enterprise. Custom objects are not available on lower tiers. ### Option 3: PRM-managed attribution Most mature PRMs handle multi-partner attribution natively and integrate with HubSpot via API or native connector. If you have a PRM in place, use it as the system of record for multi-partner attribution and sync a summary field to HubSpot for visibility. Sync a "Partner Attribution Summary" text field from the PRM to HubSpot deals. This keeps attribution logic in the PRM where it belongs and gives CRM users a readable summary without duplicating the data model. ### Attribution weight logic If the program pays or credits partners based on deal contribution, define the weight model before the properties are built. The properties you create should match the model exactly, so data capture and downstream calculations are aligned from day one. | Model | Description | Best for | | --- | --- | --- | | First touch | 100% credit to the partner who originated the deal | Referral-first programs | | Last touch | 100% credit to the partner most active before close | Co-sell programs | | Equal split | Divide credit equally across all attributed partners | Simple programs, early stage | | Role-based | Fixed % by role, e.g. referral 40%, delivery 40%, technology 20% | Mature programs with defined partner types | > **Pre-build requirement.** Define the weight model in writing and get Finance and the CRO to acknowledge it before building any properties. Changing the model after data is collected requires either a backfill or an acknowledged break in the time series. Neither is easy to explain in a QBR. ## Part 3: Partner rep attribution Beyond which partner organization is credited, rep-level attribution records the specific individual who worked the deal. This matters for QBRs, partner incentive reviews, and commission calculations. ### What rep-level tracking captures Partner attribution usually stops at the company level: "Acme Systems sourced this deal." Rep-level attribution goes one layer deeper: "Jordan at Acme Systems registered and progressed this deal." The distinction matters when: - Running partner rep leaderboards or incentive programs - Preparing QBR scorecards for specific partner accounts - Calculating commission or spiff payouts for individual partner reps - Diagnosing which reps at a partner are actively selling versus dormant ### Step 1: Create partner contact records Partners are companies in HubSpot. Partner reps are contacts associated to those companies. Set this up as follows: 1. Create or import partner company records under **Companies**. Tag each with a property: Company Type = Partner. 2. Create contact records for each partner rep. Associate each contact to their partner company record. 3. Add a contact property: **Contact Type = Partner Rep**. This enables filtering contacts by role in reports without relying on manual naming conventions. ### Step 2: Associate the partner rep to the deal HubSpot allows multiple contacts to be associated to a single deal. When creating or updating a partner-attributed deal, associate the partner rep contact alongside the end-customer contacts. Add these custom deal properties to make the association explicit and reportable without relying on contact association queries: | Property | Type | Trade-off | | --- | --- | --- | | Partner Rep Name | Single-line text or Contact lookup | Lookup is cleaner for reporting; text is faster to implement | | Partner Rep Email | Email | Use as a unique identifier for grouping in reports | | Partner Company | Company association or dropdown | Association is cleaner; dropdown if the company list is stable | > **Implementation note.** The contact lookup approach ties the rep to their actual HubSpot contact record, which enables richer cross-object reporting. The text field approach is faster to implement and sufficient if the only requirement is grouping closed-won revenue by rep name in a single report. ### Step 3: Report on partner rep performance In **Report Builder**, configure a combined Deals + Contacts report: - **Data source:** Deals + Contacts (combined) - **Filter:** Contact Type equals Partner Rep - **Group by:** Partner Rep Name or Partner Rep Email - **Metrics:** Deal count, closed-won amount, average deal size, pipeline stage breakdown This produces a per-rep performance view that can feed directly into QBR decks or partner incentive review cycles. ### If you use a PRM PRMs maintain their own partner rep profiles and deal registration records. Rep attribution is tracked inside the PRM and typically synced to HubSpot as a text field on the deal (partner rep name or email). This is sufficient for CRM-level reporting and deal visibility. If you need rep-level commission calculation, that calculation stays in the PRM or a dedicated incentive tool. HubSpot does not calculate or track partner rep commissions natively. ### Minimum viable configuration Rep-level attribution without a PRM, built in one afternoon: 1. Import partner reps as contacts in HubSpot with Contact Type = Partner Rep. Associate each to their partner company. 2. Associate each partner-attributed deal to the relevant partner rep contact at deal creation or registration. 3. Add Partner Rep Email as a required deal property in the partner pipeline. 4. Build a deal report grouped by Partner Rep Email showing closed-won revenue and deal count. This gives rep-level visibility without any integration and without a PRM. It requires one manual step per deal (associating the rep contact) but is fully auditable and sufficient for programs with fewer than 50 active partner reps. --- The tooling here is the easy part. What makes the number hold up is the layer above it: the definitions agreed before the properties exist, the fields enforced at stage entry, and the weight model. --- ### An ecosystem is shaped by who leaves URL: https://www.partnerimpact.net/insights/partner-ecosystem-exit-criteria Author: Bart Dirksen · Published: 2026-04-28 · Category: Ecosystem Strategy Most partner programs track who joins. Almost none decide who should leave. You have exit rules for deals. You have exit rules for employees. For partners, there is usually nothing. Just a growing list of signed agreements, with less and less activity per partner. The result is a portfolio that looks big and works like clutter. Partner managers are spread across a hundred names when fifteen of them do most of the work. And because there is no label for a dormant partner, every signed partner still counts as active. The money and attention go into recruiting new partners, while the ones already signed are managed, at best, from a spreadsheet. A few things are worth putting in writing in any program. What does dormant actually mean, in numbers? How long do you wait before you downgrade or remove a partner? Who makes that call? What happens to their tools, incentives, and access when the relationship pauses or ends? None of these questions are hard to answer. Most programs simply avoid them, and that is a big reason partner ecosystems carry so much dead weight while the top of the list does most of the work. Deciding who leaves is part of ecosystem design. For most programs, it is the part that is missing. --- ### Partner metrics, mapped to the whole journey URL: https://www.partnerimpact.net/insights/partner-metrics-bowtie Author: Bart Dirksen · Published: 2026-07-19 · Category: Operating Model & Attribution Ask a partner leader how the program is doing, and you usually get one number: partner-sourced revenue. Sometimes two, if they add deal count. Both are real, and both arrive late. By the time revenue moves, the work that produced it happened quarters ago. Revenue is not the wrong measure. The problem is that a single lagging number tells you almost nothing about where a partnership is strong, where it is stuck, or what to fix. A partner can be generating leads that never convert, closing deals that never activate, or landing customers who never expand. Each of those is a different problem with a different fix, and one revenue figure hides all of them. The map below lays out the metrics that sit underneath that number, across the full journey from first touch to expansion.
## How to read it Across the top are the seven stages a partner-influenced customer moves through: awareness, educate, select, commit, onboarding, retention, and expand. Demand generation on the left, narrowing to the moment a customer commits in the middle, then widening again through onboarding, retention, and expansion on the right. It is the same model many successful revenue teams use for direct sales, applied to the partner motion. Underneath, the metrics come in three layers, and each answers a different question. **Volume metrics (VM)** count activity: partner-sourced leads, co-branded assets, supported deals, onboarded customers. They tell you whether enough is happening at each stage to expect an outcome. **Conversion rates (CR)** measure how well one stage turns into the next. Co-marketing leads becoming qualified. Referrals becoming opportunities. Partner-assisted deals being won. This is where friction shows up. A stage with healthy volume but weak conversion is a stage that is quietly leaking. **Time metrics (T)** measure speed: time to a partner's first deal, time to first value for the customer, deal velocity, customer lifetime. A slow time to first deal after signing is one of the earliest signs a partner will never activate. ## Why three layers instead of one score Most scoring models collapse everything into a single composite, usually weighted toward revenue. That is easy to publish and hard to act on. When the number drops, you cannot see whether the cause is thin top-of-funnel volume, a broken handoff at onboarding, or a partner who lands customers that never grow. Keeping volume, conversion, and time apart keeps the diagnosis visible. Low volume points to a recruiting or demand problem. Weak conversion usually means an enablement or fit problem. Slow time is almost always a process or handoff problem. Average them together and you can no longer tell which one you are looking at. ## Using it You do not need every metric from day one. Pick the three or four that match where the program actually is. Early programs live or die on time to first deal and early conversion. More mature programs care about onboarding success, retention, and expansion revenue. The map is here so you choose deliberately, instead of defaulting to whichever number your CRM happens to report. Used well, it does something a single revenue figure never can: it lets you look at a stalled program and know which stage to walk into first. --- ### Your partner org chart is not an operating model URL: https://www.partnerimpact.net/insights/partner-org-chart-vs-operating-model Author: Bart Dirksen · Published: 2026-04-28 · Category: Operating Model & Attribution Companies change their partner org structure to fix problems that structure cannot fix. They redraw the reporting line. Partnerships moves from under the CMO to under the CRO. New titles appear. A few months later, the same problems are back: no clear owner on contested deals, no steady pipeline review, attribution fights that go all the way up with no real answer. The structure changed, but the way the team actually works did not. An org chart shows who reports to whom. That is not an operating model. An operating model answers other questions. Who decides how partners are segmented? Who approves a pricing exception or a deal registration conflict? What happens when direct sales and a partner both claim the same deal? When does the field escalate, and to whom? Most partner teams answer the org chart questions easily and the operating model questions badly. A restructure is visible, and it is fast. Building clear decision rights, a review rhythm, and shared definitions is slow and shows almost nothing on the surface. That is probably why it happens less often than it should. --- ### Work backwards from the number: a partner pipeline planner URL: https://www.partnerimpact.net/insights/partner-pipeline-target Author: Bart Dirksen · Published: 2026-08-16 · Category: Co-Sell & GTM Most partner targets are set the lazy way: take last year, add a percentage, call it a plan. The number looks reasonable in the deck and falls apart in the field, because nobody worked out the coverage underneath it. Coverage is the honest question. If partners are meant to contribute a share of new revenue, that share implies a specific volume of deals, a larger volume of qualified opportunities, and a total pipeline several times the size of the target. Miss any of those and the number was never going to land, regardless of how committed the partners were. The planner below runs that math backwards from your target.
## How to read it Start with the revenue you want from the period and the share you expect partners to contribute. The tool works down from there: - **Deals to close** comes from the target divided by your average contract value. - **Opportunities needed** applies your win rate. A 22% win rate means roughly four and a half qualified opportunities for every closed deal. - **Total pipeline required** is what has to be in the system to support that, and it is almost always larger than leaders expect. - **Partner-sourced pipeline** is that number scaled to the contribution you are asking partners to carry. The gap between the pipeline this shows and what your partners actually generate is the real state of the program. Closing it is rarely about recruiting more partners. It is about the operating model underneath the number: how partners are segmented, enabled, and routed so the coverage exists. That operating model is the subject of the book. --- ### A partner program is a system, not a channel URL: https://www.partnerimpact.net/insights/partner-program-is-a-system Author: Bart Dirksen · Published: 2026-08-11 · Category: Operating Model & Attribution Most partner functions are a pile of parts. A strategy deck, a tier structure, a PRM, a dashboard, a co-sell motion on a slide. The leader can point to every one of them. The number still misses, as the individual parts were built but never wired together. A partner operating model consists of seven domains: what you design before launch, what you run every day, and what creates accountability across the program. Underneath sits an AI layer that speeds up all seven.
Still, a company can have all seven in place and underperform, because a partner function is not the parts but the joins between them. A co-sell motion gets designed while sales compensation pays the rep the same with or without the partner. The go-to-market outruns the data spine and attribution slips. Each one is a working domain failing at its edge. Seven with weak joins produce less than five wired tightly together. Here is the part worth remembering. You cannot buy your way out of a missing domains, and you cannot work around one for long. Spend speeds up a working model; it does not build one. The AI layer sits under all seven for the same reason. It accelerates whatever is already there. It helps when the policy underneath is clear, and it hurts when nobody wrote one. The seven domains, the joins between them, and how to fix the weakest one are the backbone of my book, *Finding Traction in Partnerships — The Operating System for Partnerships That Compound*. --- ### Your partner program is rewarding the wrong things URL: https://www.partnerimpact.net/insights/partner-program-rewarding-wrong-things Author: Bart Dirksen · Published: 2026-04-24 · Category: Program Design Tier thresholds. Certifications completed. Deals registered. These made sense when partners mostly sold and set up software, and revenue was a fair stand-in for value. That model is breaking down. Enterprise buyers have moved from "buy the software and install it" to "buy the result and have someone run it for us." Previous criteria are no longer driving the partner behavior you want. Many programs are simply still measuring partners against things that no longer track where value comes from. A partner quietly building real AI deployment skills gets the same tier as one doing none of it, as long as the revenue holds up. Changing a tier program is politically hard. Partners have built their businesses around the current rules. That is a reason to manage the change carefully, not a reason to keep a structure whose logic has already worn out. A program that rewards the wrong behavior is not stable. It slowly builds a partner base that is good at things your customers no longer need. --- ### The partner program ROI most teams never run URL: https://www.partnerimpact.net/insights/partner-program-roi Author: Bart Dirksen · Published: 2026-08-23 · Category: Operating Model & Attribution Partner teams usually report gross numbers. Partner-sourced revenue, influenced pipeline, deal counts. What rarely lands on the same slide is the cost of the function that produced them, set against the margin of those deals. That omission is why partner ROI is one of the least trusted lines in most budget reviews, and why the function is one of the first to be questioned when money gets tight. The calculation is simple. Take the gross profit your partner-attributed revenue produces. Subtract the fully loaded cost of the program: team, tooling, incentives, and the rest. Divide what remains by the investment. A second number few teams work out: the revenue you need, at your margin, to cover the function.
## Before you present it This is a gross-profit return, not a cash payback. It tells you whether the program earns more than it costs, not when the cash comes back; do not blur the two. Push the margin up and the revenue needed to cover the function drops, which is how partner cases end up inflating themselves. Use the margin those partner deals have, not the blended company number. ## What the result tells you Most partner leaders avoid this figure because they suspect it is thin, which is the reason to run it. A weak return you find yourself is a problem you can still fix, while the same number surfaced in the budget review will most likely be a decision about your headcount. When it is thin, the fix is rarely more deals. It is the economics built into the program: which partners you invest in, how incentives are structured, what the function costs to run at the coverage you need. It is your partner operating system that needs work. --- ### A partner score without a recommendations layer is a report card URL: https://www.partnerimpact.net/insights/partner-score-recommendations-layer Author: Bart Dirksen · Published: 2026-06-26 · Category: Tiering & Scoring Most partner programs that add scoring put their effort into building the model. Very few put effort into the next step: telling partners what to do with the number. A score with no advice on how to move it is a report card. Partners look at it, feel ranked, and move on. The ones ranked low tend to check out, and the ones ranked high tend to coast. The recommendations layer is what turns a score into action. It tells a partner: you are at 62 points, you need 70 to qualify, and the quickest way there is two more certifications and one deal registration this quarter. That is very different from a tier badge. It is a coaching tool with a clear next step. Partners can see when they are close to a threshold and exactly what action gets them over it. Most vendor programs skip this. They publish the score, assume partners will work out the rest, and then wonder why the score never changed behavior. A score only tells a partner where they stand. What actually gets them to move is the recommendation, and most programs never build it. That gap is most of the reason points-based programs fall short of their design. --- ### When a partnership stalls, suspect structure before people URL: https://www.partnerimpact.net/insights/partnership-stalls-design-not-people Author: Bart Dirksen · Published: 2026-04-23 · Category: Operating Model & Attribution When a partnership stalls, the first guess is usually people. Wrong partner. Wrong contact. Wrong rep. The real cause is almost always the structure. Channel conflict sticks around when working together makes no sense under the compensation plan. Partners go quiet when the value they get is unclear. Co-sell stalls when there is no routing logic, no account plan, and no agreed meaning for "partner involvement." These are design problems. They look like relationship problems because relationships are where the symptoms show up. The difference matters, because the fix is different. A relationship problem calls for better conversations, more QBRs, new contacts. A design problem calls for changed decision rights, changed pay, changed process. Most programs do the first and skip the second. That is why the same problems come back quarter after quarter, with new people in the same seats. --- ### Points-based scoring that's still a revenue scoreboard URL: https://www.partnerimpact.net/insights/points-based-scoring-collapsed-weights Author: Bart Dirksen · Published: 2026-06-26 · Category: Tiering & Scoring A lot of partner programs moved to points-based scoring to get away from revenue-only thresholds. Most just rebuilt the same thing in a new shape. On paper it looks broad: three categories, weighted inputs, one combined score. But when performance is 60 or 70 percent of that score, the other two categories are just decoration. You can call them Skilling and Customer Success, but the math is still a revenue scoreboard. The mistake that is easy to miss is not choosing the wrong model. It is choosing the right model and then weighting it as if nothing changed. A common benchmark: 40 percent for engagement and capability signals, 30 percent for pipeline, 30 percent for revenue. That lean toward leading signals is on purpose. It rewards partners for building the habits that create revenue, not just for the revenue they already booked. Flip the weighting and you stop measuring the partnership and start measuring last quarter. --- ### The partner portal went live. Nobody came. URL: https://www.partnerimpact.net/insights/program-before-proposition Author: Bart Dirksen · Published: 2026-04-28 · Category: Program Design The partner portal went live. Nobody came. This happens more often than programs admit. The tiers are built. The badges are ready. The benefits are written up. The onboarding is mapped. And recruiting still moves slowly, because the basic question was never answered first: why would a strong partner choose this over the other relationships already fighting for their attention? Most partner programs are built from the inside out. Internal logic, internal process, internal comfort. The partner's experience gets added at the end, once the internal system is done. So it usually shows up late and feels thin. The value proposition is not a page in the portal. It is the reason a good partner, who already has options, decides to put this program first. What is the near-term money case for them? Where is the first win likely to come from, and how soon? What does the vendor's field team actually do when a partner brings in a deal? Programs that launch before they can answer those questions end up recruiting on brand or novelty. Then they struggle to activate the partners they signed. A program that can clearly explain why does not need many other tools to recruit well. --- ### Promote monthly, demote semi-annually URL: https://www.partnerimpact.net/insights/tier-promotion-demotion-cadence Author: Bart Dirksen · Published: 2026-06-26 · Category: Tiering & Scoring Promote monthly, demote every six months. Most programs fall into that gap by accident. This is deliberate behavioral design, not leniency. Partners who are climbing need monthly feedback to stay motivated. If the score only updates each quarter, you build a full quarter of lag into the system. Monthly upside tells a partner that what they do this month counts this month. The six-month wait on demotion does something else. It splits the drive to climb from the fear of one bad quarter. A partner who slips in March does not drop a tier until the September review. That gives a good partner room to recover from one weak quarter without losing everything they built. Programs that promote and demote at the same speed create a different problem: partners start playing it safe. Field reps at partner firms stick to what they know instead of trying new things that might dip a number. The tier stops being a goal to climb toward and becomes a position to protect. That gap between fast promotion and slow demotion is what makes a scoring model drive the right behavior across the whole portfolio, instead of just ranking partners by who had the best quarter. --- ### Why partner programs stall between year one and year three URL: https://www.partnerimpact.net/insights/why-partner-programs-stall Author: Bart Dirksen · Published: 2026-04-15 · Category: Program Design Most partner programs cross the same wall between year one and year three. Early wins come from a handful of relationships that a founder or head of partnerships is personally carrying. Those relationships produce enough pipeline to justify a program, and the company hires against that signal. Then growth flattens. ## The pattern The instinct is to blame partner quality, or the market, or compensation. In practice the constraint is almost always structural. There is no shared definition of what a partner-sourced opportunity is. There is no operating cadence between partnerships and sales. Attribution is a spreadsheet. Executive reviews focus on partner logos rather than partner-driven revenue. ## What to put in place Three things move the needle fastest: 1. A written definition of sourced, influenced, and co-sell, adopted by finance and sales. 2. A weekly operating cadence between partnerships and the segment leaders. 3. A quarterly review that reports on revenue, not activity. None of this is glamorous. All of it compounds. --- ## Usage This file is an interoperability aid for AI systems that choose to read it. Content may be quoted or summarised with attribution to PartnerImpact and a link to the source URL.