LONGSHOT

Growth Strategy & Competitive Intelligence How Polymarket, Kalshi & Novig Built Their User Bases And the Playbook for LONGSHOT to Win March 2026 — Confidential

Start Here (10-Minute Guide)

Use this page to navigate the book quickly and finish it in one sitting.

Fastest Path (10-15 Minutes)

1. Read Section 1: The First 6 Months — Deep Dive Into Early Growth Tactics for grounded case-study context.
2. Read 1.1 Polymarket and 1.2 Kalshi to compare opposite growth strategies.
3. Skim Section 1.7: Evidence Map to validate claims and open primary sources.
4. Read Section 4: The LONGSHOT Growth Playbook for direct execution guidance.

Recommended Reading Paths

Founder Path (30-40 Minutes)

• Section 1: The First 6 Months — Deep Dive Into Early Growth Tactics
• Section 4: The LONGSHOT Growth Playbook
• Section 6: Budget Framework
• Section 7: LONGSHOT’s Unique Advantages

Growth Operator Path (35-45 Minutes)

• Section 3: Venues & Channels to Target
• Section 4: The LONGSHOT Growth Playbook
• Section 6: Budget Framework
• Section 10.2: Double-Verification Results

Automation Path (20-30 Minutes)

• Section 10: Automation Plan
• Section 10.1: Validation Framework
• Section 10.2: Double-Verification Results
• Section 10.5: Additional High-Impact Automation

How to Use Evidence Quickly

• Evidence references are clickable inline links, for example: [E11](...).
• The full source directory is in Section 1.7: Evidence Map.
• If a claim matters for a decision, open the linked evidence before acting.

Section 1: The First 6 Months — Deep Dive Into Early Growth Tactics

This section synthesizes six early-growth case studies (Polymarket, Kalshi, Novig, DraftKings, FanDuel, Robinhood) and maps what founders and early employees actually did in the first live months to drive user acquisition (E30, E35, E65, E46, E50, E70, E71).

Evidence anchors: E30 E35 E65 E46 E50 E70 E71

Quick takeaways across the composite subcategories (supported by E58, E59, E66, E51, E73):

• Founder/early-team manual distribution shows up repeatedly as the earliest reliable acquisition engine.
• Market design and activation mechanics (curation, onboarding simplicity, pricing/fee framing) matter as much as paid growth.
• Channel mix differs by category (crypto social, quant/finance communities, affiliate/paid media, mainstream sports audiences), but early trust signals are always critical.
• Regulatory strategy directly changes growth pace and channel availability.
• First-month claims are strongest when anchored to dated primary artifacts (regulator filings, founder/employee posts, launch releases, contemporaneous media).

Supporting references: E58 E59 E66 E51 E73

Included Case Studies

• 1.1 Polymarket: First 6 Months (June–December 2020)
• 1.2 Kalshi: The Silent Build (2018–2021, Launch July 2021)
• 1.3 Novig: First 6 Months (Colorado Launch → Sweepstakes Pivot, Late 2023–Mid 2024)
• 1.4 DraftKings: First 1,000 Users (2012–2013)
• 1.5 FanDuel: First 1,000 Users (2009–2011)
• 1.6 Robinhood: Waitlist Flywheel and Referral-Led Launch (2013–2015)

1.1 Polymarket: First 6 Months (June-December 2020)

Growth Snapshot

• Launch timing: operation began around June 2020. E30
• Early wedge: event-contract focus with narrow initial scope (inference from early regulator and archive artifacts). E30 E31
• Core channel: founder-led community seeding is directionally supported by launch-window query artifacts; direct Reddit permalinks in this window can be unavailable/removed in current retrieval passes. E32 E33 E34 E58

Background (Concise)

• CFTC order documents a June 2020 operating start and large event-market activity before 2022 enforcement settlement. E30
• Launch-window public footprint is directionally dominated by founder-linked/manual community posts, with direct permalink durability treated as limited in this pass. E32 E33 E34 E58
• Earliest retrievable product-like homepage artifact in this pass is October 2020, so month-one UI/activation claims remain partial. E31

First 6-Month GTM Playbook

1. Launch with a narrow, high-demand market set.
2. Run direct founder distribution in existing communities.
3. Keep market creation curated to concentrate liquidity.
4. Remove onboarding friction so first trade happens fast.
5. Align expansion with tentpole events (for example election cycles).

References: E30 E32 E58

First-Month Evidence (Jun 1-Aug 1, 2020)

• CFTC settlement supports June 2020 operating start. E30
• Reddit query artifacts exist in-window; direct permalink availability in this window is inconsistent and should be treated as directional support. E32 E33 E34
• Founder-linked community artifact exists in-window (shaynecoplan post). E58
• Earliest product-like Wayback snapshot in this pass appears after month 1. E31
• No first-month founder-posted social permalink was retrievable in this pass.

LONGSHOT Takeaway

1. Concentrate liquidity into a small set of markets at launch.
2. Use founder/early-team manual community ops before scaling paid channels.
3. Prioritize onboarding and settlement clarity before volume expansion.

References: E30 E58

Earliest Verifiable Public-Forum Link (This Evidence Pass)

• Earliest retrievable public-forum artifact tied to this pass: Jan 18, 2024 post by @TheStalwart referencing Polymarket odds. E27

Source-quality note: private-company anecdotes and unaudited metrics should be treated as directional.

1.2 Kalshi: The Silent Build (2018-2021, Launch July 2021)

Growth Snapshot

• Company appears in YC W19 public materials by March 2019; this evidence set does not include a separate first-party artifact confirming exact founding month/year. E40
• Public beta launched July 26, 2021. E35
• Launch-period positioning centered on being a regulated event-contract market before broad consumer scale. E35 E39
• Tradeoff (inference): slower early distribution versus stronger trust/regulatory framing. E40 E35

Background (Concise)

• TechCrunch launch coverage describes Kalshi as converting opinions on future events into tradable contracts. E39
• YC W19 listing preceded public beta by over two years, consistent with a long regulation/operations build before mass acquisition. E40 E35
• Launch-window Reddit activity shows direct onboarding responses from early team accounts after beta opened. E36 E59 E60
• YC W19 provided early legitimacy before broad public distribution. E40

First 6-Month GTM Playbook

1. Lead with regulatory credibility (DCM-first positioning).
2. Target quant/options-style users who value direct event exposure.
3. Use early-team direct replies in community threads for conversion and onboarding.
4. Improve activation via product support loops (fees, app readiness, API onboarding).
5. Build operations/trust foundation first, then expand distribution.

References: E35 E36 E59 E60

First-Month Evidence (Jul 1-Sep 1, 2021)

• Public beta artifact dated Jul 26, 2021. E35
• Reddit activity exists in-window, including launch-period user threads. E36 E37
• Early-team conversion replies in month 1 (sumersao) are visible. E59
• Product/onboarding reply in month 1-2 (The app is in the works!). E60
• TechCrunch coverage appears near first month (Aug 30, 2021). E39

Pre-Launch Credibility Signals

• YC W19 Demo Day listing includes Kalshi. E40
• Earliest founder-linked forum artifact in this pass: Aug 29, 2022 HN post by tmansour. E26

LONGSHOT Takeaway

1. If regulation is part of the moat, expect slower early top-line growth.
2. Use direct operator-led community onboarding in launch months.
3. Treat trust operations and market quality as acquisition prerequisites from day one.

References: E35 E59 E60

Source-quality note: private-company anecdotes and unaudited metrics should be treated as directional.

1.3 Novig: First 6 Months (Colorado Launch -> Sweepstakes Pivot, Late 2023-Mid 2024)

Growth Snapshot

• Initial path: Colorado licensed launch sequence (license announcement in Oct 2023, launch PR in Jan 2024). E88 E65
• GTM in Colorado included an announced Intelitics partnership for affiliate + paid-channel acquisition support. E69 E66
• Product narrative emphasized commission-free pricing, better prices, faster in-game trading, and transparency. E65
• Pre-launch framing emphasized peer-to-peer exchange economics and sharp-bettor-oriented positioning. E89

What Novig Did on Affiliates (Evidence-Backed)

• Dec 5, 2023: Novig’s own newsroom post says it partnered with Intelitics ahead of Colorado launch to fuel affiliate and paid channels, and links to the external announcement. E69 E66
• The same report says Novig gained Intelitics platform access to manage affiliate and paid media operations (campaign monitoring, player tracking, automated reporting, dashboards). E66
• Intelitics CEO is quoted saying they were supporting Novig acquisition efforts through affiliates and paid media for scale and cost efficiency. E66
• Novig Head of Growth Marketing is quoted saying the platform would drive new customer acquisition at scale at lower cost versus other channels. E66

What this evidence does not prove yet:

• No public figures for affiliate-attributed signups, CPA, LTV/CAC, or retention lift (E66, E69).
• No public disclosure in this evidence set of affiliate partner mix, payout terms, or conversion quality by source (E66, E69).

Background (Concise)

• Seed-round release frames sportsbook margins/practices as the problem and positions Novig as a commission-free exchange alternative. E89
• Founders are described as sharp sports bettors with prior quant/finance experience; the product is framed as peer-to-peer rather than house-vs-player. E89
• License and launch releases document a Colorado-first rollout with community-led messaging and mobile app availability. E88 E65

First 6-Month GTM Playbook

1. Combine community-native distribution with explicit affiliate/paid channels.
2. Anchor messaging on clear user value: pricing, speed, transparency.
3. Differentiate with sharp-friendly positioning and social proof loops.
4. Use retention mechanics (community + streaks + leaderboards) early.
5. Avoid legal/channel mismatch that can erase acquisition gains.

References: E65 E66 E69 E88 E89

Sweepstakes-Pivot Evidence Gap (Explicit)

No dated primary artifact in this evidence set conclusively documents the later sweepstakes-pivot chronology/mechanics. Treat that part of the timeline as unverified until a first-party dated source is attached.

