CompeteIQ is a system I designed and built end-to-end — from PRD to a running production pipeline — that monitors competitors on a cadence, synthesizes what changed using Claude, and keeps a living artifact current with a human always in the loop.
A quick note on what this is: it isn't a slick battlecard for GTM teams — though they're welcome to reference what's inside it. The primary audience is the product team, and the real point is showing how I, as a product leader, use AI to design and build a workflow solution instead of just asking for one. What follows walks through both the process of building it and the system itself. Total time to build: less than a day.
Every product team agrees competitive awareness matters. Almost none of them have a reliable system for it — just a Google Doc someone updated once, three quarters ago.
CompeteIQ is a recreation of a problem I lived in a previous role. Not every company has a dedicated competitive intelligence team, or budget for an off-the-shelf tool — mine didn't. Keeping up with competitive movement was already a struggle for a product team with actual product work to do. It got harder when we expanded into new markets: new markets meant new competitors, and the ad hoc approach we'd been getting away with stopped being good enough.
Product teams struggle to maintain consistent visibility into competitive movement. Competitive reviews are time-consuming, inconsistently executed, and typically reactive rather than proactive. By the time a team synthesizes a competitor update, the signal is stale and the window for action has narrowed.
I've owned those documents. In the worst cases, maybe they're updated once or twice a year — during annual planning, or when building a business case. Usually requiring a massive overhaul from a blank slate. They're irrelevant within days. The worst is hearing about competitor news a month late.
Manual Googling, ad hoc Slack shares, or an analyst tool that still dumps the synthesis work back on you.
Not the research — the upkeep. Someone has to remember to check five sources, every cycle, forever, with no reminder when it slips.
No living record of current competitor state — so every review starts from zero instead of from "here's what changed."
The build is the least interesting part of this story. The decisions underneath it are the part that's actually PM work — so before the architecture, here's how I got there.
The PRD isn't pictured as a finished document — it went through three full rewrites before a single ticket existed. Each pass cut ambiguity that would otherwise have turned into back-and-forth during the build.
The system needed a source of truth for which competitors to track. Building an admin UI would have taken a sprint nobody asked for.
It's tempting to jump straight to "detect changes." But you can't detect a change against nothing — the baseline had to ship first, even though it felt like just setup work.
An AI that silently rewrites a shared doc is a system nobody trusts for long. Every signal needed a person to say yes before it became permanent.
Weekly runs produced too little real movement per digest and started training people to skim past the email. Bi-weekly gave each run enough signal to be worth five minutes.
Claude was a thought partner through all of it, not just a code generator — scoping the PRD, stress-testing the weekly-vs-bi-weekly cadence call, arguing through whether the artifact belonged in Drive or a purpose-built repo (Drive won: competitive intel dies the moment it lives somewhere people don't already look), and reasoning through what "human-in-the-loop" should actually gate. The decisions above are mine — but I made better ones faster with a collaborator who'd push back.
Config lives in Sheets. Orchestration and scraping run in Apps Script. Zapier is the scheduler. Claude does synthesis, scoring, and baseline generation. Gmail is the interface. Drive is the system of record.
Real screenshots and a real recording from the running system — not mockups. As I built the Apps Script pipeline, I tested at every step along the way, in the execution log, before trusting it to run unattended.
Up to ten competitors, five URLs each, in a Sheet. Adding or dropping a competitor is a row edit — no deploy, no ticket to me.
A scheduled trigger kicks off the pipeline every other Monday, reads the config, and hands rows to the pipeline step by step — no server to babysit. The same Zap can also be triggered ad hoc, so I'm not locked into the cadence when something — a launch, a board prep, a rumor — means I need fresher signal sooner.
Apps Script pulls each competitor's site, blog, careers page, G2 and Capterra profiles, then hands the raw pull to Claude alongside the existing artifact — asking it to find what's actually new.
Every signal is scored for relevance and grouped by competitor. No login, no tool to check — it shows up where product teams already work: their inbox.
Accept writes the signal straight into the competitor's artifact in Drive. Reject logs it to a feedback sheet instead of just disappearing — so the system has a record of what didn't matter, too.
Not a demo environment — the real output from a real run.
Accepting one signal from the digest above updates the News & Trends section of Applause's artifact automatically — timestamped and attributed to its source.