Where we landed Tuesday — and what comes next. A short read, then a few questions whenever you have a minute.
Two clear priorities, and a simple shape underneath them.
Everything lives in Notion, Notion feeds Claude, and Claude helps the whole team work from the same picture. — Karina, on Tuesday's call. Exactly right.
So we're focusing on two things — and leaving the content back-and-forth alone. It's already working, and we don't want to add steps to something that isn't broken.
All your numbers in one place — and easy to act on.
The tools you already use, connected so you stop copy-pasting between them.
Right now the numbers live in a few places, and someone has to go gather them. Story engagement disappears after 24 hours. Comparing this week to last month — or brand-deal posts to organic — is manual.
How the picture comes together
sequenceDiagram
autonumber
participant S as Your channels
participant R as One reporting layer
participant Y as You
participant W as The work
S->>R: Instagram, TikTok, Metricool, ShopMy, ManyChat
R->>R: Daily snapshot, nothing slips away
R->>Y: See what's working (Notion view + Slack summary)
Y->>W: Ask in plain language
W->>R: Reads the best-performing material
W-->>Y: Drafts the next post or email
A note on honesty: we start with what's already connected and add each source as we wire it in. The picture fills in as access connects — we won't show you numbers we don't have yet.
The tools the team already uses — Notion, Drive, Calendar, Gmail, Slack, ManyChat — connected so Claude works across them instead of you copy-pasting between them. The connector Karina is already using is the first piece.
The daily content recap one of your team already runs through Claude in Slack — the one that rates each hook and flags what to try next. We'd turn that into a shared report the whole team can open at a link each week. Same work she's already doing, just visible to everyone and saved over time.
The daily recap, turned into a shared report
sequenceDiagram
autonumber
participant T as Your team's recap
participant C as Claude
participant L as A weekly link
participant E as Everyone
T->>C: The recap you already run
C->>L: Published each week
L->>E: One link in Slack, saved over time
Everything here is built from what's already running plus what you share — a working thing, not a mockup.
A real working example, regardless of anything else.
A first pass at what's driving reach, with a side-by-side against a comparable creator.
What's measurable today through ManyChat — inbound volume and which flows do the work.
Laid out from your own trackers and questions, so it reflects how you already think about performance.
The more of your trackers and questions we have beforehand, the more of that reporting view is real rather than sketched.
Your chosen kickoff date, then about 12 weeks with milestones every few weeks. Nothing is on hold in the meantime — we keep rolling pieces out, and whatever's set up is yours to keep.
A sample shape — your dates, your call
The Sessions app launch and the content push across the summer are exactly the kind of activity the system gets sharper from — so the timing works in your favor either way.
A few questions would let us tune this to how the team actually works — whenever it's convenient.
Share your read →