# Retail can’t reliably earn on Polymarket
> Source report: https://gapforapp.com/reports/retail-cant-reliably-earn-on-polymarket

## 1. What we're building
Build a Polymarket earn-intelligence terminal that combines real-time market scanning, wallet analytics, execution controls, and settlement verification. The product should help users identify which markets actually have usable edge by filtering for liquidity, slippage, and resolution-risk traps, while also showing who is moving the market and whether that flow is likely “smart money” or noisy copy-trading bait. Must-have capabilities inferred from the corpus include a wallet watcher with trader profitability scoring, live whale alerts, price/volume drift alerts, cross-venue comparison between Polymarket and Kalshi, and a backtesting layer that scores strategies on realized P&L rather than raw win rate.

To make the product usable for people trying to actually earn, it should also include copy-trading guardrails, latency-aware alerts, stop-loss / max-loss controls, and a settlement/redeem workflow that verifies fills and claims winnings programmatically. The strongest feature asks to build around are: wallet following, Discord/Telegram-style real-time alerts, resolution-criteria parsing, historical data access, and a cleaner side-by-side arb scanner that warns when fees, spread, and fill risk erase the edge. If you ship one thing, ship a trustworthy “can I actually make money here?” dashboard that tells users when to trade, when to skip, and whether the strategy survives real execution.

**Working name:** Polymarket Edgewatch
**Tagline:** Wallet-signal alerts + net-edge arb scanning with risk/settlement guardrails.
**Main goal:** Help users find and execute Polymarket trades where net realized P&L stays positive after costs and resolution-risk.
**Target users:** Active retail Polymarket traders who follow KOL/KOL-wallet signals or try systematic scanning but lose money to resolution traps, copy-trading noise, and execution/risk mistakes.

**Main user result:** A short list of Polymarket markets where tracked wallet flows plus net-edge modeling indicate actionable entry, with guardrails and settlement verification.
**5-minute outcome:** User adds 1-3 wallets and selects a scan template, then receives an alert with net-edge score + resolution-risk flags and a ready-to-trade confirmation screen.
**What we solve first:** End-to-end workflow from wallet-follow signals → actionable scan/entry guardrails → post-trade realized P&L + settlement verification.
**Out of scope for MVP:**
- Full automated trading across all venues without user confirmation
- Advanced ML on-chain clustering at production scale
- Deep liquidation/dispute automation for every edge case

## 2. Why this is worth building
- Verdict: **LOW** (57/100)
- The partials show a very strong, repeated pattern: users are actively trying to earn on Polymarket, but most believe the platform’s edge is concentrated in speed, liquidity, information access, or insider-like flow rather than in generic retail skill. There are also many complaints about execution failures, withdrawal friction, unclear resolution rules, and misleading performance metrics, which all block reliable earning. The breadth of asks across wallet tracking, alerts, backtesting, copy trading, arbitrage, and settlement transparency suggests this is a persistent and high-intensity pain point rather than a niche gripe.

**Current pain:** Users manually discover signals (leaderboards/KOL wallets) and try to act fast, but they still need a way to know whether flow is actionable and whether the strategy survives execution costs. They also want trust/safety and settlement clarity, not just “you won” outcomes.
**Current workaround:** Follow KOL/leaderboards manually, then run a script that alerts only when math aligns. For security, users look for suspicious-login and withdrawal/2FA prompts, but generic tools don’t close the loop.
**Why existing tools fail:** Wallet-tracking tools are often visibility-only, while trading hinges on net-edge after fees/slippage, resolution-criteria risk, and post-trade attribution. Cross-venue arbitrage and “terminal” research can ignore execution lag and net P&L, leaving users unsure whether the opportunity is actually tradable.

## 3. Must-have capabilities
### 3.1 Wallet watcher with profitability scoring
**Why:** Users explicitly asked for a good wallet analyser, wallet-following tools, and ways to find winning traders while filtering out wallets worth following.

### 3.2 Automatic alerts when tracked wallets open new positions
**Why:** Real-time alerts are needed so users can react before price moves and not manually babysit charts.

