Control plane for hedge funds adopting Kalshi event contracts to enforce policy, reconcile positions, and survive regulatory scrutiny.

1. Institutional usage is accelerating fast enough that compliance teams now face real production deadlines instead of exploratory pilots.
2. Kalshi is explicitly building block trading and broker integrations, so event contracts are about to plug into mainstream institutional workflows.
3. One venue now concentrates most U.S. activity, which makes a standard external control layer commercially viable.
4. Trading scale is rising while state challenges remain active, making ad hoc compliance processes newly dangerous.

Catalyst. Kalshi's 800% institutional volume surge and planned block-trading and broker-integration rollout mean funds are moving from experimentation to production exactly as regulatory scrutiny intensifies.

Build an event-contract control plane that sits between Kalshi, broker pipes, and a fund's existing OMS or internal execution stack. The product ingests contract metadata, tags each market to approved strategy buckets, enforces pre-trade restrictions by desk, trader, jurisdiction, and size, and creates a clean audit trail for compliance committees. Post-trade, it normalizes fills into fund-level exposure, scenario, and reconciliation views so operations teams can close books without bespoke scripts. A reporting layer generates policy exceptions, counsel-ready review packs, and board-level summaries that make event-contract programs defensible inside institutional governance. Over time, the same data model can power portfolio analytics and capital allocation across other alternative contract types.

What's different. Most risk tools assume fixed asset classes, while generic compliance software cannot reason about contract-specific event triggers, settlement logic, or jurisdictional ambiguity. This startup's wedge is a contract taxonomy and policy engine purpose-built for event markets, with approvals and reconciliation wired directly into institutional trading workflows. As it sees more contracts, exception patterns, and governance decisions, it builds a proprietary rules and audit dataset that gets harder for internal teams to replicate.

Jobs to be done

flowchart LR
  Buyer[Hedge fund COO or CCO] --> Pain[Manual approval and reconciliation for event contracts]
  Pain --> Product[Event contract control plane]
  Product --> Outcome[Faster go-live with compliant institutional trading]

Executive takeaways

• Institutional event-contract trading is becoming operationally real faster than governance stacks are adapting.
• The strongest wedge is not raw execution but policying, approvals, and reconciliation around venue-specific contracts.
• Most real competition comes from adjacent surveillance suites, venue-native primitives, and internal extensions rather than a direct category leader.
• Regulatory ambiguity is both the main risk and the reason buyers may pay for a dedicated control layer.

Market definition

Software that lets institutional users approve, monitor, and reconcile event-contract trading across venue rules, broker workflows, and internal risk policy.

Customer and buyer

Initial users are heads of risk, compliance, and operations at U.S. macro funds, prop firms, and a small set of brokers adding event-contract access; the economic buyer is usually the COO or CCO because the pain is governance and auditability, not order entry alone.

Buying triggers

• RFQ, FIX, subaccount, and broker-style workflows turn exploratory trading into a production approval problem that spreadsheets handle poorly. [1][14][22][24][26][36]
• Broker distribution makes event contracts more visible to investment committees and legal teams, which raises the bar for documented controls. [3][44][46][47]
• Surveillance messaging and enforcement pressure increase the cost of letting traders use a new contract class without explicit permissions and audit trails. [9][10][58][59][60]

Willingness to pay

Budget is most defensible when the buyer already funds surveillance, market-risk, and reporting tools; in that context, a focused event-contract control plane can support six-figure annual spend if it shortens go-live approvals and reduces manual review and reconciliation. [48][49][50][52][53][58][59]

Category dynamics

Growth signal 800% institutional volume growth over six months on Kalshi (platform-specific, not category CAGR)

Validation signals

• Kalshi has already shipped RFQ, quote, subaccount, settlement, and FCM-facing data surfaces that look like real institutional plumbing.
• Robinhood and Interactive Brokers are explicitly explaining event contracts as hedgeable financial products, broadening distribution beyond Kalshi direct.
• Adjacent compliance vendors now market prediction-market surveillance directly, validating specialized governance pain.
• Kalshi is publicly investing in surveillance partners and enforcement processes, which increases buyer pressure for defensible controls.

Regulatory & technical constraints

• A production deployment must account for participant screening, insider-trading controls, and category-specific policy rules for sensitive markets.
• Integration is not just order entry: buyers need API/FIX coverage for RFQs, orders, positions, subaccounts, settlements, and streaming updates.
• Entity onboarding, authorized-user setup, and Advanced API/FIX access introduce operational lead time before a fund can trade live.

The market is fragmented across venue-native APIs, broad surveillance vendors, broker access layers, and in-house extensions. That leaves room for a specialist product if it owns contract taxonomy, pre-trade entitlement logic, and post-trade auditability rather than trying to replace execution or surveillance systems outright.

Why incumbents do not win by default

• Native venue tooling. Kalshi already exposes RFQ, FIX, subaccounts, positions, and settlements, but those are building blocks for trading access rather than fund-specific policy approval and counsel-ready audit workflows.
• Generic surveillance vendors. Eventus and Solidus can monitor market abuse and market-risk patterns, but they are not built around strategy-level permissions, entity-specific rulebooks, or close-the-books reconciliation for event contracts.
• Broker-native access. Robinhood and Interactive Brokers help distribute and explain event contracts, but their workflow focus is client access and education, not institutional governance across desks, users, and legal interpretations.
• In-house extensions. A fund can wire venue APIs into its own OMS notes and scripts, but then it must maintain rule changes, restricted-person logic, and settlement mapping itself.

