Atlassian
Atlassian now sells both halves of agent work: the index agents read and the intent they execute.
A side-by-side editorial comparison of Aha! and Notion — release velocity, themes, recent moves, and the top alternatives to consider.
Aha! is threading one AI assistant through every product it owns, and giving it a screen of its own.
Elle, the AI assistant across Aha! software, now has a dedicated screen in My work with persistent chat history, and teams can encode their own standards as skills Elle applies automatically. Its reach keeps widening across artifacts: whiteboard diagrams convert directly into clickable prototypes, and design systems carry brand colors, typography, and components into prototypes in Aha! Roadmaps so generated concepts arrive in house style. User groups let a single handle stand in for a team across mentions, to-dos, and watchers. The feed also carries CEO essays and competitor comparison posts alongside the release notes.
Every release now lands on the agent: what triggers it, what it can reach, what it costs.
Since Notion 3.6 shipped External Agents, essentially the whole changelog has been agent infrastructure. Custom Agents gained a meeting-note trigger, calendar tools, and a one-click path to share docs into their context; Workers got usage tracking in the credits dashboard ahead of the beta ending; and the model picker now exposes scorecards for speed, intelligence and cost with a per-request effort dial. The one non-agent item in the window is high contrast mode.
Elle, the AI assistant across Aha! software, now has a dedicated screen in My work with persistent chat history, and teams can encode their own standards as skills Elle applies automatically. Its reach keeps widening across artifacts: whiteboard diagrams convert directly into clickable prototypes, and design systems carry brand colors, typography, and components into prototypes in Aha! Roadmaps so generated concepts arrive in house style. User groups let a single handle stand in for a team across mentions, to-dos, and watchers. The feed also carries CEO essays and competitor comparison posts alongside the release notes.
The assistant is being promoted from a feature inside screens to a surface those screens orbit. Skills were the structural move — they turn team expertise into instructions Elle follows on every task, which is what makes an assistant usable in an organization with standards rather than only by individuals. Everything since has widened what Elle can reach without changing that foundation: journeys on whiteboards, whiteboards into prototypes, prototypes into design-system output. The through-line is the handoff between artifacts, which is where product work usually stalls, and the MCP server earlier in the year opened the same data to outside agents.
Expect the artifact chain to keep closing — prototypes feeding back into requirements or releases — and Elle skills to spread into the remaining Aha! products. The dedicated Elle screen will accumulate more of the work surface.
Since Notion 3.6 shipped External Agents, essentially the whole changelog has been agent infrastructure. Custom Agents gained a meeting-note trigger, calendar tools, and a one-click path to share docs into their context; Workers got usage tracking in the credits dashboard ahead of the beta ending; and the model picker now exposes scorecards for speed, intelligence and cost with a per-request effort dial. The one non-agent item in the window is high contrast mode.
Notion is assembling the unglamorous half of an agent platform - triggers, permissions, connections, metering - rather than adding capabilities. The sequencing is deliberate: agents that can act on your calendar and fire off meeting notes need a permission model and a visible bill before anyone runs them on a team. Surfacing model cost and effort to the end user points the same way, pushing the spend decision down to whoever writes the prompt.
The Workers beta ending is the next dated event to watch, and pricing for it is the likeliest announcement; expect further agent triggers beyond meeting notes and more connected tool surfaces on the calendar pattern.
Other PM products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Aha! or Notion.
Atlassian now sells both halves of agent work: the index agents read and the intent they execute.
ProdPad publishes weekly product-leadership essays and no release notes at all.
Teamhood's feed is an SEO comparison engine aimed at teams leaving other tools.
NocoBase back-ports its DeepSeek work to the 2.2.0 line and makes email sync survive a restart
A numbered performance program surfaces between the automated CI tags
Hostaway builds out the direct-booking stack while tightening who sees what
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Aha! and Notion are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Aha! and Notion are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other PM products to evaluate alongside.
Top Aha! alternatives in PM are ranked by recent ship velocity. Browse the "Aha! alternatives" section above for the current picks, or visit /alternatives/aha for the full list with editorial commentary on each.
Top Notion alternatives in PM are ranked by recent ship velocity. Browse the "Notion alternatives" section above for the current picks, or visit /alternatives/notion for the full list with editorial commentary on each.