# Making money on Polymarket is structurally hard
> Source report: https://gapforapp.com/reports/making-money-on-polymarket-is-structurally-hard

## 1. What we're building
A Polymarket profit assistant focused on identifying exploitable edges: live wallet tracking, liquidity/fee-aware setup filtering, market-mispricing alerts, and a backtesting layer that simulates latency and slippage before users place bets. It should help users avoid thin books, low-EV markets, and misleading order-book walls, while surfacing only high-conviction opportunities backed by public data. Ideally it would support both manual traders and lightweight automation, with clear risk controls and performance attribution.

**Working name:** Polymarket Edge Desk
**Tagline:** Profit-assist dashboard: wallet follow + EV/liquidity filtering + latency/slippage backtests.
**Main goal:** Users reliably get a short list of higher-conviction Polymarket opportunities with simulated execution realism and clear reasons to act.
**Target users:** Solo and active traders who want an EV-first workflow for Polymarket without building data pipelines.

**Main user result:** In one session, the user receives actionable Polymarket opportunities that pass liquidity/fee-aware filtering and survive a latency/slippage backtest.
**5-minute outcome:** Connect wallets (or choose a tracked wallet), view fresh high-conviction alerts, and open a market detail page with execution-risk and why-it-was-recommended.
**What we solve first:** Filter out thin/expensive and stale setups, then validate remaining candidates using latency+slippage backtesting and an execution-risk score.
**Out of scope for MVP:**
- Direct order placement via trade execution (no trading wallet integration in MVP)
- Full portfolio P&L reconciliation across all wallets and transfers
- Trading strategy research beyond alerting/backtesting (e.g., autonomous bot)

## 2. Why this is worth building
- Verdict: **LOW** (42/100)
- There is strong evidence of a real pain point: users want to earn on Polymarket, but most reports point to loss-heavy outcomes, weak intuition, or dependence on technical edges. The corpus repeatedly mentions bots, whale tracking, arbitrage, and insider-like information as the paths to profit, which implies the opportunity is not in generic “tips” but in tooling. The market looks attractive because the need is clear and repeated, but the product must be sophisticated to survive fees, latency, and false signals. That makes it a strong opportunity, especially for analytics or automation.

**Current pain:** Retail traders repeatedly encounter opportunities that look good at a glance but collapse once liquidity, fees, and realistic execution timing are considered. They also receive signals that go stale, making recommendations misleading.
**Current workaround:** Users manually inspect markets/order books and rely on intuition or late information, then only realize execution/liquidity issues after losses. Some attempt automation but overfit to unrealistic fill assumptions.
**Why existing tools fail:** General assistants and non-Polymarket trading tools don’t model Polymarket-specific execution realism (latency + slippage) and market microstructure traps. Users report slow/poor outcomes when using generic reasoning or advice for Polymarket-style bets.

## 3. Must-have capabilities
### 3.1 Market mispricing alerting (public-data derived)
**Why:** Users need a way to detect exploitable mispricing rather than betting blindly in hard-to-earn environments.

### 3.2 Liquidity + fee-aware setup filtering (avoid thin books)
**Why:** Structural difficulty implies many bets are suppressed by thin liquidity and hidden cost/fee dynamics; filtering reduces bad trades.

### 3.3 Backtesting layer with latency and slippage simulation
**Why:** A common failure mode in automated/assisted approaches is unrealistic execution assumptions; backtests must simulate what actually happens.

### 3.4 Execution-risk scoring before users place bets
**Why:** Users need a clear risk/quality score to decide when an alert is actionable versus likely to fail.

### 3.5 Order-book wall / depth interpretation for misleading liquidity cues
**Why:** Users can be misled by apparent walls; depth-aware parsing avoids false confidence.

### 3.6 Live wallet tracking for actionable timing (whale-follow workflow)
**Why:** Profit assistance should include live wallet tracking so users can react to new positions quickly when it matters.

### 3.7 Alert freshness / staleness indicator (age of signal)
**Why:** Slow results were called out explicitly; users need to know whether a signal is still timely.

### 3.8 Performance attribution (why this trade was recommended)
**Why:** To avoid repeated bad cycles, users need to understand whether recommendations worked due to edge vs. luck.

## 4. Use cases & user stories
A web SaaS dashboard that ingests public mispricing/microstructure signals, filters out low-EV thin-book traps, simulates execution with latency and slippage, and generates wallet-follow alerts. It explains recommendations with freshness, liquidity/fee context, order-book depth interpretation, and performance attribution to help users learn what works.

### Use cases
**4.1 Trader filters out thin/expensive markets before betting**
A retail trader opens the dashboard and receives a handful of candidate bets. Each candidate includes a liquidity/fee-aware EV check plus a warning if the order book looks thin or execution would likely slip. The trader skips low-confidence markets and only places bets where the simulated backtest (latency + slippage) indicates a reasonable chance of positive EV.

