Aha! vs Clarizen

Aha! publishes a steady run of concrete, narrow features across Roadmaps and Builder as one-line update posts, interleaved with occasional product-management essays. This window covers user groups for mentions and assignment, a design system for AI-generated apps, long-document handling, virtual user testing for prototypes, and user-defined skills for the Elle assistant. Aha! Builder, which turns plans into working applications, is absorbing most of the AI investment.

The arc is legible across three months: Aha! held the product data, then exposed it through an MCP server in May, then acted on it when Builder began generating applications in June, and now lets customers define how the assistant behaves. Skills make Elle configurable by the teams using it rather than only by Aha!, which repeats for the assistant what Builder did for applications. The Roadmaps side meanwhile keeps receiving unglamorous collaboration and document work, so the classic tool is not being starved while the AI half expands.

Skills are the obvious thing to extend next, most likely with sharing or governance controls, since Aha! sells to organizations that standardize process. On the Builder side, testing landed in July and deployment and handoff remain the visible gaps.