DEV Community

Vhub Systems
Vhub Systems

Posted on

How to Detect When a Competitor Launches a New Feature Before Your Sales Team Notices

#javascript #webdev #productivity #tutorial

Your sales rep is halfway through a demo when the prospect asks: "Can your product do X? We heard [a competitor] just added that last month."

You had no idea.

It's one of the most deflating moments in B2B sales — and it's almost entirely preventable with a two-hour automation setup. This article shows you how to build it.

The Problem: Competitor Product Intelligence Has a Structural Gap

Most B2B SaaS teams have no real-time monitoring for competitor product changes. They rely on:

  • Sales reps to surface insights from customer conversations (reactive, weeks late)
  • Marketing team members to manually check competitor websites (inconsistent, unmaintained)
  • Paid competitive intelligence tools that often lag by days and cost $200–$500/month
  • Social media monitoring that misses silent changelog updates entirely

The result: your team learns about competitor feature launches from prospects, not from internal intelligence. By then, the deal may already be tilted.

The root cause isn't effort — it's structure. Competitor product pages, changelogs, and blogs change without notifying you. There's no RSS feed for competitor product decisions. No Slack integration that fires when a rival ships a major update. You have to pull that data — and almost nobody has a system to do it automatically.

Why Manual Monitoring Breaks Down

Let's be specific about where the gap is:

Changelog pages. Most SaaS companies maintain a changelog at /changelog or /releases. These pages are updated on irregular schedules — sometimes weekly, sometimes after a silent 6-week freeze followed by a burst of three major features. Nobody on your team checks this every week.

Product/feature pages. Feature landing pages quietly gain new sections, new capability descriptions, new comparison tables. A "Basic plan" quietly becomes "Starter + AI Assistant." You won't notice unless you're watching.

Blog posts. Feature launch announcements typically go out as blog posts first — before the feature even fully ships. A blog post titled "Introducing [Feature Category]" is often your earliest warning signal, and it's completely searchable.

SERP visibility. When a competitor is about to ship, they often start appearing in new search queries. Monitoring their brand name alongside product terms ("new feature," "launch," "update") gives you early signal before the blog post even ranks.

None of this is hidden. All of it is publicly accessible. The problem is that pulling and comparing it at scale requires infrastructure most teams don't have.

The Defense Pattern: Structured Change Detection

Here's the architecture that works:

  1. Extract — pull the full text content of competitor changelog pages, product pages, and blog post listings weekly
  2. Diff — compare today's content to last week's stored snapshot
  3. Alert — when new sections or new posts appear, fire a Slack message or email to your product/sales lead

The key insight is that you don't need to read competitor pages — you need to detect changes in them, and then have a human read only the changed sections. That's a five-minute weekly review instead of a 30-minute manual audit.

Implementation: Apify + JavaScript

Apify provides two actors that handle this well on a free tier:

  • apify/website-content-crawler — extracts clean text from any webpage, including JS-rendered content
  • lanky_quantifier/google-serp-scraper — runs Google searches and returns structured results

Here's a working Node.js implementation:

import { ApifyClient } from 'apify-client';
import * as fs from 'fs';
import * as crypto from 'crypto';

const client = new ApifyClient({ token: process.env.APIFY_API_TOKEN });

// Pages to monitor — add competitor changelogs, feature pages, blog indexes
const PAGES_TO_MONITOR = [
  'https://competitor-a.com/changelog',
  'https://competitor-a.com/features',
  'https://competitor-b.com/whats-new',
  'https://competitor-b.com/blog',
];

// SERP queries to monitor for launch signals
const SERP_QUERIES = [
  '"competitor-a" new feature 2024',
  '"competitor-a" launch announcement',
  '"competitor-b" product update',
];

async function extractPageContent(url) {
  const run = await client.actor('apify/website-content-crawler').call({
    startUrls: [{ url }],
    maxCrawlPages: 1,
    outputFormats: ['text'],
  });

  const { items } = await client.dataset(run.defaultDatasetId).listItems();
  return items[0]?.text || '';
}

async function checkSerpForLaunchSignals(query) {
  const run = await client.actor('lanky_quantifier/google-serp-scraper').call({
    queries: query,
    maxPagesPerQuery: 1,
    resultsPerPage: 10,
  });

  const { items } = await client.dataset(run.defaultDatasetId).listItems();
  return items.filter(r => r.position <= 5).map(r => ({
    title: r.title,
    url: r.url,
    snippet: r.snippet,
  }));
}