**4.2 Wallet-driven follow alerts with execution realism**
A user wants to follow a tracked wallet’s activity without waiting for intuition. The system flags when a watched wallet opens or increases a position and immediately shows whether that timing aligns with an edge after modeling latency and slippage. If the simulated execution erases the edge, the alert is downgraded to 'watch' instead of 'bet'.

### User stories
- **As a Solo Polymarket trader**, I want an always-on alert feed that only triggers when a market passes liquidity/fee-aware EV filters, *so that* I don’t waste money on bets that look good on the surface but fail after real-world execution.
- **As a Active day trader**, I want a backtest that models latency and slippage before I place a bet, *so that* I know whether the recommendation still holds when I’m late or when fills slip.

## 5. Pages & form factor
**Form factor:** Web SaaS profit-assistant dashboard
**Why:** A web SaaS enables deep, continuously updated market-data processing (order book/liquidity/fees, signal freshness, backtests) plus wallet-follow workflows that require reliable integration and state. It also matches the “profit-assist workflow” concept (alerting, filtering, execution-risk scoring) without forcing users into a constrained UI like an extension.

### Pages
**5.1 Dashboard**
Daily landing page showing only actionable alerts and filtered high-conviction setups.
Key elements:
- Hot alerts list (only higher-conviction markets)
- Signal freshness/staleness indicator
- Execution-risk summary (gating status)
- Backtest result snippet (expected edge + risk)
- Wallet-follow status (last sync / next poll)

**5.2 Alerts Center**
Inbox of detected mispricings with filtering controls and one-click drill-down.
Key elements:
- Alerts table (market, event, detected edge)
- Liquidity/fee-aware filter toggles
- Alert age slider / freshness filter
- Stale alert banner + auto-hide rule
- Drill-down button to Market Detail

**5.3 Market Detail**
Full explanation and trading justification for a single recommended market.
Key elements:
- Order book / depth interpretation (walls vs real liquidity)
- Latency + slippage simulation panel
- Execution-risk score breakdown (why blocked vs allowed)
- Backtest assumptions and confidence bands
- Performance attribution (why recommended)

**5.4 Wallet Follow**
Track actionable timing from selected wallet(s) and align recommendations with observed trades.
Key elements:
- Tracked wallets list
- Last observed trade time (and elapsed time)
- Whale-follow correlation hints for matching markets
- Sync status indicator
- Auto-create “timing window” recommendations

**5.5 Backtesting Lab**
Re-run and compare strategies with simulated execution costs to validate setups before action.
Key elements:
- Scenario builder (entry/exit rules, edge threshold)
- Latency model settings
- Slippage + fee model settings
- Result charts (P&L distribution / hit rate)
- Exportable backtest report

**5.6 Execution Risk Center**
User-facing gating controls explaining when the assistant will not recommend placing bets.
Key elements:
- Risk score meter with “Allowed / Review / Blocked”
- Liquidity thin-book warnings
- Spread/wall mitigation notes
- Freshness gating explanation
- Override requests (optional) with audit log

**5.7 Settings**
Configure wallet tracking, alert thresholds, data freshness limits, and notification routing.
Key elements:
- Wallet integration + refresh cadence
- Alert threshold preferences (edge, confidence, max risk)
- Freshness/staleness limits
- Notification routing (in-app; optional email/Discord later)
- Data sources & permissions status

### Key functions
- **Ingest Market Mispricing Alerts** *[on: Alerts Center]*
  - Trigger: New market-data snapshot arrives or user refreshes
  - Detects mispricing opportunities from public data, then tags each with freshness, liquidity, fee, and preliminary edge.
- **Filter Thin-Book Setups** *[on: Alerts Center]*
  - Trigger: User toggles liquidity/fee-aware filters or threshold presets
  - Automatically excludes markets likely to be low-EV due to thin books, adverse fees, or unreliable fills.
- **Show Alert Freshness Status** *[on: Dashboard]*
  - Trigger: Alert is rendered
  - Displays an age-of-signal indicator and visually de-emphasizes or hides stale signals.
- **Run Backtest With Latency Simulation** *[on: Market Detail]*
  - Trigger: User clicks “Run backtest” on a market card
  - Simulates execution delay and measures how much expected edge survives realistic timing and slippage.
- **Simulate Slippage and Fees** *[on: Backtesting Lab]*
  - Trigger: User clicks “Recompute” after adjusting model settings
  - Applies fee and slippage models to produce more truthful P&L and confidence outcomes.
- **Score Execution Risk Before Action** *[on: Execution Risk Center]*
  - Trigger: Market detail loads or model parameters change
  - Calculates an execution-risk score that explains whether the setup is safe to act on.
- **Interpret Order-Book Walls** *[on: Market Detail]*
  - Trigger: Order book depth data updates
  - Summarizes wall/depth structure to avoid misleading liquidity cues in low-liquidity markets.
- **Track Wallet Trades** *[on: Wallet Follow]*
  - Trigger: User sets up tracked wallets and presses “Sync now”
  - Continuously records observed wallet trade timing for later recommendation alignment.
