Build a competitor changelog so you stop being surprised

The problem with how most founders track competitors

The usual flow: a customer mentions a competitor's new feature, you spend an hour scrambling to figure out what it does, you feel behind, you do nothing different in your roadmap, you forget within a week. Six weeks later, the same thing happens with a different feature.

This is reactive. It's expensive (hours of unplanned work) and useless (no compounding insight).

The competitor changelog system

For each top-3 competitor, maintain a single Brain node that's a running changelog. Update it weekly. 15 minutes total per week.

The weekly drill (15 min)

For each competitor:

1. Their changelog/blog/release notes — 5 min. If they don't publish one, check their website footer for "what's new" or scan their X account for product announcements.
2. Their pricing page — 1 min. Has anything changed? Tier names? Feature gates? "Contact us" threshold?
3. Their job listings — 4 min. New roles tell you what they're investing in. A burst of "Enterprise AE" listings = they're moving upmarket. New "ML engineer" role = they're shipping AI features. New "Solutions Architect" = enterprise deals are stalling on integration.
4. One competitor mention in customer convos this week — 5 min. What did the customer say about them? Are they being praised, dismissed, or compared? Capture the exact quote.

What to save in the Brain node

## <Date>

**Released:** <feature/announcement>
**Implied:** <what this tells you about their bet>
**Hiring:** <new roles + what they imply>
**Customer signal:** <quote + context>
**Your read:** <one sentence on how this affects your strategy>

Why this compounds

After 6 weeks, your competitor brain_node is a 6-entry timeline of their actual moves. Patterns emerge that no individual data point reveals:

• They've hired 4 enterprise AEs in 6 weeks → they're going upmarket
• Their last 3 features all involved API/webhooks → they're building toward platform positioning
• Customer mentions shifted from "cheaper" to "more reliable" → their messaging has matured

These patterns become citations Cameron can pull when you're building strategy: "Notable that this is exactly the moment Competitor X moved upmarket — your brain_node has the exact week they posted the AE roles."

The discipline

Calendar it. Weekly recurring 15 minutes. No exceptions. The compounding only works if it's consistent. Three weeks of skipped logging defeats the whole system.