First-Month Evidence Matrix (Colorado Window: Nov 1, 2023-Jan 1, 2024)

• Wayback shows novig.us live by Nov 8, 2022 (pre-window baseline). E56
• Oct 3, 2023 PR says Novig secured a Colorado Internet Sports Betting Operator license and planned a fall launch. E88
• Aug 22, 2023 PR discloses $6.4M seed and Colorado launch plan with product/founder framing. E89
• Intelitics partnership confirms affiliate + paid acquisition path in-window. E69 E66
• Jan 4, 2024 launch release documents early product-value messaging. E65

Earliest Verifiable Public-Forum Link (This Evidence Pass)

• Earliest retrievable Novig URL artifact in this pass: Sep 4, 2025 post by @Novig. E28

LONGSHOT Takeaway

1. A niche community can seed liquidity fast.
2. Use performance channels only after trust and legal structure are stable.
3. Keep credibility controls tight; reversals and disputes compound retention damage.

References: E65 E66 E69 E88 E89

Source-quality note: private-company anecdotes and unaudited metrics should be treated as directional.

1.4 DraftKings: First 1,000 Users (2012-2013)

Growth Snapshot

• Founders: Jason Robins, Matt Kalish, Paul Liberman; Boston Globe reports they left VistaPrint to start DraftKings in early 2012. E90
• Earliest retrievable launch artifact in this pass is an Apr 8, 2012 beta homepage capture. E46
• TechCrunch (Sep 2012) reports DraftKings had announced a $1.4M seed round led by Atlas Ventures in July 2012. E49

Background (Concise)

• Boston Globe reports the founders set up after leaving VistaPrint and launched their first baseball contest weeks later, with 160 free entries and $100 total prizes. E90
• TechCrunch coverage documents early product simplification and mobile-focused iteration in 2012. E49
• Inference from these artifacts: early GTM emphasized narrow contest formats and measurable conversion loops before broad brand scaling. E46 E49 E90

Source links:

• Boston Globe (May 1, 2017)
• TechCrunch (Sep 7, 2012)

First 6-Month GTM Playbook

1. Launch during a tentpole sports moment to concentrate demand.
2. Treat acquisition as direct-response: test small, scale only positive unit economics.
3. Concentrate users into liquid contests instead of spreading activity thin.
4. Use guaranteed prize pools to make the lobby feel active during cold start.
5. Add credibility and distribution via league/media relationships as traction rises.

References: E46 E49 E90

Day-1 Claim Validation (Explicit)

• Verified in this pass: early-2012 launch period, beta web presence, and first baseball contest details. E46 E90
• Verified in this pass: $1.4M Atlas-led seed-round reporting in 2012. E49
• Not yet verified from a primary artifact in this pass: exact “MLB Opening Day one-on-one contest” phrasing and “StarStreet launched the same day” comparison.

First-Month Evidence (Apr 1-Jun 1, 2012)

• Wayback capture confirms web presence in-window (Apr 8, 2012). E46
• Dedicated TechCrunch product coverage appears later (Sep 7, 2012). E49

Earliest Verifiable Founder-Linked Public Link (This Evidence Pass)

• Earliest retrievable founder-linked DraftKings URL in this pass: Jul 7, 2020 post by @mattkalish. E29

LONGSHOT Takeaway

1. Launch around an event window with concentrated user intent.
2. Operate channel tests with strict CAC, retention, and liquidity gates.
3. Pay for liquidity quality early; scale spend only after conversion + retention are proven.

References: E46 E49 E90

Source-quality note: private-company anecdotes and unaudited metrics should be treated as directional.

1.5 FanDuel: First 1,000 Users (2009-2011)

Growth Snapshot

• TechCrunch launch coverage says FanDuel came from the HubDub team and opened after a private-beta period in July 2009. E51
• The same launch coverage describes short-cycle daily contests, social integrations, and fast feedback versus season-long fantasy formats. E51
• Wayback confirms pre-launch web presence by Apr 20, 2009. E50

Background (Concise)

• FanDuel is described as a new product from the HubDub prediction-market team. E51
• TechCrunch reports the idea emerged after SXSW meetings with HubDub users. E51
• Early article details show baseball-first launch, NFL expansion intent, and legal framing around fantasy carve-outs. E51

First 6-Month GTM Playbook

1. Launch with short-cycle contests that resolve quickly versus season-long formats.
2. Convert an existing adjacent audience (HubDub users) into the new product.
3. Embed social-sharing loops early (Twitter/Facebook) for distribution.
4. Start with one sport/category wedge, then expand coverage once the loop works.
5. Keep legal/rules framing explicit to reduce adoption friction.

References: E50 E51

First-Month Evidence (Jul 1-Sep 1, 2009)

• TechCrunch article in-window describes FanDuel in private beta. E51
• Wayback capture confirms early web presence (Apr 20, 2009). E50
• No first-month founder-posted social permalink was retrievable in this pass.

Supporting Historical Context

• Contemporaneous launch coverage with HubDub/SXSW origin context. E51
• Archived homepage presence in early 2009. E50

LONGSHOT Takeaway

1. Prioritize short-cycle product loops that let users realize value quickly.
2. Reuse adjacent communities when launching a new market format.
3. Pair distribution hooks with clear market/rules framing from day one.

References: E50 E51

Source-quality note: private-company anecdotes and unaudited metrics should be treated as directional.

1.6 Robinhood: Waitlist Flywheel and Referral-Led Launch (2013-2015)

Growth Snapshot

• Public waitlist opened in early 2014; reported demand reached roughly 150,000 signups early. E72
• Pre-launch demand scaled to more than 500,000 users on the waitlist. E70
• Launch window in late 2014 still had around 500,000 users queued for access. E71
• Durable channel signal: Robinhood’s S-1 later reported that over 80% of new funded customers in 2020 and Q1 2021 came organically or via referral. E73

Background (Concise)

• Core wedge: zero-commission stock trading in a market where incumbents still relied on explicit trading fees. E70 E72
• Distribution design: invite queue mechanics converted demand into a self-propagating waitlist before broad launch access. E70 E71
• Positioning emphasized mobile-first access for newer retail investors and first-time participants. E71 E72

First 6-Month GTM Playbook

1. Lead with a single, high-contrast value proposition (free trades).
2. Capture demand before full launch using a waitlist asset.
3. Turn each signup into distribution with referral-driven queue movement.
4. Use earned media to compound social proof while access is constrained.
5. Keep first-funded-account onboarding simple once invites are released.

References: E70 E71 E72 E73

First-Month Evidence (Feb 1-Apr 1, 2014)

• CNBC’s February 2014 coverage reported approximately 150,000 users had already signed up to try the product. E72
• TechCrunch documented subsequent waitlist growth to more than 500,000 before broad launch. E70 E71
• S-1 acquisition mix supports that referral/organic channels were not a one-off launch tactic, but a long-lived growth engine. E73

How The Waitlist Reached 500K+ (Evidence-Backed)

1. Sharp wedge at launch: zero-commission trading versus incumbent per-trade fees created a strong signup incentive. E70 E71
2. Private beta queue architecture: Robinhood accumulated demand in a pre-launch waitlist while product security/reliability was being hardened. E70 E71
3. Mobile-first + first-time investor positioning: messaging explicitly targeted younger/newer investors underserved by legacy brokerage UX. E70 E72
4. Earned-media amplification: Robinhood’s own 2014 recap cites broad top-tier media coverage during the early-access period, consistent with top-of-funnel demand acceleration. E96
5. Controlled invite rollout: launch-period reporting describes onboarding the waitlist over time rather than opening instantly, preserving reliability while converting queued demand. E71 E96

Limit note:

• Public sources do not provide full channel-by-channel attribution for every waitlist signup in 2014, so mechanism-level inference is stronger than exact channel mix attribution.

LONGSHOT Takeaway

1. In regulated finance categories, waitlist + referral mechanics can produce qualified demand before expensive paid scaling.
2. Scarcity only works when paired with a sharp economic wedge and fast activation once access opens.
3. Referral loops should be treated as product design and distribution infrastructure, not a side campaign.

References: E1 E2 E70 E71 E72 E73 E96

Source-quality note: private-company metrics in media coverage are directional; filings and dated first-party artifacts should be weighted higher.

1.7 Evidence Map (Primary Sources Used in March 2026 Revision)

Core Growth and Market References

• E1 — Paul Graham, Do Things That Don’t Scale (manual acquisition, partnership caution): https://www.paulgraham.com/ds.html
• E2 — Paul Graham, Startup = Growth (weekly growth-rate discipline): https://www.paulgraham.com/growth.html
• E3 — a16z, Marketplace Glossary (liquidity as core marketplace metric): https://a16z.com/the-marketplace-glossary/
• E4 — a16z, GMV Retention (cohort health and marketplace retention): https://a16z.com/gmv-retention-the-marketplace-metric-most-ignore/
• E5 — Google Search Central Blog (March 2024 core/spam updates; scaled content abuse): https://developers.google.com/search/blog/2024/03/core-update-spam-policies
• E6 — Google Search Central docs (people-first, helpful/reliable content guidance): https://developers.google.com/search/docs/fundamentals/creating-helpful-content
• E7 — Nasdaq exchange matching tech page (sub-40 usec, 14 usec implementation): https://www.nasdaq.com/solutions/fintech/nasdaq-eqlipse/trading-technology/exchange-matching
• E8 — DraftKings 2025 Form 10-K (sales and marketing $1.379B; costly acquisition risk language): https://www.sec.gov/Archives/edgar/data/1883685/000188368526000013/dkng-20251231.htm
• E9 — Flutter 2024 annual filing (sales and marketing $3.205B): https://www.sec.gov/Archives/edgar/data/1635327/000162828025009852/flut-20241231.htm
• E10 — CFTC Press Release 9179-26 (Feb 4, 2026 withdrawal of 2024 event-contract proposal): https://www.cftc.gov/PressRoom/PressReleases/9179-26
• E11 — CFTC Press Release 9185-26 (Feb 25, 2026 prediction-markets enforcement advisory): https://www.cftc.gov/PressRoom/PressReleases/9185-26
• E12 — Robinhood 2025 Form 10-K (Rothera JV and Jan 20, 2026 MIAXdx acquisition): https://www.sec.gov/Archives/edgar/data/1783879/000178387926000023/hood-20251231.htm

