The WhiteLotto Keno platform overview covers the product conversation. This guide focuses on the questions needed to build a realistic operating and cost brief, without assuming a guaranteed margin or a universal launch model.
Define the product before modelling its economics
Document the number-selection rules, allowed stakes, prize table, draw frequency, sales cut-off and supported channels. Identify whether you need one game configuration or multiple variants, and who can approve a change.
For the portfolio decision, read the role of custom games alongside jackpot resale. Keep that strategic question separate from the implementation brief: an attractive game concept still needs a complete operating flow.
- Which rules and prize-table version apply to each ticket?
- How are changes communicated, scheduled and tested?
- Which currencies, languages and channels belong to the initial release?
- Which operator, supplier or third party owns each delivery task?
Separate configuration from permission to operate
A configurable game does not establish permission to offer it in a market. Keep product specifications, market approval requirements and operating responsibilities as separate workstreams. Ask the appropriate regulatory advisers to define the requirements for your intended model.
Record the required approvals and dependencies in the launch plan. Do not treat a technical demonstration, available language or payment integration as confirmation that a market is ready for launch.
Build a cost scenario from explicit inputs
Start with assumptions rather than a headline profitability percentage. Separate ticket sales, prizes, acquisition costs, payment costs, supplier fees and operating expenses. Keep deposits and withdrawals separate from game revenue to avoid counting the same money twice.
| Input | Question for the model |
|---|---|
| Game activity | What stake mix, ticket volume and draw participation are assumed? |
| Prize funding | Who funds prizes, and how are payout exposure and cash timing assessed? |
| Platform and game fees | Which setup, recurring, usage or revenue-share fees apply? |
| Payments and distribution | Which processing, refund, agent and channel costs are included? |
| Operations | What support, monitoring, reconciliation and change effort is required? |
Distinguish expected economics from draw-level exposure
Compare lower, base and higher activity scenarios using the same cost categories. Separate fixed costs from variable costs and define the revenue base used in any supplier fee. The platform pricing and TCO guide covers the wider platform contract.
An expected prize-cost assumption is not a prediction of the payout on a particular draw. Ask how the prize table, possible winning combinations and exposure limits are reviewed, how funds are made available, and who handles an exception. Do not replace that analysis with a promised percentage return.
Specify fixed prizes or a shared prize pool before integration
A fixed-prize design applies the specified prize table to qualifying participation. A pari-mutuel or shared-pool design allocates a defined pool under agreed rules among qualifying winning units. Neither label specifies the whole operating model: record the pool’s funding base, eligible units, deductions and allocation method. A shared prize pool is also different from a syndicate of players buying tickets together.
Keep that mechanism distinct from the custom-game portfolio business case and the platform fee model. If the rules include a starting amount, supplementary funding or rollover, define its owner through the prize-funding brief; do not infer that responsibility from the game’s name.
| Rule area | Decision to document | Acceptance evidence |
|---|---|---|
| Pool close | Included participation and closing reference | Late or rejected participation cannot silently enlarge the closed pool. |
| Allocation | Prize tiers and qualifying winning units | The allocation explains every award against the same rule version. |
| Rounding | Precision and residual-amount treatment | Rounded awards and the recorded residual reconcile to the allocated amount. |
| No winner | Carry-forward or other specified treatment | The unawarded amount has a traceable destination, not a missing entry. |
| Cancellation | Refund and allocation reversal rules | Ticket adjustments and pool movements explain the same cancellation. |
Accept the allocation, not only the winning screen
Take a controlled set of tickets through pool closing, a result with several winners, rounding and final settlement. Repeat with no winner and with cancellation. Retain the input population, rule version, allocation calculation and final movements so that operations can reproduce the explanation.
Specify how a corrected result affects an already calculated allocation using the draw and results workflow. Record calculation and settlement references in the integration requirements. Use the UAT checklist to agree who accepts residuals, reversals and carried balances before launch.
Bring your proposed allocation rules to WhiteLotto. CONTACT to discuss the game and operating scope.
Connect draw integrity to wallet settlement
Specify the draw source, schedule, final-result authority and mapping from result to ticket outcome. Require traceable references for the rule version, draw, ticket and settlement. The draw-integrity and audit-trail checklist helps structure that review.
- What happens if a result is late or a scheduled draw cannot proceed?
- How are duplicate results or settlement retries prevented from producing unintended credits?
- Who may suspend a game, correct an incident or authorise a reversal?
- Can finance reconcile stakes, awards and adjustments by game and draw?
Use operating acceptance cases, not only a game demo
Agree expected results, owners and evidence for each case. Include operator training, support escalation and a controlled pause procedure in the launch-readiness checklist. Faster draw cadence must be evaluated against the resulting transaction, monitoring and support workload.
- Issue a ticket before the cut-off and reject one after it according to the agreed rule.
- Complete a draw and trace both a winning and a losing ticket through settlement.
- Test a delayed result and repeated settlement message without using production funds.
- Demonstrate a rule or prize-table change without altering the terms of an already issued ticket.
- Reconcile a test reporting period, including a cancellation or authorised adjustment.
Ask for a scoped commercial response
Request a delivery matrix that distinguishes existing capability, configuration, custom work, third-party dependencies and exclusions. Compare implementation effort, recurring costs, data access, change ownership and exit terms. A useful buying decision connects those terms to your game rules and operating assumptions rather than to a generic promise of quick profitability.
Discuss Keno or custom-game platform fit
Bring your proposed rules, channels, draw cadence, prize-funding assumptions and launch requirements. WhiteLotto can discuss product scope, integration boundaries and the next steps for your project.
Wojciech Lysak is Managing Director of White Lotto and a senior iGaming B2B expert with nearly 20 years of experience. He specializes in white label online lottery platforms, turnkey solutions, gaming systems, and scalable B2B solutions for operators across global markets.
A recognized industry leader and visionary, he actively participates in major iGaming events worldwide and has led the creation of multiple successful platforms and projects across the gaming sector.
If you’re interested in starting your own online business in the iGaming sector, Wojciech will help you take your first steps on the path to success. LinkedIn