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 Asana — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Bonsai | Asana |
|---|---|---|
| Sector | PM | PM, Collab |
| Velocity score | 6.3 | 6.3 |
| Sparks · 30d | 1 | 1 |
| Top themes | crm, proposals, mcp, agency-tools | ai-teammates, agentic-automation, ai-studio, rules-engine |
| Last editorial update | 1d ago | 13h 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.
AI Teammates get a skills library while the core work surface quietly gets fixed.
Asana is shipping on two tracks at once. The agentic track is moving fast: AI Teammates gained a Skills Library of specialized capabilities, then the ability to read, create, and update project rules with a review step before publishing, while AI Studio began critiquing the rule instructions users write. The second track is long-overdue core work — threaded task comments went live, Notes was rebuilt and renamed Pages, and subtask view controls landed in the task pane.
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.
Asana is shipping on two tracks at once. The agentic track is moving fast: AI Teammates gained a Skills Library of specialized capabilities, then the ability to read, create, and update project rules with a review step before publishing, while AI Studio began critiquing the rule instructions users write. The second track is long-overdue core work — threaded task comments went live, Notes was rebuilt and renamed Pages, and subtask view controls landed in the task pane.
The AI Teammates architecture is becoming composable rather than monolithic: start from a role-shaped teammate, attach skills, then let it operate on the automation layer itself. That last step matters — an agent that writes and edits rules is acting on the system that runs the work, not just on tasks inside it, and Asana has consistently gated it behind human review. Meanwhile the base product is closing gaps that predate any of this, which suggests the AI work is not consuming the whole roadmap.
Expect the Skills Library to open to customer-authored or third-party skills, and expect the review step on agent-generated rules to become the template for wider write access.
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 Asana.
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.
Everhour's public feed is a keyword operation; the product itself says nothing.
Aha! is removing the objections to letting product managers ship working software.
See all Bonsai alternatives → · See all Asana alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Bonsai and Asana 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 Asana 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 Asana alternatives in PM are ranked by recent ship velocity. Browse the "Asana alternatives" section above for the current picks, or visit /alternatives/asana for the full list with editorial commentary on each.