Event-contract trading is crossing from exploratory usage into production institutional workflows, but approval, surveillance, and close-the-books processes are still handled with legal memos, spreadsheets, and internal scripts. This company sells a control plane to U.S. macro hedge funds and prop firms that are preparing their first live Kalshi deployment and need machine-readable permissions, limits, and audit evidence before compliance will approve trading. The initial product wedge is narrow by design: pre-trade policy enforcement plus post-trade reconciliation for Kalshi event contracts, without trying to replace OMS, execution, or broad surveillance suites. The go-to-market system is coherent around one trigger: when a fund enables entity onboarding, Advanced API or FIX access, RFQ, or broker connectivity, the COO or CCO must either formalize controls or block launch. Pricing should therefore start as a six-figure annual SaaS subscription plus implementation because the buyer is funding governance and operations risk reduction, not retail-style order flow. The strongest evidence is venue momentum, concentrated U.S. liquidity, institutional workflow primitives, and visible regulatory pressure; the biggest missing fact is how many funds are in active near-term pilots versus only monitoring the category. If that customer count is shallow, the company should stay small and productize the rules engine for adjacent regulated micro-derivative workflows rather than force a pure Kalshi-only outcome.

Problem

• Funds evaluating live event-contract trading still rely on manual legal review, spreadsheet permissions, and email approvals because existing risk and compliance stacks do not classify or control venue-specific contracts well.
• As Kalshi adds RFQ, broker, subaccount, and settlement workflows, manual controls become fragile under larger position sizes, monthly close requirements, and regulatory scrutiny.

Solution

• Deliver a control plane that converts Kalshi market metadata into firm-specific strategy buckets, trader entitlements, jurisdiction rules, and exposure limits enforced before orders are sent.
• Normalize fills, positions, and settlements into reconciliation and audit outputs so compliance and operations teams can approve launches faster and close books without bespoke scripts.

Why we win

• The product is aimed at the actual blocker to production adoption—policy approval and reconciliation—while incumbents focus on venue access, surveillance alerts, or generic compliance workflows.
• A reusable contract taxonomy plus accumulated exception and governance data should get more valuable with each listed contract, customer policy decision, and integrated desk.

Milestones

flowchart LR
  Wedge[First-production Kalshi fund rollouts] --> MVP[Policy and reconciliation MVP]
  MVP --> Proof[Two production fund deployments]
  Proof --> Expansion[Broker modules and adjacent venue expansion]

Founding team

Experiment roadmap

Risk assessment

What must be true

• At least 10 target U.S. funds or prop firms have live or imminent event-contract rollouts in the next 12 months.
• COO or CCO buyers view approval speed and auditability as budget-worthy pain, not just temporary pilot inconvenience.
• A specialist vendor can shorten compliance approval time materially versus internal scripts.
• Kalshi or broker workflow growth persists long enough for a specialist to win multiple customers before incumbents react.
• The rules engine generalizes into adjacent regulated event or micro-derivative products if the Kalshi-only market stalls.

Open diligence questions

• How many named funds are in active implementation versus exploration only?
• What exact control gaps make buyers reject existing OMS, surveillance, or spreadsheet workflows?
• Does the buyer prefer a standalone control plane or an embedded module from an existing vendor?
• Which contract classes create the strongest internal approval friction and therefore the best initial product templates?
• How likely is Kalshi to subsume this wedge with native institutional governance features?

Model sanity

• Revenue engine. Base-case revenue is driven by founder-led conversion of 2 design-partner wins in year 1 into roughly 7 production-equivalent customers by Q4Y2 and 11.6 by Q4Y3 at $240K blended ARPU.
• Must go right. The company must prove that COO/CCO buyers will fund a standalone control layer early enough to justify the first GTM hire in year 2.
• Model breaks if. If sales cycles slip about 15% versus plan, the model loses about $335K of year-3 revenue and cash turns negative before the next round.
• Next-round proof. A credible seed story is 6-8 production customers plus a broker or consultant referral channel and first adjacent-venue rules pilot before cash falls below roughly $0.55M.

Scenarios

Sensitivity

flowchart LR
  TargetAccounts --> PaidPilots
  PaidPilots --> ProductionCustomers
  ProductionCustomers --> SubscriptionRevenue
  SubscriptionRevenue --> GrossProfit
  GrossProfit --> Cash

Flags: The base case still ends year 3 EBITDA-negative, so the company likely needs a seed round before self-funding growth. · Customer counts are modeled as production-equivalent revenue units because paid pilots and implementation-heavy first contracts mix services with SaaS early on. · The market remains concentrated around one venue, so regulatory or platform changes can impair both demand and retention faster than the P&L alone shows.

• Regulatory perimeter shrinks. If regulators or states materially narrow allowed contracts, the initial market could grow slower than expected. Mitigation: Focus first on clearly permitted institutional use cases and build a policy engine portable to adjacent regulated event and micro-derivative products.
• Platform dependency on Kalshi. Heavy reliance on one venue could make the company vulnerable to API, pricing, or distribution changes. Mitigation: Integrate through broker and OMS workflows early so the product remains valuable wherever event contracts are distributed.
• Institutions may build in-house. Large funds could try to extend existing risk systems instead of buying a new vendor. Mitigation: Win mid-market design partners first, productize the long tail of contract taxonomy and audit workflows, and prove faster approval cycles than internal builds.