AI-Native and Automation System References

These references support automation implementation choices (tooling, evaluation, and guardrails). They are not primary case-study evidence for early user-acquisition behavior.

• E13 — OpenAI Cookbook: Function calling/tool orchestration pattern: https://cookbook.openai.com/examples/how_to_call_functions_with_chat_models
• E14 — OpenAI Cookbook: Batch workflow processing pattern: https://cookbook.openai.com/examples/batch_processing
• E15 — OpenAI Cookbook: Getting started with OpenAI Evals (continuous evaluation): https://cookbook.openai.com/examples/evaluation/getting_started_with_openai_evals
• E16 — OpenAI Cookbook: Structured Outputs intro: https://cookbook.openai.com/examples/structured_outputs_intro
• E17 — Meta Business: Meta Advantage+ campaigns/product overview: https://www.facebook.com/business/ads/meta-advantage-plus
• E18 — Google Ads Help: Value-based Smart Bidding guidance: https://support.google.com/google-ads/answer/6268632
• E19 — Google Analytics Help: Predictive audiences (behavior-signal segmentation): https://support.google.com/analytics/answer/9846734
• E20 — Ethereum.org: Proof-of-Stake finality reference: https://ethereum.org/en/developers/docs/consensus-mechanisms/pos/#finality
• E21 — Ethereum.org: Transaction lifecycle reference (submitted/included/confirmed context): https://ethereum.org/en/developers/docs/transactions/
• E22 — Chainlink Docs: Data feed selection and risk mitigation: https://docs.chain.link/data-feeds/selecting-data-feeds#risk-mitigation
• E23 — OpenZeppelin Defender Docs: Monitor module for smart-contract risk alerting: https://docs.openzeppelin.com/defender/module/monitor

Public-Forum Links and Launch Discovery References

• E24 — HN thread: Launch HN: Kalshi (YC W19) with score/comments metadata: https://news.ycombinator.com/item?id=33696486
• E25 — HN Launches index entry containing Kalshi score/comments listing: https://news.ycombinator.com/launches?next=34505603
• E26 — HN story by tmansour (Regulated Election Markets, Aug 29, 2022) linking founder statement: https://news.ycombinator.com/item?id=32642005
• E27 — X post by @TheStalwart (Joe Weisenthal, Jan 18, 2024) referencing Polymarket market odds: https://x.com/TheStalwart/status/1748099622822728098
• E28 — X post by @Novig (official account, Sep 4, 2025) linking app.novig.us desktop launch: https://x.com/Novig/status/1963641385807921336
• E29 — X post by @mattkalish (DraftKings co-founder, Jul 7, 2020) linking draftkings.com/tech-for-heroes: https://x.com/mattkalish/status/1280572019533373443

Company-Specific First-Month GTM Evidence

• E30 — CFTC Order (Polymarket): operation began approximately June 2020; over 900 event markets by Jan 2022: https://www.cftc.gov/PressRoom/PressReleases/8478-22
• E31 — Wayback (Polymarket product homepage snapshot, Oct 22, 2020): https://web.archive.org/web/20201022083220/https://polymarket.com/
• E32 — pullpush Reddit query (Polymarket, Jun 1-Aug 1 2020, count=9): https://api.pullpush.io/reddit/search/submission/?q=polymarket&after=1590969600&before=1596240000&size=100&sort=asc&sort_type=created_utc
• E33 — Reddit permalink (r/Augur, ‘The Polymarket Playbook’, Jun 12, 2020; may be unavailable/removed in some retrieval contexts): https://www.reddit.com/r/Augur/comments/h7ori4/the_polymarket_playbook/
• E34 — Reddit permalink (r/Polymarket Lounge, Jun 19, 2020; may be unavailable/removed in some retrieval contexts): https://www.reddit.com/r/Polymarket/comments/hc5jos/rpolymarket_lounge/
• E35 — Kalshi news post (archived): ‘The Kalshi Public Beta is Live’ (datePublished Jul 26, 2021): https://web.archive.org/web/20251219054410/https://news.kalshi.com/p/kalshi-public-beta-is-live
• E36 — pullpush Reddit query (Kalshi, Jul 1-Sep 1 2021, count=8): https://api.pullpush.io/reddit/search/submission/?q=kalshi&after=1625097600&before=1630454400&size=100&sort=asc&sort_type=created_utc
• E37 — Reddit permalink (r/Kalshi, ‘Why are fees so high?’, Jul 1, 2021): https://www.reddit.com/r/Kalshi/comments/obrbvw/why_are_fees_so_high/
• E39 — TechCrunch (Aug 30, 2021): This Sequoia- and Henry Kravis-backed prediction market wants to turn opinions into money: https://techcrunch.com/2021/08/30/this-sequoia-and-henry-kravis-backed-prediction-market-wants-to-turn-opinions-into-money/
• E40 — TechCrunch (Mar 18, 2019): YC W19 Demo Day startup list including Kalshi: https://techcrunch.com/2019/03/18/here-are-the-85-startups-that-launched-today-at-y-combinators-w19-demo-day-1/
• E41 — TechCrunch (Dec 14, 2022): earliest Polymarket mention retrievable in this pass: https://techcrunch.com/2022/12/14/despite-the-crypto-winter-and-other-scandals-blockchains-seem-here-to-stay-in-the-sports-betting-market/
• E43 — TechCrunch WP API search for Novig (empty result set in this pass): https://techcrunch.com/wp-json/wp/v2/posts?search=Novig&per_page=100&page=1&orderby=date&order=asc
• E44 — pullpush Reddit query (Novig, Nov 1 2023-Jan 1 2024, count=0): https://api.pullpush.io/reddit/search/submission/?q=novig&after=1698796800&before=1704067200&size=100&sort=asc&sort_type=created_utc
• E45 — HN Algolia in-window query (novig.us, Nov 1 2023-Jan 1 2024, nbHits=0): https://hn.algolia.com/api/v1/search_by_date?query=novig.us&tags=story&numericFilters=created_at_i%3E%3D1698796800%2Ccreated_at_i%3C%3D1704067200&hitsPerPage=20
• E46 — Wayback (DraftKings earliest capture in this pass, Apr 8, 2012): https://web.archive.org/web/20120408145644/http://www.draftkings.com/
• E49 — TechCrunch (Sep 7, 2012): DraftKings’s Big Baller App Is A Made For Mobile Fantasy Sports Experience: https://techcrunch.com/2012/09/07/draftkingss-big-baller-app-is-a-made-for-mobile-fantasy-sports-experience/
• E50 — Wayback (FanDuel early capture, Apr 20, 2009): https://web.archive.org/web/20090420030506/http://www.fanduel.com/
• E51 — TechCrunch (Jul 21, 2009): FanDuel turns fantasy sports betting into a social game: https://techcrunch.com/2009/07/21/fanduel-turns-fantasy-sports-betting-into-a-social-game/
• E56 — Wayback (Novig snapshot Nov 8, 2022 title: ‘Novig - The Future of Sports Betting’): https://web.archive.org/web/20221108083839/https://www.novig.us/
• E58 — pullpush Reddit query for submissions by shaynecoplan (includes Jun 19, 2020 r/Polymarket Lounge): https://api.pullpush.io/reddit/search/submission/?author=shaynecoplan&after=1590969600&before=1604188800&size=500&sort=asc&sort_type=created_utc
• E59 — pullpush comment id h4z3jlm (sumersao: “the exchange is live now @ kalshi.com”, Jul 12, 2021): https://api.pullpush.io/reddit/search/comment/?ids=h4z3jlm
• E60 — pullpush comment id h8q0z5y (sumersao: “The app is in the works!”, Aug 12, 2021): https://api.pullpush.io/reddit/search/comment/?ids=h8q0z5y
• E61 — pullpush comment id hjquoj0 (liortulip self-identifies as a Kalshi software engineer, Nov 8, 2021): https://api.pullpush.io/reddit/search/comment/?ids=hjquoj0
• E62 — pullpush comment id hl6r3o4 (liortulip asks for sign-up bonus/referral feedback, Nov 18, 2021): https://api.pullpush.io/reddit/search/comment/?ids=hl6r3o4
• E63 — pullpush comment id hl6r9o1 (liortulip acknowledges paper-trading onboarding idea, Nov 18, 2021): https://api.pullpush.io/reddit/search/comment/?ids=hl6r9o1
• E64 — pullpush comment id hl6ri3x (liortulip API starter-code support + PM for issues, Nov 18, 2021): https://api.pullpush.io/reddit/search/comment/?ids=hl6ri3x
• E65 — PRNewswire (Jan 4, 2024): Novig Colorado launch release with founder quote (Jacob Fortinsky): https://web.archive.org/web/20240105020419/https://www.prnewswire.com/news-releases/novig-debuts-first-of-its-kind-commission-free-sports-betting-app-in-colorado-302026625.html
• E66 — GamblingInsider (Dec 5, 2023): Intelitics partnership for Novig affiliate + paid-channel acquisition in Colorado, includes Novig Head of Growth quote: https://web.archive.org/web/20240724153213/https://www.gamblinginsider.com/news/23255/intelitics-partners-with-novig-for-colorado-expansion
• E67 — Sports Business Journal (Feb 6, 2012): FanDuel in-depth profile (active URL path in this pass): https://www.sportsbusinessjournal.com/Journal/Issues/2012/02/06/In-Depth/FanDuel/
• E68 — FanDuel founder context substituted with durable launch-period source (TechCrunch, Jul 21, 2009): https://techcrunch.com/2009/07/21/fanduel-turns-fantasy-sports-betting-into-a-social-game/
• E69 — Novig newsroom post (Dec 5, 2023): “Novig Announces Partnership with Intelitics”; first-party confirmation of affiliate + paid-channel focus and link to Intelitics announcement: https://www.novig.us/articles/novig-announces-partnership-with-intelitics
• E88 — PRNewswire (Oct 3, 2023): Novig secured Colorado Internet Sports Betting Operator license and announced fall-launch timing: https://web.archive.org/web/20231018174412/https://www.prnewswire.com/news-releases/novig-secures-co-license-paving-the-way-for-fall-launch-301945730.html
• E89 — PRNewswire (Aug 22, 2023): Novig announced $6.4M seed funding, founder background, and Colorado launch framing: https://web.archive.org/web/20240105055436/https://www.prnewswire.com/news-releases/novig-announces-6-4m-in-seed-funding-from-leading-investors-ahead-of-launch-in-colorado-301906148.html
• E90 — Boston Globe (May 1, 2017): DraftKings origin profile (founders leaving VistaPrint, early 2012 first contest details): https://www.boston.com/news/business/2017/05/01/five-years-later-draftkings-readies-for-its-second-act/

