Fan:Base
An FRM is to the fan what a CRM is to the customer.
One account for your fans, one back office for your teams, engagement modules that plug into it. The code and the data belong to you.
Book a callWhat you do not control today.
Your fans are anonymous.
Hundreds of thousands of visitors per season, live views, entries in a prediction game. You know the volume, you do not know the people.
Your tools are rented.
The contest runs on one vendor, ticketing on another, the newsletter on a third. Each one keeps your data, its features and its design.
Your sponsors want proof.
A measurable, named, segmentable audience. Today you show them impressions.
What Fan:Base is.
The core of your fan relationship, in two inseparable components, built for you.
The fan account
A single, persistent identity that works from one application to the next. Profile, avatar, participation history, points, consents. The fan signs in once and finds the same account everywhere.
- Fan:Predict Round 3 +120
- Fan:Vote Finals +80
- Fan:Play Quiz +40
The back office
Where your teams see the audience as a whole. Unified view, segmentation, engagement ranking weighted by action, commercial exports. This is where the programme is run and where the proof for your partners is produced.
The core is poured first. Activations plug into it afterwards, and each one enriches the same base.
What plugs into the core.
The prediction game. Your teams create competitions and athletes, open and close entry windows, publish rankings. Season standings included.
Live voting and judging, powered by the [VRSVS]* engine already proven in competition. The crowd judges, scores or breaks a tie, in real time during the session.
Short engagement formats, quizzes, polls, calendars. Enough to keep the off season alive and recruit accounts continuously.
These three modules are the most requested. Any mechanic that makes sense for your discipline can be built and plugged into the same core. What you already run can be connected to it too.
What is decided during scoping.
The API
Developer access to your own core. Your teams or your vendors connect authentication to your existing applications and read your data from the outside. Key and scope management, published documentation, test environment.
The fan facing engagement ranking
The team view is included in the core. The version your fans consult to place and compare themselves requires a dedicated application.
The connections
Email tools, messaging, commerce. Each connection is assessed against what your existing stack allows.
- Website
- Mobile app
- Ticketing
- Fan accounts
- Back office
Every mechanic can host a partner.
Every fan mechanic can host a partner, at several stackable levels. Naming, naming plus branding, branding alone, discreet presence. Branding covers image and video.
Because the code belongs to you, no format is imposed on you. A sponsor slot can become a video window, a full branding can take on a brand's identity for the duration of a stop.
Naming
The mechanic carries the partner's name.
Naming and branding
The name, plus the visual identity across the whole screen.
Branding only
The visual identity, image and video included, without the name.
Discreet presence
A dedicated slot, with no hold on the rest of the screen.
How it unfolds.
Scoping
One to two weeks. Perimeter, selected modules, engagement ranking weighting, access architecture, season calendar.
Mockups
You approve what your fans will see before a line of code is written. Your identity, your colours, your slots.
Build and launch
Development of the core then the modules, acceptance testing, onboarding of your teams on the back office.
Season
Your teams create competitions and launch campaigns on their own. We keep the platform running and build the evolutions.
Three distinct notions.
The setup
The development, configuration and deployment of each selected module. Ownership is transferred on delivery.
The annual retainer
Keeping everything running from year 2. Hosting, monitoring, backups, fixes, security updates.
Sparks
The development unit, 1 Spark equals 2 hours. Evolutions, new features, support for your teams. A single counter for the whole programme, carried over from one year to the next, toppable with packs.
Frequently asked questions.
Who owns the code? +
You do, from delivery. Database, source code, design. If you change vendor, everything stays with you.
How is this different from a subscription engagement platform? +
A rented platform imposes its formats, its slots and its design, and keeps your data. A single fan account valid across all your tools is structurally impossible there.
Is this an off the shelf product? +
Fan:Base is a proven core, built and branded for each organisation. The selected modules, the mechanics, the ranking weighting and the calendar are decided with you during scoping.
How long does it take to deploy? +
Count 8 to 12 weeks between scoping and launch for a core and a first module.
What budget? +
Every deployment is priced at scoping, based on the selected modules, the perimeter and the season calendar. We give you a firm quote at the end of scoping, before any development commitment.
Do we need to import our existing contact base? +
No, and it is preferable not to. The programme starts on a clean base, fans create their own account, consent is collected at the right moment for the right purpose.
What about our current website? +
It stays with its vendor. The integration is limited to a sign in button and a shared navigation bar that we build and embed in the programme's applications.
Let's talk about
your next season.
A one hour scoping call is enough to know whether Fan:Base fits your situation.