executive-engagement-playbook
Skill0 starsChanged 8 months agoMITView on GitHub
Framework for when and how to involve executives -- yours and the customer's -- in the account relationship. Covers timing, framing, preparation, and follow-through for executive engagement at renewal, expansion, escalation, and strategic alignment points. Use when asked about executive engagement strategy, when to go high, how to involve leadership, how to prepare for an executive meeting, or when a situation warrants moving beyond the CSM-level relationship. Also triggers for questions about executive sponsorship, VP-level engagement, C-suite involvement, strategic account elevation, or when leadership involvement could unlock an outcome the CSM cannot achieve alone.
In this repository57 other files it gives its agents.
- account-strategy-builderSkill
- account-swot-analyserSkill
- action-item-extractorSkill
- book-prioritisationSkill
- business-review-frameworkSkill
- call-summary-generatorSkill
- capacity-calculatorSkill
- career-dev-plannerSkill
- celebration-note-writerSkill
- change-management-advisorSkill
- check-in-email-drafterSkill
- churn-post-mortemSkill
- competitive-threat-assessorSkill
- contract-review-assistantSkill
- cs-investment-case-builderSkill
- cs-metrics-explainerSkill
- customer-apology-crafterSkill
- customer-sentiment-decoderSkill
- difficult-conversation-drafterSkill
- escalation-brief-writerSkill
- escalation-decision-frameworkSkill
- executive-briefing-writerSkill
- executive-outreach-drafterSkill
- expansion-opportunity-scorerSkill
- follow-up-email-writerSkill
- goal-setting-frameworkSkill
- handoff-intro-emailSkill
- internal-debrief-writerSkill
- internal-status-update-writerSkill
- interview-prep-csSkill
- manager-one-on-one-prepSkill
- manual-health-assessmentSkill
- meeting-agenda-builderSkill
- meeting-outcome-loggerSkill
- multi-threading-playbookSkill
- nps-response-analyserSkill
- objection-handlerSkill
- onboarding-plan-builderSkill
- peer-coaching-guideSkill
- pre-call-prepSkill
- presentation-personaliserSkill
- pricing-conversation-frameworkSkill
- process-audit-worksheetSkill
- qbr-action-trackerSkill
- qbr-content-assemblerSkill
- quarterly-planning-builderSkill
- re-engagement-email-writerSkill
- renewal-conversation-openerSkill
- renewal-risk-scorerSkill
- save-play-designerSkill
- stakeholder-map-builderSkill
- stakeholder-research-prepSkill
- success-plan-creatorSkill
- territory-transition-plannerSkill
- usage-pattern-interpreterSkill
- value-narrative-builderSkill
- week-plannerSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 26
Not every situation warrants executive involvement.
- Distinctive: line 135
Do you have a specific ask for the engagement?
- Distinctive: line 138
Do you have a follow-up plan?
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Executive Engagement Playbook
Framework for knowing when to involve executives (yours and the customer's) and how to make that involvement productive. Going high is a high-leverage tool used sparingly. Overuse devalues it. Underuse leaves outcomes on the table that only executive relationships can unlock.
How to Use
Provide:
- The account situation (what is happening and why executive involvement might help)
- Who you are considering involving (from your side and from the customer's side)
- What outcome you need that the CSM-level relationship cannot deliver
- The current state of executive relationships at this account (existing or non-existent)
- Any risks or sensitivities (the customer's executive is difficult, your executive has no context, the timing is sensitive)
When to Engage Executives
Not every situation warrants executive involvement. The decision framework:
When Executive Engagement Is High-Value
| Situation | Why Executives Help | What to Avoid |
| Strategic renewal (top 10% ARR) | Signals commitment from your company. The customer's executive wants a peer relationship | Do not bring an executive in for a routine renewal. It sets a precedent you cannot sustain |
| Expansion opportunity (significant ARR growth) | Executive-to-executive alignment accelerates the deal and provides air cover for the budget | Do not use executive engagement as a sales tactic. It is a relationship play, not a closing technique |
| Active escalation (P1, extended, or trust-damaging) | Executive acknowledgement signals the severity of your response. The customer's frustration needs a higher-level outlet | Do not bring an executive in before you have a resolution plan. Executive acknowledgement without a path forward is worse than CSM accountability alone |
| Champion departure at a strategic account | Executive continuity bridges the gap. The relationship survives at a higher level while you rebuild at the operational level | Do not wait until the account is at risk. Executive engagement should happen within days of the departure, not weeks after the relationship erodes |
| Competitive threat (decision-imminent stage) | Executive commitment can be the tiebreaker. A call from your VP to their VP signals partnership depth the competitor cannot match | Do not use executive engagement as a last resort when the deal is already lost. It signals desperation, not partnership |
| Annual strategic alignment | Once per year, an executive check-in reinforces the relationship and ensures strategic alignment beyond the operational level | Do not make this a product demo or a sales pitch. It is a strategic conversation about the partnership |
When Not to Engage Executives
| Situation | Why Not | What to Do Instead |
| Routine account management | Overuse of executive engagement devalues the channel. The customer's executive will stop taking your executive's calls | Handle at the CSM level. Build the relationship before you need it |
| Product feature request | Executives do not resolve feature requests. Product teams do | Escalate through the product team via ic-escalation-router |
| CSM cannot get a response from a contact | Going over someone's head to get a response destroys the relationship | Try a different channel, a different contact, or a direct conversation about the silence |
| To impress the customer | The customer can tell when executive engagement is performative | Earn the relationship through value delivery, not through title inflation |
Preparation Framework
Executive involvement without preparation wastes the most expensive resource in the building. Prepare thoroughly.
For Your Executive
They need to walk into the interaction knowing:
| Prep Element | Content | Why |
| One-pager account brief | ARR, health, relationship history, the current situation, what you need | They have 5 minutes of prep time. Give them the story in one page |
| The ask | What specifically you need them to do or say | "Have a strategic conversation" is not a brief. "Ask their VP whether the renewal is on track from their perspective and reinforce our commitment to the API roadmap" is |
| Landmines | Topics to avoid, sensitivities, past failures | Nothing is worse than your executive stepping on a landmine you could have flagged |
| Success criteria | How you will know the engagement worked | "They agree to a quarterly executive check-in" or "They commit to the renewal timeline" -- specific and measurable |
For the Customer's Executive
They need a reason to engage that serves their interest:
| Framing | Works For | Example |
| Value visibility | CFOs, CROs who need ROI evidence | "I wanted to ensure you had visibility into the value your team is delivering with our product" |
| Strategic alignment | VPs, C-suite who care about where the partnership is going | "I wanted to discuss how our roadmap aligns with your priorities for next year" |
| Issue resolution | Executives frustrated by an unresolved problem | "I understand the [issue] has not met your expectations. I want to discuss our resolution plan directly" |
| Partnership deepening | Executives who value vendor relationships | "As one of our most important customers, I wanted to establish a direct relationship at my level so you always have a senior point of contact" |
Execution Framework
The Executive Conversation Structure
| Phase | Duration | Content |
| Opening | 2 minutes | Brief rapport. Acknowledge their time. State the purpose. No small talk beyond what they initiate |
| Your executive's perspective | 5 minutes | Your executive shares what they know about the partnership and the value. This validates the investment at a peer level |
| Their executive's perspective | 10 minutes | Listen. Ask what their priorities are. What does success look like from their position? This is the most valuable part of the conversation |
| Forward look | 5 minutes | Align on next steps. What does the partnership look like in the next 12 months? Any concerns from either side? |
| Close | 3 minutes | Confirm any commitments. Set cadence for future engagement (annual, quarterly, or as-needed). Thank them |
Total: 25 minutes. Executive meetings should be tight. If you have 30 minutes, use 25 and give them 5 back. They will remember that more than any data point.
After the Executive Engagement
| Follow-Up Action | Timing | Owner |
| Send a brief thank-you email from your executive to their executive | Within 24 hours | Your executive (you draft it) |
| Send a summary of the conversation to your team | Same day | CSM |
| Update the stakeholder map | Same day | CSM |
| Execute on any commitments made during the conversation | Per commitment timeline | CSM + relevant teams |
| Brief your champion on what was discussed (appropriate level of detail) | Within 48 hours | CSM |
| Schedule the next executive touchpoint (if recurring cadence was agreed) | Within 1 week | CSM |
Output Format
## Executive Engagement Plan: [Account Name]
### Situation
[Why executive engagement is warranted]
### Engagement Type
[Strategic alignment / Escalation response / Renewal / Expansion / Champion departure]
### Your Executive
- Who: [Name, Title]
- Prep needed: [One-pager brief, landmine briefing, specific ask]
### Their Executive
- Who: [Name, Title]
- Framing: [How the meeting is positioned to them]
- Expected priorities: [What they care about]
### The Ask
[Specific outcome you need from this engagement]
### Conversation Plan
[Structured 25-minute agenda]
### Success Criteria
[How you know the engagement worked]
### Follow-Up Plan
[Post-engagement actions with timeline]Quality Gates
- Is executive engagement necessary for this situation, or could you achieve the outcome at the CSM level? The bar should be high. If the answer is "probably not, but it would be nice," do not ask for executive time
- Do you have a specific ask for the engagement? "Have a relationship call" is not a reason to consume executive bandwidth. "Confirm renewal commitment and align on the API roadmap investment" is
- Is your executive prepared? An unprepared executive who asks the wrong question or misrepresents the account state does more damage than no executive involvement at all
- Is the customer's executive expecting the engagement, or will it be a surprise? Surprise executive outreach can feel like escalation over the contact's head. Ensure the path is clear -- ideally through the champion
- Do you have a follow-up plan? Executive engagement without follow-through wastes the relationship capital it generated. Every commitment made must be tracked and delivered
Principles
- Executive engagement is a scarce resource. Use it for moments that materially affect the outcome -- renewals, expansions, escalations, strategic alignment. Do not spend it on situations the CSM should handle
- The customer's executive values their time more than yours. Every minute of the conversation should serve their interest, not just yours. If they walk away thinking "that was useful," you have succeeded. If they walk away thinking "that was a sales call," you have damaged the channel
- Preparation is 80% of the work. A well-prepared executive in a 20-minute meeting creates more value than an unprepared executive in an hour
- Executive relationships compound. The first engagement is the hardest. Once established, the channel exists for future use -- annual check-ins, renewal confirmations, strategic alignment. The investment pays forward
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.