Start with the deliverables
“Casino script” is a broad search term. It may mean a visual theme, code installed on your infrastructure or a platform run by a third party. Ask for a clear list: files, usage license, hosting, administration panel, documentation, updates and support. Record what is excluded too. An attractive demo helps assess the experience but cannot replace that list.
Separate the showcase from the operation
The homepage organizes banners, search and games. Behind it are registration, access roles, backoffice tools, transaction history, support and monitoring. Compare both layers. Try the demo on desktop and mobile, then ask to see administrative tasks such as publishing a campaign, finding a transaction and reviewing a failure. A game image alone does not prove distribution rights.
Check the game catalog
Request the providers, game types and titles actually available for your project. Ask who handles contracts, validation, cover updates, title removal and integration incidents. An advertised total may combine demos, third-party catalogs and games without rights for your target market. The final quantity and access conditions should appear in the proposal.
Examine payments end to end
Deposits and withdrawals need different checks. Request a flow for each: creation, identification, confirmation, callbacks, reconciliation, disputes and support. Confirm which gateway is eligible, who supplies credentials and who resolves differences between the panel and the provider. An integration mentioned in sales material still needs validation and agreed terms.
Test a realistic workflow
Prepare a short test before the meeting: find a game by name, filter a category, open it on mobile, create a test user and locate the event in the panel. Ask how the team changes banners, checks logs and handles a simulated outage. Record what worked and what still requires development, so you can compare suppliers using evidence.
Document responsibilities in the scope
Document deployment, customization, hosting, migration, data ownership, security, backups, support and acceptance criteria. Distinguish the software delivery from the authorizations needed for the intended activity. If games, gateways or timelines are unresolved, list them as contractual open items. A well-defined white label project explains who owns each step and when validation can begin.