INT-06 · SEC. 09 Competitive Intelligence

Competitor Changelog Strategy Read

Classify six months of a competitor's changelog to see where they're headed before they announce it.

FORMAT: prompt
DIFFICULTY: beginner
TIME: 10 min
TOOLS: universal
MODELS: any
COPIES: 0 so far

When to use this

A competitor ships constantly and you only ever see one release note at a time, so every entry looks random. Six months of entries classified in one pass shows the direction. Use before roadmap planning or a strategy review, not as a weekly habit.

The pattern

Pastes as plain text

Visit the changelog or release notes page of the competitor I name at the bottom of this prompt. Read the last 6 months of entries, or the last 30 entries, whichever is more. Default to 6 months unless I say otherwise.

Classify every entry into exactly one bucket:
- CORE: deepens the existing product for existing users
- EXPAND: opens a new use case, market, or user type
- ENTERPRISE: compliance, permissions, SSO, audit, admin controls
- CATCH-UP: something the rest of the category already had
- MAINTENANCE: fixes, performance, infrastructure

Then:
1. Show the bucket counts, and the trend: compare the first 3 months against the last 3. A shift in mix is the signal (e.g. ENTERPRISE going from 10% to 40% of entries means they're moving upmarket).
2. Name the 2-3 entries that don't fit their current public positioning. Off-positioning releases are usually the first public evidence of a strategy change.
3. In three sentences, state where they're most likely headed over the next two quarters and which of my customer segments that puts at risk. Mark this as inference, not fact.

Competitor changelog URL:

Real example output

41 entries over 6 months. Counts: CORE 16, MAINTENANCE 10, ENTERPRISE 9, EXPAND 4, CATCH-UP 2.

Trend: ENTERPRISE went from 2 of 20 entries in the first 3 months to 7 of 21 in the last 3. EXPAND is flat.

Off-positioning entries: "HIPAA compliance toolkit" (they market to marketing teams, not healthcare), "Audit log export API" and "EU data residency," both shipped in the last 6 weeks.

Inference: they're building toward regulated, larger accounts; expect an enterprise tier or a repackaging within two quarters. At risk: my 50-200 seat fintech customers, who are mine today mostly because this competitor lacked compliance features.

Why it works

One release note is noise; the mix over time is strategy. Forcing a single bucket per entry and comparing early months against late months turns a changelog into a measurable trend, and the off-positioning entries are where companies leak their next move before any announcement.