PRESENTS · MAVEN COHORT 2 · SESSION 4 OF 5
SAT JUN 13, 2026 · 12:00 PM EDT
Deploy &
make the case
From your CoS to your team's. From routine to runtime.
Today: MCP · the supply chain · Dispatch · Computer Use · Shark Tank Round 1
CO-INSTRUCTORS
S
Sandhiya Thiruvengadam
Leader, HRBP & AI · Apexon
Q
Q Hamirani
Chief People Officer, Highlevel · Adjunct Faculty, LBS
Session 4 · Slide 1/15
What you shipped this week
Three Routines now firing on schedule. Three HR leaders running systems, not chatbots.
A PEOPLE LEADER · COHORT 2
"My Friday-recap routine fired
at 5 PM. It pulled the week's
decisions from Granola and
posted to my Slack. I cried."
SHIPPED:
routines/friday-recap.md
Granola → Slack DM @5PM Friday
WHAT BROKE:
First run pulled too much. Tightened
prompt to "5 decisions max."
A PEOPLE LEADER · COHORT 2
"Morning briefing every weekday
at 7. By Wednesday my team
asked how I was suddenly
remembering everything."
SHIPPED:
routines/morning-brief.md
0 7 * * 1-5 · Slack DM
NEW QUESTION:
"How do I get Claude to also pull
from Outlook?" → today's MCP slide.
A PEOPLE LEADER · COHORT 2
"Exit-interview synthesizer.
Runs the morning after every
exit. My CHRO read the first
one and called it 'unusual.'"
SHIPPED:
routines/exit-synth.md
Triggered, not scheduled · Hook fired
FIRST PRODUCTION USE:
CHRO is now reviewing the framework.
This is "make the case" landing.
PATTERN
Three routines built last week became three "make the case" moments. Today: how to scale that.
↩ HOME Session 4 · Slide 2/15
Today's path
Open the kitchen. Make the pitch. Round 1 of Shark Tank.
1
RECAP + MAP
Where you are · the back of house opens
2
ANATOMY
MCP · the standard that connects everything
3
THE TRIO
API vs Connector vs MCP · learn the difference
4
HANDS-ON
Install your first MCP server · live
5
DISPATCH + COMPUTER
Parallel sub-agents + Claude drives a browser
6
MAKE THE CASE
Executive Objection Framework · 5 common pushbacks
7
SHARK TANK ROUND 1
12 pitches · 90 seconds each · 3 advance
MODULE 4 · OUTCOME
"I can connect Claude
to my actual data,
and pitch it to the
people who can scale it."
BY THE END OF TODAY
✓ 1 MCP server connected to your CoS
✓ Executive pitch drafted
✓ Shark Tank R1 pitch delivered (90 sec)
✓ Restaurant Map: 9 of 9 zones met
Next week (Session 5): your capstone showcase.
↩ HOME Session 4 · Slide 3/15
How to use Claude · the restaurant
Same map. Back of house opens today. The kitchen is the heart of the operation.
FRONT + BACK · 4 NEW ZONES OPEN TODAY
✓ DONE ① CHAT
Chat
Session 1
✓ DONE ② PROJECT
Claude Project
Session 2
✓ DONE ③ THE FILE ON YOU
CLAUDE.md
Session 2 · loaded every session
✓ DONE ④ SKILLS
Skills
Session 1
✓ DONE ⑤ ROUTINES
Routines
Session 3 · 1+ firing daily
YOU ARE HERE ⑥ DISPATCH
Dispatch
parallel sub-agents
"Research 5 candidates at once."
Met today · Slide 8.
YOU ARE HERE ⑦ COMPUTER USE
Computer Use
Claude drives a browser
"Pull 20 PDFs and tag them."
Met today · Slide 8.
YOU ARE HERE ⑧ HOOKS
Hooks
what fires after every meal
"After every reply, log to Notion."
One-mention today · Slide 9.
⑨ BACK OF HOUSE · TODAY'S MAIN EVENT
YOU ARE HERE APIs · Connectors · MCP
Slides 5 + 6 + 7 = anatomy, trio, hands-on install.
By Slide 11 you've got 1 MCP server connected to your CoS. Routine 2 next week pulls live data.
API Connector MCP
DOORS ↔ ZONES
Door 1 ✓ · Door 2 ✓ · Door 3 = NOW (zones ⑥⑦⑧⑨ all open today). Tomorrow: capstone with everything lit.
↩ HOME Session 4 · Slide 4/15
Anatomy of an MCP server
One standard. Any tool. Any model. Here's what's inside a working MCP server config.
~/.claude/mcp-servers/granola/server.json
5 THINGS THIS SERVER DOES
1
{
2
"name": "granola-mcp",
3
"version": "1.0.0",
5
"transport": "stdio",
7
"capabilities": {
8
"tools": true,
9
"resources": true
10
},
12
"tools": [
13
"list_meetings",
14
"get_transcript",
15
"search_meetings",
16
"get_notes_from_meeting"
17
],
19
"resources": [
20
"granola://meetings/recent",
21
"granola://folders/{folder}"
22
],
24
"auth": {
25
"type": "oauth2"
26
}
27
}
⚙
SERVER METADATA · name + version
⚙
TRANSPORT · how Claude reaches the server
⚙
CAPABILITIES · what this server can do
⚙
TOOLS · functions Claude can CALL
⚙
RESOURCES · data Claude can READ
⚙
AUTH · how the server proves it's you
NEW WORD ↑
MCP = Model Context Protocol. Open standard so any model (Claude, GPT, etc.) can plug into any tool with one shared shape. Think of it as "USB for AI." Slide 6 unpacks it.
★ HOW THIS TRANSLATES TO YOUR STACK
same idea, different brand · pick the door your company already pays for
★ CLAUDE · RECOMMENDED
MCP (native protocol)
MICROSOFT COPILOT
Copilot Connectors · Microsoft Graph Connectors
GOOGLE GEMINI
Gemini Extensions · Workspace integrations
OPENAI CHATGPT
GPT Actions · OpenAPI plugins
↩ HOME Session 4 · Slide 5/15
API · Connector · MCP · the three things
Three different things that all let Claude talk to your data. Restaurant analogy fixes the confusion.
A
THE FIRST THING
API
RESTAURANT ANALOGY
The kitchen's order window.
Say this format, get that dish.
WHAT IT IS
A contract a service exposes.
Call this URL with this shape,
get back this shape.
EXAMPLE
GET /api/users/123
→ { "name": "Sandhiya" }
WHO USES IT DIRECTLY
Developers writing code.
Not you (in this course).
YOUR TAKEAWAY
"APIs are the doors."
C
THE FAMILIAR ONE
Connector
RESTAURANT ANALOGY
A waiter trained for ONE kitchen.
Pre-built. Knows that menu cold.
WHAT IT IS
A pre-built adapter that wraps
ONE specific API for use inside
a specific platform.
EXAMPLES
· Claude's Slack connector
· Microsoft's Outlook connector
· Zapier's 7,000 connectors
WHO USES IT
You. Today. With one click.
YOUR TAKEAWAY
"One waiter per kitchen. Stuck inside one platform."
M
THE NEW STANDARD
MCP
RESTAURANT ANALOGY
Universal staff-training standard.
Any waiter can serve any kitchen.
WHAT IT IS
An open protocol so ANY model
(Claude, GPT, etc.) can talk to
ANY tool through ONE shape.
EXAMPLES
· Granola MCP (your transcripts)
· Drive MCP (your files)
· Slack MCP (your messages)
WHO USES IT
You. Today. In Claude Code.
YOUR TAKEAWAY
"USB for AI. Plug once, works anywhere."
CHEAT SHEET
API = the door. Connector = a waiter trained for one door. MCP = a universal pass that opens any door.
↩ HOME Session 4 · Slide 6/15
Install your first MCP · live
7 minutes. Open Claude Code. Connect Granola. Watch your CoS suddenly see all your meetings.
★ LIVE BUILD · FOLLOW ALONG
~/my-cos · claude code
$ cd ~/my-cos
$ claude mcp add granola
Fetching MCP server from anthropic/mcp-servers...
✓ Found granola-mcp v1.0.0
✓ Installing dependencies...
✓ Server registered to .claude/mcp.json
Opening browser for Granola OAuth...
✓ Authorized · token saved
$ claude mcp list
ACTIVE SERVERS:
● granola-mcp · 4 tools · 2 resources
tools: list_meetings, get_transcript,
search_meetings, get_notes_from_meeting
$ claude
› What did the CHRO say in Tuesday's 1:1 about
the comp band changes?
reading: granola://meetings/recent
✓ found 1 match · "CHRO 1:1 Tue Jun 10"
reading: granola://meeting/{id}/transcript
★ She said comp band changes are "directionally
right but timing is wrong." Slow the rollout.
source: CHRO 1:1 · Jun 10 · 14:23-14:31
THE 4-STEP INSTALL
1
cd into your CoS folder
The same one from Session 3.
2
claude mcp add granola
Or slack, drive, gmail · whichever first.
3
OAuth in the browser
Click "allow." Token saves locally.
4
Ask Claude a real question
"What did X say about Y in last week's meeting?"
CLEAR CHECK
✓ Consent · OAuth, granted by you
✓ Limits · token scoped to read-only
✓ Explainable · cites the source meeting
✓ Auditable · .claude/mcp.json tracks it
✓ Reversible · claude mcp remove granola
YOUR ROUTINE (NEXT WEEK)
"Every Friday 5PM, pull the week from
Granola and synthesize." → now possible.
↩ HOME Session 4 · Slide 7/15
Door 3, advanced · Dispatch + Computer Use
Two more zones from the kitchen. You won't build these today. You should know they exist.
⑥
THE RUNNER
Dispatch
WHAT IT DOES
Claude spawns N parallel sub-agents on one job.
Each does part of the work. Results merge.
HR EXAMPLE
"Research 5 candidates for the L7 role."
Dispatch:
→ sub-agent 1: research Asha Patel
→ sub-agent 2: research Daniel Kim
→ sub-agent 3: research Mia Roman
→ sub-agent 4: research Chen Wei
→ sub-agent 5: research Layla Hassan
✓ all 5 returned in 90 seconds
Merging into briefing...
★ comparison table ready
WHEN YOU'LL REACH FOR IT
Long-running parallel research. Bulk synthesis. Comparison work.
⑦
THE KITCHEN LINE
Computer Use
WHAT IT DOES
Claude drives a virtual browser like you would.
Clicks, scrolls, fills forms. You watch.
HR EXAMPLE
"Pull 20 PDFs from Workday and tag them."
Claude Computer:
opens workday.com
navigates to Reports
filters: department = Sales
downloads 20 review PDFs
reads each, extracts ratings
builds calibration spreadsheet
✓ done in 14 minutes (you didn't click once)
★ requires confirmation for sensitive actions
WHEN YOU'LL REACH FOR IT
Vendors with no API. Bulk repetitive UI work. Workday + similar.
RULE OF THUMB
If the data is behind an MCP, use MCP. If it's only behind a browser, use Computer Use. Always require confirmation before sensitive actions.
↩ HOME Session 4 · Slide 8/15
Hooks · what fires after every meal
Zone ⑧ in one slide. Not deep today. Know they exist · use them later.
WHAT IS A HOOK?
A shell command that fires
automatically when Claude
does something specific.
RESTAURANT ANALOGY
What happens after every meal:
· table gets cleared
· receipt is printed
· tip is logged
· kitchen restocks
ONE HR EXAMPLE
"After every Claude reply, log it
to /audits/audit-trail.md."
Now your compliance trail builds itself.
CLEAR governance "Auditable" · solved.
.claude/hooks/post-reply.sh
1
#!/bin/bash
2
# Fires after every Claude reply
4
TIMESTAMP=$(date -u +"%Y-%m-%dT%H:%M:%SZ")
5
SUMMARY=$1
7
echo "$TIMESTAMP · $SUMMARY" \
8
>> audits/audit-trail.md
10
git add audits/audit-trail.md
11
git commit -m "audit: $TIMESTAMP"
13
exit 0
REGISTER IN CLAUDE.md
hooks:
post-reply: .claude/hooks/post-reply.sh
Done. Now every reply auto-logs.
Your CLEAR "auditable" requirement just got solved by 14 lines of bash.
DON'T BUILD ONE TODAY
Hooks are the deepest zone. Know they exist. We come back to them in Cohort 3 or in the post-cohort office hours.
↩ HOME Session 4 · Slide 9/15
Make the case · 5 objections you'll hear
Going from your laptop to the company is a different game. Here's the playbook (from Cohort 1).
OBJECTION 1
"What if it hallucinates
comp data?"
YOUR RESPONSE
"Three guardrails: it ONLY reads from approved
MCP servers (Workday, etc.), it CITES every
number with source, and it WAITS for me on
anything sensitive. Show me an example?"
OBJECTION 2
"Legal won't approve
it touching PII."
YOUR RESPONSE
"My data classification is 4-Level. L3+ data
stays in our SOC2 stack only. CLEAR governance
framework gives them an audit trail. Let me
walk legal through it."
OBJECTION 3
"This will replace HR
jobs eventually."
YOUR RESPONSE
"It replaces the parts of my job I hate:
copy-pasting, summarizing, scheduling. It
gives me back time for what HR is actually
for: humans. That's a feature."
OBJECTION 4
"What's the ROI?"
YOUR RESPONSE
"$20/month Claude Pro + ~30 hours saved per
month per HRBP on synthesis and prep =
payback in week 1. I have a tracking spreadsheet.
Want to see this quarter's numbers?"
OBJECTION 5
"How does this scale
across the team?"
YOUR RESPONSE
"It's a markdown file and a connector. I share
the file, they swap their working-style doc in,
they install the same connector. Onboarding
is 30 min not 6 months. Want a pilot?"
YOUR 90-SEC PITCH
1. Problem (in your role)
2. What you built (live demo if
possible)
3. Time saved · with numbers
4. The 1 risk you've controlled
5. The ask: pilot, budget, time
→ Shark Tank Round 1 starts in 10 minutes.
↩ HOME Session 4 · Slide 10/15
🦈 Shark Tank · Round 1
Twelve pitches · 90 seconds each · three advance to the capstone showcase.
FORMAT
90 seconds · 12 pitches
1
90 seconds · zero filler
Use Slide 10's 5-beat script. We hold the line.
2
Live demo encouraged
Share screen, show your CoS or routine running.
3
Three judges vote per pitch
Sandhiya, Q, plus one guest CHRO.
4
Top 3 advance to Round 2
Capstone showcase · Session 5 · Sat Jun 20.
5
Everyone gets written feedback
Posted in cohort chat within 48 hours.
6
No prize · just clarity
The prize is the pitch you now have for your CHRO.
JUDGING RUBRIC
5 criteria · 1-5 each
1 · PROBLEM CLARITY
Did they name a real, specific HR pain?
2 · BUILD CRAFT
Did the demo actually work? Production-ready?
3 · TIME SAVED
Did they quantify? With real numbers, not vibes?
4 · RISK CONTROL
CLEAR + data classification visibly applied?
5 · THE ASK
Did they make a clear, concrete ask?
TIE-BREAKER
"Which one would I actually want to ship at my org next quarter?"
That's the question Q and Sandhiya are asking.
↩ HOME Session 4 · Slide 11/15
Pick your path · commit before Saturday
Capstone is the celebration · not the choice. Pick now · share your commit on Saturday.
PATH A
Scale inside your org
Take your CoS + your pitch deck.
Pilot it on your HR team.
FIRST 3 STEPS
1. Send the pitch deck to your CHRO this week
2. Ask: "Can 3 HRBPs pilot this in July?"
3. Plan a 30-min onboarding workshop
BEST FOR YOU IF
Your CHRO is curious and your time-saved
numbers are real. You enjoy the politics.
POST-COHORT SUPPORT
Sandhiya office hours · 1st Wed/month · 60 min.
Bring your pitch deck · we'll workshop it.
PATH B
Go deeper as a builder
Build your own MCP server.
Custom Hooks. Skill packs to share.
FIRST 3 STEPS
1. Clone the Anthropic Cookbook this week
2. Build a custom MCP server for YOUR stack
3. Open-source it · post in #builders
BEST FOR YOU IF
You liked Claude Code more than expected.
You want to teach Cohort 3 someday.
POST-COHORT SUPPORT
Q office hours · 1st Mon/month · 90 min.
Code review · MCP architecture · builder talk.
PATH C
Lead the conversation
Write. Speak. Run workshops.
Become the AI-for-HR voice in your network.
FIRST 3 STEPS
1. Write one LinkedIn post about your CoS
2. Volunteer a 30-min internal session
3. Apply to speak at one HR conference in '26
BEST FOR YOU IF
You want to redefine what HR leadership
looks like. You've been asked to speak before.
POST-COHORT SUPPORT
GPL community · monthly virtual mic.
Sandhiya + Q will both amplify your work.
★ COMMIT THIS WEEK · BEFORE SATURDAY JUN 20
Post your path letter (A / B / C) + one sentence why in #cohort-2 by Friday Jun 19.
At capstone we celebrate your commits · no judgment · no upgrade path. Some people pick all three over time. Today, pick one.
↩ HOME Session 4 · Slide 12/15
🤖 Use AI Now · this week
Two things by Friday Jun 19: a 2nd MCP installed + a pitch deck draft.
TASK 1 · DUE WED JUN 17
Connect MCP #2
Pick the data source you reach for most.
Slack, Drive, Gmail, Outlook, Workday, Greenhouse, Lever.
RECIPE
$ claude mcp add [server-name]
$ claude mcp list
Then ask a real question that uses both your
Granola MCP and the new one. See what happens.
SHARE
Screenshot the surprising answer. Show one peer.
Caption: which MCP + the moment it clicked.
CLEAR check before you install: Consent (you own the data), Limits (read-only),
Reversible (one command to remove).
TASK 2 · DUE FRI JUN 19
Pitch deck draft
For your actual leadership team.
Use the 5-beat script from Slide 10. 5 slides max.
THE 5 SLIDES
1. The problem in your role
2. What you built (screenshot/demo link)
3. Time saved · numbers · before/after
4. CLEAR risk frame (what you control)
5. The ask (pilot, budget, time, sponsor)
CLAUDE HELP
› Help me turn this CoS into a 5-slide
pitch for my CHRO using the 5-beat
script in Maven Session 4.
CAPSTONE FUEL
Bring this deck to capstone (Sat Jun 20).
Everyone presents. Everyone learns from everyone.
↩ HOME Session 4 · Slide 13/15
Take these with you · Session 4 pack
MCP registry · Cookbook · slash commands cheat sheet. Bookmark all of these.
🗺
EXTERNAL · ANTHROPIC
MCP Server Registry
100+ MCP servers · search by tool, by category.
Granola, Slack, Drive, Gmail, Outlook, Notion, Workday.
URL · mcp.anthropic.com
📕
EXTERNAL · ANTHROPIC
Claude Cookbook
Real-world workflows · 40+ recipes you can fork.
Includes a "build your own MCP server" walkthrough.
URL · github.com/anthropics/cookbook
🎤
PITCH TEMPLATE · IN MAVEN HOME
Executive Pitch · 5 slides
5-slide Keynote/PowerPoint template + the 5-beat script.
Pre-filled with the 5 objections from Slide 10.
FILE · exec-pitch-template.pptx
📋
CHECKLIST · IN MAVEN HOME
MCP Install Checklist
CLEAR check + first prompt to try + rollback plan.
Use before every new connector.
FILE · mcp-install-checklist.md
SLASH COMMANDS · THE 5 YOU'LL USE
Type "/" in Claude Code to see them all
/init
create CLAUDE.md from scratch
/compact
compress context · long sessions
model picker
Sonnet 4.6 ⇄ Opus 4.7 thinking
/ultraplan
multi-step plan before coding
/ultrareview
multi-agent code review
WHEN TO USE EACH
/init — first time setting up Claude Code in a folder. Generates CLAUDE.md from a guided interview./compact — when your terminal session gets long. Claude summarizes the chat and starts fresh with the summary.model picker — Sonnet 4.6 for fast everyday. Switch to Opus 4.7 with Extended Thinking for hard problems./ultraplan — before any non-trivial change. Forces Claude to write a plan first so you can correct it before any code runs./ultrareview — after you ship. Multi-agent review of the diff. Catches things one Claude misses.Don't memorize. Type "/" and read the menu.
SAVE THIS SLIDE
Everything we cited today, plus your slash commands cheat sheet, in one place. Your post-cohort starter kit.
↩ HOME Session 4 · Slide 14/15
Where you are · one to go
Capstone next Saturday. Everyone presents. Everyone learns. Bring your build.
✓ DONE SESSION 1 · MAY 16
Start where you are
· 9-zone map intro
· Anatomy of a Skill
Shipped:
✓ 1 Skill · CLAUDE.md draft
✓ DONE SESSION 2 · MAY 30
Build the AI for you
· CoS Stack anatomy
· SCALE · Connectors
Shipped:
✓ CoS v1 · Claude Code
✓ DONE SESSION 3 · JUN 6
Make it safe to ship
· Anatomy of a Routine
· Sandhiya CoS + Q ATS
Shipped:
✓ 1 Routine · git commit
★ TODAY SESSION 4 · JUN 13
Deploy + the case
· Anatomy of MCP
· Supply Chain Trio
· Dispatch · Computer Use
· Pitch round (today)
Ship by Fri Jun 19:
→ MCP #2 connected
→ Pitch deck draft
"Kitchen is open."
NEXT WK SESSION 5 · JUN 20
Capstone
· Final Restaurant Map
all 9 zones lit
· Everyone presents · 4 min each
· Peer review · pick 3 to learn from
· Graduation
You'll ship:
→ Live capstone demo
NEXT WEEK · SESSION 5 · CAPSTONE SHOWCASE
"See you Saturday, June 20, 12:00 PM EDT for graduation."
Bring: your CoS, your pitch deck, your favorite Routine, your hardest question. Everyone presents · 4 minutes each · peer review by all.
★ NOT A CONTEST · A LEARNING ROUND · YOU PICK 3 BUILDS YOU'LL STEAL
↩ HOME Session 4 · Slide 15/15
SESSION 4 DECK · COHORT 2
Cohort 2 is in the room.Session 4 — Deploy & make the case. These slides walk through it live with Q & Sandhiya. Cohort members sign in to open the deck; everyone else: catch Cohort 3.
ALREADY IN COHORT 2?
Welcome back. The deck loads behind the sign-in.
SIGN IN WITH YOUR INVITE →
WATCHING FROM OUTSIDE?
Cohort 3 opens later this summer. We'll save you a seat.
CATCH COHORT 3 →