Robinhood Early-Growth Evidence

• E70 — TechCrunch (Sep 23, 2014): Robinhood raised $13M and reported half a million waitlist signups pre-launch: https://techcrunch.com/2014/09/23/robinhood-stock-app/
• E71 — TechCrunch (Dec 11, 2014): Robinhood launch coverage citing 500,000 waitlist signups: https://techcrunch.com/2014/12/11/robinhood-free-stock-trading/
• E72 — CNBC (Feb 27, 2014): Robinhood coverage citing more than 150,000 people on the waiting list: https://www.cnbc.com/2014/02/27/robinhood-a-new-app-offers-free-stock-trades.html
• E73 — Robinhood S-1 filing (Jul 1, 2021): over 80% of new funded customers in 2020 and Q1 2021 acquired organically or through referral program: https://www.sec.gov/Archives/edgar/data/1783879/000162828021013318/robinhoods-1.htm

Channel and AI-Native Content Distribution References (2025-2026)

• E74 — LinkedIn Marketing Solutions: Thought Leader Ads overview (supported objectives, creator-permission model, format constraints): https://business.linkedin.com/marketing-solutions/native-advertising/thought-leader-ads
• E75 — LinkedIn for Marketing (Aug 13, 2025): Introducing Thought Leader Event Ads; cites 1.6x higher engagement for Thought Leader Ads vs single image ads: https://www.linkedin.com/pulse/introducing-thought-leader-event-ads-build-trust-influence-pcelc
• E76 — Reddit Business Blog: Reddit Ads strategy best practices (goals/KPIs/community-native creative/testing guidance): https://www.business.reddit.com/blog/reddit-ads-best-practices-strategy
• E77 — Instagram for Business: Instagram Best Practices hub (creative, format, and measurement guidance): https://business.instagram.com/instagram-best-practices
• E78 — Meta newsroom (Jan 28, 2026): 2026 AI update including ads improvements, Meta AI business assistant testing, and Instagram recommendation originality metrics: https://about.fb.com/news/2026/01/2026-ai-drives-performance/
• E79 — Meta newsroom (Apr 24, 2025): spammy-content crackdown and original creator protection signals: https://about.fb.com/news/2025/04/cracking-down-spammy-content-facebook/
• E80 — TikTok Newsroom (Jun 16, 2025): Symphony AI creative tools update for scalable content production: https://newsroom.tiktok.com/en-us/creativity-at-scale-meet-our-latest-symphony-generative-ai-tools
• E81 — TikTok Newsroom (Jan 14, 2026): TikTok Next 2026 trend forecast for marketers (AI + data + creator/community strategy): https://newsroom.tiktok.com/introducing-tiktok-next-2026-our-trend-forecast-for-marketers-for-the-year-ahead-ca
• E82 — Reddit Inc. News (Jan 5, 2026): Max campaigns beta for AI-powered ad optimization: https://redditinc.com/news/now-in-beta-max-campaigns-for-ai-powered-ad-performance-and-unique-audience-insights
• E83 — Cloudflare Blog (Dec 15, 2025): 2025 year in review including AI crawler traffic and bot-share metrics: https://blog.cloudflare.com/radar-2025-year-in-review/
• E84 — Similarweb (Jul 29, 2025): AI referral traffic by industry, including LinkedIn among top tech/social AI-referral domains: https://www.similarweb.com/blog/insights/ai-news/ai-referral-traffic-winners/
• E85 — arXiv (Feb 6, 2025): Signals in the Noise: How Smart Is Social Media for Business Analysis? (X/Twitter engagement analysis): https://arxiv.org/abs/2502.04593
• E87 — arXiv (Nov 11, 2024): Intraday Trading Algorithm with Twitter Sentiment and Dynamic Stop-Loss for Cryptocurrency Markets: https://arxiv.org/abs/2411.06567
• E96 — Robinhood newsroom (Jan 5, 2015): #RobinhoodRewind 2014; first-party statement that over 600,000 signed up for early access and over 150,000 were invited post-launch, with mention of broad top-tier media coverage: https://robinhood.com/us/en/newsroom/robinhoodrewind-2014/
• E91 — Google Search Status Dashboard ranking history (shows 2025 and 2026 core/spam/discover update cadence): https://status.search.google.com/products/rGHU1u87FJnkP6W2GwMi/history
• E92 — OpenAI product launch (Oct 31, 2024) and adoption update (Feb 5, 2025) for ChatGPT Search (expanded from paid users to all available regions): https://openai.com/index/introducing-chatgpt-search/
• E93 — OpenAI product launch (Jan 23, 2025) and integration update (Jul 17, 2025) for Operator into ChatGPT agent mode: https://openai.com/index/introducing-operator/
• E94 — OpenAI product launch (Oct 21, 2025) for ChatGPT Atlas; page notes ChatGPT Search had quickly become one of ChatGPT’s most-used features: https://openai.com/index/introducing-chatgpt-atlas/
• E95 — OpenAI API launch (Apr 14, 2025) for GPT-4.1 series; includes migration signal by deprecating GPT-4.5 preview in July 2025: https://openai.com/index/gpt-4-1/

Section 1: How They Got Their First 1,000 Users

This synthesis is updated against the March 2026 evidence pass in Section 1.1-1.6.
Two early winning paths appear in the evidence:

1. founder/early-team manual distribution (Polymarket, Kalshi, Novig)
2. disciplined paid + liquidity operations after launch timing alignment (DraftKings, FanDuel)

Polymarket: Founder-Led Crypto Distribution + Event Timing

• Founded/launch context (verified in this pass): Polymarket was operating around June 2020, with founder-linked community activity visible during launch window. E30 E58
• Most defensible first-1,000-user thesis: crypto-native users acquired via founder outreach, early Reddit/community activity, and tightly curated high-interest markets.

First-Month Evidence (Jun 1-Aug 1, 2020)

1. Launch timing is verified: CFTC states Polymarket operated from approximately June 2020 (E30).
2. Founder-run community operations are directionally supported: launch-window Reddit query artifacts and founder-attributed metadata exist, but direct Reddit permalinks in this window can be unavailable/removed and should not be treated as sole proof (E32, E33, E34, E58).
3. Web archive evidence is partial: earliest product-like homepage retrievable in this pass is Oct 22, 2020 (E31).

Lesson for LONGSHOT

Polymarket’s first users appear to have been won through manual community seeding and market curation, with social-permalink evidence treated as directional when unavailable (E30, E32, E58).
No dated month-one paid-channel artifact was retrievable in this pass, so paid-channel contribution in that window remains unverified.
For LONGSHOT, that means first concentrating liquidity into a small set of culturally relevant markets and driving founder-led distribution in high-context communities.

References: E30 E32 E58

Kalshi: Regulation-First Build + Early Team Activation

• Founded/launch context (verified in this pass): Kalshi appears in YC W19 public materials and has a dated Jul 2021 public-beta artifact. E40 E35
• Most defensible first-1,000-user thesis: initial users came from finance/quant-adjacent audiences and early community onboarding after regulatory readiness.

First-Month Evidence (Jul 1-Sep 1, 2021)

1. Public beta timing is verified: “The Kalshi Public Beta is Live” is dated Jul 26, 2021 (E35).
2. Early community operations are verified: in-window Reddit activity exists, and early-team account sumersao posted direct conversion CTAs plus onboarding updates (E36, E37, E59, E60).
3. Pre-launch credibility channel is verified: YC W19 Demo Day listing includes Kalshi (E40).

Lesson for LONGSHOT

Kalshi shows the regulation-first tradeoff: slower initial growth but stronger trust and institutional credibility (E35, E36, E59, E60).
For LONGSHOT, this argues for early trust scaffolding (transparent rules, dispute operations, clear market standards) even while acquisition stays hands-on.

References: E35 E36 E59 E60

Novig: Embedded Sharp-Bettor Community + Colorado Affiliate/Paid GTM

• Founded/launch context (verified in this pass): Jan 2024 launch PR and Dec 2023 partner announcement document Novig’s early GTM framing and named founder/exec context. E65 E66
• Most defensible first-1,000-user thesis: acquisition combined pre-existing sharp-bettor community demand with explicit affiliate and paid channels during Colorado rollout.

First-Month Evidence (Colorado window: Nov 1, 2023-Jan 1, 2024)

