Onboarding
What happens between signing and launch, and what each side owes the other.
Launching takes anywhere from a few days to a few months. The platform work is days. Everything else is content, artwork, legal review and deciding what you actually want fans to do.
A named FanBase contact runs the sequence below with you. Each step says which side owns it.
What we need from you
Gather these early. Every one of them has blocked a launch at some point.
| What we need | Detail |
|---|---|
| Domain | The address the app lives on, for example hub.yourclub.com. You add a DNS record we specify. |
| Brand assets | Logo, cover image, background art, accent colour. Sizes are in General settings. |
| Sign-in methods | Which of Google, Discord, X, Twitch and Shopify fans use to get in. |
| Shopify store domain | If you are connecting a store, the original .myshopify.com address, not your custom one. |
| Languages | Which of the supported locales you want offered. |
| Leaderboard basis | XP or quests completed. It is set when we build your community and reordering it later moves fans who earned their place. See Leaderboards. |
| Admin team | Names and email addresses of everyone who needs access, and the role each of them needs. |
| Legal pages | Your privacy policy and terms, or a decision to use ours. |
| Existing fan list | If you are migrating people in, a CSV. Ask us for the format before you export. |
What we send you
| What you get | Detail |
|---|---|
| Admin panel access | On a sandbox first, then production. |
| Your community's identifiers | Tenant (the id for your organisation on the platform), community slug and app id. Your developer needs these for the SDK. |
| A sandbox environment | A full copy of your app to break safely. |
| Shopify install link | If you are connecting a store. It expires in about a week, so use it when it arrives. |
| Data API key | On request, for pulling your community's data into your own systems. See Data API. |
The steps
Kickoff and a panel demo
A demo of the platform, then the admin panel open in front of your team. Bring the people who will run it day to day, not only the person who signed. The teams that launch well are the ones whose community manager has already built ten quests before launch day.
We agree the milestones and a target launch date here.
We build your community
We create your community and its configuration. We connect your sign-in providers. We hand you a sandbox.
This is a manual setup on our side today, so allow a couple of days and tell us early if the domain is unusual. Self-serve creation is planned. See status.
You configure and fill it
The part that takes real time, and the part only you can do.
Set your branding and navigation. Decide your economy: what XP is called, whether you run a spendable currency, and what a level means. Build your first quests. Tag them. Set up your rewards. Stock the store. Write the copy fans read.
Aim for twenty to thirty quests at launch across a mix of difficulty.
Connect what you already run
Shopify, so purchases pay out and points are worth something. Discord, so quests and events announce themselves. Google Analytics or Tag Manager, so sign-ups can be attributed to the campaign that paid for them.
Test, then reset
We test in production before anyone is invited. You should too, with your own team, on a phone and a laptop, in both light and dark if you offer both.
Then wipe the balances your testing created, before fans arrive rather than after. See Reset balance.
Launch
Gated early access or a public launch. Launch strategy covers the options and which ones have worked.
We monitor the platform through launch day and can co-market it.
After launch
Your FanBase contact stays on the account. Most partners keep a regular call for content ideas and campaign planning, because a steady stream of new quests and posts is what keeps fans coming back.
Timelines
Honest numbers from real launches rather than a best case.
| Phase | How long |
|---|---|
| Platform setup on our side | One to three days |
| Configuration and content by you | One to three weeks |
| A club with custom onboarding screens, legal review and a store migration | Two to three months |
| A community with no custom work, reusing an existing setup | Under a day |
The variable is almost never the software. It is artwork, approvals and deciding what a quest should reward.
If you are building your own front end
Steps one, two, four and seven are the same. You skip the app configuration and your developer takes over after step two with the identifiers we send.
Point them at the FanBase SDK quickstart. Quests are still built in the admin panel, so your community team still needs step three.