Jurisdiction control plane for prediction-market operators to block banned states, suppress ads, and prove compliance before felony laws hit.

1. Minnesota creates the first explicit felony deadline, which forces operators to ship controls on a known timeline instead of waiting for broader policy clarity.
2. The CFTC's same-day lawsuit means firms must operate inside an unresolved federal-state conflict and need auditable proof of exactly what they enforced where.
3. A 14-plus-state legislative queue turns compliance from a one-state exception into a repeatable product problem.
4. Because the ban reaches advertising and circumvention support, the first valuable product spans more than geofencing and can own multiple operational systems.

Catalyst. Minnesota's first-in-the-nation felony ban, the CFTC's immediate injunction request, and a 15-plus-state bill pipeline create a near-term need for operators to operationalize legal posture instead of treating it as quarterly research.

Build a jurisdiction control plane that ingests a platform's state exposure and pushes machine-readable policies into signup, geolocation, wallet funding, trading, CRM, and affiliate systems. The product would maintain a live state-by-state rule graph, generate required blocklists and disclosure variants, and automatically suppress banned acquisition channels when a bill passes or an injunction changes scope. It would produce evidence bundles showing what controls were active for each state and effective date, giving legal teams a defensible record during regulator inquiries or litigation. Over time, operators could use the same layer to simulate revenue impact before entering or exiting a state and to coordinate external vendors against a single source of truth.

What's different. Existing legal research, geofencing, and CRM tooling each solve one slice of the problem, but none become the system of record for state-by-state market legality and downstream control enforcement. This company would differentiate by owning the policy graph plus the execution layer across onboarding, trading, payments, and acquisition channels, then turning every policy change into evidence. The result is harder to replace than a point geolocation vendor because it sits in the workflow where legal posture becomes product behavior.

Jobs to be done

flowchart LR
  Buyer[Compliance and legal teams] --> Pain[State bans create trading and advertising exposure]
  Pain --> Product[Jurisdiction control plane]
  Product --> Outcome[Blocked users, suppressed channels, and audit-ready evidence]

Executive takeaways

• This wedge is real because prediction-market compliance has escaped the legal-memo stage and become an operational control problem spanning access, ads, affiliates, and evidence.
• The near-term buyer is concentrated and sophisticated, so the startup only works if it lands as execution middleware rather than another research dashboard.
• Incumbents already sell geolocation, fraud, and regulatory intelligence, but the market still lacks a clean system of record that turns legal posture into cross-system actions and defensible logs.
• The beachhead is narrow; expansion into DFS, sweepstakes/social casino, and other state-fragmented fintech or gaming workflows is necessary to build a venture-scale company.

Market definition

Software that converts state-by-state legal posture into runtime eligibility, marketing suppression, partner controls, and auditable evidence for operators whose products are legal in some jurisdictions and prohibited or contested in others.

Customer and buyer

Primary users are general counsel, chief compliance officers, product-risk leaders, and growth-ops owners at prediction-market and adjacent real-money platforms. The economic buyer is usually the GC or CCO because the budget unlocks when legal deadlines create board-level or regulator-level exposure.

Buying triggers

• A new state ban or effective date forces immediate changes to trading access, advertising, and circumvention controls. [1][2][3]
• Copycat legislation or new age and advertising restrictions in other states turns one-off legal work into a repeatable multi-state program. [5][9][10][11]
• Ongoing federal-state litigation and CFTC enforcement guidance make compliance teams prove what controls were active at a specific moment, not just what policy they intended to follow. [7][12][13][15]

Willingness to pay

The spend envelope already exists because location compliance is mission-critical rather than optional: Radar advertises custom enterprise pricing, BetSaracen says it cannot run a sportsbook without geolocation, and wagering operators already buy bundled geo-compliance and anti-spoofing capabilities instead of relying on internal tools alone. [29][31][33]

Category dynamics

Growth signal 39% YoY uplift in new accounts in enforcement states (regulated-market demand proxy, not category CAGR)

Validation signals

