If you run a lottery and you are shopping for a new platform, you have probably noticed something odd: nobody publishes pricing. Not the large incumbents, not the mid-tier vendors, not the startups. You can find pricing pages for project management software, CRM tools, even enterprise ERP systems. But lottery technology? You get “contact us for a quote.”

There is a reason for that. Lottery platform costs vary enormously depending on operator size, jurisdiction, game types, integration complexity, and commercial model. A number on a website would be misleading. But the lack of transparency makes it harder for operators to budget, compare vendors, or even know what questions to ask.

This article breaks down the real cost components of a lottery platform so you can walk into vendor conversations with a clear picture of what you are actually paying for.

How Lottery Platforms Are Actually Sold

Here is the first thing to unlearn: generic software pricing logic does not transfer to lottery. Perpetual licenses, the staple of enterprise software, are rare in this industry. Almost every lottery technology deal is built around revenue share in some form. The real questions are what percentage, applied to which revenue base, with what minimums, and what you pay before the first ticket is sold.

Tier-one technology contracts are how national and state lotteries have bought their platforms for decades. These are long-term technology or facilities-management agreements, typically five to ten years, where the vendor delivers and operates the central system and gets paid a percentage of sales or gaming revenue. Retail contracts historically run in the low single digits of total sales. iLottery contracts run far higher, commonly 15 to 30 percent of digital revenue once game content is included. The vendor often funds part of the capital investment itself and recovers it through the percentage over the contract term.

The important consequence: the ongoing side is where the money is. For a mid-sized operator, the vendor’s annual take under a tier-one contract easily runs into millions per year, every year of the term. Anyone comparing platforms on the upfront number alone is measuring the wrong thing.

SaaS models are the newer alternative, and they share the same revenue-share DNA, recalibrated for operators who are not billion-euro lotteries. A modest setup fee, a lower percentage, minimums sized for SME economics, and a platform that is pre-built, pre-integrated, and hosted by the vendor, with game content usually part of the deal. This is how Lottery as a Service works in practice.

The two structures rhyme. What separates them is the percentage level, the revenue base it applies to, the minimums, the size of the implementation project, and how many people you need on your side to run the result. The rest of this article walks through those components.

Setup and Implementation Fees

Even in a revenue-share deal, most vendors charge something before go-live: setup, configuration, implementation, sometimes milestone-based delivery fees.

At the tier-one end, implementation is a project in its own right, and once integration work, retail rollout, and data migration are counted, it routinely runs into the millions. At the SME-calibrated end, setup fees for a pre-built SaaS platform typically land in the low-to-mid six figures, because the platform already exists and the work is configuration, branding, and integration rather than a build.

One term worth understanding when you compare offers: the revenue base. A percentage of GGR (gross gaming revenue) and a percentage of NGR (net gaming revenue, after taxes, bonuses, or other deductions) are very different numbers on the same business. Two offers quoting “12 percent” can differ by a third or more in real money depending on the base. Pin the definition down before you compare anything.

Integration

This is where budgets go sideways. The platform contract gets approved at the board level, and then the real spending starts.

Integration covers connecting the lottery platform to your existing infrastructure: retail systems, payment providers, identity verification services, responsible gaming tools, draw management hardware, regulatory reporting feeds, CRM systems, and whatever other technology sits in your stack. Every operator’s environment is different, and every integration is custom work.

For a medium-complexity deployment, expect integration costs between $300,000 and $1.5 million. For a large national lottery replacing a legacy system with active retail and digital channels, that number can reach $3 million or more.

Timeline matters here too. A twelve-month integration project does not just cost engineering fees. It costs twelve months of delayed revenue. If your digital channel would generate $2 million per month once live, a six-month delay in go-live is $12 million in opportunity cost that never shows up on the project budget.

One integration deserves its own paragraph: payments. Regulated lottery operators almost always work with local payment providers specific to their jurisdiction, because that is what the licence, the banks, and the players require. No vendor arrives with your local PSP already wired in. What a well-built SaaS platform offers instead is an open payment architecture and a team that has connected local providers many times before, which turns a months-long custom project into a routine one. The integration still happens; it just stops being the thing that blows up the timeline.

Beyond payments, a managed SaaS model shifts most integration work to the vendor as part of onboarding, and the pre-built platform keeps the baseline cost far lower. Custom integrations with legacy retail systems can still add cost and time.

Ongoing Fees, and What They Do Not Cover