### 3.3 Live whale-flow detection with smart-money versus retail-FOMO classification
**Why:** The corpus repeatedly asks for a way to distinguish smart money from retail noise and to rank clustered suspicious purchases.

### 3.4 Cross-venue market comparison and arb scanner for Polymarket vs Kalshi
**Why:** Users want automatic analysis across both venues, but only when fees, spread, liquidity, and execution lag still leave real edge.

### 3.5 Resolution-criteria parsing and rule-risk warnings before entry
**Why:** Users want to inspect exact resolution criteria and auto-read the fine print to avoid bad bets and dispute surprises.

### 3.6 Backtesting and post-trade analysis based on realized net P&L
**Why:** Users asked for P&L that shows net edge, strategy backtesting, and a workflow that explains why trades failed rather than just whether they won.

### 3.7 Execution guardrails including stop-loss, max-loss, sizing, timing, and rebalancing controls
**Why:** The requested automation layer includes sizing, timing, rebalancing, and mandatory stop-loss behavior to prevent copy-trading blowups.

### 3.8 Settlement and redemption workflow with auto-redemption plus audit/ledger verification
**Why:** Users want programmatic verification of fills, settlement, and winnings claims, plus audit logs and export consistency.

### 3.9 Security and account-status alerts for logins, withdrawals, holds, and confirmations
**Why:** Security transparency was a direct must-have: suspicious login alerts, withdrawal confirmation emails, 2FA prompts, and account hold visibility.

### 3.10 High-density sortable/searchable market scanner with clean UI
**Why:** Users asked for a lightweight, responsive, information-dense tool that can scan many markets and quickly isolate the few worth trading.

## 4. Use cases & user stories
Web SaaS dashboard that (1) watches selected Polymarket wallets, (2) classifies smart-money vs retail-FOMO signals, (3) scans and ranks Polymarket markets using net-edge logic (liquidity/spread/fees/resolution criteria), and (4) verifies settlement/redemption with an auditable ledger. MVP focuses on Polymarket-first; cross-venue arb and copy-trading automation are guarded and partially manual init

### Use cases
**4.1 A retail trader follows a smart wallet into a live market**
A user opens the dashboard and sees a live alert that a tracked wallet with a strong profitability score has just bought into a fast-moving market. The system shows the wallet’s prior performance, whether the trade looks like informed flow or retail copy-trading bait, and how stale the signal is. Before entering, the user checks the market’s resolution criteria, sees the spread and slippage estimate, and uses the built-in stop-loss/max-loss controls to decide whether the edge survives execution.

**4.2 A trader scans Polymarket and Kalshi for only executable edge**
The user runs the cross-venue scanner over hundreds of contracts and gets a short list of markets where price gaps still remain after fees, liquidity, and fill risk are modeled. The system compares Polymarket and Kalshi side by side, flags rule-risk traps, and ranks only the markets that still show positive expected value on realized net P&L assumptions. After the trade resolves, the workflow verifies settlement, auto-redeems winnings, and records the outcome for post-trade analysis.

### User stories
- **As a Small-account Polymarket trader**, I want to be alerted the moment a profitable tracked wallet opens a position, *so that* I can decide fast enough to follow or skip before the market moves away
- **As a Execution-conscious prediction market trader**, I want to see net P&L, slippage, fees, and resolution-risk warnings before I place a trade, *so that* I only enter markets where the strategy still works after real-world execution costs

## 5. Pages & form factor
**Form factor:** Web SaaS dashboard with optional Chrome extension companion
**Why:** Reddit evidence repeatedly frames the need for “set-and-forget” monitoring, scanning/filtering, and a wallet analysis UI—best served by a web app. A browser extension can later surface quick context on Polymarket pages, but core value comes from continuous background detection, scoring, history, and risk/settlement workflows.

### Pages
**5.1 Dashboard**
Daily landing page — show confluence alerts, tracked-wallet events, and scan/exec status so users don’t babysit markets.
Key elements:
- Live Alerts Feed (smart-money vs FOMO classified)
- Tracked Wallets Activity Summary (counts + newest events)
- Whale-Flow Detection Status (last run, reliability, last failure)
- Net Edge / Realized P&L widget (primary metric view)
- Resolution Risk / Rule-Risk quick warnings

