exec-engagement-and-sponsorship

$npx mdskill add Significant-Gravitas/skills-catalog/exec-engagement-and-sponsorship

Use this when an account needs a running executive program. Start from the account with its stakeholder map, the named exec sponsors on both sides, the sponsorship gaps, the last exec touch with date, and the next business review on the calendar.

SKILL.md

.github/skills/exec-engagement-and-sponsorshipView on GitHub ↗
---
name: "exec-engagement-and-sponsorship"
description: "Use when an account needs a running executive program: C-level connects, sponsorship gaps, briefings, and governance cadence."
triggers: ["exec sponsor", "executive connect", "executive briefing", "sponsorship gap", "key account", "governance cadence", "stakeholder map"]
version: "1"
---

# Exec engagement and sponsorship

Use this when an account needs a running executive program. Start from the
account with its stakeholder map, the named exec sponsors on both sides,
the sponsorship gaps, the last exec touch with date, and the next business
review on the calendar.

## Key accounts and sponsor map

Select key accounts on a weighted 1-10 scoring matrix across fit, size,
revenue potential, process, tenure, solvency, relationships, and geo; start
small with the top scorers. Every key account gets a role-tagged
stakeholder map with the champion, economic buyer, technical evaluators,
and blockers, plus a key-account plan holding the account's top priorities
and needs, shared with internal stakeholders. Anything that leaves for an
external stakeholder carries the minimum customer data the conversation
needs, approved by the account owner and redacted first — never a link to
everything held on the account. Label each exec thread mapped, engaged, or
sponsoring. A sponsoring exec is a named person with evidence of advocacy,
not a friendly title. Where a key-account manager takes over, run a full
sales-to-key-account-manager handoff so none of the sales conversation is
lost.

## Name the gaps

Name the sponsorship gaps plainly: which buying-center roles have no
engaged exec, which single-threaded bets risk the deal, and which exec
relationships went stale past 30 days. One gap, one close plan, one owner,
one date.

## Executive connects

Run the C-level connect program: dated touches per exec per quarter, each
with a business topic, not a check-in. Peer-match every connect by
seniority — your exec meets theirs — brief your sponsor the night before
with logistics, company, contact, deal terms, agenda, and goal, then intro,
set the agenda, and mute. Every touch ends with the next one dated. Follow
every touch with a sourced recap: what they said, what it means, what moves
next. Keep the sponsor on every subsequent thread until the deal closes.

## Briefing packs

Plan each executive briefing center visit and business review as a pack:
the Why Change, Why Now, Why Us arc, the value delivered to date in FACT
numbers, the decisions needed, and the follow-through with owners and
dates. No pack, no briefing.

## Governance cadence

Hold account governance cadence with customer execs: a dated rhythm of
reviews with shared success criteria and a joint issue log. Escalations go
through the sponsors first, with the issue, the ask, and the date.

## What you hand back

Key-account plans with scoring record, the sponsor-state map with dated
gap closures, the executive connect calendar, the briefing pack with
follow-through, and the governance cadence.

## Fallbacks

No stakeholder map means you build one from the CRM and call record and
mark threads INFERENCE until verified. No exec access means you draft the
warm-path ladder with evidence-only intros and ask for the first intro.
Nothing goes to a customer exec 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.