How Much Does Charity Raffle and Lottery Software Cost in 2026?
$80,000 to $450,000, and the number of jurisdictions you sell into moves the figure more than ticket volume ever will.
On this page
$80,000 to $450,000, and the number of jurisdictions you sell into moves the figure more than ticket volume ever will. A first release covering licensed ticket issuance with sequential auditable numbering, age and location eligibility gating, payments engineered for draw night concurrency, the draw with retained evidence and winner notification runs $80,000 to $170,000 in 14 to 20 weeks in Digital Heroes delivery experience. A full platform adding subscription and calendar draws, bonus and early bird structures, in venue point of sale (POS), prize claim workflow, regulator reporting and a fundraising system link runs $200,000 to $450,000 across 8 to 14 months. Every additional province or state is a separate rule set for eligibility, numbering, unclaimed prizes and reporting, and often a separate certification with calendar time you cannot compress.
The bands a licensed draw build falls into
Two bands and one line that sits outside both.
The first band is the compliance core: ticket issuance with a provably sequential ledger, an eligibility gate that runs before the payment step, payment handling designed for the spike rather than the average, the draw itself with a sealed pool and a retained evidence pack, and winner notification. That is $80,000 to $170,000 and ships in 14 to 20 weeks. It is the smallest thing you can responsibly put a licence behind.
The second band is the programme platform. Subscription draws that enter a supporter every month with failed payment handling, calendar draws, early bird and stacked structures with their own numbering, in venue point of sale on handheld devices, prize claim with identification and withholding, the regulator reporting pack, and the link into your donor database with source attribution. That runs $200,000 to $450,000 over 8 to 14 months.
The line outside both is certification. Where your regulator requires the system to be reviewed or approved before use, that time sits after the software is finished and it does not shrink by adding engineers. Put it on the plan as its own item with its own date, because it is the most common reason a first draw slips a season.
What drives a raffle build up
Jurisdiction count. Each one carries its own eligibility rules, its own numbering and record keeping expectations, its own treatment of unclaimed prizes and its own reporting format. Ontario's electronic raffle requirements are the strictest common reference point, and a system built to that standard tends to satisfy others, but tends to is not the same as does, and the second jurisdiction is a real phase rather than a configuration flag.
In venue sales. Handhelds, printers, staff logins, and arena connectivity that fails exactly when 70 percent of your money is arriving turns a web problem into a field operations problem with hardware, training and a support plan.
Payment architecture at draw night concurrency. Designing and load testing for hundreds of sales a second is different engineering from a checkout that handles a steady trickle, and the idempotency and reconciliation work that stops a buyer paying without receiving a ticket is not optional.
Subscription draws, which look small and arrive with recurring billing, failed payment recovery and entitlement questions about whether a lapsed supporter is in this month's pool.
Unusual draw structures. Stacked draws, early bird prizes needing their own numbering, and ticket packs with different odds all sit outside what packaged products expose.
What keeps the number down
Launch with one draw type in one jurisdiction, online only. Prove the compliance core through a real draw and an audit before adding anything.
Treat in venue point of sale as phase two. It is the single largest add on and it is the one most tied to hardware decisions you may not have made.
Defer the donor database integration. It matters strategically, but consent handling, deduplication and gift versus non gift transaction treatment all need decisions before a record moves, and those decisions are yours to make rather than something a developer can shorten.
Have your licence conditions, draw structures, close times, prize claim rules and reporting formats documented before kickoff. Charities that arrive with these settled move materially faster than those still deciding what they will sell.
Do not build your own payment processing. Use an established processor and spend the engineering on the ledger, the gate and the evidence, which are the parts nobody else can build for you.
A worked example that adds up
A hospital foundation running a weekly 50/50 with jackpots into six figures, plus one annual calendar draw, in a single province, online only for year one.
- Discovery, licence condition capture, draw structure definition: $10,000
- Ticket issuance with pre allocated blocks and an append only ledger: $26,000
- Eligibility gate with age declaration and geolocation with recorded method: $18,000
- Payments with idempotency keys and processor reconciliation: $29,000
- Draw engine with sealed pool, hash, documented random source, draw certificate: $21,000
- Winner notification and prize claim workflow: $14,000
- Regulator reporting pack generated from the ledger: $13,000
- Load testing and remediation to a defined peak: $9,000
That is $140,000, which sits near the top of the first release band because the foundation insisted on the reporting pack in phase one rather than assembling the first few reports by hand. Delivery ran nineteen weeks, followed by five weeks of regulator review before the first live draw.
Year two added subscription draws at $27,000 and in venue handheld sales at $46,000, taking the programme to $213,000. A second province, evaluated and then deferred, was quoted at $34,000 for the rule set alone, excluding any certification.
How the spend phases
Weeks one and two are licence conditions and draw structures, with your compliance counsel in the room. The policy question that must be answered here is what happens when a location check is inconclusive, which happens constantly inside arenas. That is a decision for counsel, and the software then applies it consistently.
Weeks three to ten build the ledger, the gate and payments. The ledger goes first because everything else depends on it and because it is the part a regulator will test.
Weeks ten to sixteen build the draw engine and the evidence pack, then the claim workflow and reporting.
Load testing belongs at week sixteen, not week nineteen. Finding a write bottleneck a week before launch is how a draw gets postponed. Agree the peak you will test to and how it will be simulated before the contract is signed.
Then regulator review, which is calendar time. Book it early and treat any date given to you as the earliest rather than the expected.
The ongoing costs nobody quotes
Hosting sized for the peak rather than the average. You pay for headroom you use for three hours a week, and trying to avoid that is how draws fall over.
Payment processing fees, which are volume driven rather than software driven but belong in the annual sum because they scale with your success.
Support on draw night. Someone competent has to be awake and reachable during every close, and that is a rota rather than a licence.
Annual load testing before the season, because your platform, your processor and your traffic all change.
Rule and reporting changes when your regulator updates requirements, plus any recertification that follows.
In our delivery experience charities budget 18 to 26 percent of build cost per year across hosting, support, draw night cover and small changes. On a $140,000 build that is roughly $25,000 to $36,000 annually, before processing fees.
Comparing a build against your current renewal
This comparison is different from most software decisions, because packaged raffle platforms commonly price per ticket or as a share of sales rather than as a flat subscription. That means your cost rises exactly as your programme succeeds, which is the opposite shape from a build.
Do the sum from your own agreement. Take last year's gross ticket sales, apply the per ticket or percentage terms as written, add any platform fee, hardware rental and support charge, then project it against the sales you expect in three years rather than the sales you had. Compare that against the build band plus three years of the run costs above.
Two lines belong in the comparison that appear in neither quote. First, staff time assembling the licence report, reconciling a processor export against a spreadsheet, and answering regulator questions from records that were never designed to answer them. Second, what an export contains: the full ticket ledger, the draw evidence and the buyer records with consent state. Your licence obligations sit with your charity, so if a regulator asks for draw evidence you cannot be waiting on a supplier to grant access to your own records.
When buying beats building
Buy if you run one or two conventional draws a year in a single jurisdiction with a modest jackpot. Rafflebox is a genuinely capable product for that shape, particularly for Canadian charitable draws, and building would be an expensive way to reinvent ticket numbering. Ascend Fundraising Solutions is worth evaluating if your volume is concentrated in venue, because they bring experience with the hardware and staffing that large in venue draws actually require.
Buy also if your team has no appetite to own a system regulators inspect. That is a legitimate position, and the wrong reason to build is that a platform fee looked large in isolation.
Build when draws have become a recurring programme with a calendar rather than an event, when you sell across jurisdictions with different rules, when your draw structures do not fit the shapes a product exposes, when per ticket fees have grown large against your charitable proceeds, or when supporter data from draws is strategically important and needs to sit in your own systems with clean attribution. The tipping point is scale plus structure. Once draws are a programme, running them on someone else's fixed workflow starts costing more in compliance overhead and lost flexibility than the software would.
If you would rather someone argued with your brief than agreed with it, Digital Heroes builds and runs its own products, so the people choosing your architecture live with those decisions on their own revenue. You keep the specification either way.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- Per the Standish Group CHAOS 2020 report (reviewed at this URL), across tens of thousands of software projects roughly 31% end successfully, about 50% are 'challenged', and roughly 19% fail outright; small projects succeed far more often than large ones, and Agile approaches succeed at markedly higher rates than Waterfall. Source: The Standish Group (2020) →
- McKinsey's Developer Velocity research finds best-in-class tools are the top contributor to software business success, yet only about 5% of executives ranked tools among their top-three software enablers, signaling underinvestment in developer tools (this finding originates in McKinsey's Developer Velocity study rather than the linked generative-AI article). Source: McKinsey & Company (2023) →
- The NRF discontinued its long-running annual shrink report, stating that a broad study of retail shrink 'is no longer sufficient for capturing the key challenges and needs of the industry' - important context that qualifies how POS/shrink benchmarks should be cited going forward. Source: Retail Dive (2024) →
- PMI's Pulse of the Profession research found organizations waste an average of roughly 9.9% of every dollar invested in projects due to poor performance - equivalent to about $1 million wasted every 20 seconds collectively worldwide. Source: Project Management Institute (PMI) (2018) →
Frequently asked questions
What is the total cost of a custom raffle and lottery platform?
$80,000 to $170,000 for a first release with compliant sequential ticket issuance, age and location gating, payments built for draw night concurrency, the draw with retained evidence and winner notification, shipping in 14 to 20 weeks. A full platform with subscription and calendar draws, in venue point of sale, prize claim and regulator reporting runs $200,000 to $450,000 across 8 to 14 months.
A single province hospital foundation running a weekly 50/50 landed at $140,000, then added subscriptions and handheld sales in year two for a further $73,000.
What does it cost to operate each year?
In our delivery experience charities budget 18 to 26 percent of build cost per year, so roughly $25,000 to $36,000 on a $140,000 build, before payment processing fees. That covers hosting sized for the peak rather than the average, support cover on every draw night, annual load testing before the season, and rule changes when your regulator updates requirements.
Payment fees scale with your success rather than with the software, but they belong in the annual sum because they are the largest recurring line for most programmes.
How long from kickoff to our first live draw?
Fourteen to twenty weeks of build, then regulator review where your jurisdiction requires the system to be examined before use. In the worked example that was nineteen weeks of delivery followed by five weeks of review.
Treat the review date you are given as the earliest rather than the expected, and book it early. It is the most common reason a first draw slips a season, and it cannot be compressed by adding engineers.
Is Rafflebox cheaper than building our own platform?
For one or two conventional draws a year in a single jurisdiction, yes, and building would be hard to justify. The comparison changes shape as you grow, because packaged platforms in this category commonly price per ticket or as a share of sales, so cost rises exactly as your programme succeeds.
Do the sum from your own agreement: last year's gross ticket sales under the terms as written, plus platform, hardware and support charges, projected against the sales you expect in three years rather than the sales you had.
Why does a second province or state cost so much?
Because it is a rule set, not a setting. Eligibility, ticket numbering and record keeping, unclaimed prize handling and reporting all differ, and many jurisdictions require their own certification with its own calendar time.
In the worked example the rule set alone was quoted at $34,000, excluding certification. That is why jurisdiction count moves a raffle budget more than ticket volume does, and why launching in one and adding the second as a deliberate phase is the cheaper path.
How much of the budget goes on the draw itself?
Less than people expect on the mechanism and more than they expect on the evidence. The draw engine with a sealed pool, a cryptographic hash, a documented random source and a draw certificate was $21,000 in the example, roughly 15 percent of the build.
What you are paying for is reproducibility months later: which tickets were in the pool, when it was frozen, how one was selected and who witnessed it. A draw you cannot reconstruct is a draw you cannot defend, and confirming your specific evidentiary obligations with your regulator and counsel comes before any of this.
What does in venue selling add to the price?
It was $46,000 in year two of the worked example, the largest single add on. You are buying handheld devices, printers, staff logins, offline tolerance for arena connectivity that fails when most of your money is arriving, plus training and a support plan.
Treat it as its own phase after the online core has run real draws. Ascend Fundraising Solutions is worth evaluating here, because in venue draws are as much a staffing and hardware operation as a software one.
Can we afford to skip the regulator reporting pack in phase one?
You can, and some charities do, assembling the first few licence reports by hand from a payment export and a spreadsheet. It costs about $13,000 to build and saves perhaps a week of delivery.
We would keep it. Reports generated from the same ledger that issued the tickets take minutes and reconcile by construction. Assembled by hand they take days and they disagree with each other, which is the version a regulator notices.
What makes the estimate rise after work has started?
Draw structures that were described simply and turn out not to be, particularly early bird prizes needing their own numbering and ticket packs with different odds. Load testing that finds a write bottleneck late, which is why the test belongs at week sixteen rather than week nineteen.
And policy decisions left open, above all what happens when a location check is inconclusive. That is a question for your compliance counsel, and paying engineers to wait for the answer is the most expensive delay in the project.
What are the biggest mistakes first-time software buyers make?
Choosing the lowest bid, paying more than 30-40% upfront instead of on milestones, skipping a written specification, and having no maintenance plan for after launch. The most expensive of the four in Digital Heroes rescue projects is the missing spec: without written acceptance criteria, done becomes an argument instead of a checklist, and every disagreement resolves in the vendor's favor. Fix those four and you have avoided most of the ways these projects fail.
We run everything on Airtable and spreadsheets. When is it time to go custom?
The switch usually makes sense when you hit one of two walls: Airtable's record caps (125,000 records per base on the Business plan) or logic the tool cannot express, like multi-step approvals with conditional pricing. There is also a simple cost signal: 25 people on Business at roughly $45 per seat per month is about $13,500 a year, forever, for a tool you are already fighting. Custom is worth it when the workflow is core to how you make money; for peripheral processes, staying on Airtable is the right call.
How do we get years of data out of our old system and into the new one?
Treat migration as a planned sub-project: a field-mapping document, at least one dry run on a copy of your data, then a cutover with the old system kept read-only for 30 days as a safety net. On Digital Heroes projects it consumes 10 to 15% of the budget when the old system has an export, and more when data must be pulled out screen by screen. Ask any vendor to walk you through their last migration before you sign.
Will custom software work with the tools we already use, like QuickBooks and Stripe?
Yes, and this is one of custom software's genuine advantages: QuickBooks, Stripe, Shopify, and most mainstream business tools publish documented APIs built for exactly this. Expect each standard integration to add one to two weeks of build time, and be suspicious of any quote that lists five integrations without asking what data flows in which direction. The hard cases are legacy systems with no API, which is a question to raise in discovery, not in week nine.
Our developer disappeared mid-project. Can another team pick up the code?
Yes, this is a routine engagement, provided the code exists somewhere you can access, so your first move is securing the repository, hosting, and domain credentials today. A takeover starts with a one to two week paid code audit that ends in one of three verdicts: continue the build, keep the design but rebuild the weak parts, or start over. Digital Heroes has inherited enough projects to say plainly that sometimes the rebuild is cheaper than the rescue, and an honest agency will tell you which one you have before taking your money.
How do I vet a software development agency before signing a contract?
Ask to speak with two past clients whose projects resemble yours in size and industry, and ask exactly who will write your code, since some agencies sell senior faces and deliver junior or subcontracted hands. Demand a written specification with acceptance criteria before any fixed price, and check that their portfolio links to products that are actually live. An instant quote given without questions about your workflows is the clearest warning sign there is.
What should I prepare before contacting a software development agency?
A one-page brief beats a 40-page requirements document: the business problem in plain words, who will use the system, the 5 to 10 workflows it must handle, the tools it must connect to, and your budget range and deadline driver. You do not need wireframes, a specification, or technical vocabulary; producing those is the agency's job during discovery. Stating a budget range up front is the single best move, because it gets you honest scoping instead of a quote engineered to win the meeting.
How long does it take to build a custom web or mobile app from scratch?
Plan on 8 to 16 weeks for a focused first version and 4 to 9 months for a larger platform, which is the typical spread across Digital Heroes builds. The first 2 to 3 weeks go to discovery and design before any production code ships. The two things that stretch timelines most are integrations with legacy systems and slow feedback from your side, not developer speed.
Who can build a custom software system?
Digital Heroes builds custom software systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, with an assigned senior team rather than an account manager.
Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.
What makes Digital Heroes different from other software companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
Related guides
Published · Last updated .
