Qualification rule
Qualified when the operator manages two or more creators, can name the fan actions they want to compare across the roster, and accepts a scoped pilot before multi-artist payouts or full organization admin are promised.

Team ops pilot
Use this brief to decide whether a team should pilot Fanful across a small roster, what analytics matter, and which onboarding, permission, payout, and reporting boundaries stay explicit.
Qualified when the operator manages two or more creators, can name the fan actions they want to compare across the roster, and accepts a scoped pilot before multi-artist payouts or full organization admin are promised.
Measured when a qualified visitor uses this checklist path.
fanful_team_ops_v1
Checklist-style offer
List the creators, projects, or communities the team would include in a first pilot and who can approve each launch.
Choose the shared fan actions to compare: media plays, email signup, shop/support checkout, memberships, lessons, live attendance, community replies, or return visits.
Name the reporting questions the operator needs answered by creator, campaign, offer, source, and fan lifecycle stage.
Write the current boundaries for onboarding, permissions, Stripe Connect, payouts, fulfillment, and cross-artist fan identity before sales copy promises them.
Measure team-ops pilot intent with UTM campaign `fanful_team_ops_v1`, creator-interest lead quality, consult readiness, and the first roster page or campaign ready for review.
https://fanful.net/campaign-offers/team-ops-pilot-brief?utm_source=meta&utm_medium=paid_social&utm_campaign=fanful_team_ops_v1&utm_content=team_ops_static&utm_term=creator_teams&utm_source_platform=linkedinUse the brief to qualify a consult or pilot around a small roster, with Fanful owning the fan-home, attribution, and relationship signals it can support today.
Creator interest
Fanful uses this to separate raw interest from qualified leads while preserving the campaign, source, and first-party attribution that brought you here.