AI can tell your team what changed, not just that a page moved.

Decide which sources are allowed to make a claim.

A social post can announce an experiment.

Documentation can describe a capability not yet available to all customers. A pricing page can change without a release note. Treating every source as equal makes the brief noisy.

Create a source hierarchy for each competitor. Strawberry can watch the official pages you name and keep the evidence attached when it finds a material change.

Show what changed before explaining why it matters.

“Competitor launched AI” is not actionable intelligence.

The team needs the old claim, new claim, scope, and apparent user. It also needs to know whether the feature is live, announced, or merely described.

Strawberry can prepare a concise change record rather than a stream of copied text. The product lead can then decide whether it matters to positioning, roadmap, enablement, or nothing at all.

Connect the feature claim to the market question your team has.

A feature matters differently to a sales team.

It also matters differently to a product manager and a customer success lead. The same update could affect a deal objection, an integration gap, a positioning page, or no active decision.

Ask Strawberry to map the verified change to the questions you already track. It should distinguish observation from interpretation and preserve the source for anyone who wants to check it.

Make the weekly brief short enough to be read.

A watchlist fails when it produces twenty minor alerts and no decisions.

Use a routine to prepare a weekly digest that prioritises new, material, and verified changes. Retain the full source log for deeper review.

Save the product-specific rules as a skill: competitors, sources, materiality threshold, and the questions each change must answer.

Frequently asked questions