Separate published supplier charges from the cost of doing the work. Public pricing exists for some publisher products, but this research did not establish a representative market average for negotiated US demo licences.
Which public prices can you actually use as reference points?
Slots Launch’s pricing page displays the following monthly plans. The page defines a request as a game load and says plans can be used across unlimited sites; confirm currency, taxes, overages and applicable permissions in the order. (slotslaunch.com)
| Published plan | Displayed monthly price | Included monthly requests |
|---|---|---|
| Mars | $10 | 1,000 |
| Venus | $25 | 5,000 |
| Neptune | $45 | 12,000 |
| Saturn | $115 | 35,000 |
Other reference points are materially different products:
- First Look Games advertises free DGS access for affiliate publishers, subject to its onboarding and available content. (firstlookgames.com)
- MarketJS lists Slots – Spin To Win at US$1,999, with one-domain, one-project use in its licensing summary. This is an adjacent original HTML5 product, not access to a catalogue of branded casino demos. Its prize-oriented presentation also requires review against this guide’s no-prize scope. (marketjs.com)
- A direct studio arrangement requires an actual quotation or permission proposal. This research did not verify a standard public price for the requested independent US-facing use.
Do not convert the supplied desk notes’ earlier budget hypotheses into market averages.
What belongs in a twelve-month cost model?
Use this proposed formula:
First-year economic cost = one-off supplier charges + implementation labour + legal/privacy work + recurring supplier fees + hosting/testing tools + maintenance labour + expected migration work.
Distinguish internal staff time from cash payments. Also distinguish guaranteed commitments from optional usage and contingency.
Illustrative first-year budget
Every rate and effort figure below is an assumption for demonstrating the calculation—not a wage survey, quotation or typical implementation cost.
| One-off activity | Assumed effort and rate | Economic cost |
|---|---|---|
| Brief, sourcing and permissions administration | 24 hours × US$75 | US$1,800 |
| Engineering | 40 hours × US$100 | US$4,000 |
| QA and remediation coordination | 24 hours × US$75 | US$1,800 |
| Editorial mapping | 16 hours × US$60 | US$960 |
| External legal/privacy review | 6 hours × US$300 | US$1,800 |
| One-off total | 110 hours | US$10,360 |
| Recurring activity | Monthly assumption | Annual cost |
|---|---|---|
| Supplier subscription | US$45 | US$540 |
| Incremental hosting/testing tools | US$50 | US$600 |
| Maintenance | 6 hours × US$75 = US$450 | US$5,400 |
| Recurring total | US$545 | US$6,540 |
Illustrative first-year economic cost: US$16,900, before tax, unexpected overages, incident work and migration. The assumed supplier fee is a modelling input, not a statement that a particular plan supplies your required rights or coverage.
How do you calculate cost per usable, authorised game?
For a monthly service-only comparison:
Monthly supplier fee ÷ usable games during that month.
For a fuller annual comparison:
Annual economic cost ÷ the sum of usable game-months.
If the example maintains 100 usable games in each of 12 months, it has 1,200 usable game-months. US$16,900 divided by 1,200 is approximately US$14.08 per usable game-month. The supplier subscription alone would be US$0.45 per game-month.
Do not divide annual costs by the latest, unusually large catalogue snapshot and present the result as a stable monthly unit cost.
How should you forecast usage charges?
Build the forecast from your own funnel. For example, these assumptions produce:
100,000 monthly page visits
× 5% initiating a demo
× 1.2 iframe loads per initiation
= 6,000 visitor-driven loads
+ 900 QA and monitoring loads
= 6,900 total assumed monthly loads
Ask how retries, bots, staging, failed launches and monitoring are counted. Obtain written answers on overages, quota exhaustion and whether access stops or charges continue.
What should be agreed before production work expands?
Use a commercial schedule covering setup charges, minimum term, renewal, price changes, quotas, support hours, incident acknowledgement, title withdrawals, API deprecation, data export and termination.
Negotiate these as requested protections—not as benefits the supplier necessarily offers. Make final production approval conditional on resolving rights and material legal/privacy issues, even if limited staging work is already authorised.