The Executive Access Workshop

A 60-Minute Team Working Session Where Reps Earn C-Level Meetings With Business Outcomes Not Product Tours

Why Run This Session

Executives take meetings about risk, money, and peer outcomes—not feature tours. Reps who ask champions to "set up a demo with your CEO" get ghosted because the ask has no business reason and no executive time respect.

Executive access is earned with a ninety-second outcome narrative, peer proof, and one decision—not with slideware. Deals that need C-level sponsorship for budget or risk must be flagged early; deals that do not should not waste executive calendar.

This workshop drafts the narrative, practices champion routing with forwardable blurbs, and logs exec meetings only where the agenda ends in a decision.

Managers who skip this ritual pay for it in forecast calls: reps defend numbers they cannot tie to buyer-side evidence or CRM artifacts. Running the session quarterly keeps new hires from inheriting bad habits from shadow pipeline—and gives RevOps a consistent field to audit when conversion or stage velocity drops.

The hour is not enablement theater; it is the minimum viable discipline before you scale headcount or raise quota.

What Reps Will Walk Out With

• Ninety-second executive narrative (outcome, peer proof, one ask) peer-critiqued
• Forwardable champion blurb drafted for one live enterprise deal
• Twenty-five-minute exec agenda with explicit decision line
• List of anti-patterns posted to team channel
• CRM updated with Exec Meeting Needed flag and target date

Who Should Be in the Room

Enterprise AEs and sales manager; SEs optional for fact-checking proof points. Each AE brings one deal that genuinely requires executive sponsorship (budget, risk, strategic alignment)—not every mid-market opp.

Before the Meeting (Manager Prep — 15 Minutes)

1. Collect two anonymized exec-meeting agendas that ended in a decision vs. One that became a demo.
2. Enablement shares approved peer proof stories with metrics—no unverified claims.
3. Manager identifies which deals in pipeline incorrectly lack exec strategy.
4. Confirm CRM field Exec Meeting Status or equivalent.

The 60-Minute Agenda

This session runs 0:00 to 1:00. The agenda blocks below sum to exactly 60 minutes.

Frame — Features vs. Executive Risk (0:00–0:08, 8 minutes)

Read a failed exec-request email that asks for a product tour. Manager says: "Executives fund risk reduction and peer outcomes—your ask must match."

Facilitator script: Poll: who has an exec meeting on calendar with a written decision line? Count hands.

CRM setup (first two minutes): Flag deals >$X ARR with Exec Meeting Needed = Yes where strategy missing.

Close this block: Share anti-pattern list starter: demo request, roadmap dump, unpaid consulting.

Timer and room mechanics (Frame — Features vs. Executive Risk): Keep the countdown visible. At the halfway mark, pause only for CRM confirmation—not for open discussion.

Facilitator circulate: Walk the perimeter; sit with the quietest pair first. Ask each rep to show their screen: opportunity updated, task logged, or worksheet row complete before they earn the break. If someone finishes early: They peer-review a partner's CRM entry or listen for the pair role-play—never email or Slack.

Manager line to repeat: "The artifact in CRM is how we know this hour worked—not attendance." Energy: Stand during pair work; sit only for solo CRM writing. These norms keep the block dense and protect the sixty-minute boundary.

Outcome Headline & Peer Proof (0:08–0:20, 12 minutes)

Template: "We help [peer type] achieve [metric] in [timeframe]." Strip product nouns. Pair proof must include number and peer segment.

Facilitator script: Manager rejects three volunteer headlines live—team learns the bar.

Live demo in CRM: Store approved narrative in opportunity note Exec Narrative v1.

Manager checkpoint: Enablement validates proof claims against case study library.

Timer and room mechanics (Outcome Headline & Peer Proof): Keep the countdown visible. At the halfway mark, pause only for CRM confirmation—not for open discussion. Facilitator circulate: Walk the perimeter; sit with the quietest pair first.

Ask each rep to show their screen: opportunity updated, task logged, or worksheet row complete before they earn the break. If someone finishes early: They peer-review a partner's CRM entry or listen for the pair role-play—never email or Slack. Manager line to repeat: "The artifact in CRM is how we know this hour worked—not attendance." Energy: Stand during pair work; sit only for solo CRM writing.

These norms keep the block dense and protect the sixty-minute boundary.

Champion Routing & Agenda Build (0:20–0:35, 15 minutes)

Draft forwardable blurb and 25-minute agenda: context (5), peer story (10), decision (10). Silent write then pair review.

Facilitator script: Manager says: "If the champion cannot forward it without editing, rewrite."

CRM action (required before timer ends): Log Task: Send champion blurb by [date]; attach agenda doc link.

Circulate and challenge: Cut any agenda item that is product feature depth.