**5.2 Wallet Watch**
Manage wallet watchlists and inspect wallet trades with profitability scoring and alert configuration.
Key elements:
- Wallet List with Filters (category, size thresholds, smart-money score)
- Wallet Trade Timeline (entries/exits by market)
- Profitability Score / Insider Suspicion Score view
- Per-wallet Alert Toggles (new position, fill events, auto-liquidation signals)
- Wallet History Export link

**5.3 Strategy Builder**
No-code (or low-code) strategy builder for entry criteria, timing, sizing, and confluence rules (stop-loss, risk gating, regime tags).
Key elements:
- Strategy Templates (e.g., ORB breakout style)
- Rule Canvas (entry filters, confirmation rules, volume/momentum constraints)
- Risk Controls Panel (stop-loss, max-loss, sizing, session limits)
- Regime Tagging toggles (enable/disable strategies by regime)
- Cross-System Consensus weighting sliders (confluence rules)

**5.4 Market Scanner & Arb**
Scan/filter Polymarket contracts, rank “few markets that actually matter,” and surface cross-venue comparisons (Polymarket vs Kalshi) and arb opportunities.
Key elements:
- Contract Scan Filters (sports vs non-sports, size, liquidity proxies)
- Ranked Markets List (importance/edge scoring, “only the markets that matter”)
- Cross-Venue Price Comparison table (Polymarket vs Kalshi)
- Arb Scanner panel with execution feasibility warnings (fees/slippage)
- Resolution Criteria Preview

**5.5 Execution Console**
Preview and execute trades with guardrails (stop-loss, max-loss, sizing, timing, and safe auto-actions).
Key elements:
- Pre-Trade Checklist (rule-risk scanner + resolution criteria parse)
- Order Plan Builder (side/size/timing + liquidation behavior on fill)
- Auto-Liquidation on Fill toggle (if strategy requires neutrality)
- Risk Budget Meter (max-loss per session/trade)
- Execution Error Inbox (e.g., 403/region issues) and remediation hints

**5.6 Strategy Runs & Post-Trade Analysis**
Analyze realized net P&L, explain why a trade failed, and provide a workflow to refine strategies based on outcomes.
Key elements:
- Net Edge / Realized P&L dashboard (net of fees/slippage)
- Trade Failure Explanation timeline (what rule failed, data mismatch, timing)
- Reconciliation view (expected vs realized, resolution traps flags)
- Backtesting vs Live comparison charts
- Session Journal (manual vs automated actions)

**5.7 Settlement & Redemption**
Guided settlement/redeem workflow with verification, auto-redemption, and audit/ledger confirmation to build trust.
Key elements:
- Settlement Queue (markets awaiting redeem)
- Auto-Redemption Controls (with review step and confirm buttons)
- Audit/Verification Ledger panel (what was redeemed and when)
- Dispute filing/notes link (when relevant)
- “Withdraw confidence” status (security events + required confirmations)

**5.8 Security & Notifications**
Account trust/safety center: suspicious logins, withdrawal confirmations, and 2FA prompts so users can act/withdraw safely.
Key elements:
- Suspicious Login Alerts panel
- 2FA requirement prompts (withdrawals/logins)
- Withdrawal confirmation email status
- Security Events Timeline (login, auth changes, redemption/withdrawal)
- Proxy wallet creation controls (1-click creation)

### Key functions
- **Classify and alert smart-money vs retail FOMO** *[on: Dashboard]*
  - Trigger: Wallet watcher detects new positions from tracked wallets that match configured trade-size/timing thresholds
  - Push a confluence alert with classification labels (smart-money vs noisy FOMO), plus the specific rule signals that triggered.
- **Add wallet to watchlist** *[on: Wallet Watch]*
  - Trigger: User clicks “Add Wallet” and submits an address
  - Create a tracked-wallet profile with per-wallet filters and event alerting on new positions and fills.
