On this page
This is an operational launch checklist. It does not imply FanPay Link has team roles, CRM integration, bulk workflows or automatic revenue splits.
Map the work before adding tools.
Identify who supplies the original, checks the content record, agrees the offer, prepares the shared message and reconciles the sale. These are responsibilities in your own operation; they do not establish software permissions or dashboard features.
Keep the first offer specific enough that everyone can identify it. Record its creator, original file reference, intended channel, listed price and the applicable content checks. Use references rather than unnecessary personal data.
Resolve dependencies with sales.
Create an account in the app to start onboarding. Do not make an unconfirmed export, role, split or migration capability a hidden requirement in a launch date.
- Confirm creator and content eligibility.
- Confirm the agency account and payout arrangement.
- Check fees and the base for your creator agreement.
- Demonstrate any required integration or operational feature.
- Set the scope and timing for a small pilot.
Run a small, observable pilot.
Complete the validation step, review the preview and full fan total, and share through a controlled placement. Record what actually happened: which path was checked, which issue appeared and whether a payment was confirmed.
The public demo takes no real payment. Keep a successful simulation separate from a real operational result. Use the pilot record to decide which dependencies remain before adding more creators or offers.
Keep existing commitments in view.
If the pilot is part of a platform switch, keep an inventory of active links, open balances and existing purchased access. Replacing promotional destinations does not automatically migrate those obligations. Expand only after each affected path has a clear owner and confirmed next step.
Prepare an agency pilot.
A responsibility, dependency and observed-outcome worksheet for one controlled offer.
Download the worksheet