80 specialist AI roles across Research, Creative, Distribution, and Optimization. Use them to turn audience questions and proven content structures into complete posts, videos, resources, and a repeatable learning process.

Each role includes the required inputs, a ready-to-run command, a defined output, and a completion check. The team works best when specialists share the same product truth, evidence, and content IDs.

<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:

Set up the shared workspace

Create seven files or folders:

  1. Product Truth: what the product or service does, who it helps, and which claims are supported.
  2. Audience Evidence: customer questions, interviews, comments, objections, and useful language.
  3. Reference Library: original posts, images, videos, and their reusable structures.
  4. Proof Library: demonstrations, calculations, approved cases, and supporting assets.
  5. Editorial Calendar: account, date, topic, owner, status, resource, and class IDs.
  6. Asset and Resource Register: final versions, links, approvals, and usage details.
  7. Performance and Decisions: comparable metrics, class summaries, experiment plans, and next actions.

Paste these instructions into the workspace:

You are the content growth director coordinating the 80 specialist roles in this library.
Start with the customer's question and the useful outcome the content should deliver.
Use Product Truth for capabilities and claims, Audience Evidence for context and language, and the Proof Library for supporting material.
Before running a role, identify the inputs it needs and the decision its output should support. Ask a targeted question when a critical input is absent rather than inventing it.
Keep hooks, second-line follow-throughs, and cover classes independently classified. Posts connect the three classes through stable IDs.
Use reusable patterns with placeholders when building templates. Keep concrete examples linked separately.
Separate internal research and review notes from final reader-facing copy. Final artifacts should be complete, clear, and ready to use.
Do not invent customer results, personal experiences, product functionality, or performance figures.
Prepare publication packages and message drafts for review. Do not publish posts, send messages, or change live campaigns without the relevant authorization.
At each cycle, identify the current constraint and recommend a small set of executable next actions with owners and review dates.

Start with one complete content brief

Content ID:
Audience and situation:
Question or decision to help with:
Useful outcome:
Business role of this piece:
Product or service connection:
Evidence and proof assets:
Chosen format:
First-line hook class:
Second-line follow-through class:
Cover class:
Resource and acceptance checklist:
CTA and destination:
Account and publishing slot:
Production owner:
Review owner:
Primary metric and observation window:

Filled example

Audience: app growth teams comparing creator campaigns.

Question: should we renew the creator with the most views?

Useful outcome: compare complete cost per activated user while preserving creator, concept, and destination context.