DEV Community

ICE
ICE

Posted on

I Pivoted from 7 APIs to 1 Monitoring Tool — Here's Why

I built a website change monitoring tool over a weekend. Here's why it's more valuable than the 7 APIs I built before it.

The Mistake

I spent hours building 7 developer APIs — screenshots, PDFs, QR codes, email verification, the works. Beautiful landing pages, SDKs, documentation.

Zero paying users. Because screenshot APIs are a commodity. There are 20+ free alternatives.

The Pivot

Then I asked myself: what problem do people actually pay money to solve?

Answer: "Tell me when this webpage changes."

  • Visualping charges $14-199/mo for this
  • ChangeTower charges $29-249/mo
  • Distill.io charges $15-80/mo

People pay because change monitoring saves real time and catches real opportunities:

  • Competitor changed their pricing? You know first.
  • Dream job posted? You're first to apply.
  • Government page updated? You have documentation.
  • Product back in stock? You grab it.

What I Built

A simple API that lets you monitor any webpage:

# Create a monitor
curl -X POST https://api.16761.tech/monitors \
  -H "Authorization: Bearer YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "url": "https://competitor.com/pricing",
    "name": "Competitor Pricing",
    "frequency": "hourly",
    "email": "you@company.com"
  }'
Enter fullscreen mode Exit fullscreen mode

Every check:

  1. Takes a full-page screenshot
  2. Compares it pixel-by-pixel with the previous one
  3. If change > 0.5% (filters out rendering noise) → sends alert with screenshot

Pricing

Plan Monitors Frequency Price
Free 2 Daily $0
Pro 20 Hourly $9/mo
Business 100 15-min $29/mo

70%+ cheaper than alternatives.

Tech Stack

  • Playwright for real Chromium rendering
  • Node.js + Express
  • Pixel-diff comparison
  • Telegram alerts (email coming)
  • Cron-based worker

Try It

  1. Get a free key: api.16761.tech/signup
  2. Create a monitor
  3. Wait for changes

Landing page: 16761.tech/watch

Lesson Learned

Don't build tools looking for a problem. Find the problem first, then build the minimum tool that solves it.

7 APIs with zero revenue vs 1 monitoring tool with clear value prop. The pivot took 2 hours.

Questions? Comments below 👇

Top comments (0)