Agent skill
partner-revenue-desk
Operating model for tracking, attributing, and accelerating partner-sourced revenue.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/development/partner-revenue-desk-gtmagents-gtm-agents
SKILL.md
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
- Revenue Taxonomy – sourced vs influenced vs co-sell, stage definitions, SLAs.
- Process Flow – intake → validation → attribution → approval → reporting.
- Data Stack – CRM objects, PRM integrations, BI dashboards, alerting.
- Incentive Hooks – payout rules, MDF governance, exception workflows.
- 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-playbookandrun-partner-qbrfor closed-loop reporting.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?