1. Affiliate/paid strategy is verified in-window: Dec 5, 2023 Intelitics partnership states Novig used affiliate and paid channels for Colorado expansion (E66).
2. Founder GTM messaging is documented near-window: Jan 4, 2024 launch PR includes product-value hooks (“better prices, faster in-game trading, more transparency”) (E65).
3. Founder-posted social-link evidence remains a gap: earliest retrievable Novig URL post in this pass is from the official account on Sep 4, 2025 (E28).

Lesson for LONGSHOT

Novig validates that a focused niche can seed early liquidity, but growth channels and legal structure must stay aligned (E65, E66).
For LONGSHOT, preserve transparent settlement and trust ops from day one to protect channel gains from credibility shocks.

References: E65 E66

Legacy DFS Control Cases (DraftKings + FanDuel)

The 2009-2013 DFS control cases reinforce a related pattern: narrow contest formats and concrete launch timing before broad channel expansion (E46, E49, E50, E51, E90).

References: E46 E49 E50 E51 E90

1. DraftKings (2012): Wayback confirms early web presence in April 2012; dedicated TechCrunch coverage appears later in September 2012 (E46, E49).
2. FanDuel (2009): Wayback and TechCrunch artifacts exist in-window (E50, E51).

Updated Cross-Company Takeaways (March 2026)

1. Founder/early-team manual distribution is repeatedly verified in early launch windows.
2. DFS control cases also show an alternate early win: disciplined paid acquisition paired with liquidity operations.
3. Liquidity concentration and market curation matter more than broad channel count in month one.
4. Regulatory posture directly determines channel availability and growth speed.
5. Paid/affiliate channels can work early only when trust, market quality, and onboarding clarity are already in place.
6. Treat private-company DAU/volume/profitability claims as directional unless anchored to primary artifacts.

References: E30 E35 E65 E66 E46 E50

Section 2: High-Value Prediction Market User Segments

Why This Matters

Competitive analysis and marketplace literature show that a relatively small cohort of high-intent users often drives disproportionate liquidity and repeat volume in two-sided markets (E3, E4, E30).

References: E3 E4 E30

Core Principle

• Not all users contribute equally to marketplace health.
• Prioritize users who improve depth, spreads, fill rate, and repeat volume.
• Optimize for cohort quality first, then total signups.

Segment Priority for LONGSHOT

Launch-Month Segments (Evidence-Aligned)

Direct launch-window artifacts most strongly support sharp discretionary and API/quant-adjacent cohorts as early liquidity builders (founder/early-team community operations plus quant-style onboarding/support loops). E58 E59 E60 E61 E65 E66

1. Sharp discretionary traders (Primary wedge). Behavior: Trade around mispricing and news flow; usually high repeat activity. Why they matter: Improve price discovery and early liquidity quality. How to win: Fast execution, transparent rules, no hidden friction, tight spreads on core markets.

2. API/quant traders (Liquidity stabilizers). Behavior: Systematic order placement, market making, arbitrage, model-driven entries. Why they matter: Increase depth and book resiliency, especially in volatile windows. How to win: Reliable API, stable latency, clear rate limits, predictable settlement behavior.

Expansion Segments (After Liquidity Stabilizes)

These segments are expansion hypotheses to validate with cohort data after launch-market liquidity is stable.

3. Narrative/social traders (Distribution multiplier). Behavior: React to cultural events and share positions publicly. Why they matter: Bring incremental demand and awareness when market cards are shareable. How to win: Simple onboarding, clean market pages, social proof, event-timed market launches.

4. Casual entertainment users (Late expansion). Behavior: Lower intent, lower retention, high sensitivity to UX friction. Why they matter: Can scale MAU, but often weak on liquidity contribution in early stage. How to win: Only after core book quality is stable; use guided onboarding and simpler market sets.

Qualification Rules (Who Counts as “High-Value”)

Track users by 30-day and 90-day contribution with an emphasis on sustained behavior.

1. Net contribution to top-market depth.
2. Positive impact on spread quality.
3. Repeat funded trading sessions.
4. Low abuse/risk flags.
5. Retained activity after incentives taper.

Segment Scorecard (Weekly)

1. Funded activation rate by segment.
2. D7/D30 retention by segment.
3. Volume per active user by segment.
4. Spread/depth impact on target markets.
5. Incentive cost per retained high-value user.
6. % of total volume from top decile users.

Operating Implication for LONGSHOT

Use segments as the control layer across acquisition, onboarding, incentives, and retention.

1. Acquire for liquidity quality and sustained cohort outcomes.
2. Onboard high-value cohorts with the fastest path to first quality trade.
3. Gate incentive spend by retained cohort quality.
4. Expand to broader segments only after core market health stays stable for multiple weeks.

References: E3 E4 E2

Section 3: Venues & Channels to Target

Why This Section Looks Different

This chapter translates the findings from Section 1 and Section 2 into a practical channel plan.

Detailed, platform-by-platform content playbooks (including LinkedIn, X, TikTok, Instagram, Reddit, and AI-native updates from Jan-Feb 2026) are in 3.1 Tried-and-True + AI-Native Content Growth by Channel.

• From Section 1: early wins came from founder-led community distribution, careful market curation, and friction removal. Large partner integrations can accelerate growth, but concentration risk becomes real. E12 E58 E59
• From Section 2: optimize for liquidity quality and repeat high-intent behavior. E3 E4

Channel Selection Rules

1. Start where high-intent users already coordinate.
2. Earn trust with analysis and execution. Avoid link drops. E1
3. Reduce onboarding friction before scaling paid or partner channels.
4. Never let one external partner own your demand curve. E12
5. Treat every channel test as a measurable experiment. E2

Tier 1: First 90 Days (Highest ROI)

1) Founder-Led Community Ops (Discord, Telegram, Reddit)

This is the closest match to proven early patterns from Polymarket, Kalshi, and Novig.

• Polymarket founder-linked Reddit operations are visible in month 1. E58 E34
• Kalshi early-team accounts handled onboarding and support directly in launch-period threads. E59 E60 E61
• Novig leaned into community-native bettor behavior and affiliate/paid expansion support early in Colorado. E65 E66

Execution rules:

• Assign named operators (not anonymous brand posting).
• Publish market thesis threads with substantive context.
• Run weekly office-hours style Q&A for onboarding and product feedback.
• Track liquidity-producing users by source cohort.

2) X (Crypto/Finance Twitter) for Distribution Velocity

X can be a fast path from insight to market participation when posts contain clear, auditable thesis.

• The evidence set includes finance-X artifacts where market commentary and odds discussion are visible; treat as directional channel signal, not causal proof. E27
• Founder and operator accounts appear repeatedly in the retrievable discovery artifacts for this category. E26 E28 E29

Execution rules:

• Each post should include: position, odds delta, why now, what would falsify.
• Publish after-action reviews on settled markets.
• Use the market card as the primary shareable unit.

3) Onboarding Friction Removal + Partnership Readiness

Do this in parallel with community work. Do not delay until after growth starts.

• Social + email login paths.
• Embedded wallet creation.
• Regulated fiat on-ramp options.
• Fast first-trade flow with clear risk disclosures.

References: E1 E3 E12

Partnership guardrails (from Kalshi-style concentration risk):

• Cap single-partner share of funded users.
• Cap single-partner share of volume.
• Keep direct channels compounding even during partner spikes. E12

Tier 2: After Initial Liquidity (Weeks 12+)

4) Programmatic Discovery: SEO + PSEO + LLM SEO

Use programmatic discovery only after market quality and settlement reliability are stable.

• SEO: high-quality canonical pages (market explainers, resolution docs, methodology pages).
• PSEO: templated market pages at scale only when each page includes unique market data, transparent method, and non-thin commentary.
• LLM SEO: structure pages for answer-engine retrieval (clear entities, cited sources, concise Q&A blocks, unambiguous settlement language).

Guardrails:

• Use current ranking-update cadence as the operating baseline (not a one-time 2024 rule snapshot). E91
• Publish only people-first pages with original analysis and source transparency. E6
• Treat AI-answer visibility as a first-class channel and monitor AI crawler/referral share directly. E83 E84

5) Niche Financial Media and Newsletter Syndication

Package LONGSHOT probabilities as decision support for finance-native audiences.

• Substacks and newsletters
• Podcasts and live spaces
• Data-driven market recap formats

6) API and Quant Community Distribution

Once market quality is stable, expose data endpoints for high-frequency and model-driven users.

• Prioritize reliability and latency consistency over feature volume.
• Build risk and monitoring controls from day one. E7 E22 E23

Tier 3: Scale Channels (Post-PMF Only)

Use these only after retention and liquidity quality are stable by segment.

• Paid affiliates and performance media (with strict quality gates)
• Co-branded distribution deals (with partner concentration caps)

Deprioritized until late stage (not strongly supported by first-month case evidence):

• Broad creator/short-video loops
• Campus ambassador programs

Why this is last:

• Large incumbents spend heavily on marketing; brute-force spend is not an early-stage edge. E8 E9
• Historical DFS launch coverage shows narrow initial formats and staged expansion before broad channel scaling. E49 E51 E90

Weekly Operating Cadence

1. Pick one channel experiment per target segment.
2. Define success as liquidity-quality outcomes and cohort durability.
3. Ship, measure, and review within 7 days. E2
4. Scale only what compounds retention, spread quality, and repeat participation.

Channel Anti-Patterns

• Over-indexing on vanity signups while books stay thin.
• Dependence on one distribution partner for most volume. E12
• SEO at scale without unique analytical value or answer-engine retrieval utility. E6 E91
• Aggressive growth moves without regulatory sensitivity. E10 E11

Primary Sources Used in This Section

Core strategy and growth discipline: E1, E2, E3, E4

Search policy and answer-engine visibility: E6, E83, E84, E91

Distribution concentration and scale economics: E8, E9, E12

Early channel behavior and founder-linked discovery artifacts: E26, E27, E28, E29, E34, E49, E51, E58, E59, E60, E61, E65, E66, E90

