The plan is to complete testing and applicable approvals, then deploy a customer-specific service. Each stage has an explicit acceptance outcome rather than an assumed calendar date.
The starting point
A substantial build already exists.
The account and wallet foundation, sportsbook/trading logic, game estate, safer-play workflows, CRM/rewards, multi-brand administration, reporting/billing and delivery surfaces are implemented. The next stage is to define, assess, integrate and operate a specific commercial service using that foundation.
Agree the initial operator, jurisdiction, business/licensing role, game slate, contractual responsibilities and acceptance criteria. Early conversations are founder-reported; no signed customer or committed revenue is represented.
Acceptance outcomeAgreed scope and accountable owners
02
Next
Prepare independent testing
Freeze an identifiable build; assemble RNG, game maths, advertised RTP, recovery, settlement and security evidence; obtain scoped test-house estimates.
Acceptance outcomeNamed testing engagement and submission-ready build
03
Next
Complete assurance & integrations
Close findings; connect and accept live identity, exclusion, location, payments and settlement feeds. Build the scoped ISO 27001 programme and decide SOC 2 timing with customers and auditors.
Acceptance outcomeAccepted integrations and documented assurance outcomes
04
External gate
Obtain applicable approvals
Complete the licences and approvals required by the chosen operating model and jurisdiction. Record independent game/RNG results and the scope of any security certification/report.
Acceptance outcomeEvidence of applicable approvals; no date assumed
05
After gates
Run the first operator deployment
Customer-specific brand, user journeys and configuration; migration if needed; security review, operational rehearsals, acceptance and controlled launch.
Acceptance outcomeSigned acceptance and controlled commercial release
06
Then
Expand with measured results
Add further games, brands and integrations based on customer demand, unit economics and the approval scope. Develop broader cross-product opportunities separately.
Acceptance outcomeRepeatable deployment and customer outcomes
What the next steps actually involve
Ten workstreams. Specific work and outcomes.
This is the proposed execution plan. The current evidence establishes a working build and early commercial conversations; it does not establish contracted auditors, assigned named owners or external completion dates. Lead roles below describe who needs to own the work. Assurance, integration and operations can progress together once the launch scope is agreed.
01 / DefinePROPOSED NEXT WORK
Agree the first operator and launch scope
Turn the early conversations into one specific service that can be tested, budgeted and accepted. The platform’s full breadth should not make the first release unbounded.
What we already have
Working player demos, operator tools, headless delivery, tenant configuration and the existing feature catalogue.
What happens next
Document the target operator, customer audience, jurisdiction and commercial operating model.
Decide which party supplies software, hosts facilities and contracts with players; obtain advice on the resulting licence responsibilities.
Select the first games, markets, channels and customer workflows.
Agree migration needs, provider responsibilities and the customer’s acceptance questions.
Reconcile the delivery budget against that scope and seek a documented customer commitment.
What completion means
Both sides can identify exactly what will launch, who is accountable and what evidence is needed. No unsigned interest is counted as a contract.
02 / DemonstratePROPOSED NEXT WORK
Build the customer-specific demonstration
Show the prospective customer’s business in action: brand, acquisition journey, player experience and staff workflow.
What we already have
Seven existing brand demos, the shared widget/skin system, custom API delivery and the customer demo brief builder.
What happens next
Translate the customer’s positioning into navigation, content hierarchy, typography, colour, mobile layout and supported journeys.
Build onboarding through to account history, using an isolated play-credit evaluation session.
Represent the selected sportsbook or game catalogue and demonstrate rules and account controls.
Provide a supervised operator walkthrough for reporting, player servicing, trading and audit.
Record representative journeys and gather specific acceptance feedback.
What completion means
The customer can evaluate their actual workflows and the team can estimate the remaining work. A polished demo is still an evaluation environment.
03 / TestPROPOSED NEXT WORK
Prepare games, RNG and integration evidence
Make the implemented product independently assessable, using an identifiable release and a bounded first slate.
What we already have
Game engines, published-return checks, deterministic round evidence, recovery tests and the internal verification tools.
What happens next
Freeze the release identifiers, engine versions, paytables, rule text and configuration for the submitted scope.
Assemble RNG design, seed lifecycle, game-maths/return calculations and round-reproduction examples.
Run the relevant simulations, financial-integrity, interrupted-round and integration checks; retain the results with the build identity.
Obtain a scoped external testing engagement and submission requirements.
Submit the agreed build, track findings and retest changes that affect the assessment scope.
What completion means
The relevant external findings are resolved and the independent results identify the actual assessed build and scope. Internal test counts are supporting evidence.
04 / AssurePROPOSED NEXT WORK
Complete the ISO 27001 management-system work
Extend the implemented technical controls into a scoped, operated information security management system.
What we already have
Staff authentication, tenant controls, audit, financial integrity, privacy workflows and the assurance evidence map.
What happens next
Define the service and organisational scope, assets, data, suppliers and customer responsibilities.
Carry out risk assessment and treatment; maintain the Statement of Applicability with justification and evidence.
Assign control owners and implement policies for access, change, incidents, suppliers, retention and business continuity.
Collect operational evidence, train staff and rehearse recovery and incident handling.
Perform internal audit and management review; commission the independent certification assessment and close findings.
What completion means
The management system has been assessed within its stated scope, with findings resolved and any certificate described accurately. Product code alone is insufficient.
05 / AssurePROPOSED NEXT WORK
Plan and evidence the customer’s SOC 2 requirements
Determine which assurance report customers need and plan the evidence collection accordingly, rather than promising a generic badge.
What we already have
The same authentication, availability, audit and transaction-integrity controls described on the assurance page.
What happens next
Confirm the customer procurement requirements and the service boundaries for the examination.
Agree the relevant Trust Services Criteria and report type with the examiner.
Describe the service, controls, responsibilities and evidence sources.
Close readiness gaps and collect evidence for the agreed examination scope and period.
Undertake the examination and handle report access, exceptions and remediation.
What completion means
An independent report exists for the actual scoped service and is described by its type and period. Planned assurance is not a completed examination.
06 / IntegratePROPOSED NEXT WORK
Contract and accept the launch providers
Replace demonstration configuration with provider connections suitable for the chosen customer and jurisdiction.
What we already have
Payment, identity, exclusion, location, odds/content and settlement interfaces and internal workflows.
What happens next
Agree a provider matrix covering identity, national exclusion, geolocation, gaming payments, official settlement data and chosen external content.
Confirm eligibility, commercial rights, contractual responsibilities and data-processing arrangements.
Configure credentials and tenant-specific policy without exposing secrets in customer interfaces.
Exercise success, refusal, timeout, retry, duplicate callback, dispute and exception paths where applicable.
Record integration acceptance and align failure behaviour with the operator’s launch policy.
What completion means
Each required integration works under accepted production configuration and its rights, failure handling and owner are documented.
07 / ProvePROPOSED NEXT WORK
Measure representative performance and resilience
Substantiate the speed and stability proposition with reproducible measurements under a realistic workload.
What we already have
Static customer delivery, headless API, shared brand assets, health checks and concurrency probes.
What happens next
Define representative device/network profiles, journeys, concurrency and workload mixes.
Measure customer loading, API latency percentiles, errors and settlement behaviour under the stated environment.
Exercise contention, retries, delayed feeds and provider failures without placing production customer funds at risk.
Document bottlenecks, capacity changes and repeat the relevant measurements after remediation.
Agree monitoring, alert thresholds and the customer’s actual service expectations from the results.
What completion means
Claims can be tied to a workload, build, environment and result. The site’s three public reads remain browser round trips, not a substitute for this work.
08 / OperatePROPOSED NEXT WORK
Rehearse the operating service
Show that the customer service can be monitored, reconciled, supported and recovered after launch.
What we already have
Audit and reporting services, health/alerts, deployment runbooks, ledger reconciliation and round recovery.
What happens next
Assign support, finance, incident and deployment responsibilities with escalation routes.
Verify backup location, restoration, recovery objectives and a recorded recovery drill.
Establish release/change approvals, access reviews and secret/key rotation responsibilities.
Complete customer acceptance on the agreed devices, journeys, account controls and staff operations.
Perform and reconcile any agreed migration with an explicit rollback/recovery plan.
Identify the deployed build/configuration and use a controlled release window with active monitoring.
Review incidents, conversion, repeat engagement, service costs and customer outcomes after launch.
Scope subsequent brands and games against demonstrated demand, delivery effort and the relevant approval boundaries.
What completion means
The customer has accepted the live service, operating evidence is retained and expansion decisions are based on actual outcomes rather than implementation counts.
The first operator deployment
A complete launch specification.
A
Commercial & regulatory
Jurisdiction, business role, licence responsibilities, contracts, provider rights and the initial game/content slate.
B
Customer experience
Brand, acquisition path, onboarding, wallet, sportsbook/games, account and responsible-play journeys across supported devices.
The founding team reports early conversations and readiness to progress deployment planning. That is prospect interest, not a representation of signed business or approval.
Help take the engine to market
The foundation is built. Be part of what comes next.
Explore the working engine, meet the team and discuss the investment that advances independent testing and first customer deployments. Bring your questions; we’ll show you the product behind the proposition.