In a revenue-share contract, hosting, maintenance, and support live inside the percentage. That part is clean. The costs that surprise operators sit next to the percentage, not inside it.

Change requests are the big one. Under a tier-one contract, new features, new game formats, jurisdiction changes, and integrations beyond the original scope are typically scoped and billed as separate projects, often at time-and-materials day rates. Over a ten-year term, an operator that wants to keep innovating can spend as much on change requests as on the base fee. This is where “the platform is paid for” turns out to be untrue in practice.

Minimums are the other one. Most rev-share contracts carry monthly or annual minimum fees so the vendor’s floor is protected if revenue underperforms. Sensible in principle, but minimums calibrated for a tier-one operator can be punishing for a smaller one. Ask for the minimum schedule early; it tells you who the contract was actually designed for.

SaaS models aimed at smaller operators tend to keep more inside the fee: platform updates, new standard features, and regulatory maintenance are usually part of the service, with custom work billed separately at a smaller scale. The structural difference is not that change is free, but that the baseline platform keeps evolving without a project invoice attached.

Game Content

A platform without games is a very expensive empty room, and “games” means three different things with three different cost profiles.

Classic lotto and draw games are usually part of the platform itself: the draw engine, prize logic, draw management, and winner handling. Their cost hides inside the platform scope rather than appearing as a content line item, but scope matters. Adding a new draw game format, a secondary draw, or a bundle mechanic under a tier-one contract is typically a billed change project. Check how much freedom you have to configure new draw formats yourself versus paying for each one.

Instant win and eInstant games and raffle products are content in the licensing sense: they need to be licensed, integrated, certified, and maintained. Under a tier-one contract this is almost always a separate line item. You either license games from the platform vendor’s studio, contract with third-party providers, or build your own content, which requires a game studio, certified RNG, and an ongoing production pipeline.

Third-party game licensing typically runs between 10% and 30% of the net gaming revenue those games generate. Under a traditional contract, every additional provider means its own integration project, certification round, and commercial negotiation, so the administrative overhead adds up fast.

This is one place where SaaS platforms have a structural edge: content aggregation usually comes as standard. The platform ships with a certified game library, and third-party studios connect through the aggregation layer rather than through one-off integrations, so contracting additional content becomes a commercial decision instead of an engineering project.

Regulatory and Certification Costs

Every jurisdiction has its own certification requirements. The platform, the RNG, the games, and sometimes the hosting environment all need to be tested and certified by accredited labs before you can go live.

Initial certification for a new market typically costs $50,000 to $200,000 and takes two to six months. Ongoing recertification (required whenever you update the platform or release new games) adds $20,000 to $80,000 per year depending on the jurisdiction and the frequency of your release cycle.

These costs exist regardless of which commercial model you choose, and no model makes them disappear: a SaaS platform entering your jurisdiction still has to certify its platform and its games for that jurisdiction, the same as anyone else. What differs is who runs the process and how practiced they are at it. In many tier-one contracts the operator coordinates certification with the testing lab, or pays the vendor to do it as a billed project. A SaaS vendor that has already been through certification in multiple jurisdictions handles it as part of the service, arrives with the documentation and lab relationships in place, and integration for the new market tends to be easier. The lab still tests everything; you just spend less time managing the queue.

The Costs Nobody Puts in the RFP

Here is where experienced operators nod and less experienced ones get surprised.

Staffing. A platform you operate yourself requires people to run it. Platform administrators, technical operations staff, database administrators, QA testers, a security officer, a compliance manager, integration engineers. For a full iLottery deployment, you are looking at eight to fifteen additional headcount. At fully loaded costs of $80,000 to $150,000 per person per year, that is $640,000 to $2.25 million annually in staff costs alone.

A SaaS model reduces the operator-side team to two to five people (typically a product owner, a marketing lead, a compliance contact, and one or two support staff) because the vendor runs the technical operations.

Training. Every new platform means training your existing team. Plan for $30,000 to $100,000 in direct training costs plus the productivity dip during the transition period.

Change management. If you are replacing an existing platform, you are also migrating player accounts, transaction histories, responsible gaming records, and active promotions. Data migration alone can take three to six months and cost $100,000 to $500,000 depending on the complexity of your legacy system and data quality.

Vendor lock-in. This is a cost that does not appear on any invoice but matters at renewal time. If your platform vendor owns the player database, the game integrations, and the regulatory certifications, switching vendors means rebuilding from scratch. The more proprietary the implementation, the higher the switching cost, and the weaker your negotiating position when the contract comes up for renewal.

