Playbook
The daily loop, the first thirty days, and the compliance posture.
Everything we walk through on the sales call, written down so you can read it at your own pace. If something is missing, email us — we’ll add it.
Four pillars
What the engine actually does, end to end.
The engine reads next week from last week: the format that won, the hook that held, the send-time that landed. The calendar is a rolling draft, not a one-off brainstorm.
Every draft lands in the dashboard editable. Pin phrases the engine must use, phrases it must never use, and approve by exception. Nothing leaves unsanctioned.
Review the calendar, the DM queue, and the month-end report. Edge cases route to you before they go out. The rest runs on its own.
CAN-SPAM opt-outs, accurate sender info, and AI-generated disclosure where the platform requires it. Every send is logged with timestamp and actor, exportable for legal review.
Per-channel cadence
A starting rhythm per network.
These are starting points, not rules — the engine reads your engagement and shifts cadence toward what’s working. Channels not in your plan are off the table entirely.
4–5 / week
Reels + carousels, story reply-DMs
3–4 / week
Native video + community replies
TikTok
3–5 / week
Short-form vertical, comment-to-DM funnels
2–3 / week
Founder POV + comment-based reach
X
3–5 / week
Threads, quote-posts, niche replies
First thirty days
What the first month actually looks like.
- 1
Week 1
Onboarding sprintYou hand over brand voice, channels, approval posture, and a sample of past content. We wire the rest, import your calendar, and connect the networks.
- 2
Week 2
First drafts in the dashboardThe engine ships a week of drafts across the agreed channels. You edit, pin, and approve. We tune voice against the corrections.
- 3
Week 3
Live publishing beginsApproved drafts go out on the optimal-slot schedule. Replies and DM triage run on autopilot with the edge-case handoff live.
- 4
Week 4
First read on what workedThe monthly report lands: what format won, what hook held, what slot landed. The next calendar reads from these signals, and the loop is closed.