Slot maths built to be signed off

Yes. Send yours or we will send ours, and we can sign before the discovery call if you want to talk about an unreleased game. Everything you share is treated as confidential either way. Unreleased work is never named publicly, and a game only appears in our track record once it is live.

You do. The maths model, the code written specifically for it, the documentation and the prototype build are yours on final payment, to use, change and certify as you see fit. What stays with us is the tooling: the simulation framework the model runs on and the Unity front end that drives the prototype. Where the model relies on part of the framework, the documentation explains how that part works, so your engineers can reproduce its behaviour in your own engine without needing ours.

Nothing touches your pipeline until handover. We build, simulate and test on our own framework, then hand over one package: the maths model and the code written specifically for it, a documented build, the maths documentation (RTP by component, hit rates, max win and its frequency, volatility, and the simulation results behind each figure), documentation of how the parts of our framework the model uses actually work, and the prototype. The framework itself stays with us. Your engineers integrate on their own schedule, in your own engine. If you want us alongside them while they do, development assistance covers it: we review the implementation against the model so the shipped game matches the one that was signed off.

It depends on scope, which is why the quote follows the call. As a guide, a maths model to agreed RTP targets takes 3 to 5 weeks, and design through to a playable prototype takes 8 to 12 weeks. The quote states the timeline for your game, and if anything moves it you hear from us before it does.

Fixed price, invoiced in stages at the milestones set out in the quote, so you pay as the work is delivered. Invoices are due within 30 days. The deliverables transfer to you on final payment.

The handover package exists so this is caught before certification, not after: every figure comes with the simulation that produced it, so your team and the test house can check it. If a test house result still differs from ours, we find out why. If the difference is in our model, we fix it at no cost to you. If it is in the implementation, we show your engineers exactly where the two diverge, under development assistance if that is in place, or as a scoped piece of work if it is not.

Yes, and a first title with no maths lead in the building is where we are most useful. You get a model documented to the standard a test house expects without hiring for it, and a fixed quote before you commit. The discovery call is the same whether you are a two-person studio or an operator commissioning an exclusive.