Platform Strategy

Strategy for launching and evolving the Silver Frog gaming platform.

Last Updated: January 2026 Status: Draft

Approach

Start with a turnkey B2B platform to launch quickly, then incrementally build custom components while the turnkey generates revenue. This de-risks the launch while building domain expertise.

Phase	Duration	Focus
Turnkey Launch	Month 0-6	Get to market, learn operations
Parallel Build	Month 6-18	Build custom components, A/B test
Migration	Month 18-24	Gradually move players to custom platform

Component Architecture

High-level view of platform components and their dependencies.

flowchart TB
    subgraph Core ["Core (High Risk - Migrate Last)"]
        Wallet[Wallet]
        Games[Game Integration]
        Payments[Payments]
    end

    subgraph Player ["Player-Facing (Medium Risk)"]
        Bonus[Bonus Engine]
        RG[Responsible Gambling]
        Account[Player Account & Auth]
    end

    subgraph Internal ["Internal Tools (Low Risk - Migrate First)"]
        Analytics[Analytics / BI]
        Backoffice[Back-office]
        CRM[CRM / Marketing]
    end

    Wallet --> Games
    Wallet --> Payments
    Wallet --> Bonus
    Account --> Wallet
    Account --> RG
    Account --> Bonus

    Analytics -.->|reads| Wallet
    Analytics -.->|reads| Account
    Analytics -.->|reads| Games
    Backoffice -.->|reads/writes| Account
    Backoffice -.->|reads| Wallet
    CRM -.->|reads| Account

Component Descriptions

Component	Description	Build vs Buy
Wallet	Real balance, bonus balance, pending withdrawals. Atomic transactions.	Build (eventually)
Game Integration	Aggregator API, session management, result verification	Buy (Hub88, St8)
Payments	Deposits, withdrawals, processor integrations	Buy (Nuvei, etc.)
Bonus Engine	Promotions, wagering requirements, bonus logic	Build
Responsible Gambling	Limits, self-exclusion, affordability checks	Build + Buy
Player Account	Auth, KYC status, profile, preferences	Build
Analytics	Player behavior, revenue metrics, dashboards	Build
Back-office	Admin panels, player management, operations	Build
CRM	Marketing automation, player communication	Build or Buy

Migration Risk Tiers

Components grouped by migration risk and recommended order.

flowchart LR
    subgraph Tier1 ["Tier 1: Zero Risk (Parallel)"]
        A1[Analytics]
        A2[Back-office v2]
        A3[CRM]
    end

    subgraph Tier2 ["Tier 2: Low Risk (A/B Test)"]
        B1[Bonus Engine]
        B2[Notifications]
        B3[RG Enhancements]
    end

    subgraph Tier3 ["Tier 3: Medium Risk (Bridge)"]
        C1[Player Account]
        C2[Custom KYC Flow]
    end

    subgraph Tier4 ["Tier 4: High Risk (Last)"]
        D1[Wallet]
        D2[Game Integration]
        D3[Payments]
    end

    Tier1 --> Tier2 --> Tier3 --> Tier4

Tier 1: Zero Risk

Run in parallel alongside turnkey from day one. No player impact.

Component	Approach	Value
Analytics	Sync turnkey DB to own analytics stack	Understand players before building
Back-office	Build custom, use alongside turnkey's	Better operator experience
CRM	Connect to turnkey player data	Own communication channel

Tier 2: Low Risk

Can A/B test with subset of players. Rollback is easy.

Component	Approach	Value
Bonus Engine	Feature flag: 10% -> 50% -> 100%	Differentiation, flexibility
Notifications	Route through own system	Own the channel
RG Enhancements	Layer on top of turnkey	Exceed compliance requirements

Tier 3: Medium Risk

Requires sync layer between systems. More complex rollback.

Component	Approach	Challenge
Player Account	SSO bridge, gradual migration	Session management
KYC Flow	Own flow, sync status to turnkey	Data portability

Tier 4: High Risk

Core systems. Migrate last, requires careful planning and potential downtime.

Component	Approach	Challenge
Wallet	Full migration with reconciliation	Real money, must be atomic
Game Integration	Swap frontend, keep aggregator	Session continuity
Payments	May keep B2B provider	Processor relationships

Migration Timeline

gantt
    title Platform Migration Timeline
    dateFormat YYYY-MM
    section Turnkey
        Launch & Operate           :t1, 2026-03, 6M
        Revenue Generation         :t2, 2026-06, 18M
    section Tier 1
        Analytics                  :a1, 2026-06, 2M
        Back-office v2             :a2, 2026-07, 3M
        CRM                        :a3, 2026-08, 2M
    section Tier 2
        Bonus Engine               :b1, 2026-10, 4M
        Notifications              :b2, 2026-11, 2M
    section Tier 3
        Player Account             :c1, 2027-02, 3M
        Custom KYC                 :c2, 2027-03, 2M
    section Tier 4
        Wallet                     :d1, 2027-06, 4M
        Game Integration           :d2, 2027-08, 2M

Bridge Architecture

During migration, a bridge service syncs data between turnkey and custom components.

flowchart TB
    subgraph Custom ["Custom Platform (Growing)"]
        CA[Analytics]
        CB[Back-office]
        CC[Bonus Engine]
        CD[Player Auth]
    end

    Bridge[Bridge Service]

    subgraph Turnkey ["Turnkey Platform (Shrinking)"]
        TW[Wallet]
        TG[Games]
        TP[Payments]
        TB[Legacy Bonus]
    end

    CA <-->|data sync| Bridge
    CB <-->|operations| Bridge
    CC <-->|wallet ops| Bridge
    CD <-->|sessions| Bridge

    Bridge <--> TW
    Bridge <--> TG
    Bridge <--> TP
    Bridge <--> TB

Bridge responsibilities:

• Data sync: Turnkey events -> Custom analytics
• Auth forwarding: Custom auth -> Turnkey sessions
• Wallet operations: Custom bonus engine -> Turnkey wallet API
• Player sync: Bidirectional player data updates

Build vs Buy Summary

Category	Build	Buy (Keep B2B)
Always Build	Analytics, Back-office, Bonus Engine, CRM	-
Build Eventually	Wallet, Player Account, Responsible Gambling	-
Always Buy	-	Game Aggregator, KYC Provider, Payment Orchestration

Rationale for "Always Buy":

• Game Aggregator: No value in building, Hub88/St8 have 10K+ games
• KYC Provider: Sumsub/Onfido are cheap per-verification, compliance expertise
• Payment Orchestration: High-risk, compliance nightmare, use Nuvei/Worldpay

Success Metrics

Phase	Metric	Target
Turnkey Launch	Time to first player	< 8 weeks
Turnkey Launch	Monthly GGR to break-even	~€150K
Parallel Build	Custom component adoption	50%+ players on custom bonus
Migration	Full migration completion	24 months from launch
Migration	Player churn during migration	< 5%

Risks & Mitigations

Risk	Mitigation
Turnkey lock-in	Negotiate exit clauses, own player data
Revenue doesn't cover dev costs	Lean team initially, prioritize revenue
Migration breaks player experience	Incremental migration, feature flags
Game providers don't integrate with custom	Keep aggregator, only swap frontend