Skip to content
Back to skills

Size Partner Sourced Pipeline

ASecurity

Size partner-sourced vs partner-influenced pipeline with a defined attribution rule, so the program number is one finance trusts and nothing is double-counted with direct. Reach for this before any partner-revenue claim.

  • 7 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 23, 2026
ai-agentsrust

Security analysis

A100/100

Scanned September 23, 2026

npx -y skills add mcorbett51090/RavenClaude --skill size-partner-sourced-pipeline --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Size Partner Sourced Pipeline?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Size Partner Sourced Pipeline
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/mcorbett51090-size-partner-sourced-pipeline/badge)](https://www.skillsdirectory.com/skills/mcorbett51090-size-partner-sourced-pipeline)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: size-partner-sourced-pipeline
description: "Size partner-sourced vs partner-influenced pipeline with a defined attribution rule, so the program number is one finance trusts and nothing is double-counted with direct. Reach for this before any partner-revenue claim."
---

# Skill: Size partner-sourced pipeline

Sourced ≠ influenced; conflating them inflates the program and burns trust (§3 #1).

## Step 1 — Write the attribution rule down first
Define **sourced** (partner originated the opportunity — registered before direct engagement) and **influenced** (partner touched a deal direct already had). Pick one rule and state it; the rule matters more than the number.

## Step 2 — Classify the pipeline
Tag each open opportunity sourced / influenced / direct using the rule and the deal-registration timestamps. Ambiguous deals default to influenced, never sourced.

## Step 3 — Compute both numbers separately
Report partner-**sourced** pipeline and ARR against a baseline, and partner-**influenced** separately. Never sum them into one "partner pipeline" figure.

## Step 4 — Reconcile against the direct number
Confirm sourced deals are not also counted in a rep's direct quota attainment — reconcile with `sales-revops` so the company number isn't double-counted.

## Step 5 — Report the conversion
Add deal-registration → closed-won conversion and the sourced-ARR trend, each with a definition and window ([`../../knowledge/partnerships-kpi-glossary.md`](../../knowledge/partnerships-kpi-glossary.md)).

## Output
A sourced/influenced split with the written attribution rule, partner-sourced ARR vs a baseline, deal-reg conversion, and a reconciliation note confirming no double-count with direct. Every metric ships with a definition and window.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…