onboard-and-enable-partners

$npx mdskill add Significant-Gravitas/skills-catalog/onboard-and-enable-partners

Use this when an agreement is signed. Start from the partner, the agreement model, the named owner on each side, portal and training access, and the first joint motion.

SKILL.md

.github/skills/onboard-and-enable-partnersView on GitHub ↗
---
name: "onboard-and-enable-partners"
description: "Use when a partner agreement is signed: run the 30/60/90 onboarding arc, stand up the enablement kit, and plan the first co-marketing motion."
triggers: ["onboard a new partner", "partner 30/60/90 arc", "partner enablement kit", "partner kickoff agenda", "welcome package for a partner", "partner certification path", "first co-marketing motion"]
version: "1"
---

# Onboard and enable partners

Use this when an agreement is signed. Start from the partner, the
agreement model, the named owner on each side, portal and training
access, and the first joint motion.

## Start inside five business days

Enablement starts within five business days of signature with a Day 1-5
kickoff: a timed two-hour agenda covering introductions, goals, access,
and the first motion.

Then set the arc and file it where the owner actually looks:

- Days 0-30: discovery, portal access, core training, the welcome package
  (guide, contacts, logins, incentives), and a co-authored joint business
  plan — why, goals, benchmarks, how the two sides work, how success gets
  measured.
- Days 31-60: certification or shadowed calls, plus the first joint
  demand motion.
- Days 61-90: the first joint win, a pipeline review, and the
  next-quarter plan.
- Month 6: an independence check — are they selling without training
  wheels.
- Month 12: a plan revisit with year-two goals.

One owner on each side. Every milestone dated.

## Stand up the kit, tiered by model

A reseller gets the full playbook; a referral partner gets a one-pager.
The full kit is: a pitch sheet their sellers can use this week, a
battle card against the top competitor (Legal-reviewed), a demo script, a
return-on-investment calculator, case studies, an FAQ, a security pack,
three qualifying questions with exact wording, the top three objections
with a one-paragraph answer each, and training with tiered certifications
— Foundation passes at 80, Pro at 85, Expert at 90 — expiring at twelve
months with mini-certifications on each release.

Only certified sellers lead co-sell. Each artifact names its owner and
its refresh date, and refreshes inside five days of any release. Name the
response SLA for partner requests while you are at it.

## Plan the first co-marketing motion

One dated item — a webinar, a joint post, or an event — with who brings
the audience, who makes the asset, and how spend and market development
fund (MDF) claims work.

Check the MDF fiscal-year expiry, and reallocate unspent or
underperforming funds quarterly on documented results. An undated idea
stays a backlog line, never a commitment.

## Run the health checks

At each 30-day mark: milestones hit, certification progress, first
pipeline. A miss gets a dated rescue line with an owner, not silence.

## What you hand back

The 90-day arc with owners and dates, the enablement kit list, the first
co-marketing item, and the health-check schedule.

## Fallbacks

No portal or learning system yet means the arc runs on documents and live
sessions, and you name the access gap at the top. 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.