Define the audience and job
Start with the audience situation the creator can credibly address. Product category, use case, level of awareness and desired next action matter more than a broad follower count. Community discussions, customer evidence and product behavior can reveal the language and proof people need.
A discovery brief should explain why a creator or community is relevant and which evidence supports the choice. It should not turn public profile data into a claim about conversion quality.
- Audience situation and market
- Product proof available to demonstrate
- Desired action and qualified outcome
- Channel norms and prohibited claims
Build testable creator briefs
A useful brief states the audience, message, proof, deliverables, constraints and review criteria. It leaves space for the creator's own language while protecting product truth and platform fit. Each angle should correspond to a learning question rather than a generic request for engaging content.
For AI products, show both the workflow and a realistic output when the audience needs to inspect how value is produced. Do not hide limitations that materially change expectations.
- One observable learning question
- Required product proof
- Claims and disclosure review
- Deliverable and revision boundary
- Measurement and result window
Keep outreach and rights human-controlled
Discovery and drafting can be assisted, but messages, negotiations and publication represent the business. They require an accountable person and platform-appropriate review. Content reuse also requires explicit rights, duration, territory and placement scope.
An Agent completion record is not proof that a message was sent or permission was granted. External service state and the relevant identifier must be retained before the workflow advances.
- Human approval before contact
- No invented relationship history
- Rights and disclosure attached to the asset
- Revocation and expiry remain visible
Measure beyond reach
Views and engagement describe distribution, not product value. Define the downstream signal the campaign is intended to influence: qualified site behavior, activated creation, paid-quality traffic or another observable outcome. Keep the population and source join visible.
When first-party joins are missing, the readout should stay at the reach or traffic layer. It can recommend a measurement task without claiming sales or retention impact.
- Reach and content engagement
- Qualified traffic or lead signal
- Activation or product-quality event
- Paid outcome when billing is connected
Reuse only supported winners
A creator asset becomes a reuse candidate when the rights are clear, the creative quality is understood and the result is strong enough for the intended next channel. Organic reach alone is not sufficient evidence for paid scale.
Store the winning pattern as a scoped proposal: audience, angle, proof, format, source, time window and limitations. Revalidate it when the channel, market or offer changes.