3.1 Tried-and-True + AI-Native Content Growth by Channel

Why This Addendum Exists

This chapter gives a channel-by-channel execution layer for LONGSHOT across LinkedIn, X/Twitter, TikTok, Instagram, Reddit, and other compounding channels. It is split into:

• startups in betting, crypto, exchanges, and fintech (higher trust/compliance burden)
• startups in general (broader B2B/B2C use)

It combines timeless distribution patterns with AI-native updates from January 2026 plus late-2025 distribution data. These updates should be treated as directional platform signals, not direct proof of user-acquisition lift for LONGSHOT. E82 E81 E78 E83

References: E1 E2 E75 E78 E81 E82

Timeless Channel Playbook (Still Works)

LinkedIn

For betting/crypto/exchanges/fintech:

• Founder and operator POV posts on market structure, risk, compliance, and product decisions.
• Use thought-leader amplification formats to build institutional trust with decision-makers.
• Publish post-mortems after major market events (what moved, what resolved, what was wrong).

For startups in general:

• Keep a consistent “problem -> insight -> proof” publishing rhythm.
• Use founder + domain-expert faces, not only brand-page voice.
• Reuse long-form customer learnings into shorter native posts.

Evidence (directional): E74 E75

X (Twitter)

For betting/crypto/exchanges/fintech:

• Run real-time market commentary loops: thesis -> move -> settlement review.
• Ship rapid analysis during macro, election, sports, and crypto volatility windows.
• Keep an archived track record of calls to build credibility.

For startups in general:

• Treat X as a message-testing layer before scaling creative elsewhere.
• Use recurring formats with stable hooks (weekly teardown, launch notes, “what changed”).
• Pair fast posting with explicit falsifiability to reduce noise.

Evidence (channel artifact + directional context): E27 E28

TikTok

For betting/crypto/exchanges/fintech:

• Education-led short video formats (risk framing, market mechanics, event explainers).
• Repeatable “what this market implies” formats tied to tentpole events.

For startups in general:

• Creator-native storytelling cadence beats polished ad creative early.
• Build serial formats before one-off trend chasing.

Evidence (directional): E80 E81

Instagram

For betting/crypto/exchanges/fintech:

• Reels for explainers, carousels for myth-vs-fact and compliance-safe education.
• Keep content creator-led and original; avoid ad-like tone in organic feed.

For startups in general:

• Reels + Stories for top-of-funnel discovery and lightweight engagement loops.
• Repurpose high-performing assets from other channels into native visual formats.

Evidence (directional): E77 E78 E79

Reddit

For betting/crypto/exchanges/fintech:

• Earn trust with substantive comments, AMAs, and transparent assumptions.
• Use named operators for support and product dialogue, not anonymous brand-only posting.
• Prioritize high-signal subreddits where users already debate odds, regulation, and execution.

For startups in general:

• Comment quality and follow-up speed outperform pure link-dropping.
• Community norms should define cadence and tone by subreddit.

Evidence (primary + directional): E58 E59 E76

Other Channels (Compounding)

For betting/crypto/exchanges/fintech:

• Owned newsletter for market recap, risk notices, and retention loops.
• YouTube/podcast explainers for higher-trust education and longer shelf life.
• SEO/PSEO pages for market rules, settlement logic, and definitions.

For startups in general:

• SEO + email is a high-control compounding stack hypothesis; validate with attribution data before scaling.
• Use syndication and partnerships only after retention and conversion quality are stable.

Evidence (policy + directional data): E6 E83 E84 E91

AI-Native Layer (Last Couple Months as of March 4, 2026)

Newest launch/adoption signals in this evidence set span January 2025 through January 2026 across OpenAI and major distribution platforms. E78 E81 E82 E92 E93 E94 E95

1. Platform-native AI systems are being pushed aggressively by major networks and model vendors.

• Meta announced additional AI tools for growth/performance (January 28, 2026). E78
• Reddit launched Max campaigns beta (January 5, 2026). E82
• TikTok’s 2026 trend report centers AI-powered creative and relevance loops (January 14, 2026). E81
• OpenAI expanded Search availability (Feb 5, 2025), launched Operator (Jan 23, 2025), integrated it into ChatGPT agent mode (Jul 17, 2025), and launched Atlas (Oct 21, 2025) noting Search became one of ChatGPT’s most-used features. E92 E93 E94 E95

2. Answer-engine visibility likely matters more as AI crawler and referral signals rise.

• Cloudflare’s 2025 year-in-review shows AI crawler traffic rising materially on the open web. E83
• Similarweb’s AI referral tracking shows measurable AI-origin traffic by domain; treat this as directional signal rather than causal proof for any single channel. E84

3. Human originality and recency discipline still gate durable performance.

• Keep people-first, original pages and re-check against ongoing ranking-update cadence rather than static 2024 assumptions. E6 E91
• LinkedIn reports stronger engagement when content comes from authentic thought leaders, not only brand accounts. E75

90-Day Execution Pattern for LONGSHOT

1. Pick one channel owner and two recurring formats per platform.
2. Run one timeless-format experiment and one AI-assisted variant per platform every two weeks.
3. Scale only channels producing funded activation, repeat participation, and spread/liquidity quality.
4. Add compounding layers (newsletter, SEO explainers, archive pages) after channel-message fit is proven.

KPI gates:

• Betting/crypto/exchange/fintech: funded activation, first qualified trade, D30 retained traders.
• Startup-general: activated users, D30 retention, content-assisted pipeline/revenue.

References: E1 E2 E3 E4 E6 E74 E75 E76 E77 E78 E79 E80 E81 E82 E83 E84 E91 E92 E93 E94 E95

Section 4: The LONGSHOT Growth Playbook

How to Read This Playbook

This section converts findings from Section 1, Section 2, and Section 3 into an execution sequence.

• Section 1 takeaway: early traction in this category comes from founder-led distribution, curated markets, and low-friction onboarding. E1 E34 E58 E59
• Section 2 takeaway: optimize for liquidity quality, repeat high-intent users, and durable cohort behavior. E3 E4
• Section 3 takeaway: sequence channels by maturity and guard against partner concentration risk. E12

Operating Principles

1. Keep weekly growth discipline from day one. E2
2. Treat liquidity as the core product KPI and operating focus. E3
3. Scale only channels that improve cohort quality over time. E4
4. Remove onboarding friction before increasing paid spend. E1 E2
5. Build for regulatory durability while growing. E10 E11

Phase 0: Foundations (Now -> Testnet)

Objective

Create a measurable launch system before pushing for scale.

Must-Ship Work

• Event taxonomy and market quality rubric (clear settlement rules, high user relevance).
• Core liquidity dashboard: spread, depth, fill rate, time-to-fill, repeat trader rate.
• Source-cohort dashboard: which channels produce repeat traders vs. one-time signups.
• Compliance and risk baseline: onboarding controls, market review workflow, incident escalation.

Exit Criteria

• Dashboard metrics update daily with no major data gaps.
• Initial candidate launch set (size defined by liquidity-support and operator-review capacity) passes quality rubric.
• Founding-trader outreach list is segmented and active.

Phase 1: Pre-Launch / Testnet

Objective

Recruit and activate a focused founding cohort that can seed real liquidity at launch.

Core Actions

1. Recruit a manually serviceable founding cohort from Discord/X/Reddit communities with direct operator outreach (size set by operator support capacity, not top-of-funnel targets). E1 E58
2. Run paper-trading and testnet loops to validate onboarding and execution UX before real capital.
3. Publish market thesis content before launch (why this market exists, how it settles, what invalidates the thesis). E5 E6
4. Launch with curated markets (avoid unbounded open creation at day zero).

Phase 1 KPIs

• Activation rate of invited founding traders.
• First-trade completion rate.
• Repeat trading within 7 days.
• Early spread/depth stability in launch candidates.

Phase 2: Mainnet Launch (First 90 Days)

Objective

Prove repeatable liquidity quality and cohort retention with durable volume quality.

Core Actions

1. Concentrate incentives on priority markets with explicit spread/depth/fill SLAs.
2. Time launch pushes around tentpole attention windows (sports, macro, elections, crypto catalysts).
3. Run API-first onboarding for power users and quants where LONGSHOT execution quality can be differentiated. E7
4. Keep fee strategy simple and transparent while the book is building.

Phase 2 KPIs

• Weekly active traders.
• Market-level spread and depth by hour/day.
• Fill reliability under peak load.
• 4-week retention for high-intent cohorts.

Decision Gate to Enter Phase 3

Move forward only when liquidity quality holds across multiple event categories and sustained periods.

Phase 3: Expansion (Months 4-12)

Objective

Scale distribution without losing control of market quality, risk posture, or channel mix.

Core Actions

1. Expand market catalog with quality filters and post-settlement review loops.
2. Add referral loops only where invited users preserve liquidity quality.
3. Productize data distribution (newsletter/media/API feeds) after internal quality thresholds are stable.
4. Pursue partnerships with explicit concentration caps per partner channel. E12

Risk Controls in Phase 3

• Partner concentration limit on funded users and volume share.
• Channel-level CAC payback thresholds before budget scaling.
• Regulatory review checkpoints for new market categories. E10 E11

Post-PMF Experiments (Evidence-Bound)

These are optional and should come after strong liquidity fundamentals are established.

1) Programmatic Discovery Engine (SEO + PSEO + LLM SEO)

Build discovery infrastructure only after market-quality and settlement-quality metrics are stable.

• SEO for canonical market/methodology pages
• PSEO for scaled market pages with unique data + non-thin commentary
• LLM SEO for answer-engine retrieval (structured Q&A, clear entities, source citations)

Guardrail: do not publish thin or unverifiable generated pages at scale. E5 E6

2) Embedded Distribution via APIs/Partners

Expose market data and execution entry points in partner surfaces, but only with concentration safeguards.