- **Rank tracked wallets with an insider/suspicion score** *[on: Wallet Watch]*
  - Trigger: User opens a wallet profile or adjusts wallet ranking filters
  - Compute and display an “insider score” based on trade size, timing, and impact to help users focus on the few best signals.
- **Configure alerts for new positions** *[on: Wallet Watch]*
  - Trigger: User toggles alert settings per wallet (position opened, fill detected, threshold met)
  - Enable push notifications for tracked wallets only when events match conditions (reduces chart babysitting).
- **Build an ORB breakout strategy template** *[on: Strategy Builder]*
  - Trigger: User selects template “5-Minute Opening Range Breakout”
  - Generate a pre-wired strategy with breakout timing and confirmation rules that users can tune for their risk/market universe.
- **Add volume + momentum confirmation rule** *[on: Strategy Builder]*
  - Trigger: User selects “Confirmation” in the rule canvas
  - Require both volume threshold and momentum confirmation before entry to reduce FOMO entries and improve signal quality.
- **Enable stress-gated parameter updates** *[on: Strategy Builder]*
  - Trigger: User sets a “stress level” threshold in strategy settings
  - During high-stress regimes, the product increases mutation thresholds and blocks unsafe parameter changes.
- **Tag strategy with market regimes and auto-disable outside regimes** *[on: Strategy Builder]*
  - Trigger: User sets regime labels and allowed operating windows
  - Ensure strategies only execute in regimes where they were validated, preventing edge decay from regime mismatch.
- **Run Polymarket contract scan and rank top “few markets”** *[on: Market Scanner & Arb]*
  - Trigger: User clicks “Scan” or sets an auto-scan schedule
  - Automatically filter hundreds of contracts and produce a ranked list of the few markets with actionable edge.
- **Inspect exact resolution criteria before entering** *[on: Market Scanner & Arb]*
  - Trigger: User clicks “Resolution Criteria” from a market row
  - Parse and display exact resolution rules, plus associated rule-risk warnings, before any order is placed.
- **Execute order with net edge guardrails** *[on: Execution Console]*
  - Trigger: User clicks “Execute” after reviewing risk checklist
  - Place orders only when net edge and risk limits pass, and show the trade plan with stop-loss/max-loss controls.
- **Auto-sell immediately on LP fill (auto-liquidation option)** *[on: Execution Console]*
  - Trigger: LP order fill event is detected
  - If strategy requires neutrality, immediately place the sell leg to reduce exposure drift.
- **Explain why a trade failed (post-trade workflow)** *[on: Strategy Runs & Post-Trade Analysis]*
  - Trigger: User opens a completed/failed trade from history
  - Provide a structured explanation of which rule/data/timing constraint caused the failure and what to adjust next.
- **Export full Polymarket trade/position history** *[on: Strategy Runs & Post-Trade Analysis]*
  - Trigger: User clicks “Export history”
  - Download clean, complete trades and positions so users can audit outcomes and calculate session-level net P&L.
- **Request/dispute resolution flow assistance** *[on: Settlement & Redemption]*
  - Trigger: User selects a resolved market that requires dispute filing actions
  - Provide a clearer dispute filing workflow with step-by-step guidance so users can respond to resolution events.
- **Send/verify suspicious login alerts and 2FA prompts** *[on: Security & Notifications]*
  - Trigger: Security event occurs (suspicious login, withdrawal/login attempt) or user changes security settings
  - Alert users to suspicious logins, enforce 2FA prompts on withdrawals/logins, and show security event status.

### UX details
- **Alerts feed ordering:** Sort alerts by confluence strength (rule match completeness) and recency so users act on the highest-signal events first.
- **Chart-free operation:** Default to push/alert-driven monitoring with a minimized “market babysitting” UI; charts are secondary drill-downs.
- **Wallet ranking UI:** Always show the numeric “insider score” next to wallet names to make ranking understandable at a glance.
- **Market list filtering:** Include quick filters like “non-sports” and a trade size threshold to cut noise and spotlight high-impact flow.
- **Pre-trade resolution safety:** Block/soft-block execution until resolution criteria preview is acknowledged when rule-risk is detected.
- **Risk controls defaults:** Make hard stop-loss mandatory by default for strategies that place automated orders (disable execution if missing).
- **Execution plan on LP fill:** Provide an explicit “auto-liquidate on fill” toggle with a clear label and confirmation step to avoid surprise sells.
- **Discovery shortcuts:** Offer a leaderboard-based discovery shortcut for wallet following to avoid manual navigation through “pm -> more -> leaderboard”.