function hashContent(text) {
  return crypto.createHash('sha256').update(text).digest('hex');
}

function loadSnapshot() {
  if (fs.existsSync('./competitor-snapshot.json')) {
    return JSON.parse(fs.readFileSync('./competitor-snapshot.json', 'utf-8'));
  }
  return {};
}

function saveSnapshot(snapshot) {
  fs.writeFileSync('./competitor-snapshot.json', JSON.stringify(snapshot, null, 2));
}

async function runMonitor() {
  const snapshot = loadSnapshot();
  const changes = [];
  const newSnapshot = {};

  // Check competitor pages for content changes
  for (const url of PAGES_TO_MONITOR) {
    console.log(`Checking: ${url}`);
    const content = await extractPageContent(url);
    const hash = hashContent(content);
    newSnapshot[url] = { hash, checkedAt: new Date().toISOString() };

    if (snapshot[url] && snapshot[url].hash !== hash) {
      changes.push({
        type: 'PAGE_CHANGED',
        url,
        message: `Content changed on ${url}`,
      });
    }
  }

  // Check SERP for launch signals
  for (const query of SERP_QUERIES) {
    const results = await checkSerpForLaunchSignals(query);
    const topResult = results[0];
    if (topResult) {
      const key = `serp:${query}`;
      const topUrl = topResult.url;
      newSnapshot[key] = { topUrl, checkedAt: new Date().toISOString() };

      if (snapshot[key] && snapshot[key].topUrl !== topUrl) {
        changes.push({
          type: 'SERP_CHANGED',
          query,
          newTop: topResult,
          message: `New top result for query: "${query}"`,
        });
      }
    }
  }

  saveSnapshot(newSnapshot);

  if (changes.length > 0) {
    console.log('\n🚨 COMPETITOR CHANGES DETECTED:');
    changes.forEach(c => console.log(`  - ${c.message}`));
    await sendAlert(changes);
  } else {
    console.log('\n✅ No changes detected this week.');
  }
}

async function sendAlert(changes) {
  const webhookUrl = process.env.SLACK_WEBHOOK_URL;
  if (!webhookUrl) return;

  const text = changes.map(c => `• *${c.type}*: ${c.message}`).join('\n');
  await fetch(webhookUrl, {
    method: 'POST',
    headers: { 'Content-Type': 'application/json' },
    body: JSON.stringify({
      text: `🔍 *Competitor Intelligence Alert*\n\n${text}\n\nReview manually and route to product/sales.`,
    }),
  });
}

runMonitor().catch(console.error);
Enter fullscreen mode Exit fullscreen mode

Scheduling the Monitor

Run this weekly using Apify's built-in scheduler or a cron job:

# cron entry — runs every Monday at 8am
0 8 * * 1 cd /your/project && node monitor.js >> /var/log/competitor-monitor.log 2>&1
Enter fullscreen mode Exit fullscreen mode

Or schedule it directly in the Apify console as a recurring Task — no server required.

What to Monitor

Start with these page types for maximum signal density:

Page Type Why It Matters
/changelog or /releases Direct feature shipping signal
/features or /product Quiet capability expansions
/blog (index page) First announcement vehicle
SERP: "brand" + "new" + "feature" Pre-launch SEO positioning
SERP: "brand" + "vs" + "your-brand" Comparison page updates

Three to five competitors, four to six pages each — that's 15–30 monitored URLs. Apify's free tier handles this easily.

Cost

Apify free tier: $5/month credit, renewing monthly. A weekly run monitoring 20–30 URLs via website-content-crawler costs roughly $0.10–$0.30 per run. You'll stay within free tier limits.

The alternative cost: One lost deal to a competitor feature you didn't know existed can be worth $5,000–$50,000 in ARR. The monitoring pays for itself the first time it fires.

What You Actually Get

The system fires when something changes. A human then spends five minutes reading the changed section and deciding whether to act. That's the design — automated detection, human judgment on significance.

No more learning about competitor launches from prospects. No more scrambling to prepare objection handling the day before a major demo. Your sales team gets early warning. Your product team gets signal on what your market values enough to ship.

The gap between "reactive" and "proactive" competitive intelligence is two hours of setup time and $0 in monthly cost.

This tutorial uses Apify actors available at apify.com. The website-content-crawler and google-serp-scraper actors are free-tier compatible. No API key required for the Apify free plan — create an account and you're ready to run.

Top comments (0)