Chord vs June
Side-by-side trajectory, velocity, and editorial themes.
Chord is rebuilding Copilot on Anthropic models, Enriched Context, and a breaking SQL infra change.
Chord is a CDP that has spent the last quarter rebuilding its Copilot AI from the inside. The reasoning layer switched to Anthropic models, the context capture got expanded as Enriched Context, and the SQL generation pipeline took a breaking infrastructure change. Around that, the regular CDP work — Iterable data modeling, searchable tables, Activations sync redesign — continues at a steady release cadence.
Copilot is becoming the product. Each release this year has tied AI further into the CDP's core data plane — modeling, querying, activations — rather than treating it as a sidebar. Live documentation grounding and feedback memory in the latest release signal a push to keep Copilot accurate as the schema evolves underneath it.
Expect a deeper agentic move where Copilot proposes activations or builds segments end-to-end. The Iterable-style data modeling work hints at where AI assistance lands next.
June's last visible push was a tight May 2025 B2B sprint — Custom Objects, SQL traits, PostHog integration.
June is product analytics for B2B SaaS, and the only visible release activity in the input is a concentrated four-week sprint in May 2025: SQL computed traits, PostHog as a data source, increased computed-trait limits, and the GA of Custom Objects after a two-month rollout. Each release is paired with small fixes (Slack alerts, HubSpot reverse sync) suggesting a stable maintenance cadence around the headline launches.
The May 2025 batch is internally consistent: every release widens what June can model (Custom Objects), how flexibly customers can compute on it (SQL traits), or how easily it slots into existing data plumbing (PostHog source). All three target the B2B-SaaS persona that wants more than user/account analytics. After this burst the changelog goes quiet in the input — it's not clear from the entries alone whether the product moved to a slower cadence, switched publishing channels, or paused.
The entries don't support a confident prediction about what comes next. If publishing resumes from the same direction, the obvious extensions are deeper integrations with reverse-ETL or warehouse-native sources and richer pre-built health-score templates on top of SQL computed traits.
See more alternatives to Chord →
See more alternatives to June →