## 6. Monetization
**Model:** (unspecified)

## 7. Competitors to beat
| Name | Why it fails | Price | Mentions |
|---|---|---|---|
| Pregame.com for line research | Used as a research tool, but commenters still worry about line movement and whether the book price makes the strategy unprofitable. | free research tool mentioned; no price stated | - |
| PolyApex | The posts are promotional launch posts only; this chunk does not contain any user feedback validating effectiveness, so no clear reason is given for failure beyond being another trading/copy-trading product in a crowded space. | - | - |
| Cross-venue arbitrage between Kalshi and Polymarket | Harder than it sounds because execution lag, liquidity differences, and bridge/path limitations can erase edge; one user notes the market may already move before you can act. | Not mentioned | - |
| Cross-venue arbitrage between Polymarket and Kalshi | Users imply it exists but is constrained by fees, liquidity, and differing venue quirks. | not mentioned | - |
| DraftKings 2-team 6-point teasers | Commenters say the price is too high at -135 or -160, making it a hard pass or no longer viable. | -135 / -160 | - |
| kreo | Mentioned as useful for tracking and following smart money moves as they happen, but the comment implies it is an alternative when users need real-time action rather than post-hoc analysis. | not stated | - |
| Pinnacle | Only mentioned as a benchmark alternative for a tennis model; the post asks whether to switch, implying uncertainty about whether it is the right benchmark, but no explicit failure is stated. | - | - |
| Referral cashback / fee rebate campaign via Discord | Users may see it as scammy/risky; it also depends on trust in a third-party Discord and on an assumed future airdrop/referral reward. | 30% cashback on their fees; returns 100% of the fees received daily | - |

## 8. Distribution
- Top subreddits to launch in: r/Daytrading, r/investing, r/Polymarket, r/CryptoCurrency, r/Polymarket_news, r/wallstreetbets, r/Polymarket_Traders, r/sportsbook, r/polymarketAnalysis, r/PredictionsMarkets

## 9. Users & roles
**Primary persona:** Retail Polymarket trader
**Secondary personas:**
- Risk-aware automated trader (strategy user)
- Security-conscious trader (account trust focus)

**Roles:**
- **Trader** — Create watchlists, configure alerts/guardrails, run scans, preview/submit trades, and verify settlement.
- **Read-only analyst** — View wallet analytics, backtests, and scan results; cannot execute trades.

## 10. Data model & integrations
- (no data model extracted)

## 11. States
**Empty state:** User sees an onboarding screen to add wallets, choose scan template, and enable alerts.
**Error state:** User sees a red banner with the failed step (scan, parse, alert, or settlement verification) and next actions.

## 12. Analytics & metrics
- (not synthesized for this report)

## 13. Risks & open questions
- (no risks/questions extracted)

## 14. Post-launch
- See https://gapforapp.com/reports/retail-cant-reliably-earn-on-polymarket for DM-able hot leads (workarounds × buying intent).
- See https://gapforapp.com/reports/retail-cant-reliably-earn-on-polymarket for verified key quotes you can use as landing copy.

## 15. Suggested build order (3-week MVP cut)
- Week 1: §3 must-haves + §5 page 1.
- Week 2: §5 remaining pages + auth/persistence if needed.
- Week 3: §6 monetization wiring + analytics + launch checklist.

## 16. Setup hints (your stack overrides these)
- `pnpm create next-app . --typescript --tailwind --app`
- `npx shadcn@latest init`
- The agent SHOULD ask the user before committing to a stack.

