Most write-ups of this idea start with a market-size number and a list of tools you could build. That is the wrong end of the problem. A sports analytics product is not a software business with a data cost attached. It is a data licensing business with a software layer on top, and the licensing terms decide almost everything else: what you can charge, who you can sell to, which countries you can operate in, whether an app store will list you, and whether a payment processor will keep you.
The two largest companies in this sector both publish their accounts. In 2025 Sportradar reported total revenue of 1,290 million euros and profit for the period of 100 million euros, or 7.8 per cent of revenue. Its sport rights costs in the second quarter alone were 106.2 million euros against 318 million euros of quarterly revenue, and 210.2 million euros across the first six months, which works out at roughly a third of revenue going straight to rights holders. Genius Sports reported 2025 group revenue of 669.5 million dollars against cost of revenue of 515.6 million dollars, and a net loss of 111.6 million dollars, wider than the 63.0 million dollar loss in 2024.
Two caveats on those figures. Sportradar's sport rights line is a specific disclosed cost, and it runs at around a third of revenue. Genius Sports does not break out data rights separately; its 515.6 million dollar cost of revenue includes rights payments alongside other direct costs, so 77 per cent is the ceiling of what rights could be, not the rights figure itself.
Even read conservatively, the picture is the same. These are the incumbents. They have the exclusive contracts, the scale, the sportsbook customers and the public listings. One of them still pays roughly a third of revenue straight to rights holders, and the other is still loss-making at nearly 670 million dollars of turnover.
That is the context to hold in your head before you write a line of code.
If you want a single case study in how sports data rights destroy companies, it is IMG Arena. Endeavor Group built a betting data business on a portfolio of exclusive rights deals with sports federations. In March 2025 it agreed to hand the entire business to Sportradar. Not sell it, hand it over. Under the announced structure Sportradar paid no consideration; instead Endeavor paid a total of 225 million dollars, comprising 125 million dollars in cash to Sportradar and up to 100 million dollars in prepayments to certain rights holders. The deal closed on 3 November 2025.
Reporting at the time was blunt about why: Endeavor could not find a buyer willing to assume the rights commitments, and chose to pay to escape them rather than keep funding them. Before completion, IMG Arena was asked to exit a loss-making European Leagues Association agreement.
A company inside one of the largest sports agencies in the world signed multi-year data rights contracts, could not monetise them, and paid a quarter of a billion dollars to be released. If your plan involves acquiring sports data rights, that is the base rate you are working against.
There is a persistent myth that scores and statistics are free because facts cannot be copyrighted. The first half is broadly right in the United States. The second half does not follow, because the thing being sold is not the fact. It is speed, completeness, contractual certainty and the right to say the word "official".
The commercial structure that has emerged is exclusive, long, and expensive.
The practical consequence for a small operator is simple. For the major North American and European leagues, there is no window in which you buy official low-latency data directly from the league. The league has already sold it, exclusively, to a counterparty with a nine or ten-figure balance sheet. Your only routes are a sublicence from that counterparty, a downstream feed with delay, aggregated bookmaker odds rather than event data, or unofficial collection.
The leagues' negotiating position is not purely commercial. Several US states have written official league data into statute for certain wager types, which converts a commercial preference into a legal requirement for licensed operators.
The Kansas Legislative Research Department listed six states requiring official league data for proposition bets, in-play wagers, or both: Arizona, Illinois, Michigan, North Carolina, Tennessee and Virginia. Sportshandle's coverage lists a wider set including Kansas, Massachusetts and New York. Tennessee's statute requires licensed operators to use official league data exclusively for live betting, subject to an exception. Sources differ on the precise current list and the scope of each mandate, and the mandates have been amended since first enactment, so check the current statute and regulator guidance in each state you care about rather than relying on any list, including this one.
The point for you is second-order but important. Mandates guarantee the leagues a captive institutional buyer for the official feed. That sets the floor price for the whole market. Every downstream product, including yours, is priced above a floor that a regulator helped establish.
This is where most independent projects live, and where most of them are wrong about their exposure. The honest summary is that scraping sports data is rarely a criminal computer-misuse problem in the US, frequently a contract problem everywhere, and a serious intellectual property problem in the UK and EU.
The Computer Fraud and Abuse Act is the statute people fear. In Van Buren v United States (2021) the Supreme Court read the "exceeds authorized access" provision narrowly, framing it as a gates-up-or-down inquiry. In hiQ Labs v LinkedIn the Ninth Circuit held, twice (most recently in April 2022 after remand in light of Van Buren) that automated collection from publicly accessible pages that do not require an account does not amount to access "without authorization" under the CFAA.
So far so encouraging. Then read what happened next.
In November 2022 the district court held that provisions of a website user agreement prohibiting data scraping and the creation of fake profiles are enforceable as a matter of contract. The parties then entered a consent judgment: 500,000 dollars against hiQ, findings of liability under California common law trespass to chattels and misappropriation, and injunctive relief that effectively ended hiQ's ability to scrape LinkedIn at all.
hiQ won the constitutional-scale argument and lost the business. That is the correct model for how this usually goes. The CFAA is not your main risk. The terms of service you clicked through, and the tort claims that survive alongside them, are. Note also that the consent judgment is a stipulation, not a judicial finding, and carries no precedential weight; it tells you about commercial outcomes, not about what a future court must hold.
Two decisions matter and both are helpful to builders, within limits.
In NBA v Motorola (2d Cir 1997) the court held that professional basketball games are not original works of authorship protected by the Copyright Act, that the NBA's state-law misappropriation claim was preempted except for a narrow "hot news" category, and that transmitting real-time scores and statistics to pagers was not misappropriation. In C.B.C. Distribution and Marketing v Major League Baseball Advanced Media (8th Cir 2007, certiorari denied 2008) the court held that although using players' names and statistics for profit implicated Missouri right-of-publicity law, the First Amendment superseded those rights in the context of fantasy baseball products.
This is the part US-centric writing about sports data almost always omits, and it is the part most likely to cause a British or European founder real trouble.
Directive 96/9/EC created a sui generis database right, separate from copyright, protecting substantial investment in obtaining, verifying or presenting the contents of a database. The UK implemented it in the Copyright and Rights in Databases Regulations 1997 and retained a domestic version after leaving the EU.
Two cases define the boundary.
In British Horseracing Board v William Hill (Case C-203/02, 9 November 2004) the Court of Justice held that "investment in the obtaining of the contents" means resources used to seek out existing independent materials and collect them, and excludes resources spent creating the materials in the first place. BHB's expenditure on selecting horses, verifying eligibility and drawing up race lists was investment in creating data, not obtaining it, and so did not attract the sui generis right. Fixture lists and entry lists generated by the organiser of an event therefore sit outside the right.
But in the Football DataCo litigation against Stan James and Sportradar, the Court of Appeal of England and Wales held that database right did subsist in the Football Live database of live match events, and that Sportradar and Stan James were jointly liable for the acts of UK users who accessed the data through a link on Stan James' website. Live match-event data collected by observers is obtained, not created. And so it is protected.
The distinction is not academic. Fixtures and schedules: probably unprotected. Live in-play event data compiled by human or automated observers: likely protected in the UK and EU, with no US equivalent.
Jurisdiction was settled separately. In Football Dataco v Sportradar (Case C-173/11, 18 October 2012) the Court of Justice held that sending data from a server in one member state to a user in another constitutes re-utilisation, and that the act is localised in the country where the alleged infringer intended to target the public. Hosting your servers outside the UK or EU does not put you outside the right if you are marketing to British or European users.
The third route is sending someone to the ground with a phone. This has been litigated to a conclusion, and the conclusion is unhelpful for small operators.
Football DataCo and Genius Sports sued Sportradar and, unusually, individual data scouts as representative defendants. The pleaded causes of action were breach of confidence and trade secrets, breach of contract (the ground regulations and ticket conditions), trespass to land, inducement of breach of contract, and conspiracy to cause loss by unlawful means. Sportradar counterclaimed on competition law grounds, alleging abuse of dominance in the award of the exclusive contract.
It settled in 2022. Sportradar agreed to refrain from unofficial in-stadia scouting of Premier League and Football League matches, and took a sublicence from Genius for a delayed secondary feed running to 2024. Genius retained the exclusive right to provide low-latency official Football DataCo betting data through 2024. Football DataCo retained the right to license its data as it saw fit in future. The financial terms were confidential.
Sportradar is a listed company with over a billion euros of revenue and a serious competition-law argument. It lost the ability to collect English football data unofficially and ended up as a customer of its competitor, on a delayed feed. If that is the outcome for Sportradar, it is not a viable strategy for a two-person startup.
The practical rule
Strip out the case names and the operating rule is short:
- Historical and post-match statistics from public sources carry low legal risk in the US and moderate risk in the UK and EU, and have low commercial value.
- Live in-play event data is the valuable product and is the most protected, by database right in the UK and EU, by exclusive contract everywhere, and by ground regulations at the venue.
- Bookmaker odds are a different asset again. They are the bookmaker's own commercial output. Sportsbook terms of use routinely prohibit automated access, scraping and commercial reuse. You will not be prosecuted, but you can be blocked, sued in contract, and cut off from the affiliate relationship that may be funding you.
- Whatever the law says, the counterparty's response to scraping is usually technical and commercial before it is legal: rate limits, IP bans, feed changes and account closure. A product whose supply chain can be switched off by a competitor's engineer on a Tuesday afternoon is not a durable business.
What Data Actually Costs, at Every Tier
Here is the price ladder as published in mid-2026. Verify each of these against the vendor's own page before you build a model on them, because API pricing changes without notice.
The Odds API. Free tier at 500 credits per month covering most bookmakers. Paid tiers at 30 dollars per month for 20,000 credits, 59 dollars for 100,000, 119 dollars for 5 million and 249 dollars for 15 million. Note the unit: a credit is not a request. One request returns live and upcoming games for a given sport, market and bookmaker region, and the credit cost scales with the number of markets and regions you query.
API-Football and the wider API-Sports family. A free plan at 100 requests per day, with paid plans starting at 19 dollars per month. Third-party comparison sites report a top self-service tier around 39 dollars per month for 150,000 requests. Treat the higher-tier numbers as third-party reporting rather than confirmed.
SportsGameOdds. A free tier plus paid tiers reported by third-party comparisons in the range of 99 to 499 dollars per month, billed on objects returned rather than requests.
OpticOdds. No published pricing. The pricing page is a multi-step quote request form asking for company size and required services before anyone will discuss numbers with you. No entry price is quoted here. Figures circulate in betting communities, but nothing could be confirmed against a primary source, and a number you are told not to budget with is worse than no number at all. Assume low thousands per month is possible and get a real quote before planning around it. Additional sports charged separately, but none of those figures could be confirmed against a primary source and none should be used for budgeting.
Sportradar and Genius Sports. No public price list at all. Sportradar's developer portal offers trial access via its marketplace and states plainly that its APIs are a business-to-business service not intended to be called directly from a client application. Genius Sports sells through commercial agreements. Enterprise sports data contracts in this tier are negotiated, typically annual, typically with minimum commitments, and typically include restrictions on redistribution and on serving end consumers. No list price is published, and no verifiable figure for what a small buyer pays could be found. Anyone quoting a confident number for what Sportradar charges a startup is guessing.
The step between the two halves of that ladder is the single most important economic fact in this business. There is a self-service tier at 20 to 250 dollars a month that gives you aggregated bookmaker odds and basic fixture and result data. There is an enterprise tier for official low-latency event data that starts at a negotiated annual contract. There is very little in between, and the products bettors actually pay for tend to sit on the wrong side of the gap.
How API pricing bites in practice
The trap is not the headline price. It is the multiplication.
Consider a positive-expected-value tool covering four sports, three betting markets per sport, and two bookmaker regions, refreshing every sixty seconds during the active window. The billing unit on most odds APIs multiplies by markets and regions. That is 4 x 3 x 2 = 24 billable units per refresh cycle. At one refresh a minute, that is 1,440 units an hour, 34,560 a day, and just over a million a month if you run continuously. On a 5 million credit plan at 119 dollars a month you are fine. Add player props (which can mean dozens of markets per game rather than three) and refresh every fifteen seconds because line movement is the product, and you multiply that by something between twenty and eighty. You are now shopping for the 249 dollar plan and then quickly past it.
The general shape: cost scales with markets multiplied by books multiplied by refresh frequency, and all three of those are exactly the dimensions along which your product competes. Every feature request from a serious user makes your gross margin worse. That is an unusual and unpleasant property for a software business, and it is the specific reason data bills kill these projects rather than infrastructure bills.
Two mitigations are worth building in from day one. First, adaptive polling: refresh frequently only for events starting soon or with volatile lines, and back off hard elsewhere. Second, fan-out separation: poll the upstream API once and serve all your users from your own cache. Never let user count drive upstream calls. If your architecture makes an upstream request per user page load, your marginal cost per user is an API bill, not a hosting bill, and no consumer price point will save you.
Infrastructure Cost Per User: The Part That Is Genuinely Cheap
Having established that data is expensive, it is worth being precise about what is not.
Published rates as of mid-2026:
- Supabase. Free tier: 500 MB database, 5 GB egress. Pro: 25 dollars per month, 8 GB database, 250 GB egress included, then 0.09 dollars per GB egress, 0.03 dollars per GB cached egress, 0.125 dollars per GB additional database storage. Team: 599 dollars per month.
- Vercel. Fast Data Transfer: first 1 TB included, then 0.15 to 0.35 dollars per GB depending on region. Edge Requests: first 10 million included, then 2.00 to 3.20 dollars per million. Additional team seats 20 dollars per month.
Now model a real-time odds product. Assume a logged-in user with the board open sends 40 KB of JSON per minute over a websocket or polling connection, and spends 90 minutes a day in the product. That is 3.6 MB a day, roughly 108 MB a month of egress per active user. At Supabase Pro's 0.09 dollars per GB overage, that is under one cent per user per month in data transfer. A thousand daily-active users is roughly 108 GB, comfortably inside the 250 GB included allowance.
Compute is similarly forgiving if you have separated fan-out from upstream polling. One ingestion worker maintaining a normalised odds table, and a read path served from cache, will run on a small instance for tens of dollars a month at this scale.
So a plausible fully loaded infrastructure cost for a thousand active users is in the region of 50 to 150 dollars a month. That range is an estimate derived from the published rates above, not a sourced figure. Against that, an odds API bill of 119 to 249 dollars a month, plus any premium feed, plus payment processing at typical card rates, and the shape becomes obvious: at small scale your data bill exceeds your infrastructure bill by a wide margin, and infrastructure only starts to matter if you get the polling architecture wrong.
The costs that genuinely scale badly are the ones people forget: websocket connection concurrency if you use a managed realtime service billed per connection, egress if you push full board state rather than deltas, and background job minutes if you recompute models on every tick rather than on change.
B2C Pricing: What the Market Actually Charges
You can see real prices without guessing, because subscription tiers are disclosed on app store listings.
The OddsJam iOS listing shows in-app subscription tiers including Trends at 19.99 dollars per month, Fantasy Optimizer at 59.99 dollars, Sharp Money and Gold at 199.99 dollars, Positive EV Global at 399.99 dollars, and Positive EV Monthly and Platinum at 499.99 dollars, with a seven-day free trial. The listing carries a 18+ age rating, a "Frequent Simulated Gambling" content descriptor, and a problem-gambling helpline notice.
That is the ceiling of the consumer market and it tells you something specific: the high price points are attached to the features that require the most expensive data. Arbitrage, positive-EV and middling tools need wide bookmaker coverage refreshed fast. The 19.99 dollar tier is trends and historical data, which is cheap to source. The 499.99 dollar tier is the live cross-book board, which is not.
Three consequences follow for anyone entering underneath.
You cannot win on price alone. Undercutting a 199 dollar product with a 49 dollar product only works if your data costs less, and if your data costs less, your product is worse at the thing users are paying for. This is not a market where a leaner cost structure gives you an edge, because the dominant cost is a licence fee that does not care how efficient you are.
Your addressable market is small and self-selecting. The people who will pay 200 dollars a month for a betting tool are people betting enough volume that a small percentage edge exceeds 200 dollars a month. That is a narrow population, and it is a population that talks to each other, compares tools obsessively, and cancels without sentiment.
Free tiers are expensive here. In most SaaS, a free tier costs you hosting. In this one, a free tier that shows live odds costs you API credits per refresh, per market, per region. Design free tiers around delayed or aggregated data, or around historical analysis, not around the live board.
There is no reliable public data on what independent sports analytics tools earn. Private companies in this niche do not file revenue publicly, and the numbers that circulate (annual recurring revenue claims in forum posts, founder interviews, launch-day screenshots) are self-reported, unaudited and selected for being impressive. There is no denominator anywhere: nobody publishes how many people built a betting tool and how many of those are still trading two years later.
What can be said from audited filings is narrow but useful. The two largest firms in the sector disclose their accounts, and one of them lost 111.6 million dollars in 2025 on 669.5 million dollars of revenue. That does not tell you what a solo product earns. It does tell you that scale, exclusive rights and sportsbook customers are not sufficient conditions for profitability here. Any specific income figure attached to this niche, including any you find elsewhere on the internet, should be treated as unverifiable unless it comes from a filing.
The Churn Problem Nobody Mentions: Your Best Customers Get Limited
This is the structural issue that separates betting tools from ordinary analytics SaaS, and it deserves its own section because it is not obvious until it happens to your cohort data.
If your tool works, your users win. If your users win, sportsbooks restrict their accounts. Once restricted to trivial stake sizes, the user cannot act on your signals and cancels.
This is not speculation. The Massachusetts Gaming Commission opened an inquiry into the practice in July 2023 and convened a public roundtable in May 2024; reporting at the time noted that the state's active licensed operators did not attend. A further session followed in September 2024. Operator data subsequently supplied to the Commission showed that account restrictions affected around 0.64 per cent of accounts, and that above-average winnings were associated with a higher likelihood of restriction. In December 2025 the Commission approved a regulation, effective 1 June 2026, requiring sportsbooks to notify customers within 48 hours of restricting an account and to give a specific, individualised reason rather than a boilerplate one, applied retroactively to accounts limited before that date.
Read that 0.64 per cent figure carefully, because it is easy to misread as reassuring. It is 0.64 per cent of all accounts, the overwhelming majority of which are casual losing accounts that no book has any reason to touch. Among the population your product exists to serve (bettors placing volume and beating the closing line) the rate is necessarily far higher. The Commission's own finding was that winning is associated with restriction.
Your business model therefore has a built-in ceiling: the better your product performs for a given customer, the shorter that customer's useful life. Plan for it explicitly. Products that survive this tend to broaden into bankroll tracking, closing-line-value analysis, and multi-account management, which retain value after limitation, rather than living purely on live arbitrage and positive-EV alerts, which do not.
Also note the jurisdictional divergence. The Massachusetts rule is a Massachusetts rule. Great Britain, Australia and most other markets have their own and different approaches to operator discretion over stake limits. Do not assume any of this transfers.
B2B: Selling to Operators Instead of Bettors
The alternative to selling tools to bettors is selling technology to the industry: odds screens for media companies, pricing or risk tools for smaller operators, model outputs for traders, or data visualisation for broadcasters.
The economics are better in some ways and much worse in others.
Better: contract values are larger, churn is contractual rather than emotional, and you are not fighting the limiting problem. Worse: your customers are licensed entities, and doing business with them drags you into their regulatory perimeter.
The concrete version, using Tennessee as an example because its fee schedule is published in statute and regulation. Under Tennessee's sports gaming rules, vendors must register, and the fee for the first three-year registration period is 150,000 dollars, payable in instalments. Renewal fees are then banded by vendor category: 150,000 dollars for geolocation services, online sports wagering platform software or player account management; 75,000 dollars for risk management services, oddsmaking services, or sports data feeds or software; 45,000 dollars for independent testing laboratories; and 30,000 dollars for KYC or payment processing, vendors with direct interface to patron accounts or platforms, and vendors compensated under revenue-share arrangements.
Read that middle band again. "Sports data feeds or software" is explicitly a registrable vendor category with a five-figure renewal fee, in one state, on top of a six-figure initial registration. Colorado operates a similar structure, with a Vendor Major licence required for entities that manage, administer or control wagers on a sports betting system. Every state has its own scheme, its own fees and its own definitions.
The lesson is not that B2B is impossible. It is that the moment your software touches a licensed operator's wagering process, you inherit a licensing cost structure that assumes you are a company with a compliance department. Selling read-only analytics to a media company is a different proposition from selling anything that touches pricing or wager acceptance. Know which side of that line your product sits on before you sign the first contract, and get local advice, because the line is drawn differently in every jurisdiction.
The Affiliate Route and What It Costs
Many consumer betting tools are not really subscription businesses at all. They are affiliate businesses with a software front end, earning cost-per-acquisition or revenue share for sending signed-up depositors to sportsbooks.
This changes your regulatory position again, and the position varies enormously.
In the United States, several states require affiliates to register or be licensed. Industry sources report cost-per-acquisition affiliate registration fees of nothing in New Jersey, 200 dollars in Michigan, 500 dollars in Tennessee, Virginia, Colorado and Indiana, 1,000 dollars in West Virginia and 2,500 dollars in Pennsylvania. These figures come from law firms and industry commentators rather than from the regulators' own fee schedules, and at least one of them sits awkwardly beside Tennessee's statutory vendor registration fee of 150,000 dollars for the first three-year period. The likeliest explanation is that affiliates fall into a separate and cheaper registration category from technology vendors, but that could not be confirmed from a primary source. Verify with the specific regulator before budgeting either number.
In Great Britain, affiliates are not themselves licensed by the Gambling Commission. Instead, the obligation is pushed onto the operator through the Licence Conditions and Codes of Practice. Social responsibility code provision 1.1.2 makes licensees responsible for the actions of third parties with whom they contract for any aspect of the licensed business, requires contract terms obliging the third party to conduct itself as if bound by the same licence conditions and codes of practice, requires the third party to supply information the licensee needs for regulatory reporting, and requires the licensee to be able to terminate promptly where an affiliate has breached a relevant advertising code. Condition 1.1.3 adds requirements for third parties providing user interfaces through which customers access remote gambling facilities.
The practical effect is that a British operator will contractually impose its entire compliance burden on you, audit you, and terminate you without much argument if a regulator or the Advertising Standards Authority takes an interest in something you published. You carry the compliance cost with none of the licence's protections.
Two further points that apply everywhere. Affiliate income is concentrated and volatile. Deals are renegotiated, revenue-share tails are cut when operators change platform, and a single regulatory change in a single market can remove a meaningful share of revenue overnight. And affiliate revenue conflicts directly with the product promise. A tool that tells users which book has the best price is structurally at odds with a commercial arrangement that pays you more for sending users to a particular book. Users in this niche are unusually good at detecting that, and the reputational damage is not recoverable.
Distribution Risk: The App Stores Will Not Simply Let You Ship
If your plan includes a mobile app, read the store policies before you build, not after.
Apple. App Review Guideline 5.3.4 requires that apps offering real money gaming or lotteries have the necessary licensing and permissions in the locations where the app is used, be geo-restricted to those locations, and be free on the App Store. It also states plainly that "illegal gambling aids, including card counters, are not permitted on the App Store." Guideline 5.3.3 prohibits using in-app purchase to buy credit or currency for real money gaming. Guideline 5.3 opens by warning that this category is one of the most regulated on the store and to expect extra review time.
An odds and analytics tool is not itself real money gaming, so 5.3.4 does not automatically apply. But "gambling aids" is the review category you are closest to, and the outcome depends on a reviewer's judgement about whether your app assists gambling that is legal where it is used. That is not a determination you can make in advance with certainty.
Google. The Real-Money Gambling, Games and Contests policy is more explicit and more restrictive. It requires approved gambling apps to be published by an approved governmental operator or a licensed operator holding a valid operating licence in each country where the app is distributed. Critically for this niche, it prohibits apps that provide gambling support or companion functionality. The policy names "functionality that assists with wagering, payouts, sports score/odds/performance tracking". And gives as an explicit violation example "a dedicated sports odds tracker app containing integrated gambling ads linking to a sports betting site."
That example describes, almost word for word, the default business model for a consumer sports analytics app. Assume mobile distribution through Google Play is difficult to impossible for an ad-and-affiliate-funded odds tracker, and plan for web-first delivery, progressive web app installation, or a materially different product scope.
The consequence for customer acquisition is significant. You lose store search, store-driven install flows, and the trust signal of being in the store. You must acquire every user through channels you own or rent.
Payment Processing: The Other Switch Someone Else Controls
Stripe's list of restricted businesses prohibits, among other things, "Games of chance including gambling, internet gambling, casino games, sweepstakes and contests, and fantasy sports leagues with a monetary or material prize"; "Sports forecasting or odds-making with a monetary or material prize"; and, in its Japan-specific restrictions, "Consultation and advisory or prediction services relating to online gaming or gambling". It separately prohibits "get rich quick" schemes, including "sites that promise fast and easy money".
A subscription analytics tool that does not itself accept wagers or award prizes is not squarely within the first two prohibitions. But you are one marketing page away from the third and fourth. Landing copy promising guaranteed profit, risk-free arbitrage or a specific monthly return moves you from an adjacent category into a prohibited one, and the enforcement mechanism is not a warning letter. It is an account review, a payout hold and a termination.
Practical mitigations: keep marketing copy factual and free of return promises; disclose clearly that the product provides information and does not accept wagers; maintain a second processor relationship before you need it; keep a cash buffer sized to cover a rolling reserve being imposed; and read the restricted business list for every country you sell into, because it varies by country, as the Japan clause demonstrates.
Prediction Markets: The 2026 Wildcard
Something is shifting underneath this whole sector and it is worth understanding even if you never touch it.
Sports event contracts on CFTC-regulated designated contract markets, offered by exchanges such as Kalshi, have created a parallel venue for what looks a great deal like sports betting, regulated federally rather than state by state. The legal position in mid-2026 is genuinely unsettled and the courts are split.
On 6 April 2026 a divided panel of the Third Circuit held that the CFTC has exclusive jurisdiction over sports-related event contracts, finding them to be "swaps" under the Commodity Exchange Act and holding New Jersey's gambling laws field- and conflict-preempted as applied to trading on a registered designated contract market. In January 2026 a Massachusetts Superior Court reached the opposite conclusion, rejecting the swaps characterisation as "overly broad" and granting an injunction effective 8 March 2026. On 8 July 2026 a federal judge in Manhattan declined to block New York's regulators, holding the state's gambling laws not preempted as applied to sports contracts; New York's Attorney General sued Kalshi on 31 July 2026, alleging an illegal gambling operation. The CFTC Chair announced in January 2026 that the agency would proceed with a prediction markets rulemaking.
Why this matters to a data product. If sports event contracts settle into a federally regulated national venue, the data requirements change: settlement sources, resolution criteria, and cross-venue price comparison between exchange contracts and sportsbook odds all become products in their own right. It also creates a distribution channel that is not subject to state-by-state gambling affiliate registration. Equally, if the state-law challenges succeed, that channel narrows sharply.
Do not build a business that depends on the outcome. Do watch it, because it is the most likely source of a genuinely new product category in this sector over the next two years.
Tax and Structure
Briefly, because it is boring and it is where small SaaS businesses get caught.
- UK. The VAT registration threshold is 90,000 pounds of taxable turnover in a rolling twelve months, or where you expect to exceed it within the next 30 days. Digital subscription services supplied to UK consumers are standard-rated.
- European Union. VAT on electronically supplied services to consumers is due where the customer is located, and for non-EU suppliers there is no registration threshold. The non-Union One Stop Shop scheme lets you register in a single member state and account for VAT across the bloc, but you must still determine and evidence each customer's location. If you sell to EU consumers, this obligation starts at your first sale, not at some revenue level.
- United States. Whether SaaS is subject to sales tax varies by state, and economic nexus rules mean you can acquire a filing obligation in a state where you have no physical presence once you cross that state's sales or transaction thresholds. There is no national rule. Get advice keyed to the states where your customers actually are.
- Everywhere. If any part of your revenue is affiliate commission from gambling operators, expect additional scrutiny of the source of funds from banks and processors, and expect operators to require tax documentation before paying.
None of this is optional and none of it is expensive to get right early. It is expensive to get wrong for three years and then fix.
A Realistic Cost Model
These are illustrative ranges built from the published prices above plus reasoned estimates. None of the totals is a sourced figure. Treat every number as an estimate and rebuild it with live quotes before committing to anything.
Scenario one: historical analysis tool, no live data. Self-service statistics API at 19 to 39 dollars a month, hosting at 25 to 50 dollars, domain and email at 5 dollars, payment processing at roughly 3 per cent of revenue. Total fixed cost under 100 dollars a month. This is genuinely bootstrappable. It is also the least defensible product, because the data is cheap for everyone including your competitors, and the value to a bettor is modest.
Scenario two: live odds comparison, one region, moderate market coverage. Odds API at 119 to 249 dollars a month, hosting and database at 50 to 150 dollars, error monitoring and support tooling at 50 dollars, plus your time. Call it 250 to 500 dollars a month fixed before marketing. At a 49 dollar price point you need roughly ten paying subscribers to cover costs and perhaps forty to make it worth doing. Achievable, and this is where most independent projects should aim.
Scenario three: multi-region, player props, low latency, arbitrage detection. This is the product that competes with the 199 to 499 dollar tier, and it requires a data package that is not on a self-service pricing page. Enterprise odds feeds in this class are negotiated annually with minimum commitments, and no confirmable figure for what such a contract costs could be found. Budget on the assumption that the annual data commitment is the largest line in your business and that it is payable whether or not you acquire customers, which is precisely the structure that destroyed IMG Arena.
Who should skip this
State it plainly.
- Anyone who cannot absorb the data cost for twelve months without revenue. Sports data contracts are commitments, not usage-based utilities, once you leave the self-service tier. If your plan requires the data bill to be funded by month-three subscription revenue, the plan does not work.
- Anyone building principally on scraped live data. Not because you will go to prison (you almost certainly will not) but because in the UK and EU it engages a database right that has already been enforced successfully against a listed competitor, and because everywhere it makes your supply chain someone else's to switch off.
- Anyone whose growth plan runs through mobile app stores. Google Play's policy names sports odds tracker apps with gambling ad links as a violation example. Apple's category is judgement-based and slow. If you have no viable web acquisition channel, you have no business.
- Anyone uncomfortable with the customer relationship. Your paying customers are gambling. Some proportion of any gambling population is experiencing harm. You will receive support emails from people in distress, and if you are honest with yourself you will find some of your revenue comes from people who should not be spending it. If that troubles you, it should, and this is not the niche for you.
- Anyone who needs a stable regulatory environment. State mandates change, affiliate registration requirements change, prediction market jurisdiction is actively contested in three courts simultaneously, and league data contracts turn over on multi-year cycles that reshape the supply market when they do.
- Anyone without either a genuine data edge or a genuine distribution edge. Building the software is now the easy part. If your only asset is that you can build the app, you are competing on the dimension that has become cheapest, against incumbents whose advantage is contracts you cannot sign.
If You Are Still Going
A sequence that respects the economics rather than fighting them.
Start where the data is cheap and the analysis is hard. Historical performance, closing line value tracking, bankroll analytics, model backtesting against archived data. These need statistics APIs at tens of dollars a month, not live feeds at thousands. They also retain value for a user after their sportsbook accounts are restricted, which directly addresses the churn problem.
Prove willingness to pay before you buy expensive data, not after. A waiting list with deposits, or a manual service delivered by spreadsheet, tells you more about demand than a built product does, and costs nothing in licence fees.
Separate ingestion from serving on day one. One process polls upstream and writes to your store; every user reads from your store. This is the difference between marginal cost per user of fractions of a cent and marginal cost per user of an API credit.
Instrument your credit consumption before you instrument anything else. Know, per feature, how many billable units it consumes per hour. When you later have to cut costs, you will need to know which feature to cut.
Read the actual terms of every feed you use. Redistribution rights, caching rights, whether you may serve the data to consumers at all, attribution requirements, and what happens on termination. Several self-service APIs restrict redistribution in ways that are incompatible with the product people instinctively build.
Get jurisdiction-specific advice before you take money from operators. Vendor registration, affiliate registration and advertising rules differ by state and by country, and the fee schedules are large enough to matter to a small business.
Write your marketing copy as if a payment processor's risk team will read it, because one will. No guaranteed returns, no risk-free framing, no income claims.
Decide early whether you are a subscription business or an affiliate business. Trying to be both compromises the product promise and confuses your regulatory position. Pick one and be honest about it on the pricing page.
What Would Change This Picture
Three things worth watching, none of which you can control.
Rights renewals. The current exclusive contracts have end dates. When a major league's data rights come up, the market briefly reopens. Nothing suggests the leagues will sell to small buyers, but the terms downstream distributors offer do move when they are competing for a renewal.
Prediction market resolution. If federal jurisdiction over sports event contracts is settled in favour of the exchanges, a large adjacent market opens with different data needs and a different regulatory perimeter. If it is settled the other way, the state-by-state structure hardens.
Regulatory attention to limiting. Massachusetts is the first state to require individualised justification for account restrictions, effective 1 June 2026. If other regulators follow, the useful life of a winning customer extends, and the unit economics of consumer betting tools improve materially. If they do not, the churn ceiling stays where it is.
The rest is execution against a cost structure you do not control, in a market whose most valuable input has already been sold, exclusively, to someone else.