Evidence direction: embedded distribution can accelerate growth and also create dependency risk. E12

3) Automated Incentive Reallocation

Use rule-based budget governors to shift incentives toward cohorts that improve depth, fill quality, and retention.

Evidence direction: large incumbents emphasize disciplined acquisition economics; undisciplined promo spend is structurally expensive. E8 E9

Weekly Growth Operating Rhythm

1. Select one channel and one segment for each weekly test.
2. Define success with liquidity-quality and retention metrics.
3. Ship and review in a 7-day cycle. E2
4. Scale winners, kill weak tests quickly, and document why.

Anti-Patterns to Avoid

• Optimizing for gross signups while books remain thin.
• Copying large-incumbent paid playbooks too early. E8 E9
• Over-reliance on a single distribution partner. E12
• Publishing low-value market pages at scale. E5
• Expanding market scope faster than compliance/risk controls can support. E10 E11

Primary Sources Used in This Section

Strategy and growth discipline: E1, E2, E3, E4

Search and content quality: E5, E6

Execution quality, unit economics, and partner concentration: E7, E8, E9, E12

Early channel behavior and regulatory context: E34, E58, E59, E60, E10, E11

Section 5: Resource Allocation & Time Investment

This section defines how to allocate limited growth bandwidth across phases for a pre-revenue, pre-mainnet crypto-native startup (E2, E3, E4).

References: E2 E3 E4

How to Use This Section

Use this as an evidence-aligned operating split for the first launch phases, not a generic startup template.

• Polymarket/Kalshi/Novig evidence favors direct operator distribution early. E34 E58 E59 E60 E65 E66
• DraftKings/FanDuel evidence favors narrow launch formats and staged expansion once core loops are visible. E46 E49 E50 E51 E90

Pre-Launch Phase: Time Priorities (Evidence-Aligned)

1. Highest priority: founder/operator distribution and community ops.
   Direct outreach, community replies, launch-thread seeding.

2. High priority: market design + settlement clarity.
   Curation, resolution clarity, and quality checks before scaling.

3. Medium priority: onboarding friction removal.
   First-trade flow, wallet/deposit path, and activation support.

4. Medium priority: instrumentation + trust operations.
   Liquidity dashboards, risk/event monitoring, incident routing.

5. Experimental only: paid tests.
   Small tests only before conversion-quality proof.

Post-Launch Phase (First 90 Days): Time Priorities

1. Highest priority: liquidity operations and spread/depth monitoring.
2. High priority: cohort retention and reactivation loops.
3. Medium priority: founder/operator distribution loops.
4. Medium priority: trust/compliance/risk workflows.
5. Experimental scale-up: paid/affiliate channels (quality-gated).

Operating Rule

Treat time allocation like budget allocation: scale what improves both growth and market quality metrics, and cut what only inflates top-of-funnel volume (E2, E4, E3).

References: E2 E4

Section 6: Budget Framework

This budget is a trigger-based framework tied to early winning patterns in the case studies, not a fixed spend template.

• Polymarket/Kalshi/Novig: manual operator distribution and onboarding support appear first. E34 E58 E59 E60 E65 E66
• DraftKings/FanDuel: launch windows show narrow initial formats with staged expansion once product loops are measurable. E46 E49 E50 E51 E90

References: E8 E9 E3 E4

Budget Order (First 6 Months)

1) Liquidity and Market Quality (Core Line Item)

Use as the largest controllable line after launch.

• Purpose: spread/depth/fill reliability on priority markets.
• Trigger to increase: sustained improvement in liquidity metrics + retained cohort quality.
• Trigger to cut/reallocate: degraded fill reliability or weak retained-volume quality.

Budget posture: treat this as the largest controllable post-launch line item.

2) Founder/Operator Distribution and Community Operations

• Purpose: direct outreach, onboarding support, and feedback loops in high-intent communities.
• Trigger to increase: rising funded activation from operator-led cohorts.
• Trigger to cut/reallocate: high top-of-funnel response with weak funded/retained conversion.

Budget posture: reserve dedicated operator capacity from launch.

3) Referral / Incentive Programs (Quality-Gated)

• Purpose: accelerate qualified acquisition, not raw signup volume.
• Qualification gate: deposit + first trade + retained activity threshold.
• Hard stop-loss: pause when retention/GMV-retention cohorts miss targets.

Budget posture: cap and reverse quickly when retained quality weakens.

4) Paid Acquisition Experiments (Only After Conversion Proof)

• Purpose: controlled channel tests, not scale spend.
• Start condition: onboarding friction and first-trade conversion are stable.
• Scale condition: payback, retention, and liquidity contribution hold by cohort.

Budget posture: keep a small experiment pool until economics are repeatedly validated.

5) Programmatic Discovery (SEO + PSEO + LLM SEO)

Use only after market quality and settlement quality are stable.

• SEO: canonical pages (market explainers, methodology, resolution references).
• PSEO: scaled market pages only with unique data + non-thin analysis.
• LLM SEO: answer-engine-ready structure (clear entities, concise Q&A, source citations).
• Publish gate: reject thin or unverifiable generated pages. E5 E6

Budget posture: fund only quality-gated content systems and QA/editorial operations.

6) Trust, Risk, and Compliance Operations

• Purpose: maintain market integrity while acquisition scales.
• Trigger to increase: incident volume, dispute latency, or abuse flags rise.
• Never defer: escalation routing and incident response ownership.

Budget posture: maintain non-discretionary baseline coverage for people and monitoring tooling.

Pre-Launch Budget Use (Monthly)

Before mainnet, budget should validate:

• First-trade activation quality
• Operator-led community pull
• Market-definition and settlement clarity
• Instrumentation for liquidity and cohort quality

Operating Rule

Budget follows evidence and cohort quality:

1. Scale only what improves liquidity + retention together.
2. Keep paid/performance in experiment mode until quality gates pass.
3. Keep programmatic discovery quality-gated (SEO, PSEO, LLM SEO) from day one.

References: E2 E3 E4 E5 E6

Section 7: LONGSHOT’s Unique Advantages

Evidence-Aligned Advantage Model

1) Execution Quality as the Entry Requirement

Infrastructure performance claims are useful only if they convert into better book quality (tighter spreads, deeper books, faster fills, lower failure rate).

Operational implication:

• Track execution claims against real market outcomes weekly.
• Prioritize reliability metrics over feature volume.

References: E7 E3

2) Trust Operations as Acquisition Infrastructure

Case evidence shows early growth depends on trust-bearing behavior: direct operator replies, transparent settlement logic, and visible support loops.

Operational implication:

• Keep market-definition, resolution, and dispute workflows explicit.
• Treat abuse/surveillance controls as part of GTM, not only compliance.

References: E11 E58 E59 E60

3) Distribution Mix Discipline

Large integrations can accelerate growth and also create dependency risk.

Operational implication:

• Maintain direct channels even during partner spikes.
• Enforce concentration thresholds for funded users and volume share.

References: E12

Competitive Reality (2026)

The market context has shifted versus prior cycles; detailed competitor snapshots should be treated as directional and refreshed quarterly.

• CFTC policy context changed in February 2026 (proposal withdrawal plus enforcement advisory), increasing uncertainty for operator GTM decisions. E10 E11
• Robinhood’s 2025 10-K discloses the January 20, 2026 MIAXdx acquisition and Rothera event-contract JV context. E12
• Strategic pressure remains real because incumbents with broad distribution and large marketing budgets can move quickly when policy windows open. E8 E9 E12

References: E8 E9 E10 E11 E12

Strategic Implication

LONGSHOT advantage should be operated, not narrated:

1. Convert infra performance into measurable liquidity quality.
2. Keep trust/integrity workflows visible in the user journey.
3. Diversify distribution so no single channel controls the demand curve.

Section 10: Automation Plan Double-Verified Against Timeless and AI-Native Growth Tactics

This section evaluates the automation backlog through two lenses:

• Lens A: timeless growth principles
• Lens B: recent AI product launches with observable traction signals

Lens B references in this section are launch-and-adoption signals from 2025-2026 platforms and model releases, used to prioritize what is actually getting pulled into production now.

Automation is retained only when it improves core marketplace outcomes (liquidity, retention, GMV retention, growth rate), maps to recent proven platform behavior, and can be operated with explicit guardrails (E3, E4, E78, E82, E92, E93, E94, E95).

References: E3 E4 E78 E82 E92 E93 E94 E95

10.1 Validation Framework

Lens A: Timeless Growth Wisdom

Do things that do not scale first, then scale only what proves repeatable. Keep weekly growth discipline and optimize for liquidity and cohort quality over vanity signups (E1, E2, E3, E4).

References: E1 E2 E3 E4

Lens B: AI-Native Execution

Prioritize tactics that match recent launches with observable pull from real operators: platform-native AI campaign systems (Meta/Reddit/TikTok), answer-engine distribution shifts, and fast model/runtime migration cycles in the OpenAI stack (E78, E81, E82, E83, E84, E92, E93, E94, E95).

References: E78 E81 E82 E83 E84 E92 E93 E94 E95

Decision Rule

Keep automation that improves growth and market quality simultaneously. Add guardrails when automation could degrade acquisition quality, create low-value content, or increase channel dependency; validate against current ranking-update cadence and AI-referral/crawler shifts (E6, E12, E83, E84, E91).

References: E6 E12 E83 E84 E91

10.2 Automation Backlog (Evidence-Bound by Stage)

This backlog is ordered by fit with observed early winning tactics in Sections 1.1-1.6, then by later-stage scale utility.

Stage A: Launch-Window Aligned (First Priority)

1. Founder/Operator pipeline automation.

   • Why this fits evidence: Polymarket/Kalshi show directional evidence of direct operator outreach and reply loops in launch periods (query artifacts + early-team comments).
   • What to automate: contact stages, follow-up timers, owner assignment, and conversion notes. References: E32 E58 E59 E60