• Polymarket already enforces jurisdiction restrictions and bans VPN circumvention, showing that behavior-level geographic controls are accepted in-market.
• BetSaracen describes geolocation as mission-critical and switched vendors over cost, support, and control concerns rather than building in house.
• Sleeper chose third-party geo-compliance because state-by-state DFS rules required reliable location verification and anti-circumvention controls.
• Xpoint's High 5 deployment suggests adjacent sweepstakes/social operators will buy jurisdiction tooling as regulation tightens.

Regulatory & technical constraints

• Controls must reconcile CFTC exchange obligations with state gambling restrictions, so a generic geofence alone is insufficient.
• VPNs, proxies, and spoofing create obvious circumvention vectors, requiring multilayer detection and confidence-based handling.
• Advertising and acquisition controls must respect gambling-ad rules, country restrictions, and granular location exclusions.
• Affiliate and influencer channels add disclosure and recordkeeping requirements when campaigns are changed or suppressed.

Competition splits into three groups: geolocation and anti-fraud vendors that enforce where a user is, regulatory-intelligence vendors that explain what the rules are, and manual counsel-plus-ops workflows that stitch the rest together. The startup wins only if it sits between those layers and becomes the place where legal posture becomes executed workflow.

Why incumbents do not win by default

• Geolocation and fraud vendors. GeoComply, Radar, and Xpoint already verify jurisdiction and detect spoofing, but they do not win the workflow-orchestration layer by default because legal teams still need policy mapping, marketing suppression, and evidence packaging across non-geo systems.
• Regulatory intelligence vendors. Vixio and similar providers help teams track litigation and policy change, but they stop at intelligence rather than pushing executable controls into trading, CRM, or affiliate workflows.
• Cloud and location infrastructure. Cloudflare, MaxMind, and ad-platform controls provide useful primitives for headers, IP intelligence, and geographic exclusions, but they are components rather than a prediction-market-specific control plane.
• Outside counsel and manual operations. Counsel can interpret statutes and geofencing vendors can block users, but neither produces a durable state-by-state source of truth that coordinates product, marketing, and audit evidence in one place.

Prediction Market Jurisdiction Rail should launch as a control plane for CFTC-regulated prediction-market operators, not as a generic legal research dashboard or a standalone geofencing product. The first customer is a nationwide operator with retail web and mobile distribution, active paid and affiliate acquisition, and an August 2026 deadline to block Minnesota users and related marketing activity before felony exposure begins. The immediate pain is operational: legal teams must turn a changing state rulebook into enforced controls across signup, trading, CRM, affiliates, and evidence collection while federal and state authorities still disagree on jurisdiction. The MVP should begin with human-approved policy management, ad and CRM suppression, evidence exports, and API-based block rules before promising deep automated trading-engine orchestration. Founder-led sales should be tied to enacted bans, injunction hearings, and effective-date deadlines, with a paid pilot that converts into an annual contract priced by controlled states and workflows. The strongest reason to believe is that current alternatives remain fragmented across outside counsel, geolocation vendors, and manual operations, while the first buyer already spends on mission-critical geo-compliance. The biggest reason for caution is that the beachhead buyer pool is concentrated and may prefer this capability bundled into an incumbent geo vendor rather than purchased as a new control layer. Market sizing in the inputs is modeled rather than externally audited, so the board-level question is whether the company can secure two to three paid design partners quickly enough to prove a repeatable wedge before expanding into DFS, sweepstakes, and adjacent state-fragmented financial products.

Problem

• Prediction-market operators now face state-by-state felony, injunction, and advertising exposure that can change faster than product, marketing, and support teams can manually respond.
• Current alternatives split legal interpretation, geolocation, channel suppression, and audit evidence across different vendors and spreadsheets, leaving operators unable to prove what controls were active by state and date.

Solution

• Provide a jurisdiction control plane that converts versioned state legal posture into enforced rules for signup, trading access, CRM messaging, paid acquisition, affiliate activity, and evidence retention.
• Launch with policy APIs, channel-specific suppression workflows, approval logs, and regulator-ready evidence bundles so buyers can operationalize legal decisions before they trust full automation.

Why we win

