PRESENTS · SESSION 4 · PART 2 · WIRE IT UP SAT JUN 13, 2026 · 12:00 PM EDT Deploy & make the case From your spec to your real data. From a plan to a working tool. Today: connect Claude to your real data, bundle it, and ship one workflow. ← PART 1 · START WITH THE PROBLEM CO-INSTRUCTORS S Sandhiya Thiruvengadam Leader, HRBP & AI · Apexon Q Q Hamirani Chief People Officer, Highlevel · Adjunct Faculty, LBS Session 4 · Part 2 · Slide 1/12
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 the end of today you have one connector wired to your build. API Connector MCP DOORS ↔ ZONES Door 1 ✓ · Door 2 ✓ · Door 3 = NOW (zones ⑥⑦⑧⑨ all open today). Tomorrow: capstone with everything lit. ↩ HOME Session 4 · Part 2 · Slide 2/12
Today's path. You have a spec. Three simple moves to make it real. No code required. 1 CONNECT Give Claude your real data connectors let it reach your Slack, Drive, Gmail, the sheet the INPUT in your spec, made live 2 BUNDLE Package it, and share it a plugin holds your whole kit. Claude even ships an HR one. one move, the whole team has it 3 SHIP Pick one workflow and sharpen it not ten. One you run every week, made worth keeping the one you hand to your team By the end: Claude reaches your real data, and you have one workflow worth keeping. ↩ HOME Session 4 · Part 2 · Slide 3/12
Connectors: it's just like plugging in. Four words you'll hear. Here's the whole thing, on one plug. API the shape of the socket the contract a service exposes. Developers use it, not you. Connector a cable for one device pre-built for ONE service. One click. (Claude's Slack connector.) MCP USB-C: one shape fits all the universal plug. Any AI to any tool. This is the one that matters. Plugin a docking station bundles your cables and tools into one unit you install and share. Only two to remember: MCP, the universal plug. Plugin, the dock that holds your kit. ↩ HOME Session 4 · Part 2 · Slide 4/12
Claude already ships an HR plugin. The same HR tasks from Part 1, draft an offer, build an onboarding plan, look up a policy, already bundled. HUMAN RESOURCES · BY ANTHROPIC · BUILT IN 9 skills, ready to run /draft-offer · /onboarding · /comp-analysis /performance-review · /policy-lookup · /people-report 5 connectors Slack · Google Calendar · Gmail · Notion · Atlassian Try asking "Draft an offer letter for a new hire" "Look up a company policy in plain language" THE WHOLE IDEA Install it as-is. Or build your own. A plugin is just your skills + connectors, bundled. ↩ HOME Session 4 · Part 2 · Slide 5/12
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 · Part 2 · Slide 6/12
Install your first MCP · live 7 minutes. Open Claude Code. Connect Granola. Watch your AI suddenly see all your meetings. ★ LIVE BUILD · FOLLOW ALONG ~/my-project · claude code $ cd ~/my-project $ 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 project folder The one from Part 1. 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 · Part 2 · Slide 7/12
Door 3, advanced · Dispatch + Computer Use Browse only. You won't build these today, just know they exist for when you need them later. ⑥ 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 · Part 2 · Slide 8/12
The whole kitchen, at a glance. Everything you've met across the five weeks. You don't need all of it. WHAT YOU BUILD Skilla saved recipe Claude can run Routinea saved task it does for you Scheduleruns on its own, on a clock your spec becomes one of these HOW IT REACHES YOUR DATA Connectorreaches one service, one click MCPthe universal plug, any service APIthe dev plumbing underneath two words matter: MCP, Plugin SHARE IT · AND THE DEEP END Pluginyour whole kit, bundled and shared Hooksfires something after Dispatchmany helpers at once Computer Usedrives a browser for you the deep end is for later You don't need all of it. You need the one that fits your spec. ↩ HOME Session 4 · Part 2 · Slide 9/12
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 → This is the pitch you now have for your CHRO. ↩ HOME Session 4 · Part 2 · Slide 10/12
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 Wire it up · Connectors, the USB way · Claude's HR plugin · Anatomy of MCP · Dispatch · Computer Use Your sharper build: → install the HR plugin → wire one connector "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 spec, your build, 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 · Part 2 · Slide 11/12
Leave with one sharper build. Two ways. Pick one. No pitch, no judges, just one thing that works. OPTION A · THE QUICK WIN Install the HR plugin It already ships with Claude. Turn it on, run one skill on a real task today. "Draft an offer letter." "Look up our PTO policy." lowest friction. A win in ten minutes. OPTION B · THE CONNECTED BUILD Connect one source Take your Part 1 spec. Wire in ONE data source, Slack, Drive, Gmail, the sheet. Run the workflow once. Watch it reach real data. your spec, now live. THEN NAME IT Your 1 or 2 use cases. The tool for each. That's your clarity. Tip: type "/" in Claude Code to see the shortcuts. Bring your build to Session 5. ↩ HOME Session 4 · Part 2 · Slide 12/12
End of Session 4 · Part 2. You shipped. Now keep the muscle warm. ★ NEXT SESSION Session 5 · Capstone · graduation Saturday June 20, 2026 · 12:00 PM EDT · live on Maven OPEN DECK → Between now and then · 10 minutes a day on Atlas 30. Ship one thing. ↩ HOME End of Session 4 · Part 2
SESSION 4 · PART 2 · 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.

WATCHING FROM OUTSIDE?

Cohort 3 opens later this summer. We'll save you a seat.

CATCH COHORT 3 →
🏠 1 / 14