# Competitive Intelligence Digest

> Snapshots competitors' public pages and reports only what changed, ranked by what it changes for you — and says so when nothing did. Public sources only.

- Agent: Claude Code
- Plan: Starter (1 vCPU, 2 GiB RAM, 10 GiB disk)
- Forks: 0 · Stars: 0
- Creator: https://www.jurniti.com/creator-ca0ff2
- Tags: claude-code, competitive-intel, gtm, monitoring, research, sales
- Requires config (you provide): ANTHROPIC_API_KEY
- Skills: competitive-digest

**To fork:** open https://www.jurniti.com/templates/competitive-intelligence-digest and use the Fork action — it starts a Stripe Checkout for a new VM seeded with this template's persist disk (same flat plan price, no fork fee).

## README

# Nobody noticed the day their pricing page changed

Someone was assigned "keep an eye on the competition". They read three blog posts a
week and forward one to Slack. Meanwhile the only change that mattered to every open
deal went past unseen.

## The diff is the product, not the snapshot

Anyone can read a competitor's pricing page. The value is knowing **it changed on
Tuesday**.

So every source is snapshotted each run, and the digest reports **only what differs**,
with both dates and the URL. A first run has no diff — it says so plainly, because a
baseline narrated as news is manufactured significance.

## Ranked by what it changes for you

1. **Pricing or packaging** — hits every open deal today.
2. **A capability closing a gap you sell against** — your battle card line is now
   wrong, and it says *which line*.
3. **Positioning shift** — slow, but it changes who you're compared to.
4. **Hiring signal** — weakest tier, reported as directional only. *"Leaning into"*,
   never *"they will ship X"*. A job posting is not a roadmap.

A competitor's blog post is not news, and cosmetic diffs get dropped.

## Most weeks it says nothing changed

That's the correct answer, and it's why the digest is still being read in month three.
A weekly intel report that finds something every week is manufacturing it.

It also names what it checked and found **unchanged**, so silence is confirmed rather
than assumed.

## Public sources only — and the reason is practical

Pricing, docs, changelog, status, careers, public reviews. Never a logged-in view, a
trial account, a leaked screenshot, or something a customer shared in confidence.

Not squeamishness: **intelligence from a private source can't be repeated to a
prospect, cited in a deck, or defended.** It's worthless the moment it matters, and a
liability before that.

`robots.txt` checked first, one request per URL, and a blocked source **stays blocked**
and is reported as such.

## It prunes its own watchlist

If a URL hasn't changed in ten runs it says so and suggests dropping it. Watchlists
only ever grow unless something forces the question.

## What you supply

Your own Claude Code login. Nothing else — every source is a public page. List up to
five URLs per competitor.

## Where this stops

It watches and reports. It does not contact competitors, sign up for trials, or access
anything gated.

It won't state their revenue, churn, runway or customer count, won't infer roadmap from
hiring, won't explain *why* they made a change, and won't tell you a change is bad for
them.

Verified on build: the skill, the working tree, the `PUBLIC_SOURCES_ONLY` guard, the
diff-is-the-product rule, all four consequence tiers and the no-change rule are present
on a fresh fork. Running it on your own competitors is yours to do.