## 17. How to use this file
You're an AI coding agent reading this in AGENTS.md. Your job:
1. Confirm the stack with the user (their preferences override this file).
2. Scaffold an MVP covering §3 + §5 page-1 first.
3. Defer §6 (monetization) and §14 (post-launch) until §3 ships and works.
4. Re-fetch the live PRD anytime via:
   curl https://painfinder-api.fly.dev/api/public/reports/retail-cant-reliably-earn-on-polymarket/export.json?size=compact

## 18. Verbatim key quotes (top 10)
> "84.1% of participants were unprofitable."  
> — Profitability & edge, post #9281

> "The wallets making serious money are concentrated around arbitrage, market making, and execution speed."  
> — Profitability & edge, post #9281

> "Polymarket was created as a loophole for insider trading."  
> — Insider trading, post #9282

> "It's an online casino."  
> — Gambling & addiction, post #9282

> "Polymarket bettors threatened to kill a journalist over a $14M war bet."  
> — Gambling & addiction, post #9288

> "This is why we can’t have nice freedoms"  
> — Gambling & addiction, post #9288

> "made about $40k on top of my salary."  
> — Profitability & edge, post #9306

> "i wish someone grabbed me by the shoulders 2 years ago."  
> — Uncategorized, post #9306

> "if you can't shut it off at 5pm, you are going to lose things that are worth way more than your account balance."  
> — Risk management, post #9306

> "Risk management is everything."  
> — Risk management, post #9799

## 19. Manual workarounds users cobble together (top 15)
- (none extracted yet — see live report)

## 20. "I would pay for…" quotes (top 10)
- (none extracted yet — see live report)

## 21. Hot leads summary
- (none extracted yet — see live report)

## 22. Full competitor list (top 10)
| Name | Why it fails | Price | Mentions |
|---|---|---|---|
| Pregame.com for line research | Used as a research tool, but commenters still worry about line movement and whether the book price makes the strategy unprofitable. | free research tool mentioned; no price stated | - |
| PolyApex | The posts are promotional launch posts only; this chunk does not contain any user feedback validating effectiveness, so no clear reason is given for failure beyond being another trading/copy-trading product in a crowded space. | - | - |
| Cross-venue arbitrage between Kalshi and Polymarket | Harder than it sounds because execution lag, liquidity differences, and bridge/path limitations can erase edge; one user notes the market may already move before you can act. | Not mentioned | - |
| Cross-venue arbitrage between Polymarket and Kalshi | Users imply it exists but is constrained by fees, liquidity, and differing venue quirks. | not mentioned | - |
| DraftKings 2-team 6-point teasers | Commenters say the price is too high at -135 or -160, making it a hard pass or no longer viable. | -135 / -160 | - |
| kreo | Mentioned as useful for tracking and following smart money moves as they happen, but the comment implies it is an alternative when users need real-time action rather than post-hoc analysis. | not stated | - |
| Pinnacle | Only mentioned as a benchmark alternative for a tennis model; the post asks whether to switch, implying uncertainty about whether it is the right benchmark, but no explicit failure is stated. | - | - |
| Referral cashback / fee rebate campaign via Discord | Users may see it as scammy/risky; it also depends on trust in a third-party Discord and on an assumed future airdrop/referral reward. | 30% cashback on their fees; returns 100% of the fees received daily | - |
| Support chat / email support | Users report generic replies, silence, and no useful escalation path for withdrawals or security incidents. | - | - |
| TradeTheOutcome probability calibration / scenario analysis content | Used as a rigorous reference point, but the post says the author is looking for feedback rather than claiming it solves everything; another post suggests such analysis may still need validation from serious traders. | not stated | - |

## 23. Where this conversation lives (top subreddits)
- r/Daytrading (70 posts)
- r/investing (68 posts)
- r/Polymarket (65 posts)
- r/CryptoCurrency (59 posts)
- r/Polymarket_news (57 posts)
- r/wallstreetbets (49 posts)
- r/Polymarket_Traders (48 posts)
- r/sportsbook (39 posts)
- r/polymarketAnalysis (39 posts)
- r/PredictionsMarkets (12 posts)