Building a Competitor Pricing Monitor: A High-Signal Detection Engine

I built a competitor pricing monitor in 3 days, here’s how it actually works

Ahmed Errami developed a custom pricing monitor after losing a deal due to unannounced competitor price drops. The system utilizes a Next.js stack to classify changes and filter out cosmetic web noise.

Why This Matters

Generic page monitoring often fails in production because it alerts on every pixel change, including rotating banners and cookie notices. Effective competitive intelligence requires a classification engine that normalizes text to distinguish between cosmetic updates and high-signal shifts in pricing or features.

Key Insights

• Classification engine categorizes changes into PRICE_CHANGE, PLAN_CHANGE, or FEATURE_CHANGE to eliminate notification noise.
• Playwright with ‘networkidle’ and a 2-second delay is preferred over Puppeteer for scraping JS-heavy SPAs.
• Sequential processing with 3-second delays between monitors prevents rate-limiting and blocking from aggressive web servers.
• Baseline snapshots are compared against subsequent runs using a line-by-line text diff after stripping dates and social handles.
• Vercel cron workers execute the monitoring logic daily at 9am to ensure consistent data collection.

Practical Applications

• Use-case: Competitive Intelligence via sequential scraping to avoid anti-bot detection. Pitfall: Parallel scraping leads to rapid IP blocking.
• Use-case: Automated Sales Alerts using Resend for filtered PRICE_CHANGE events. Pitfall: Generic pixel diffing creates a ‘noise machine’ that users ignore.

References:

• https://dev.to/erramix01/i-built-a-competitor-pricing-monitor-in-3-days-heres-how-it-actually-works-1mg7
• https://priceblind.vercel.app/