Price Tracking Browser Extension
The idea
A browser extension that tracks prices on products you view and alerts you when they drop, monetized through affiliate commissions.
Verdict: PASS 28/100
The core product is commoditized with entrenched competitors (Honey, Rakuten, CamelCamelCamel) who have scale, brand trust, and affiliate relationships locked in. A solo founder has no distribution advantage and would be competing on pure feature parity in a race-to-the-bottom affiliate model.
Tribe
casual online shoppers who want deal notifications (no specific niche identified)
Pain level: low
Price-drop alerts solve a real but weak pain — most shoppers either don't care about incremental savings, use existing free tools (Honey, Keepa), or check prices manually. The problem is solved, not underserved.
Market size
TAM: ~$10B affiliate marketing TAM globally, but price-alert segment is <5% of that (~$500M). Most value flows to retailers and affiliate networks, not tools.
Year-1 SOM: $0–50K year 1 as a solo founder. Affiliate commissions are thin (0.5–3%), require massive traffic to monetize, and you'd need 10K+ active users just to hit $500/month.
Strengths
- Price-drop alerts are a proven use case with clear demand signals (Honey has 20M+ users).
- Browser extensions have low friction to install and can track behavior passively.
- Affiliate networks are abundant and easy to onboard (Amazon Associates, Rakuten, etc.).
Risks
- SHOWSTOPPER: Honey (owned by PayPal) and Rakuten have 100x your distribution, brand trust, and affiliate relationships; they can outbid you on commissions and out-market you on reach. You'd be competing on feature parity against free incumbents with venture backing.
- Affiliate commission rates are declining industry-wide and retailers are investing in direct affiliate programs, squeezing third-party tools.
- User retention is brutal for browser extensions; most installs are abandoned within weeks, and you'd need 50K+ installs to hit $1K/month in commissions.
- Privacy regulations (GDPR, CCPA) and browser policy changes (third-party cookies, manifest v3) are eroding the extension playbook; you'd need to rebuild tracking infrastructure constantly.
Competitors
- Honey (PayPal-backed, 20M+ users, covers coupon + price-drop across 30K+ retailers)
- Rakuten (established affiliate network with browser extension, direct retailer relationships)
- CamelCamelCamel (specialized for Amazon price history, free, owned by Wikibuy/Connexity)
- Capital One Shopping (Discover-backed, price-drop + coupon alerts, embedded in browser)
- Unnamed: dozens of indie price-alert extensions with <10K users each, mostly abandoned
Moat
None. Feature parity is easy to replicate, affiliate networks are commoditized, and network effects are absent. The only moat would be a proprietary data source (e.g., exclusive retailer partnership) or a narrow niche (e.g., luxury watches only), neither of which is in the idea.
5 actions for this week
- Spend 2 hours researching Honey's and Rakuten's affiliate payouts, user acquisition cost, and retention curves on public sources and founder interviews — understand the unit economics you'd need to survive.
- Install and use Honey, CamelCamelCamel, and 3 other price-alert extensions for a week; document what they do, what breaks, and where the UX is bad — you need a wedge.
- Cold-email 5 affiliate network managers (Amazon, Rakuten, ShareASale) asking: would you prioritize a new price-alert extension over Honey? Document responses honestly.
- If you find a wedge (e.g., luxury goods, niche category, or a retailer with poor affiliate coverage), validate it with 10 cold outreach calls to that niche buyer — does the pain justify switching tools?
- If no wedge emerges by end of week, kill this and move to the next idea; this is a feature, not a business, and you'd be grinding on affiliate commissions for 12+ months with no path to $10K MRR.
Kill criteria
If 0 of 5 affiliate network managers express interest in prioritizing your extension over incumbents, OR if you cannot identify a specific niche (product category, geography, or user cohort) where existing tools have <50% market penetration, kill this by end of week. Do not build a generic price-drop extension; the game is over.
More idea teardowns
Run a free teardown on your own idea · Browse the teardown library