Question 1

How is the base price structured?

Accepted Answer

Each tier is a fixed monthly fee per Sub-Space. Customers can choose monthly billing or annual billing, with annual billing saving 20%. The fee includes the EPS and API/hr throughput allowance for that tier, the feature set, and the onboarding model. Starter is self-serve, while Growth and above include managed onboarding and integration support.

Question 2

What happens if I exceed my tier's EPS or API limit?

Accepted Answer

We do not throttle traffic or impose hard cut-offs. The platform continues processing traffic. Usage above the included allowance is flagged in the dashboard and billed as additional headroom. If usage consistently exceeds the allowance, we review whether extra headroom or a tier upgrade is the better fit.

Question 3

If we add EPS or API/hr headroom during the contract, how is it billed?

Accepted Answer

Additional EPS and API/hr headroom is billed from the point it is added. On monthly billing, the updated run-rate appears in the next invoice cycle. On annual billing, added headroom is pro-rated across the remaining contract term and invoiced accordingly.

Question 4

Can added EPS or API/hr headroom be reduced later if usage drops?

Accepted Answer

Yes. On monthly billing, reductions can take effect in the next billing cycle. On annual billing, reductions typically align to renewal unless otherwise agreed commercially.

Question 5

When should we add headroom versus upgrade to the next tier?

Accepted Answer

Add headroom when throughput is the issue and your current feature set and support model still fit. Upgrade when you need broader functionality, stronger support, or when higher usage has become the norm and the next tier is the stronger commercial fit.

Question 6

What is a Sub-Space and how is it billed?

Accepted Answer

A Sub-Space is an isolated workspace for a single brand or label within a master licence. The first Sub-Space is included in the tier fee. Additional Sub-Spaces are billed annually, and multi-brand Sub-Spaces are available from Growth upwards.

Question 7

Can I access advanced features on the Starter tier?

Accepted Answer

No. Starter is built for tournament-led launches with self-serve integration. Achievements, loyalty and VIP journeys, reward fulfilment, webhooks, automation, and managed integration support start at Growth.

Question 8

How long does integration typically take?

Accepted Answer

Starter uses a self-serve, event-based API model, and many development teams can begin posting events within a day. Growth and above include hands-on integration support and typically complete full integration within 1 to 3 business days.

Question 9

Does CompetitionLabs replace my existing tech stack?

Accepted Answer

No. CompetitionLabs is designed to complement existing CRM systems, game data feeds, player management systems, and marketing tools without requiring replacement of current infrastructure.

Question 10

Do I need to write code to configure tournaments or missions?

Accepted Answer

No. Tournament rules, mission steps, reward structures, and player segments are managed through a visual no-code admin interface, allowing product and CRM teams to operate independently of the development team.

Question 11

How quickly can leaderboards update in real time?

Accepted Answer

Leaderboard rankings typically update in under 1 second after a qualifying player event is received, enabling near real-time visibility for players and operators.

Question 12

Can I switch tiers mid-contract?

Accepted Answer

Yes. Upgrades can be applied during the contract term, with pricing pro-rated across the remaining period. On annual billing, downgrades take effect at renewal. On monthly billing, they take effect in the next billing cycle.

Question 13

Are there minimum contract lengths?

Accepted Answer

Starter requires a 3-month commitment. Growth, Scale, and Enterprise require a minimum 1-year contract, with multi-year arrangements available for qualifying customers.

Tournament cloning

Step 1: Navigation

Step 2: Cloning the Tournament