Timer and room mechanics (Champion Routing & Agenda Build): Keep the countdown visible. At the halfway mark, pause only for CRM confirmation—not for open discussion. Facilitator circulate: Walk the perimeter; sit with the quietest pair first.

Ask each rep to show their screen: opportunity updated, task logged, or worksheet row complete before they earn the break. If someone finishes early: They peer-review a partner's CRM entry or listen for the pair role-play—never email or Slack. Manager line to repeat: "The artifact in CRM is how we know this hour worked—not attendance." Energy: Stand during pair work; sit only for solo CRM writing.

These norms keep the block dense and protect the sixty-minute boundary.

Role-Play — Champion Says No (0:35–0:48, 13 minutes)

Partner A is busy champion pushing back on exec time. Partner B practices routing and shrinking ask. Swap.

Facilitator script: Timebox to three minutes per side—force concise responses.

Pair exercise rules: Champion may only object with realistic reasons from your deals.

CRM action after swap: If no path, mark deal Not Ready for Exec—do not fake pipeline.

Timer and room mechanics (Role-Play — Champion Says No): Keep the countdown visible. At the halfway mark, pause only for CRM confirmation—not for open discussion. Facilitator circulate: Walk the perimeter; sit with the quietest pair first.

Ask each rep to show their screen: opportunity updated, task logged, or worksheet row complete before they earn the break. If someone finishes early: They peer-review a partner's CRM entry or listen for the pair role-play—never email or Slack. Manager line to repeat: "The artifact in CRM is how we know this hour worked—not attendance." Energy: Stand during pair work; sit only for solo CRM writing.

These norms keep the block dense and protect the sixty-minute boundary.

Anti-Patterns & Slack Post (0:48–0:56, 8 minutes)

Team completes anti-pattern list; owner posts to #sales within the hour. Add "exec meeting without decision" as pipeline review flag.

Facilitator script: Two volunteers read blurbs aloud for group approval.

Capture on whiteboard: Capture top five anti-patterns.

Each rep commits: Each AE states exec meeting target date or Nurture reason.

Timer and room mechanics (Anti-Patterns & Slack Post): Keep the countdown visible. At the halfway mark, pause only for CRM confirmation—not for open discussion. Facilitator circulate: Walk the perimeter; sit with the quietest pair first.

Ask each rep to show their screen: opportunity updated, task logged, or worksheet row complete before they earn the break. If someone finishes early: They peer-review a partner's CRM entry or listen for the pair role-play—never email or Slack. Manager line to repeat: "The artifact in CRM is how we know this hour worked—not attendance." Energy: Stand during pair work; sit only for solo CRM writing.

These norms keep the block dense and protect the sixty-minute boundary.

Close — CRM Exec Discipline (0:56–1:00, 4 minutes)

Round-robin: deal, exec ask in one line, champion send date.

Facilitator script: Manager says: "Exec hold without CRM note equals no credit."

Forecast / pipeline tie-in: Enterprise commit requires exec strategy field populated.

Manager records in CRM or tracker: Manager report: enterprise opps missing exec narrative note.

Timer and room mechanics (Close — CRM Exec Discipline): Keep the countdown visible. At the halfway mark, pause only for CRM confirmation—not for open discussion. Facilitator circulate: Walk the perimeter; sit with the quietest pair first.

Ask each rep to show their screen: opportunity updated, task logged, or worksheet row complete before they earn the break. If someone finishes early: They peer-review a partner's CRM entry or listen for the pair role-play—never email or Slack. Manager line to repeat: "The artifact in CRM is how we know this hour worked—not attendance." Energy: Stand during pair work; sit only for solo CRM writing.

These norms keep the block dense and protect the sixty-minute boundary.

Agenda check: 8 + 12 + 15 + 13 + 8 + 4 = 60 minutes.**

Worksheet / Artifact

How to Use This With the Buyer

1. Give the champion a blurb they can paste—reduces friction and rewrites.
2. Open the exec meeting with their priority metric, not your company history.
3. End with one decision: approve pilot scope, sponsor business case, or align on risk mitigation.
4. Send a one-page follow-up that mirrors the agenda decisions, not a sixty-slide deck.

Manager Coaching Notes

• Reject vague adjectives in outcome headlines—manager enforces on the spot.
• No exec meeting without champion path documented in CRM.
• Post anti-patterns in Slack; reference in deal review when exec access fails.
• Do not schedule exec time for deals that only need technical validation.
• Log exec meetings as activities with decision outcome within 24 hours.

The Bottom Line

Executive calendar is a scarce resource. Reps who show up with outcomes, peer proof, and one decision earn access; reps who request demos get deferred forever. This workshop makes the narrative and routing repeatable before quarter-end enterprise commits.