2. Onboarding activation rescue.

   • Why this fits evidence: early conversion depended on reducing first-trade friction.
   • What to automate: drop-off detection, step-specific nudges, completion checklists. References: E1 E2

3. Curated market launch checklist automation.

   • Why this fits evidence: curation and settlement clarity were central in early growth.
   • What to automate: market draft templates, settlement-source checks, approval workflow. References: E3 E11

4. Liquidity SLO monitoring and alerts.

   • Why this fits evidence: early books live or die on spread/depth/fill reliability.
   • What to automate: threshold alerts, owner escalation, and incident timelines. References: E3 E4

5. Weekly growth scorecard automation.

   • Why this fits evidence: weekly discipline appears across growth guidance and case-derived operating needs.
   • What to automate: KPI deltas by cohort/channel, decision queue, stop-loss flags. References: E2 E4

Stage B: After Initial Liquidity Stability

6. Incentive governor tied to retained quality.

   • Why this fits evidence: incentives work when retention/liquidity quality holds, not on raw signup growth.
   • What to automate: budget caps, anomaly flags, manual override path. References: E4 E8 E9

7. Partner concentration guardrails.

   • Why this fits evidence: embedded distribution can accelerate growth and create dependency risk.
   • What to automate: concentration thresholds, alerts, mitigation task generation. References: E12

8. Programmatic discovery quality gate (SEO + PSEO + LLM SEO).

   • Why this fits evidence: search/discovery now depends on both quality controls and answer-engine visibility dynamics.
   • What to automate: publish gate for SEO, PSEO, and LLM SEO pages (uniqueness checks, source citations, thin-content rejection, AI-referral monitoring). References: E6 E83 E84 E91

Stage C: Post-PMF Optional

9. Expanded paid-channel automation (bidding, creative variants, budget routing).

   • Use only after qualified conversion and payback windows are stable. References: E75 E78 E81 E82

10. Advanced experimentation orchestration.

    • Use after core launch loops are consistently measurable and model/tool churn is operationally managed. References: E92 E93 E94 E95

10.3 AI-Native Acquisition Tactics (Use Post-PMF Only)

Operating Rules

• Deploy AI-driven ad optimization only after conversion-quality tracking is stable (value-based goals, qualified conversion events, clear payback windows). References: E4 E75 E78 E82
• Use platform automation only where there is current launch momentum and observed operator pull (Meta/Reddit/TikTok style systems), after channel economics are proven. References: E78 E81 E82 E2
• For programmatic discovery, treat SEO, PSEO, and LLM SEO as separate systems with strict publish gates (source citation, uniqueness, non-thin value). References: E6 E83 E84 E91
• Keep human-in-the-loop review for compliance-sensitive messaging, creative claims, and major strategy shifts. References: E11 E93 E95

10.4 Launch-and-Traction Reference Addendum (AI-Native Automation)

These references emphasize recent launches and observed adoption pull, then tie automation to what is actually shipping and performing in-market.

• E75 — LinkedIn for Marketing (Aug 13, 2025): Thought Leader Event Ads launch; cites 1.6x engagement benchmark for thought-leader ads: https://www.linkedin.com/pulse/introducing-thought-leader-event-ads-build-trust-influence-pcelc
• E78 — Meta newsroom (Jan 28, 2026): AI-driven ads and recommendation updates with reported campaign lift examples: https://about.fb.com/news/2026/01/2026-ai-drives-performance/
• E81 — TikTok Newsroom (Jan 14, 2026): TikTok Next 2026 trend forecast highlighting AI-mediated discovery and content operations: https://newsroom.tiktok.com/introducing-tiktok-next-2026-our-trend-forecast-for-marketers-for-the-year-ahead-ca
• E82 — Reddit Inc. (Jan 5, 2026): Max campaigns beta launch for AI-powered ad optimization: https://redditinc.com/news/now-in-beta-max-campaigns-for-ai-powered-ad-performance-and-unique-audience-insights
• E83 — Cloudflare Radar 2025 review (Dec 15, 2025): rising AI crawler share on the open web: https://blog.cloudflare.com/radar-2025-year-in-review/
• E84 — Similarweb AI-referral analysis (Jul 29, 2025): measurable AI-origin referral traffic by industry/domain: https://www.similarweb.com/blog/insights/ai-news/ai-referral-traffic-winners/
• E91 — Google Search Status Dashboard history: 2025-2026 ranking/spam/discover update cadence: https://status.search.google.com/products/rGHU1u87FJnkP6W2GwMi/history
• E92 — OpenAI ChatGPT Search launch + Feb 2025 expansion update: https://openai.com/index/introducing-chatgpt-search/
• E93 — OpenAI Operator launch + Jul 2025 integration into ChatGPT agent mode: https://openai.com/index/introducing-operator/
• E94 — OpenAI ChatGPT Atlas launch; page notes Search quickly became one of ChatGPT’s most-used features: https://openai.com/index/introducing-chatgpt-atlas/
• E95 — OpenAI GPT-4.1 launch and GPT-4.5 preview deprecation timeline: https://openai.com/index/gpt-4-1/

10.5 Wildcard Growth Ideas (Worked Patterns from Other Startups)

These are high-variance growth bets with direct precedent in startup launch evidence. Treat each as a time-boxed experiment with explicit success and stop-loss thresholds.

References: E30 E32 E34 E35 E36 E39 E40 E49 E50 E51 E58 E59 E60 E65 E66 E69 E70 E71 E72 E73

Wildcard Ideas

1. Referral waitlist flywheel before full-open launch.

   • What this looks like: public waitlist with a visible queue rank, referral-based rank boosts, and staged invite drops to create scarcity and sharing loops.
   • Evidence-backed precedent: Robinhood reported very large pre-launch waitlist demand and later disclosed referral/organic as a dominant funded-customer source. References: E70 E71 E72 E73

2. Founder-led forum seeding in communities that already discuss prediction markets.

   • What this looks like: founders and one growth operator run daily response windows in target Reddit/Discord/X threads and push users to tracked onboarding links.
   • Evidence-backed precedent: Polymarket and Kalshi show launch-window community threads with founder or early-team participation and conversion/onboarding replies. References: E32 E34 E36 E58 E59 E60

3. Narrow launch inventory to concentrate liquidity and social proof.

   • What this looks like: launch with a tight set of high-demand markets only (size set by operator and liquidity capacity), freeze low-demand additions, and focus all distribution on making those markets feel alive.
   • Evidence-backed precedent: early Polymarket evidence points to a focused event-market wedge during the launch window rather than broad category sprawl. References: E30 E32 E34

4. One-line economic wedge campaign (no message dilution).

   • What this looks like: every launch asset repeats one core claim (for example lower cost/better price), with secondary benefits deferred until the first wedge converts reliably.
   • Evidence-backed precedent: early Robinhood and Novig coverage both center growth messaging on a strong, easy-to-repeat economic value proposition. References: E65 E70 E72

5. Launch-month concierge onboarding run by operators, not only product surfaces.

   • What this looks like: staffed launch desk (chat + social replies) with response SLAs, known-friction macros, and daily issue triage sent to product and growth owners.
   • Evidence-backed precedent: Kalshi launch evidence includes direct early-team responses tied to activation and onboarding friction. References: E35 E36 E59 E60

6. Affiliate + paid growth stack in one geo before national expansion.

   • What this looks like: stand up affiliate and paid ops in one jurisdiction, review partner-level quality weekly, and expand only after retention and fraud thresholds hold.
   • Evidence-backed precedent: Novig publicly documented an affiliate + paid-channel partnership for Colorado launch. References: E66 E69 E65

7. Fast-cycle market formats to increase repeat behavior in early cohorts.

   • What this looks like: emphasize short-duration/daily markets with clear, fast resolution windows and immediate post-settlement prompts into the next trade.
   • Evidence-backed precedent: FanDuel launch coverage highlights short-cycle daily format and feedback speed as a core behavior driver. References: E50 E51

8. Credibility-first launch sequencing before aggressive channel scaling.

   • What this looks like: stack credibility artifacts (regulatory/legal clarity, reputable launch coverage, clear market rules) before heavy paid spend.
   • Evidence-backed precedent: Kalshi’s pre-launch credibility signals (YC + regulated-market positioning + launch coverage) preceded broader public distribution. References: E35 E39 E40

10.6 Explicit Do-Not-Automate Rules (Onchain Non-DCM)

The following actions require human final authority. Automation may assist with evidence gathering, drafting, and prioritization, while accountable humans or governance retain final decisions (E11, E23, E93, E95).

References: E11 E23 E93 E95

Prohibited Full Automation

1. Final market outcome adjudication, market voids, and disputed payout decisions
2. Emergency contract controls (pause/unpause/upgrade) without multisig human approval
3. User sanctions (bans/blacklists/restrictions) based only on model output
4. Incentive-budget increases or token-emission changes without explicit cap and owner approval
5. Jurisdiction/access policy decisions and legal interpretation changes
6. Fully autonomous publication of AI-generated SEO/social content in finance-sensitive contexts
7. Personalization that targets loss-chasing or potentially harmful compulsive behavior
8. Oracle/feed source switching triggered only by automation without human validation and rollback planning

10.7 Evidence Addendum (Onchain Operations and Risk Controls)

• E20 — Ethereum Gasper/finality documentation: https://ethereum.org/en/developers/docs/consensus-mechanisms/pos/gasper/
• E21 — Ethereum transaction lifecycle documentation: https://ethereum.org/en/developers/docs/transactions/
• E22 — Chainlink Data Feeds documentation:
  • https://docs.chain.link/data-feeds
  • https://docs.chain.link/data-feeds/selecting-data-feeds
• E23 — OpenZeppelin Monitor documentation: https://docs.openzeppelin.com/defender/module/monitor

End of Document - Confidential