Case study · iGaming platform · B2B · 2026
GamingSoft
Mid-tier B2B platform goes AI-native, without breaking operator SLAs.
220-person APAC platform vendor serving 80+ operator brands embedded AI across operator onboarding, game aggregation, B2B support, and multi-jurisdiction compliance — with the integrity and licensing teams in the design room from week one.
At a glance
- 220Headcount
- 5 weeksEngagement
- 14Pioneers
- 80+Operator brands
- 11Jurisdictions
The brief
AI rollout where every workflow touches someone else's licence.
Cohort
- C-level (CEO, CTO)2
- Heads of Department6
- AI pioneers14
Drawn from Operator Onboarding, Game Aggregation, B2B Support, Integrity, Compliance, and Platform Engineering — every output reviewed against operator SLAs before it shipped.
What the pioneers shipped
Six workflows, scoped per-operator and per-licence.
Operator KYB & onboarding
Pulls registries, screens UBOs, and drafts the licensing pack per jurisdiction. Compliance officer signs off before any account goes live.
Game-studio integration triage
Reviews incoming studio submissions, flags math-model gaps and lab-cert mismatches, drafts the integration ticket the platform team picks up.
B2B support copilot
Categorises operator tickets, pulls the relevant API logs, drafts a first response. Tier-2 engineer adds the fix and sends.
Cross-operator integrity watch
Flags abnormal RTP drift, coordinated wagering, and bonus-abuse rings across operators on the platform — without exposing player PII between licensees.
Per-jurisdiction evidence packs
Quarterly evidence assembled per operator licence — MGA, Curaçao, PAGCOR, Anjouan — ready for the licensee's auditor without ten Slack threads.
Settlement reconciliation
Reconciles operator wallets, studio revenue shares, and provider invoices. Finance reviews the exception queue, not every line.
“We're a vendor — every shortcut we take is a shortcut taken in someone else's licensed business.”
Approach
Five weeks. Four sign-offs. Operator SLAs untouched.
Discover
Mapped the platform stack, the operator-facing API surface, and the SLAs attached to each licensee tier. Integrity and compliance teams defined what an agent could draft and what stayed human end-to-end.
Build
Pioneers shipped first cuts inside their function. Every workflow that exited the platform boundary — operator-facing or studio-facing — paired with integrity before staging, not after.
Operator dry-run
Three pilot operators ran every new flow against their existing SLAs and licence obligations. Anything that risked an operator's regulator answer was redesigned, not deployed.
Compound
Skills shipped to an internal marketplace. A win with one operator lifts the rest — without leaking PII or commercial terms between licensees.
Impact · Year one
Outcomes leadership signed off on.
Operator onboarding
−74%
From 6 weeks to 11 days, KYB-to-go-live.
B2B ticket time
−61%
First response on tier-2 issues, with the same engineer headcount.
Business satisfaction
9.4 / 10
Post-engagement leadership review, plus three pilot-operator references.
Why it didn't go off the rails
Vendor discipline. Licensee-facing SLAs.
Operator-data isolation
Every agent scoped to a single operator tenant or aggregates with PII and commercial terms stripped. No cross-tenant leakage — the platform's whole pitch.
No autonomous action on integrations
Agents draft integration tickets, RTP-drift alerts, and incident notes. A platform engineer signs every change that touches an operator's traffic.
Per-jurisdiction evidence by default
Every workflow that produces a record produces it in the format the relevant regulator expects — same query, same documented answer, every time.
SLA gates on every flow
If an agent flow risks an existing operator SLA — latency, uptime, dispute window — it doesn't ship. Not negotiable.
Where to start
Book an org assessment.
Ninety minutes, no slides.
We'll spend an hour with your leadership team mapping where AI creates the most leverage in your operation — and what an overlay would look like in practice.