build-partner-led-category-creation

$npx mdskill add Significant-Gravitas/skills-catalog/build-partner-led-category-creation

Use this when the market needs a new category and no single vendor can name it alone. Start from the market shift the category rides, the lighthouse partners and analysts in play, the existing joint proof (wins, numbers, quotes), and the launch window and budget.

SKILL.md

.github/skills/build-partner-led-category-creationView on GitHub ↗
---
name: "build-partner-led-category-creation"
description: "Use when the market needs a new category no single vendor can name alone: the category thesis, the lighthouse coalition, and the launch beats."
triggers: ["category thesis", "lighthouse coalition", "category name tests", "analyst briefing plan", "lightning strike launch", "shared narrative with partners", "category signals"]
version: "1"
---

# Build partner-led category creation

Use this when the market needs a new category and no single vendor can
name it alone. Start from the market shift the category rides, the
lighthouse partners and analysts in play, the existing joint proof (wins,
numbers, quotes), and the launch window and budget.

## Write the category thesis in one page

The shift. The old way and why it breaks. The new way in one sentence.
The written point of view the coalition evangelises — world changed, old
way broken, new way, stakes — which has to be true even if we did not
exist. The category name with its ownability tests: analyst adoption, the
budget-line-item test, and the would-this-have-an-encyclopedia-entry-in-
three-years test. And the three proof points that must exist before
launch.

Each claim names its evidence or stays UNKNOWN. A thesis with no named
shift is positioning, not a category.

## Build the coalition

At most five lighthouse partners, each with a named executive sponsor and
a dated commitment. Two analysts briefed early. One lighthouse customer
per partner where possible.

Each member gets a role — proof, reach, or credibility — and a dated
deliverable. A member with no dated deliverable is a logo, not a
coalition partner.

## Run the joint narrative and the proof

One shared story every partner tells. Objection-mapped proof:
closest-customer-first, every number sourced, partner claims kept in
their own words.

Then a dated beat plan — analyst briefings, the joint launch, lighthouse
wins, event moments.

Proof the owner has not approved stays internal. Nothing partner-facing
leaves without the owner's yes.

## Strike once, then compound in beats

One ignition moment three to six months after the point of view lands —
broad reach plus direct outreach, aimed at the category rather than the
product — with 30-day success criteria written before it fires.

Then dated beats, each with an owner per side, a success line, and a
recap inside 48 hours with owners and dates.

After launch, track the category signals quarterly — analyst mentions,
inbound using the name, win-rate lift — against a year-one, year-two,
year-three flywheel, and reallocate beats toward what moves. A beat that
misses twice gets one fix, then it is cut.

## What you hand back

The one-page thesis, the coalition roster with its dated commitments, the
shared narrative with its proof, and the beat plan with its recaps.

## Fallbacks

No lighthouse partners yet means thesis first, with coalition seats
marked UNKNOWN for the owner to fill. No budget means a proof-first plan
— the narrative plus one lighthouse win — before any launch beat.

No thesis, narrative, proof, or launch beat goes to a partner, an
analyst, or the public without your explicit 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.