Ever Teams
Ten tagged releases in a fortnight, and not one of them changed the product.
A side-by-side editorial comparison of Bonsai and Aha! — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Bonsai | Aha! |
|---|---|---|
| Sector | PM | PM |
| Velocity score | 6.3 | 6.3 |
| Sparks · 30d | 1 | 1 |
| Top themes | crm, proposals, mcp, agency-tools | ai-app-builder, product-management, governance, prototyping |
| Last editorial update | 23h ago | 14h ago |
| Website | — | Visit → |
Bonsai is rebuilding itself as a CRM, and the freelancer toolkit is now the back end.
Five months of releases point the same direction: a CRM data model that separates contacts from clients and allows many-to-many links, activity feeds at both contact and company level, custom views, Zoom and now Gmail and Microsoft email and calendar sync. On top of that, Bonsai shipped an MCP connector in June and a ground-up Documents builder in July that handles proposals, contracts, signatures, pricing, and packaging in a single drag-and-drop file. Cadence is roughly monthly with substantial releases each time.
Aha! is removing the objections to letting product managers ship working software.
Aha! Builder carries most of the release weight right now: AI-coded applications with built-in authentication, role-based permissions, virtual user testing, and now a design system so generated prototypes inherit company brand. The core roadmap product still gets steady editing and documentation work, including find and replace, bulk attachment actions, and a sidebar table of contents. Essays on how to evaluate AI productivity fill the gaps between releases.
Five months of releases point the same direction: a CRM data model that separates contacts from clients and allows many-to-many links, activity feeds at both contact and company level, custom views, Zoom and now Gmail and Microsoft email and calendar sync. On top of that, Bonsai shipped an MCP connector in June and a ground-up Documents builder in July that handles proposals, contracts, signatures, pricing, and packaging in a single drag-and-drop file. Cadence is roughly monthly with substantial releases each time.
Bonsai started as invoicing and contracts for solo operators and is assembling the relationship layer that sits above them — every interaction with a client captured in one timeline, then acted on from the same place. Documents and email sync are the two pieces that make Bonsai viable as the only tool an agency opens, rather than the one it exports from. The MCP connector suggests they expect that layer to be queried by an assistant as often as by a person.
The likely next step is connecting the new pieces to each other — sending Documents from a deal in the CRM, or having the MCP connector draft a proposal the way it already drafts invoices — plus pipeline reporting built on the activity data now being captured.
Aha! Builder carries most of the release weight right now: AI-coded applications with built-in authentication, role-based permissions, virtual user testing, and now a design system so generated prototypes inherit company brand. The core roadmap product still gets steady editing and documentation work, including find and replace, bulk attachment actions, and a sidebar table of contents. Essays on how to evaluate AI productivity fill the gaps between releases.
The Builder feature order reads like a checklist for making PM-built software survive contact with IT: authentication first, then permissions, then security review, then testing, now brand consistency. Aha! is arguing that the person who writes the requirements should also produce the working artifact, and it is closing the standard objections one at a time. The MCP server earlier in this arc points the same way, turning roadmap data into something other tools and agents act on.
The unaddressed part of that checklist is deployment and lifecycle: where these applications run, who supports them, and how they are retired. Expect the next Builder releases to deal with hosting or handoff to engineering rather than more authoring features.
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 Bonsai or Aha!.
Ten tagged releases in a fortnight, and not one of them changed the product.
Unito publishes migration and integration guides, not releases — the feed is pure demand-gen.
Tracecat is handing its agents the workflow engine, then hardening everything around them.
RentRedi is growing past rent collection into portfolio reporting for multi-entity landlords.
AI Teammates get a skills library while the core work surface quietly gets fixed.
Everhour's public feed is a keyword operation; the product itself says nothing.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Bonsai and Aha! 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. Bonsai and Aha! 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 Bonsai alternatives in PM are ranked by recent ship velocity. Browse the "Bonsai alternatives" section above for the current picks, or visit /alternatives/bonsai for the full list with editorial commentary on each.
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.