expansion-opportunity-brief

$npx mdskill add Significant-Gravitas/skills-catalog/expansion-opportunity-brief

Use this when an account may need more scope, seats, products, or services.

SKILL.md

.github/skills/expansion-opportunity-briefView on GitHub ↗
---
name: "expansion-opportunity-brief"
description: "Assess an expansion opportunity from customer need and usage evidence without turning weak signals into a sales claim."
triggers: ["expansion opportunity", "upsell", "cross-sell", "account growth", "more seats"]
version: "1"
---

# Expansion opportunity brief

Use this when an account may need more scope, seats, products, or services.

## Require a customer signal

Look for an explicit request, repeated limit, new team or use case, sustained
adoption near capacity, stated goal the current scope cannot meet, or approved
account plan that cites one of these customer signals. An account plan with no
documented customer signal is **needs evidence**. Cite the source and period. High usage alone is not permission to
sell, and low usage is not an expansion case.

## Build the brief

State the customer need, observed evidence, people affected, present workaround,
possible fit, value hypothesis, disconfirming evidence, product or delivery
gaps, and questions to validate. Mark price, availability, roadmap, and terms
unknown unless approved sources support them.

Use **ready to validate**, **needs evidence**, or **not a fit now**. Recommend
one customer question and one internal check.

Do not invent demand, savings, product capability, or customer intent. Do not
promise an offer or send outreach without approval.

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.