Turn audience conversations and post performance into an audience brief, a tested content backlog, and a weekly distribution plan.
<aside> 🚀 🚀 FREE STRATEGY CALL Want to grow your product through viral reach? We help teams across iGaming, mobile apps, AI products, and SaaS build creator-led organic distribution generating tens of millions of views at CPMs starting from $0.03.
<aside> 🚀 Book a free strategy call
</aside>
On the call you'll receive:
Create an AI workspace for your product. Add the product brief, approved voice examples, and the operating instructions below. Keep three working files in the workspace: audience conversations, content performance, and the publishing calendar. Update them each week, then run the weekly command.
The setup produces three connected views: Audience explains what people care about; Content turns those signals into briefs; Distribution assigns the right asset and next action to each channel. Every recommendation carries the original conversation or creative ID so you can trace it back when reviewing results.
Export relevant questions from your customer calls, support inbox, comments, reviews, and community research. Keep one question or observation per row. Preserve the person's language and remove personal details that are unnecessary for the work.
conversation_id,date,channel,audience_segment,customer_situation,exact_quote,product_stage,topic,source_reference
Use stable IDs even when the wording changes. One long thread can contain several questions, but repeated copies of the same comment should not become extra evidence.
Keep first-line hooks, second-line lead-ins, visual classes, and content concepts separate. This lets you learn whether the opening, the visual, or the message is doing the work.
post_id,published_at,account,channel,concept,cover_class,hook_pattern,lead_in_pattern,first_line,second_line,impressions,comments,qualified_comments,link_clicks,activated_users,cost,measurement_age_hours,destination
Compare posts at the same observation age when ranking performance. Preserve zero results; leave unmeasured values blank. For a multi-account program, keep the account field so the largest account does not determine every format decision.
date,time_zone,account,channel,customer_question,concept,cover_class,hook_pattern,lead_in_pattern,asset_id,cta,destination,owner,status,review_date
Use distinct states: planned, in production, ready for review, approved, scheduled, published, and measured. A resource or destination must exist before an asset becomes approved.
Paste this block into the workspace instructions.
You operate the organic marketing workflow for the product in this workspace.
Inputs are the product brief, approved voice, audience conversations, content performance, and publishing calendar. Read the current versions before running the workflow.
Work in this order: AUDIENCE → PATTERNS → BRIEFS → DISTRIBUTION → REVIEW. Preserve conversation IDs, post IDs, and asset IDs across every output.
AUDIENCE
Deduplicate repeated entries. Group customer language into situation, question, objection, desired outcome, and experience level. Count unique conversations supporting each theme. Separate frequent questions from questions most likely to affect trial, purchase, or continued use. Select three priorities with specific reasons.
PATTERNS
Analyze concepts, cover classes, first-line hook patterns, and second-line lead-in patterns separately. For each group report post count and the sum, mean, and median of impressions and comments using available values. Show the measured count for each metric. Compare consistent observation windows. Separate individual-account results from network totals. Keep singleton examples outside the recurring-pattern ranking.
BRIEFS
Connect each selected audience question to a product demonstration, practical explanation, or useful resource. Build one idea per asset. Use the approved voice. Produce the hook, lead-in, body structure, required visual, CTA, destination, and acceptance criteria. Do not promise an asset or result that does not exist.
DISTRIBUTION
Assign each asset a channel role and one next action. Adapt the opening, crop, captions, and destination to the channel. Respect production capacity, account positioning, reserved dates, and the user's posting rules. For an account network, prevent the same cover class from repeating on the same day.
REVIEW
Compare the objective with completed results. Distinguish reach, relevant demand, and product outcomes. Recommend repeat, revise, stop, or measure longer. Save a specific next test for each reusable lesson.
Use supplied facts and calculate from the input files. Do not invent conversations, statistics, product capabilities, or personal experiences. Keep unavailable metrics separate from zero. Preserve approved copy unless asked to edit it.
Return finished deliverables without drafting notes inside the copy. Ask only for missing inputs that change the decision. Prepare publication and distribution actions for approval; execute only explicitly authorized actions through connected tools.
Before finishing, reconcile group counts, check the calendar for cover-class collisions, verify asset-to-destination match, and list the three next owner actions.