- **Create Whale-Follow Timing Window** *[on: Wallet Follow]*
  - Trigger: A tracked wallet trade matches a recommended market
  - Suggests when to act based on the observed trade timing and configured alert freshness limits.
- **Explain Recommendation Attribution** *[on: Market Detail]*
  - Trigger: User opens a recommended market
  - Shows “why this trade was recommended” (key factors: liquidity, freshness, edge survival, execution risk).
- **Export Backtest Report** *[on: Backtesting Lab]*
  - Trigger: User clicks “Export PDF/CSV”
  - Exports the full assumptions + simulated outcomes for auditability and sharing.

### UX details
- **Alerts prioritization:** Default sort: highest conviction first using edge estimate × confidence × freshness, not by arrival time.
- **Staleness handling:** Auto-hide alerts whose freshness age exceeds the user-configured limit, with a “show archived” link.
- **Execution gating:** Require a clear “Allowed / Review / Blocked” status before users treat a setup as actionable.
- **Order book UI:** Highlight depth anomalies (walls vs real depth) with tooltips that explain why they may be misleading.
- **Backtest transparency:** Always display latency + slippage + fee assumptions inline above results (no “black box” mode).
- **Attribution:** In “Market Detail”, show a compact “Top drivers” panel that mirrors the scoring components used for the risk score.
- **Wallet follow alignment:** When a whale-follow timing window is created, pin it to the matching Market Detail view and display elapsed time since the trade.

## 6. Monetization
**Model:** subscription

### Suggested pricing tiers
**Starter** — $19/month — *Solo trader, just getting started*
- Watchlists + basic wallet tracking
- Liquidity/fee-aware filtering for alerts
- Backtest preview (latency + slippage)
- Email alerts

**Pro** — $49/month — *Active trader, multiple positions*
- Unlimited watchlists and advanced wallet triggers
- Profitability score + execution-risk scoring
- Deeper backtests with slippage profiles
- Discord alerts + priority support

**Team/Atlas** — $199/month — *Trading desk / small team*
- Team seats (5) and role-based access
- Whitelisting for tracked markets/wallets
- Performance attribution reports
- API access for lightweight automation

## 7. Competitors to beat
| Name | Why it fails | Price | Mentions |
|---|---|---|---|
| Xynth | Used to track clustered insider buyers and non-routine insider purchases on stocks, not Polymarket; no corpus evidence it solves Polymarket earnings specifically. | - | - |
| PutHouse.com | Built for covered calls and cash-secured puts on stocks, not Polymarket prediction markets. | - | - |
| Careerflow AI | Used for job applications and resume tweaking, unrelated to Polymarket income. | - | - |
| Claude | Users said it produced very slow or poor results on Polymarket-style bets, with losses needing multiple wins to recover and some calls being too fearful to take. | - | - |

## 8. Distribution
- reddit
- x_twitter
- discord
- seo
- Top subreddits to launch in: r/Polymarket, r/Daytrading, r/predictionmarkets, r/stocks, r/wallstreetbets, r/Options, r/algotrading, r/defi, r/CryptoCurrency, r/PillarLab

## 9. Users & roles
**Primary persona:** solo Polymarket trader
**Secondary personas:**
- active day trader
- lightweight automation user

**Roles:**
- **viewer-trader** — Can view alerts, run backtests, and configure wallet follows and alert thresholds.

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

## 11. States
**Empty state:** The Dashboard shows no alerts yet and prompts the user to add wallet(s) and set thresholds.
**Error state:** A banner shows the failing module (data ingest/backtest) and provides a retry button with last-known cached results.

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

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

## 14. Post-launch
- See https://gapforapp.com/reports/making-money-on-polymarket-is-structurally-hard for DM-able hot leads (workarounds × buying intent).
- See https://gapforapp.com/reports/making-money-on-polymarket-is-structurally-hard 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/making-money-on-polymarket-is-structurally-hard/export.json?size=compact

## 18. Verbatim key quotes (top 10)
> "84% of people on polymarket literally never make money"  
> — post #894

> "The wallets making serious money are concentrated around arb"  
> — post #807

> "I’ve used Claude for polymarket only for btc up/down 5 mins and managed to get 100$ out of 250$ that i put but every loss had to be compensated by 3/4 wins so it was a very slow rate."  
> — post #707

> "you haven’t accounted for others who miscount and publish the wrong info. Duh, 0% profit, -5k costs and 10k for excessive sunburn treatments. Next regarded idea."  
> — post #773

> "the 5-minute BTC market moves faster than any human can react to manually."  
> — post #1154

## 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)

## 23. Where this conversation lives (top subreddits)
- r/Polymarket (107 posts)
- r/Daytrading (68 posts)
- r/predictionmarkets (48 posts)
- r/stocks (46 posts)
- r/wallstreetbets (40 posts)
- r/Options (36 posts)
- r/algotrading (35 posts)
- r/defi (27 posts)
- r/CryptoCurrency (26 posts)
- r/PillarLab (20 posts)