Every Audience client runs the same six-month journey.
Every operator runs the same weekly rhythm.
This is the operator playbook. The Asana projects are where the work happens — this page is the map. When in doubt about what to do or when, this is the place that points you to the right one.
Every client runs through the same arc — onboard, unlock, refresh, expand, upsell, renew.
Each month has a campaign build and a recurring close-out, plus (in most months) an S&D moment or strategic touchpoint. Violet marks the client-facing moments; neutral marks the supporting work behind them. Month 1 is the onboard sprint; Month 6 is the renewal decision.
linkedin-payload.md directly. Lands Day 6.Six S&D moments mapped across the journey.
Each one is a moment of proactive value — strategy already done, ask only for approval. Never reactive, always feeling-cared-for.
voice-profile.md from onboard. Two modes: Handhold (drafts replies for review) or Let It Rip (auto-respond). Bonus #1 from the offer, delivered as a surprise unlock rather than at signature.Two operational sweeps and one team check-in. Same rhythm every week.
The cadence doesn't change with client count. One pass through the Airtable dashboard covers every client at once — never duplicate work per client.
The Sweep · Mon + Thu
One pass, all clients.
Single combined pass through every active client via the Airtable dashboard. One task per check covering all clients — never duplicate per client.
Platform sweep: campaign errors, paused sequences, pipeline tag updates, campaigns ending soon.
Client health check: connection volume, inbox sentiment, ICP validation, A/B performance, lead runway flags.
At-risk trigger check: see protocol below.
Monday Team Check-In
The team rhythm point.
Runs after the Monday sweep.
Campaign health review: pull Audience metrics across all active clients; flag attention items.
Weekly Slack updates: manual fill of weekly metrics update per client (uses salvaged template).
Team standup with Ike: agenda organized by priority — urgent → performance → process.
Day 7 is the Launch Call — review, approval, and live deployment in one moment.
The single most important sequence of the engagement. External promise: campaigns live within 7–14 days. Internal target: Day 7. Internal completion gate: EOD Day 5, with banner approval landing Day 6.
/profile-intake, /profile-build, /reshare-intake, /reshare-research. EOD: payload + voice profile exist; reshare candidates ready./reshare-build), Campaign Build (3 campaigns + lead lists curated). Banner runs in parallel — see right.Banner Production · Parallel
5 working days, Days 2–6.
Designer reads linkedin-payload.md directly as the brief.
- Day 2: Designer picks up payload
- Days 2–5: Design work
- Day 6: Banner delivered + internally approved
- Day 7: Included in Launch Call package
Banner is the only deliverable that lands Day 6 instead of Day 5. Everything else gates at the internal completion gate on Day 5.
A 30-minute touchpoint that retunes the voice on 60+ days of real conversion data.
The refreshed voice profile feeds directly into Month 3's Post-Engagement Targeting campaign and the AI Response Agent. For M2M continuation clients, this becomes a recurring quarterly call.
Pull the data dossier
- Inbox responses (best-converting + off-tone moments)
- AI Response Agent outputs from Month 2
- Slack channel highlights with client
- Audience platform engagement data
- Notes/recordings from kickoff + Day 7 launch call
- Pre-drafted voice profile edits
Walk + refine live
- Walk client through what's converting in their voice
- Surface tone drift / off-tone Agent moments
- Get client input — what feels right, what doesn't
- Light discussion of positioning shifts (new offer, new ICP)
- Review pre-drafted edits live
- Client signs off
Apply + confirm
- Update
voice-profile.md - Recalibrate AI Response Agent
- Brief Slack confirmation to client
- Log in Airtable
- Refreshed voice feeds Month 3 campaign messaging
Five defined triggers. Each one has a clear action.
Catch them during the Mon/Thu sweep, log in Airtable, take the defined action, and surface in the Monday team check-in. No separate Asana destination — the protocol flows through the structures you're already in.
Operator catches a trigger during the sweep → logs it in the Airtable client record → takes the defined action → surfaces in the next Monday team check-in. Resolution history stays in Airtable.
Three systems, clearly separated. Knowing which one to open is half the job.
Client-specific milestone work lives in the per-client journey project. Recurring ops live in the shared monitoring project. The Airtable Dashboard Tracker is the campaign pipeline + source of truth for per-client metrics.
This is where the milestone work lives.
One task per check, never duplicated per client.
Source of truth for the per-client metrics walked during the sweep.
Trigger fires in monitoring (80% leads contacted flag). The actual build work happens in the per-client journey project — check the upcoming month's campaign build task. If it's on track, no action. If not, accelerate. Escalate to Ike only if client input or strategy shift is required.
Audience runs on consistency. Your job is to protect it.
The system above isn't just structure for its own sake. Every client gets the same arc, every week runs the same rhythm, every at-risk signal triggers the same response — because that's how a service business scales without quality drift.
When you're unsure what to do or when, default to the playbook. When the playbook is wrong, flag it — that's how it gets better. Don't invent one-off solutions for systemic problems.