So What Does It Actually Cost?

Here is a rough total-cost-of-ownership comparison over five years for a mid-sized lottery operator (annual digital revenue of $20 million to $50 million).

Tier-one contract: implementation project running into the millions, then 15% to 30% of digital revenue once content is included, plus operator-side staffing of $640,000 to $2 million per year, change requests, certification, and training. On $30 million of annual digital revenue, the percentage alone is $4.5 million to $9 million per year. Five-year total: comfortably north of $25 million, and often far more.

SME-calibrated SaaS: setup in the low-to-mid six figures, a materially lower revenue share with content included, minimums sized for smaller operators, and a lean operator-side team of $200,000 to $600,000 per year. Five-year total: typically a third to a half of the tier-one figure on the same revenue, with go-live measured in months rather than years.

Neither model is cheap, because running regulated lottery infrastructure is not cheap. The question is whether the fee structure was designed for your size of operation. A percentage and a minimum schedule built for a billion-euro lottery do not scale down gracefully; they either price you out or make you the vendor’s least important customer. That, more than any single line item, is what a smaller operator should be comparing.

How to Evaluate What You Actually Need

Before you talk to any vendor, get clear on a few things:

What is your realistic digital revenue projection for the first three years? That number determines whether a revenue share or a fixed fee is more favorable.

What existing systems does the platform need to connect to? Every integration adds cost, regardless of the commercial model.

How large is your internal technical team, and how much do you want to grow it? If the answer is “not much,” a managed service makes more sense than a self-hosted platform.

What is your time-to-market requirement? If you need to be live in months rather than years, the implementation timeline matters as much as the price tag.

And finally: what does the contract actually say about data ownership, game portability, and exit terms? The cheapest platform on paper can become the most expensive one in practice if you cannot leave without rebuilding everything.

Frequently Asked Questions

How much does a lottery platform cost?

Almost all lottery platform deals are revenue share rather than fixed licenses. Expect a percentage of digital revenue between roughly 5% and 30% depending on vendor tier and what is included, plus setup and implementation fees ranging from the low six figures for a pre-built SaaS platform to several million for a tier-one implementation. For a mid-sized operator, annual platform costs run from the high six figures into the millions.

What is the difference between a tier-one lottery contract and a SaaS model?

Both are usually revenue-share structures. Tier-one contracts are long-term technology agreements with large implementation projects, higher percentages once content is included, minimums calibrated for very large operators, and change requests billed as separate projects. SaaS models use a pre-built, vendor-hosted platform with a smaller setup fee, a lower percentage, minimums sized for smaller operators, and game content typically included.

How long does it take to launch a lottery platform?

Tier-one implementations typically take twelve to twenty-four months from contract to go-live. SaaS platforms that are pre-built and pre-certified can go live in a fraction of that time, sometimes within a few months, because the core platform already exists and only needs configuration and branding.

What are the hidden costs of a lottery platform?

The most commonly overlooked costs are internal staffing (eight to fifteen people for a self-operated platform), change-request fees over the contract term, monthly minimums, data migration from legacy systems, regulatory certification and recertification, game content licensing, training, and the opportunity cost of delayed go-live. Also check which revenue base the percentage applies to: GGR and NGR can differ by a third or more in real money.

Is a SaaS lottery platform suitable for large operators?

SaaS models work well for small-to-mid operators who want speed and lower risk. Very large operators may prefer the control of a tier-one contract and can absorb its implementation cost as a small share of revenue. However, some large operators use SaaS as an innovation layer alongside their core system, precisely because it launches without touching legacy infrastructure. That covers instant win games, raffle, and pop-up campaigns, but also the classic lotto space itself: testing new draw game formats, secondary draws, and hybrid draw mechanics on the digital channel without waiting for a change project on the central system.

What should I ask before comparing lottery platform prices?

Start with your own business plan, because most pricing questions only have answers relative to it: your realistic digital revenue for the first three years, your channel mix, your game mix, and how large a technical team you actually want to run. A revenue share that is generous at one revenue level is punishing at another.

Then put the same list to every vendor: a total cost of ownership breakdown over five years, including setup, the revenue-share percentage and the exact revenue base it applies to, minimum fees, change-request day rates, staffing requirements, game content, certification, and exit costs. Ask who owns the player data and game certifications. Ask what happens to your costs if you need to switch vendors. And ask what is included in the base fee versus what gets billed separately.