t0ddc3by/claude-for-customer-success/executive-summary

/renewals:executive-summary [VALIDATED]

Strategic account renewal summary calibrated for executive audiences.

Use when

• A strategic account renewal requires executive sponsorship and you need a brief formatted for CRO, CEO, or board consumption
• You are preparing materials for a board or investor reporting package that includes renewal pipeline exposure
• An escalated renewal is being handed to executive leadership and they need commercial status, relationship health, and a specific recommended action without raw signal data
• You have completed /renewals:risk-assessment for an account and need to translate that risk tier into executive-ready language

Do NOT use for

• CSM-level internal prep — use /renewals:negotiation-prep for call preparation and concession authority
• Customer-facing renewal proposals — use /renewals:negotiation-prep --export for proposals the customer will see
• Risk scoring without a specific account in hand — use /renewals:risk-assessment first
• Accounts that do not meet your configured strategic account threshold (deal size or segment)

Typical Activation

/renewals:executive-summary Acme Corp — full internal executive summary for a named strategic account

/renewals:executive-summary Acme Corp --brief — condensed brief: commercial status, risk tier, and recommended executive action only

/renewals:executive-summary Acme Corp --board — board-format version with anonymization if account identity is not authorized for external sharing

Pre-flight

Read both configuration files before building any executive summary:

1. ~/.claude/plugins/config/claude-for-customer-success/renewals/CLAUDE.md
2. ~/.claude/plugins/config/claude-for-customer-success/company-profile.md

If either file is missing or contains [PLACEHOLDER] markers in fields this skill requires (GRR/NRR targets, customer segments, escalation matrix, company name, executive contacts), stop:

"Your renewals company profile isn't configured — specifically the company

profile and executive contact fields. Run /renewals:cold-start-interview

to configure these. An executive summary built without your actual targets

and company context will require significant manual editing before it's

usable."

Fields read from config:

• Company name and brand (for header)
• Customer segments and deal size tiers (for strategic account qualification)
• GRR and NRR targets (for target gap framing)
• Escalation matrix — Head of CS, CRO, CEO contacts (for recommended action)
• AE partner (for co-sponsorship context)
• Negotiation posture (affects how risk and save strategy are framed)

G-code dependency: All G-code guardrails referenced in this skill (G1–G9) are defined in the CLAUDE.md config loaded above. If Pre-flight halts or config is missing, G-codes are undefined — do not proceed with partial config.

Reasoning Protocol

Before generating output, apply these primers:

1. CLASSIFY: What type of executive summary request is this?

• Escalation Brief: Account is High/Critical risk, executive intervention needed within days. Optimize for specificity of the ask and urgency of the timeline.
• Sponsorship Request: Renewal requires sustained executive co-sponsorship — QBR participation, relationship rebuild, or strategic partnership signal over weeks.
• Portfolio / Board Roll-Up: Account included in board materials, investor briefings, or strategic portfolio reviews. Audience is non-operational; strip relationship detail.
• Proactive Visibility: Account meets strategic threshold but is on track — executive awareness without action. Clearly signal "no action needed" and name next checkpoint.

1. CONSTRAINTS: What limits the solution space?

• G4: Revenue commitment language — every ARR figure flagged [review — not yet a revenue commitment]; Finance/RevOps review required before distribution to leadership or board.
• G5: Confidentiality gradient — --brief and --full are internal-only; --board strips relationship detail; confirm audience authorization before generating.
• G7: Executive asks must name a specific person, specific action, and specific date — "executive involvement needed" is not an ask.
• Escalation routing must use the configured escalation matrix with named owner — no generic "escalate to your manager."
• Value claims require account-specific evidence — generic value language undermines executive credibility.

1. EXPERT CHECK: What would a veteran CRO or Head of CS verify first?

• Does the bottom line stand alone in two sentences — would an executive who reads nothing else know the situation and what's being asked of them?
• Is the risk tier imported from /renewals:risk-assessment, not re-derived independently? If no prior assessment exists, flag that explicitly.
• Does the "what executive involvement changes" section articulate what the executive achieves that the CSM cannot — or is it just requesting presence?

1. ANTI-PATTERNS: Common mistakes to avoid:

• ❌ Vague executive ask — "We need CRO support" without naming who calls whom, about what, by when.
• ❌ Risk drivers stated as domain labels ("engagement is low") instead of specific data points ("no executive sponsor contact in 120 days").
• ❌ Including customer-specific relationship detail or save strategy language in --board output.
• ❌ Shipping --full mode with generic value language instead of downgrading to --brief with the gap flagged.
• ❌ Including unconfirmed competitive intelligence — hedged competitive context is worse than omission.
• ❌ Manufacturing urgency for on-track accounts — prompting unnecessary executive intervention on a healthy renewal.