• The company owns the workflow where legal posture becomes live product and marketing behavior, which is the gap between regulatory intelligence vendors and pure geolocation providers.
• A proprietary policy graph plus cross-system enforcement and evidence logs can compound into switching costs that manual counsel and point vendors do not naturally create.

Milestones

flowchart LR
  Wedge[Prediction-market state deadline wedge] --> MVP[Policy graph and suppression MVP]
  MVP --> Proof[Audit evidence and pilot conversions]
  Proof --> Expansion[Adjacent regulated-category expansion]

Founding team

Experiment roadmap

Risk assessment

What must be true

• At least 2 of the first 5 serious beachhead prospects will pay for a standalone pilot instead of insisting the capability come from an existing geo vendor.
• Ad suppression, affiliate governance, and evidence export are painful enough to budget before the startup delivers full trading-engine automation.
• One design partner can deploy the first workflow set within one product-planning cycle rather than a multi-quarter enterprise integration.
• Production customers will renew and expand because the product becomes the system of record for policy execution, not just another research feed.
• Adjacent categories such as DFS or sweepstakes will recognize the same policy-graph architecture as valuable once prediction-market proof exists.

Open diligence questions

• Who owns the first budget when a state restriction lands: GC, CCO, product-risk, or growth operations?
• Which first workflow wins the deal in practice: access blocking, ad suppression, affiliate governance, or evidence export?
• How much implementation work is required to connect CRM, ad platforms, affiliate tools, and geo signals for one pilot?
• Why will operators trust a new control plane over expanding GeoComply, Radar, Xpoint, or manual counsel-led workflows?
• Which adjacent category has the fastest expansion path if pure prediction-market demand proves too small?

Model sanity

• Revenue engine. The base case reaches 13 active operator accounts by Q4Y3, with pricing expanding from pilot-equivalent Y1 revenue to the researched $300K blended ACV as more workflows and states move under control.
• Must go right. Two paid pilots must convert fast enough that founder-led selling plus one partnerships hire can add roughly three net new accounts in Y2 before broader adjacent-category expansion carries Y3.
• Model breaks if. If incumbent bundling pushes ACV toward $270K or sales cycles stretch toward nine months, downside cash falls toward about $180K before the company proves a durable second market.
• Next-round proof. A credible next round requires exiting Y2 with 6 production accounts, one adjacent-category logo, one reusable geo or identity integration, and gross margin around the 70% target.

Scenarios

Sensitivity

flowchart LR
  StateDeadlines --> QualifiedPilots
  CounselReferrals --> QualifiedPilots
  QualifiedPilots --> ProductionAccounts
  ProductionAccounts --> WorkflowExpansion
  WorkflowExpansion --> Revenue
  Revenue --> GrossProfit
  GrossProfit --> OperatingCash

Flags: The base case still depends on a narrow buyer pool, so one delayed enterprise deal or non-renewal can move the next financing date materially. · Y1 and Y2 remain heavily EBITDA negative, which means the plan requires closing the pre-seed near the midpoint of the stated $2-4M range. · The model assumes pilots priced at $30k-$75k can expand into roughly $300K multi-workflow annual accounts; if buyers resist workflow expansion, revenue undershoots quickly. · Cash reaches its low point late in Y3, so any delay in adjacent-category expansion would likely force an earlier raise even though Q4Y3 turns slightly EBITDA positive.

• Market size concentration. Prediction-market operators are still a small initial buyer pool, which could cap early ARR if expansion stalls. Mitigation: Design the product around reusable jurisdiction-policy primitives that can extend into adjacent regulated consumer finance categories within 12 months.
• Legal clarity arrives fast. A decisive federal preemption win could reduce the urgency of state-by-state tooling for core trading access. Mitigation: Prioritize surfaces that remain state-specific even under partial preemption, including advertising, age limits, affiliate controls, and state-specific disclosures.
• Integration burden. If the system is too hard to wire into trading, CRM, and acquisition stacks, buyers may fall back to manual work and point vendors. Mitigation: Launch with a narrow first release covering policy dashboard, marketing suppression, and evidence exports before expanding into deeper runtime APIs.