She Leads AI · Social Saturday
Beth and Jen Process Map
How the co-host pair runs Social Saturday from June through December 2026 — topic selection, planning, marketing alignment, live co-hosting, and the experimentation we’ll review at the September check-in. Pulled from the May 23 Beth + Jen planning conversation, not invented.
Engagement
- June through December 2026, seven months
- $500/month split, paid as one unit ($250 each)
- $1,000 signing bonus each, $2,000 total
- Three-month check-in built in for September
- SS events complimentary for Beth and Jen
Roles
- Beth — facilitation structure design, format mechanics, CoP facilitator training
- Jen — operations, inbox, difficult attendees, system access, content-chasing, marketing alignment
- Both — co-host the live sessions, two hosts present for safety
- Speaker sourcing stays in-house with Kate (explicitly out of Beth and Jen’s scope)
Locked
- Jun 6 — first CoP workshop, run by someone else while Beth and Jen observe
- Jun 13 — Layla Townsend + Michelle Muncy-Silva (pending their confirmation)
- Money paid as one path, split internally
- Boot unresponsive male-identifying attendees per women-first rule, with unblock path
Blocked on the SOW
- IP clause for Beth’s facilitation structures (license to use with future hosts)
- Cadence lock — 6 weeks CoP, 4-6 weeks speaker event, or 8-week breathing room
- September check-in mechanics — what it measures, how scope and pay can move
- Woman-of-color co-design gate before format locks (Anne flagged this in the room)
The Co-Host Workflow
Five phases — topic to analysis
Each phase lists who does what, what data moves, and what’s still open. Click a phase to expand. Color coding — coral for Beth’s work, blue for Jen’s work, gold for joint, amber for hand-offs into the main pipeline.
Phase 1
Topic and Format Selection
Rolling — 6 to 8 weeks ahead, set the rhythm
3
2
2
1
Joint Actions
Pick from the format menu — impromptu networking opener, single biggest question, open mic, speaker block (1-2 speakers), CoP workshop, celebrity interview/fishbowl, table topics, affinity rooms
Cap the experiment — pick 2 to 3 formats to actually test, park the rest. Twelve weeks isn’t enough for all eight.
Beth’s Actions
Propose the format for each Saturday and tie it to the rhythm (CoP every ~6 weeks, speaker event every 4-6 weeks, house format on remaining Saturdays)
Recommend the first new format to launch (currently the impromptu networking opener — high value, low risk)
For speaker weeks, propose split — two 20-minute blocks or one 40-minute slot with a mid-session breakout
Jen’s Actions
Surface signal from registration — “single biggest question about agentic AI” prompt collects forward-looking demand instead of speaker preference
Flag holiday weeks and recommend dark or ultra-light (e.g. Jul 4 — don’t debut a flagship on a holiday)
Hand-off
Anne approves the locked format and theme for each Saturday before Phase 2 begins
Data at this stage
SourceSpeakers Sheet (for speaker weeks only — out of B+J scope to source), CREATE turned-away bench, single biggest question responses, CoP roster
OutputLocked format + theme per Saturday, posted to the cohost guide template before Phase 2
Decision rightsBeth + Jen propose. Anne approves. Speaker bookings sit with Kate.
Barriers and Status
LOCKEDSpeakers stay in the mix at lower cadence — the earlier lean toward dropping speakers is reversed. Deep CREATE bench of women who said yes to Social Saturday.Decision in the May 23 room. Reverses earlier “no speakers” direction.
OPENExact cadence not locked — 6 weeks CoP / 4-6 weeks speaker / 8-week breathing room. Pick one and write it down.Floats in the planning doc. Needs to land in the SOW.
OPENFormat lock gate — Anne flagged she does not want to design beginner-friendly, care-centered, matriarchal community from an all-white room. Bring a woman of color into co-design before the format locks, not as a reviewer after.“Nothing about us without us.” This is load-bearing, not additive.
Phase 2
Planning the Session
2 to 4 weeks before the event
4
3
2
Beth’s Actions
Design the facilitation structure for the chosen format — opener mechanics, breakout prompts, harvest step, time blocks
Set up Zoom polls and breakout grouping (Mentimeter where it fits — annual subscriptions already in hand)
For CoP workshop weeks — train the CoP facilitators, front-loaded, possibly with Audrey
For speaker weeks — design the mid-session breakout that splits a 40-minute slot
Jen’s Actions
Coordinate pre-event prep — confirm host pairing, system access, breakout configuration
Chase Beth for facilitation structure content so it lands in the cohost guide on time
Align with Kate on speaker info (who, when, briefing status) — receive the hand-off, don’t source
Hand-off
Facilitation playbook lands in the cohost guide (delivered Friday by the Day-of Delivery Doc recipe in the main pipeline)
Speaker briefing comes from Kate — Beth and Jen need to know who’s speaking and when, not source
Data at this stage
SourceLocked format from Phase 1, CoP roster (workshop weeks), speaker briefing from Kate (speaker weeks)
OutputFacilitation playbook, breakout configuration, cohost guide content for the week
ToolsZoom polls + breakouts, Mentimeter (annual subscriptions), possibly a future event platform beyond Zoom (TBD during experiment)
Barriers and Status
OPENIP clause for Beth’s facilitation structures. Anne’s stated IP philosophy is to keep other people’s IP out of She Leads AI’s IP. The succession dream (rotating hosts running Beth’s formats) needs a perpetual royalty-free license written into the SOW or it sits on sand.The single biggest blind spot from the May 23 devil’s advocate pass. SOW gate.
OPENWhether to move to a dedicated event platform beyond Zoom for facilitation and small-group work. Gather data during the experiment.Floats in the planning doc.
OPENWhen one co-host is enough versus two, and whether an off-screen stage manager covers the gap. Open question for the experiment period.Two-host model is the safety default for now. Experiment may show when one is enough.
Phase 3
Marketing and Pre-Event Comms
5 to 2 days before the event
4
1
3
Jen’s Actions
Marketing alignment — make sure promo and registration copy match the format and the rhythm
Draft transition and experimentation messaging language (“we’re trying some new things, come experiment with us”) — first deliverable due Jun 5
Set up community-driven marketing mechanics — attendee-created selfies, custom-GPT reflection posts, designed to be shared after the session
Manage the inbox — registrations, questions, difficult attendees who surface pre-event
Joint Actions
Final read of cohost guide on Friday before the Saturday session — confirm facilitation playbook, links, run of show
Hand-off
Promo creation and distribution stay in the main pipeline (Phase 3 + 4 of the main map) — Jen aligns, doesn’t create
Cohost guide delivered Friday by the Day-of Delivery Doc recipe
Anne approves outbound experimentation messaging before it goes live
Data at this stage
SourceLocked format + theme, facilitation playbook, speaker info (when applicable)
OutputAligned promo copy, transition messaging, community-marketing template, registration page polish, inbox triage notes
ChannelsLinkedIn (Anne native), Mighty Networks (16:9 thumbnail, always manual), inbox (Gmail), pre-event Slack to host pair
Barriers and Status
OPENHashtag — “Social Saturday AI or whatever we land on.” Not locked. Decision needed before the experimentation messaging goes wide.Floats in the planning doc.
OPENWhether mass simultaneous posting by attendees gets flagged or boosted on LinkedIn. Anne doesn’t know.Affects how aggressive the community-marketing mechanic can be.
LOCKEDOne owner for speaker booking and marketing alignment. Booker and marketer cannot be split — booking with one person, marketing with another is what caused the original SS friction.Kate carries this. Capacity check is open.
Phase 4
Live Co-Hosting
Saturday 10am to noon PT
3
4
2
Joint Actions
Two hosts present for safety, in combinations that vary by event. A guest cohost steps in only when one of them has a conflict.
Open the Zoom, welcome attendees, set the women-first tone, intro the format and the speaker (when applicable)
Beth’s Actions
Run the facilitation mechanics — opener, breakouts, harvest step, time-keeping
Lead the polls and breakout-grouping logic in real time
For CoP weeks, hand the facilitation floor to the trained CoP facilitator and observe
Jen’s Actions
Real-time chat support — answer questions, drop pre-staged links, surface community contributions
Bring in a Chat Messenger role when attendance is expected to exceed 50
Handle difficult-attendee moments — boot unresponsive male-identifying attendees per the women-first rule, with the unblock path documented
Manage the harvest moment in chat — “drop the one thing you want heard”
Data captured (automatically by main pipeline)
RecordingFireflies — full session transcript
ChatZoom chat file saved to OneDrive (txt)
PollsZoom poll results, Mentimeter exports
Hand-offAll of this feeds Phase 7 + 8 of the main map (content processing, companion guide, newsletter intro)
Barriers and Status
LOCKEDTrust attendees can handle breakouts. People coming to an AI event can use Zoom. Don’t avoid breakouts out of fear.Resolved in the May 23 room.
LOCKEDKeep booting unresponsive male-identifying attendees. Trust your gut. Unblock path exists if it was a mistake.Resolved in the May 23 room.
OPENMove Zoom link to top of companion guide so attendees can grab it fast. Sticking point flagged May 11 still.Affects last-minute joiners. Phase 6 of main map.
Phase 5
Analysis and Learning
Ongoing — feeds the September three-month check-in
3
1
1
2
Joint Actions
Gather data on the 2 to 3 formats actually being tested — attendance, return rate, attendee-generated posts, felt-experience signal
Report back monthly or at format-test milestones, not just at the September check-in
Bring observations from Jun 6 (CoP workshop, run by someone else while B+J observe) into the format design
Beth’s Actions
Pull facilitation lessons — what mechanics worked, what to retire, what to keep for the rotating-host succession plan
Jen’s Actions
Track marketing signal — which experimentation messages converted, what attendees actually posted, what didn’t move
Hand-off
Lori Blair’s research and the NotebookLM serve as the before-and-after baseline (Anne to share)
September three-month check-in with Anne (and Don) — scope, compensation, process review built into the SOW
Data at this stage
InputsAttendance numbers, return rate, attendee-generated posts, chat harvest content, Lori Blair’s NotebookLM baseline
OutputMonthly notes, format-test reports, September check-in report
Success metricNot yet defined — open SOW item
Barriers and Status
OPENSuccess metric. If Social Saturday genuinely isn’t a funnel, decide what the September check-in measures instead — return rate, attendee-generated posts, felt-experience survey. Without it, the check-in has no spine.Devil’s advocate flag from the May 23 pass.
OPENDon’t pretend the pay question is closed. The September check-in should plainly review whether $500/month matches real hours, and rate moves if it doesn’t.Beth and Jen flagged this themselves then waved it off. Should not stay swallowed.
LOCKEDCap the experiment at 2 to 3 formats. Twelve weeks isn’t enough to learn from all eight cleanly.Devil’s advocate recommendation from the May 23 pass.
Still on the table
Open questions from the May 23 planning
Ten items the room floated but didn’t resolve. Each one shapes what Beth and Jen can actually do, so they want answers before late June.
Q1
Exact cadence — CoP every 6 weeks, speaker event every 4-6 weeks, or 8-week breathing room?Q2
Who else belongs in this planning — woman of color co-design gate, plus Audrey, Lori, Michelle, Pamela, a beginner, possibly Brian.Q3
Are male-identifying people allowed into the governance workshops? Tabled.Q4
Is the governance CoP free like SS, paid, or a certification?Q5
Is summer attendance predictable? One prior summer showed no drop.Q6
Which LMS is She Leads AI moving to? Michelle knows. Beth and Jen want eyes on it.Q7
Move to a dedicated event platform beyond Zoom? Gather data first.Q8
When is one co-host enough versus two? Off-screen stage manager?Q9
Does mass simultaneous posting by attendees get flagged or boosted on LinkedIn?Q10
The hashtag. “Social Saturday AI or whatever we land on.”Explicitly out of scope
Speaker sourcing and liaising
The original SS pain point gets pulled back in-house and folded into the existing CREATE speaker-onboarding machine. Booking and marketing stay under one owner so the booker never strands the marketing side. Beth and Jen only need to know who’s speaking and when. Kate carries this.
Before the SOW is signed
SOW risk flags from the May 23 devil’s advocate pass
Three items the planning conversation surfaced and didn’t fully resolve. Each one needs to land in the SOW before signing.
Risk 1 — IP for the facilitation structures
Anne’s stated IP philosophy is to keep other people’s IP out of She Leads AI’s. The succession plan (rotating hosts running Beth’s formats) and the facilitator-for-hire product are both built on structures that, by that philosophy, are Beth’s. Without a perpetual royalty-free license written into the SOW, succession sits on sand. One clause fixes this.
Risk 2 — Pay matches scope
Structure design, facilitation delivery, CoP training, content chasing, inbox and difficult-attendee management, marketing alignment, system administration, experimentation, and reporting — across near-weekly events for $250 each per month. Beth and Jen flagged it themselves then waved it off. Goodwill at signing is not the same as goodwill in week ten. The September check-in needs an explicit clause that the rate moves if real hours exceed what the base covers.
Risk 3 — Woman-of-color co-design gate
Format decisions calcify fast. By the time a woman of color is invited to react to a built format, the defaults are set and the invitation becomes “approve our plan” rather than “shape it with us.” Anne already sees this. The honest version of her own value requires the voice in the room before the lock, not after. Make it an actual gate with a name and a date, not a sentiment.