Pricing
Priced on what you process.
Put in writing.
No per-seat fees. No meter on audience size. No surprise overages. We scope pricing to your volume and the modules you turn on, then hand you the number in writing before you sign.
- No per-seat meter
- No MAU meter
- No overage traps
- No deployment premium
Playable · The deal desk
Four decisions.
Then a quote in writing.
This is the whole pricing conversation, made playable. Make the same four decisions you'd make across the table from us — pick modules, set volume, choose a deployment, flag enterprise needs — and watch the brief write itself.
0 of 4 decisions made
Sfere · Quote brief
Your scope, drafted
01 · Modules
- Awaiting your first pick…
02 · Volume basis
Pick a band…
03 · Deployment
Choose where it runs…
04 · Enterprise
Nothing flagged yet…
In-Kingdom, PDPL-governed data layer · included
Commercial basis confirmed in writing before you sign.
Illustrative scope builder — the final quote is scoped with our team.
Pricing philosophy
Billing that behaves
when your audience doesn't.
The pattern we're avoiding is familiar: an attractive entry price, a meter on every active user, and a renewal full of add-ons. Our model is built the other way around. Run the audit and watch a typical martech invoice lose its lines.
- Per-seat licences · 42 seatsNot billed
- Monthly active fan meterNot billed
- Overage · cup-final spikeNot billed
- Deployment premium · on-premNot billed
- Renewal add-on surprisesNot billed
What a Sfere invoice actually carries
- Processing volume — your contracted band
- The modules you turned on — nothing else
-
Priced on what you process
The basis is processing volume, not audience size. More fans, and more of them active, is the outcome we want for you — so it isn't the thing we bill.
-
Adopt modules, not bundles
Turn on the data and identity layer first; add activation and measurement when they earn their place. Every module is complete on its own.
-
Deployment never gates capability
Run it in your cloud, on-premise, or fully managed and the feature set stays the same. Where it runs is an operations choice, not a pricing lever.
-
Spikes are expected, not punished
A product drop or a holiday peak won't trip an overage. If sustained volume outgrows your band, we'll raise it with you first — not on the invoice.
-
No per-seat meter
Your whole team gets access; headcount isn't a basis we intend to bill on.
Priced by module
Adopt one module.
Add the rest when they earn it.
Each module is priced independently and can be adopted on its own or together. The data and identity layer is live today; the engagement layer is in preview, and we label it that way.
- Start Data & identity
- Then Activation
- Then Measurement
- Later Engagement · Preview
-
Live
Data & identity · Blocks + ID
Collection, the real-time identity graph, and one consented golden fan profile you own.
Priced independently
-
Live
Activation · Sfere Activate
WhatsApp, email, push, paid media, segmentation, and real-time triggers, all from the live profile.
Priced independently
-
Live
Measurement · Sfere Measure
Verified reach, exposure-to-outcome attribution, and a sponsor / partner portal.
Priced independently
-
Preview
Engagement · Sfere Engage
Interactivity, gamification, loyalty, and rewards — in design preview, not yet generally available.
Scoped for later, not billed today
-
Deploy your way
Your cloud, on-premise, or fully managed — in-Kingdom and PDPL-governed at the data layer.
Same capability everywhere
-
API & SDKs
A full REST API and client SDKs. Every capability is programmable.
Included with every module
How pricing works
The four decisions, in detail
The composer above is not a toy version of the sales call — it is the sales call. Here is exactly how each decision maps to the commercial basis we put in writing.
-
01
Pick your modules
Start with fan identity and data, then add activation and measurement when the timing is right. You're billed for the modules you turn on, not a bundle you don't use yet.
-
02
Priced by volume, not by headcount
The basis is what you process, not how many fans you acquire or how many of them engage. Growing your audience and getting them active shouldn't inflate the bill. The exact volume basis is set in your contract.
-
03
Enterprise needs are scoped in the same quote
SLA, SSO, audit access, and deployment specifics are part of the conversation up front, not add-ons that appear at renewal. Specifics are scoped per contract.
-
04
Talk to us for a quote
We map the platform to your use case and volume, then put the number in writing before you sign. No metered surprises, no add-ons appearing at renewal.
Pricing FAQ
Questions about pricing
No. Pricing is volume and usage based, not per active user. You pay for what you process, not for every fan you acquire, and the intent is a model that doesn't penalize you for getting fans to engage. The exact volume basis is scoped to your contract and confirmed in writing.
The capability set is identical whether you run in your own cloud, on-premise, or fully managed. Custom deployment work gets scoped into your quote when you need it; core capability is never gated behind where you deploy.
Yes. Modules are adopted independently. Most teams start with the live fan identity and data layer, then add activation and measurement later. The engagement layer is in design preview, so it isn't part of a plan you'd run today.
Book a demo. We map the platform to your use case and volume, then put pricing in writing before you commit. There's no self-serve sign-up today because we'd rather scope it properly than hand you a generic tier.
Get the number in writing
Compose your scope above, bring the brief to a demo, and we'll map the platform to your use case and volume — then put pricing in writing before you commit. No metered surprises, no add-ons at renewal.