**Weekly competitive synthesis - 2026-06-20 to 2026-06-26**

**What changed**

The ledger captured 27 public signals. AI visibility is the dominant movement with 2 signals, followed by SEO/content movement (10) and pricing/packaging (0). The strongest source-backed signal is from Constructor: [Constructor baseline captured case_study](https://constructor.com/customers).

**Strategic pattern**

The pattern is named AI search packaging. Competitors are not just describing features; they are giving AI search and retrieval a marketable wrapper across MCP, agent, commerce reasoning, personalization, and product-discovery narratives. Treat this as a Product Marketing-led positioning problem first, then escalate to Product only where internal validation shows a real capability delta.

**Recommended actions by owner**

- **Sales Enablement:** Act on Customer Proof by validating whether [Constructor baseline captured case_study](https://constructor.com/customers) changes positioning, battlecards, roadmap questions, or partner enablement. Evidence summary: Constructor public case_study source was captured as a baseline for future diffs..
- **Product Marketing:** Act on AI Visibility by validating whether [Google Vertex AI Search baseline captured blog](https://cloud.google.com/blog/products/ai-machine-learning) changes positioning, battlecards, roadmap questions, or partner enablement. Evidence summary: Google Vertex AI Search public blog source was captured as a baseline for future diffs..
- **Product:** Act on Product Release by validating whether [Coveo baseline captured press](https://ir.coveo.com/en/news-events/press-releases) changes positioning, battlecards, roadmap questions, or partner enablement. Evidence summary: Coveo public press source was captured as a baseline for future diffs..
- **Competitive Intelligence:** Act on Customer Community Voice by validating whether [Community baseline captured forum](https://news.ycombinator.com) changes positioning, battlecards, roadmap questions, or partner enablement. Evidence summary: Community public forum source was captured as a baseline for future diffs..

**Battlecard updates**

- **Constructor:** [Constructor baseline captured case_study](https://constructor.com/customers) - Constructor public case_study source was captured as a baseline for future diffs.
- **Bloomreach:** [Bloomreach baseline captured case_study](https://www.bloomreach.com/en/customers) - Bloomreach public case_study source was captured as a baseline for future diffs.
- **Google Vertex AI Search:** [Google Vertex AI Search baseline captured blog](https://cloud.google.com/blog/products/ai-machine-learning) - Google Vertex AI Search public blog source was captured as a baseline for future diffs.
- **Coveo:** [Coveo baseline captured press](https://ir.coveo.com/en/news-events/press-releases) - Coveo public press source was captured as a baseline for future diffs.

**Coverage gaps**

This v1 run uses public sources only. It does not include Gong, Salesforce, Slack, G2 paid exports, Semrush API, or internal win/loss data.