playbooks

home / skills / gtmagents / gtm-agents / partner-revenue-desk

partner-revenue-desk skill

/plugins/partnership-development/skills/partner-revenue-desk

This skill helps forecast partner-sourced revenue and automate attribution workflows across RevOps, finance, and partner teams for aligned incentives.

npx playbooks add skill gtmagents/gtm-agents --skill partner-revenue-desk

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
1.2 KB
---
name: partner-revenue-desk
description: Operating model for tracking, attributing, and accelerating partner-sourced
  revenue.
---

# Partner Revenue Desk Skill

## When to Use
- Forecasting partner-sourced/ influenced revenue for leadership updates.
- Monitoring incentives, SPIFs, and MDF utilization tied to partner pipeline.
- Coordinating RevOps, finance, and partner teams on attribution disputes.

## Framework
1. **Revenue Taxonomy** – sourced vs influenced vs co-sell, stage definitions, SLAs.
2. **Process Flow** – intake → validation → attribution → approval → reporting.
3. **Data Stack** – CRM objects, PRM integrations, BI dashboards, alerting.
4. **Incentive Hooks** – payout rules, MDF governance, exception workflows.
5. **Escalation Paths** – playbooks for disputes, double counting, or compliance risks.

## Templates
- Revenue desk runbook with RACI + cadence.
- Attribution audit checklist.
- MDF utilization tracker with projected ROI.

## Tips
- Align definitions with finance early; lock requirements before launching SPIFs.
- Automate alerts for stalled partner deals to keep velocity high.
- Pair with `build-co-sell-playbook` and `run-partner-qbr` for closed-loop reporting.

---

Overview

This skill implements an operating model for tracking, attributing, and accelerating partner-sourced revenue. It bundles playbooks, data patterns, and automation guidance to ensure consistent partner attribution, incentive governance, and operational handoffs. The goal is predictable partner revenue measurement and faster dispute resolution across RevOps, finance, and partner teams.

How this skill works

The skill codifies a revenue taxonomy and a process flow that moves partner opportunities from intake through validation, attribution, approval, and reporting. It specifies required CRM and PRM objects, BI dashboards, and alerting hooks so pipelines, MDF, and SPIFs are measured and surfaced reliably. Templates and escalation playbooks enable repeatable audits, incentive payouts, and dispute resolution.

When to use it

  • Forecasting partner-sourced and partner-influenced revenue for executive updates
  • Monitoring SPIFs, MDF utilization, and incentive compliance tied to partner pipeline
  • Coordinating attribution disputes between RevOps, finance, and partner management
  • Standardizing intake and validation of partner-sourced opportunities
  • Automating alerts for stalled partner deals to protect partner velocity

Best practices

  • Define and align revenue taxonomy (sourced vs influenced vs co-sell) with finance before launching incentives
  • Implement intake validation rules and SLAs to prevent double counting and ambiguous attribution
  • Instrument CRM and PRM objects to feed BI dashboards and alerting — avoid manual spreadsheets
  • Use RACI-based runbooks and regular cadence to keep stakeholders synchronized
  • Create escalation playbooks for disputes, compliance risks, and edge-case payouts

Example use cases

  • Run weekly partner revenue forecasts for the leadership team with attributed pipeline and expected close rates
  • Audit MDF spend against projected ROI and reclaim or reallocate unused funds
  • Resolve credit disputes quickly by following an attribution audit checklist and escalation path
  • Automate SPIF payouts once attribution and opportunity milestones are validated
  • Integrate PRM partner registration data with CRM to ensure consistent attribution downstream

FAQ

How does this skill prevent double counting between sourced and influenced revenue?

It prescribes a clear taxonomy, intake validation rules, and CRM flags that lock attribution at a defined point. Escalation playbooks handle overlaps and enforce a single-source-of-truth for reporting.

What data objects are required to implement the model?

Core objects include partner registration records, opportunity partner roles, MDF/SPIF transactions, attribution reason codes, and synced PRM events feeding BI dashboards and alerting.