A substantial build to evaluate
Inspect ${doneCount} recorded implementation items across ${buildRecord.length} delivery areas, documented APIs, internal verification and functioning play-credit journeys.
Review the built foundation06 / The investment opportunity
Back the engine.
Unlock the deployments.
The core software is built. Seven brands demonstrate the delivery flexibility. Early deployment conversations are underway. Investment now funds the independent testing, assurance and launch work needed to turn that foundation into an approved customer service.
The business we are building
A platform at the centre
of many gaming brands.
BetSystem CMS brings the customer engine and operator workflow together: accounts, wallet, sportsbook, games, safer-play controls, trading, CRM and reporting. Customers can use a site-builder integration, web widgets or a bespoke API experience to present that capability as their own brand.
Several ways to reach customers
Serve operators who need a visually composed site, an embedded web experience or a fully custom interface. The same engine supports these different delivery choices.
Explore delivery routesA defined route to deployment
The next milestone has concrete outputs: independently assessed scope, accepted integrations, operating evidence and an approved first customer release.
See the execution planWhy the architecture matters commercially
Reuse the foundation.
Differentiate the customer.
A shared engine across deployments
The platform thesis is to reuse the account, financial and product foundation while configuring or extending the experience for each customer. Repeatability needs to be measured through the first deployments.
An ongoing operator relationship
Software delivery can extend into platform service, support, integrations and product development. The commercial scope follows the operator’s responsibilities and the agreed service.
Proposed revenue routes include software licensing or platform-service fees, scoped onboarding and integration work, and ongoing support. These are commercial options to validate and contract with customers; this site does not represent a final price list or established revenue.
The proposition, with evidence
Ambition you can interrogate.
A product you can use.
API-driven
A versioned API and OpenAPI specification; Kestrel demonstrates a custom sportsbook built without the shared widget engine.
Inspect the integration surfaceBrand-flexible
Seven customer experiences, an Elementor integration, web widgets and ten recorded skin presets provide a tangible delivery toolkit.
Explore the working brandsOperationally connected
Player accounts, transaction records, trading, CRM and staff controls form a connected operator foundation.
Review operator capabilityPerformance leadership is a proposition to prove with representative benchmarks. Independent approval, willingness to pay, deployment cost and customer retention remain explicit milestones in the plan.
Use of capital
Workstreams with
measurable outcomes.
WorkstreamWhat it fundsEvidence of completion
Independent game / RNG testing
A frozen initial build, scoped external testing and remediation.
Applicable independent reports and accepted findings.
Security & assurance
Readiness work, independent security review, the scoped ISO programme and customer-led SOC 2 planning.
Closed findings, programme records and actual certification/report outcomes when obtained.
Provider integrations
Contracted identity, exclusion, location, gaming payments and settlement-grade data.
Accepted live integrations with documented responsibilities.
First operator delivery
Customer-specific design, configuration, migration if required, acceptance and launch operations.
Agreed commercial scope, signed acceptance and authorised release.
Execution runway
A focused delivery team and operating contingency sized to the scope.
A reconciled budget and milestone-based reporting.
Raise size, valuation, terms and timelines are discussed privately after scope and external estimates are reconciled. No historical financial scenario is presented here as a current offer.
Commercial progress
Early conversations.
A deployment-led next step.
Founder-reported discussions
The team has had early conversations and is ready to progress deployment scoping. No signed customer, committed revenue or investment commitment is claimed on this site.
Convert interest into evidence
Agree a prospective operator’s specification, obtain a documented commercial commitment where possible, and attach the testing and launch plan to that scope.
Diligence materials
The questions we expect
serious investors to ask.
Product & engineering
Identify the build, inspect API and tests, assess ownership and dependencies, and review representative customer workflows.
Regulatory & delivery
Review the business role, applicable licences, quoted testing scope, integration contracts and operational launch plan.
Company & economics
Confirm company details, IP ownership, team capacity, cap table, budget, customer evidence and unit-economics assumptions.
Detailed financial, company, contract and customer materials are shared directly with the team. This public site does not expose a data room or imply that documents have been completed when they have not.
Risks & dependencies
A fundable plan
makes the dependencies visible.
Approval & provider dependencies
External testing, licence decisions, payment underwriting and data rights can affect scope, cost and timing. Outcomes are not guaranteed.
Commercial & execution risk
Prospect interest must become paying deployments. Performance at representative scale, operational effectiveness and delivery capacity still need measured evidence.