Run a full research → draft → score content loop on autopilot

Zero researches trending topics, drafts post variants, tracks their performance after publish, and delivers a green/yellow/red report so you know what to scale, iterate, or kill.

Zero connects:

Why content strategy dies in the gap between ideas and numbers

Content strategy breaks in the middle: ideas get generated, posts get published, and then no one looks at what actually worked. Two months later, the same losing post formats get recycled because no one tracked which ones won. Content Experiment Engine closes the loop. Zero researches trending themes across your sources, drafts ~8 variants every cycle, tracks performance after publish, and delivers a scored report: green (scale this), yellow (iterate), red (kill). The loop runs on a fixed cadence so it keeps going even when your week gets crushed.

How to ask Zero to run the content loop

@Zero every morning at 7am: scan X posts by @competitor_a, @competitor_b, and @founder_voice plus the top Reddit posts from r/ai_builders. Generate 8 draft post variants in Notion using our template library. Every Monday, score last week's published posts (likes + RTs + replies + follows) and post green/yellow/red report to #marketing.

try it

How Zero runs research → draft → score

Zero researches trending themes across your sources

On your cadence, Zero scans the social accounts and community boards you track, clusters posts by theme, and surfaces what your audience is engaging with right now. Raw data lands in Notion for archival.

Zero drafts post variants using your template library

Zero generates multiple variants per cycle in different formats (feature drop, hot take, founder reflection, use case, contrarian), all grounded in the week's research. Drafts go to Notion for your review and approval.

Zero scores published posts and delivers verdicts

After posts ship, Zero pulls engagement metrics and scores each post against the formula you defined. Results bucket into green/yellow/red with clear next-sprint direction: which themes to scale, which to iterate, which to retire.

Scale the winners, iterate the yellows, or kill the reds

Scale the winners

Generate more variants of a green post next sprint.

@Zero next sprint, generate 5 variants on the voice-workflows theme (different angles, same underlying thesis).

try it

Iterate the yellows

Tune the posts that underperformed but showed promise.

@Zero for the yellow posts, rewrite the first line to be tighter and less jargon-heavy, keep the rest.

try it

Retire the reds

Drop formats that have failed 3+ times.

@Zero retire the 'feature drop' template. It's scored red 4 weeks in a row. Remove it from the template library.

try it

Required integrations: X, Notion, and Slack

X (Twitter)

X (Twitter). Zero pulls trending posts from accounts you track and engagement metrics on your published posts. Read access required.

Required

Notion

Notion. Zero stores trend data, manages the content queue and template library, and archives performance history. Write access to 3 databases (trends, content queue, performance) is required.

Required

Slack

Slack. Zero sends the weekly brief, scoring reports, and nudges for review. Channel write access required.

Required

Best practices for closed-loop content experimentation

●Encode your scoring formula in the prompt once and don't touch it for a quarter. Shifting the formula mid-quarter makes the green/yellow/red buckets incomparable week to week.

●Approve drafts in batches, not one at a time. Review an hour every Monday beats 15 minutes every day. The loop needs a rhythm.

●Archive everything to Notion. Six months in, the most valuable asset is the history: which themes compound, which die, and why.