After execution, verify:

• Does the summary pass the two-sentence test — can the bottom line stand alone?
• Are all ARR figures flagged with [review — not yet a revenue commitment]?
• Is the output mode (brief/full/board) matched to the actual audience, not just the requested mode?
• Confidence: [High] if CRM + risk-assessment data corroborate / [Medium] if single-source or partially stale / [Low] if user-provided context only — state which.

What makes an account eligible for executive summary

An executive summary is warranted when one or more of the following applies:

• ARR at or above the strategic account threshold configured in your profile
• Account is at High or Critical risk tier (from /renewals:risk-assessment)
• Executive escalation has been requested by either side
• The renewal requires CRO or CEO involvement to close
• The account is being included in board or investor materials
• A competitor displacement threat is confirmed

If none of these apply:

"This account doesn't appear to meet the strategic account threshold for

an executive summary. Consider /renewals:negotiation-prep or

/renewals:risk-assessment instead — or confirm that executive visibility

is needed here before proceeding."

Mode

--brief (default): One-page executive summary — commercial status, risk tier, key relationship signals, recommended executive action, and one clear ask. Appropriate for CRO weekly review or escalation routing brief.

--full: Extended summary — all --brief content plus competitive context (if applicable), relationship timeline, value delivered summary, and proposed executive engagement plan. Appropriate for accounts requiring active executive co-sponsorship or QBR preparation with the customer's executive.

--board: Board or investor format — narrows to: ARR at stake, risk level, current trajectory, and one recommended action. No customer-specific relationship detail. Uses only language appropriate for board audiences. Appropriate for board materials, investor briefings, and strategic account portfolio summaries.

Account identification and data pull

Ask: "Which account is this executive summary for? Provide the account name, and tell me the ARR, renewal date, current risk tier (if known), and any signals you want me to include."

If a CRM connector is available, pull:

• ARR and product tier
• Renewal date and days remaining
• Opportunity stage
• Escalation history (prior escalations, who was involved, outcomes)
• Executive sponsor and champion records
• Open support tickets or unresolved escalations
• Prior renewal history (tenure, prior renewals, expansion history)

If a risk assessment has already been run:

"Import the risk tier from /renewals:risk-assessment output if available —

this summary should reflect the same tier, not re-derive it independently."

Confirm the pull:

"[CRM]: [account name] · $[ARR] · renewal [date] · [N] days out ·

risk tier: [Critical/High/Medium/Low from risk-assessment or 'not yet assessed']

· data as of [timestamp]"

Executive summary content — --brief

The brief format is a single-page document structured for a 90-second read. Every section should be answerable in 1–3 sentences. Do not pad.

Section 1 — Bottom line

State the commercial situation and recommended executive action in two sentences. This is the first thing the executive reads; it must stand alone if they read nothing else.

"[Account name] ($[ARR]) renews [date] and is currently [on track / at risk

/ in active negotiation / escalated]. The recommended executive action is

[specific: e.g., 'a call from [CRO name] to [Economic buyer name] this week'

/ 'executive sponsor engagement before [date]' / 'no action needed at executive

level at this time']."

Section 2 — Commercial status

Section 3 — Relationship health

Surface the signals an executive needs — not the full domain breakdown from risk-assessment. Keep to what's relevant for the executive action being recommended.

Champion: [Name, title] — [engaged / disengaged / recently changed]

Economic buyer: [Name, title] — [aware of renewal / not yet engaged / leading negotiation]

Executive sponsor: [Name, title] — [active / departed / not yet identified]

Key signal: [One sentence — the single most important relationship fact

the executive should know. Examples: "The economic buyer is new and hasn't

built a relationship with our team." / "The champion left 60 days ago and has

not been replaced." / "The executive sponsor has been vocal about value."]

Section 4 — Risk summary

If risk tier is Low or Medium:

"No executive action required. CSM is managing the renewal through the

standard motion. [1 sentence on what would change this assessment.]"

If risk tier is High or Critical:

"Risk drivers: [2–3 specific signals — not domain summaries, specific

data points. Examples: 'Login activity dropped 40% in 90 days' / 'Competitor

evaluation confirmed by champion on [date]' / 'No executive sponsor contact

in 120 days']"

"Current save strategy: [What the CSM is doing — specific, not generic]"

"What executive involvement changes: [Specific: what an executive call or

email from [name] accomplishes that the CSM cannot. Don't ask for executive

involvement without a specific reason.]"

Section 5 — Recommended executive action

State the action clearly. One of:

Outreach ask: "[CRO / CEO / Head of CS] — a [call / email] to [Economic buyer name / Executive contact] by [date]. Purpose: [specific: relationship check-in / strategic partnership signal / negotiation support]. Draft available on request."