1
2 Comments

I built a tiny SaaS to stop manually checking competitor pricing pages — here’s what I learned so far.

Hey everyone 👋

I’ve been building a small SaaS project recently after realizing how much time I was wasting manually checking competitor pricing pages.

Every time I worked on pricing or positioning, I’d find myself opening 4-5 competitor pages, taking screenshots of tiers, spilling notes into a doc... and then doing the whole thing again a week later because, of course, everything was already stale.

So I built a tiny MVP to solve my own problem:

You input a competitor URL → it watches the page → emails you when something changes.

No accounts, no dashboards – just notifications.

A few things I’ve learned early on building this:

• The tricky part isn’t detecting changes – it’s figuring out what changes are actually important.
• Most founders don’t bother tracking competitors on a regular basis; it’s usually a wake-up call after sales calls.
• Simpler workflows look more attractive than feature-rich dashboards (at least for now).

Currently, I’m trying to answer one question:

Do founders actually care about continuous monitoring, or is it more about occasional “don’t blindside me” notifications?

If you’ve ever had to track competitors before, I’d love to hear:

How do you currently stay on top of competitor changes?

on February 27, 2026
  1. 1

    Your "the hard part isn't detecting changes, it's deciding which ones matter" line matches exactly what I hit. Most of my diffs were CSS class churn and rotating banner copy, not real pricing moves — hashing only the pricing table region killed more noise than any smarter diff algorithm did.

    On your question: in my sampling founders don't want a live dashboard, they want a "don't blindside me" ping, and they go looking for it after a lost deal, not on a weekly cadence.

    I ended up shipping just the thin hash + diff layer as an actor on the Apify Store (search changepulse there — IH won't let me post links yet), for people who want schedule + metering without owning scrape ops.

    When you ran those 3 pricing pages, what shape were the false positives — layout churn, or real copy edits that just didn't matter?

  2. 1

    Quick update:
    I ran this against 3 real pricing pages this week and noticed something interesting — feature bundle changes are much rarer than pricing changes, but potentially more impactful.

    Still refining what should count as “high-signal.”