Before — email notification
10%
response rate. Buried in an inbox, no urgency signal, easy to defer — and defer becomes never.
13 sessions · 22.5 hours · 1.5 CSTU semester credit hours
Whether it's a stakeholder group waiting on your group manager, a community that skims your newsletter, or a lead list that never opens your email — broadcast channels have a ceiling. This course teaches the workflow that removes it: direct, personalized outreach to every single person, engineered to get a response without a meeting.
The evidence
Before — email notification
10%
response rate. Buried in an inbox, no urgency signal, easy to defer — and defer becomes never.
After — automated Slack outreach
70%
engagement within 24 hours. Direct, personalized, and specific enough that a stakeholder can act on it in under 30 seconds.
What participants ship
A Claude Code–driven Slack workflow that replaces batch email notifications with personalized, direct messages to individual stakeholders.
Your own before/after numbers — not a vendor's case study. Track the gap between email and direct outreach on your actual program.
The workflow packaged so your team can run it after the course ends — not a one-off automation only you understand.
Curriculum
22.5 hands-on hours over 6.5 weeks, twice a week — built directly on your own stakeholder list, not a generic demo dataset.
You leave with: A documented baseline of your own communication failure, in numbers
Tools · Your current notification history, reviewed with Claude Code
You leave with: A working Slack integration ready to send messages
Tools · Slack API and webhook basics, workspace setup
You leave with: An agent that sends one round of personalized outreach
Tools · Claude Code agent scaffold — read a list, draft a message per recipient
You leave with: Messages that reference live status and blockers, not generic templates
Tools · Connecting your agent to the data source that already tracks your program
You leave with: A two-way loop — the agent sends, captures, and logs the response
Tools · Structured decision capture: approve / block / escalate
You leave with: A cadence and escalation policy your agent enforces automatically
Tools · Follow-up timing logic that stays urgent without becoming noise
You leave with: Segmented messaging logic — executives, ICs, and partners get different shapes
Tools · Audience-type branching inside your agent
You leave with: A dashboard showing your own before/after numbers
Tools · Response-rate and time-to-decision tracking, built by hand
You leave with: Instructor and peer feedback on your live, measured numbers — not just your build
Tools · A working demo of your agent against your own real data
You leave with: A reusable Skill your team can run without you in the room
Tools · `skill-creator` — package the workflow so it outlives this course
You leave with: A scaling plan for using this beyond your original pilot
Tools · Permissions, rate limits, and privacy handling for outreach at scale
You leave with: A one-page business case with your own numbers
Tools · Translating the response-rate lift into time saved and decisions accelerated
You leave with: A live demo and a portfolio-ready before/after case study
Tools · The full arc — diagnosis, build, measured lift, and business case — presented end to end
Who this is for
The mechanism isn't specific to program management — it's specific to broadcast versus direct. The same workflow applies wherever a group has stopped responding to batch messages:
You already know who you need to reach and what you need from them. What's missing isn't access — it's a channel that gets a response. This course assumes you can describe your audience in plain language and have (or can get) a workspace on the platform they already live in.
Get started