run-the-partner-co-sell-cadence

$npx mdskill add Significant-Gravitas/skills-catalog/run-the-partner-co-sell-cadence

Use this for the weekly operating rhythm with an active partner. Start from the partner and the joint plays, CRM movement since the last call, the deal registration log, and the open actions from last time.

SKILL.md

.github/skills/run-the-partner-co-sell-cadenceView on GitHub ↗
---
name: "run-the-partner-co-sell-cadence"
description: "Use for the weekly operating rhythm with an active partner: prep the call, keep deal registration honest, and rescue stuck joint deals."
triggers: ["weekly partner call prep", "deal registration hygiene", "stuck joint deal", "partner rescue play", "register this partner deal", "partner ask this week", "reverse registration"]
version: "1"
---

# Run the partner co-sell cadence

Use this for the weekly operating rhythm with an active partner. Start
from the partner and the joint plays, CRM movement since the last call,
the deal registration log, and the open actions from last time.

## Prep the call, most-stuck-first

What moved, what stalled, and one action per side per stuck deal. When
several partners share one prep, take the deepest pipeline first.

Layer the rhythm underneath: weekly updates, bi-weekly joint opportunity
reviews, quarterly business planning. Score partner fit per opportunity
before co-selling anything, and name the sellers on our side who actually
evangelise the partner — then propose quota relief or accelerators on
co-sold deals to the owner rather than assuming the partner side is
motivated on its own.

## Keep deal registration honest

The eligibility bar comes first: net-new, BANT-qualified — budget,
authority, need, timeline — and the partner in good standing.

Track every registration through Submitted, In-review, Approved, or
Action required with the reviewer's comments attached. Decide inside two
business days, with a reminder at one and an escalation at two. Protect
for 90 days, alert 7 days before expiry, and allow exactly one 30-day
renewal on logged activity with sign-off. Never auto-renew. Where the
program's published rules differ from these defaults, the program rules
win — cite them.

Every claimed deal names its registration identifier and date, its state,
its window, and its conflict check. Closes need a Closed-Lost reason.

Pre-write the edge rulings so nobody improvises them live: multi-partner
splits, the customer picking a different partner, and reverse
registrations — the qualified lead shells we hand to partners.

Flag duplicates, expired windows, and registrations with no activity
behind them. Abuse gets named, not smoothed over.

## Rescue stuck joint deals with exactly one motion

Diagnose in order: champion gone, buyer cold, competitor in, paper
process, partner deprioritised. Then name the one move, its owner, its
date, and what happens if it fails.

Anything that needs direct-sales closing goes to the account executive
with a clean brief. You never close it yourself.

Run a quarterly prune alongside the rescues: cut partners with no
strategic match and no delivery, and file the quarterly conflict report
with its count and its first-to-register sustained rate.

## Close with one partner ask

The single thing we need from them this week. One ask, not a list.

## What you hand back

The call prep (moved, stalled, actions), the registration hygiene list,
the rescue lines, and the one partner ask.

## Fallbacks

No CRM movement to read means you prep from the last call notes and the
open actions, and say the data is stale rather than inventing progress.
Nothing partner-facing leaves without your yes.

More from Significant-Gravitas/skills-catalog

SkillDescription
account-health-and-qbrsUse when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
accounts-receivable-follow-upReview open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.
ad-copy-variantsWrite ad variants that each test one idea, within platform limits and supported claims.
alex-getting-startedUse on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.
alliance-co-commercializationUse when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.
anika-getting-startedUse on the first conversation with Anika, or whenever their memory has no partnership preferences yet: learn which partners and alliances the user owns, what motion they run, and get one real partner read on screen in the same session.
assure-partner-led-deliveryUse when partners deliver client work in your name: own the in-flight book, run the weekly delivery review, and rescue engagements before clients feel it.
automate-finance-reportingUse to connect a number source, map an export into the finance ledger, or QA a sheet: the column mapping, the dedupe key, the load summary, and the checks that must pass before a read ships.
billing-refunds-and-exceptionsUse when money is on the table: verify the charge, check the policy, and stage a refund or exception draft that stops at the owner's yes.
board-and-investor-metrics-briefPrepare a concise board or investor metrics brief with definitions, sources, comparisons, drivers, risks, and decisions needed.