Tracecat
After a mandatory Action Gateway, the RC train is back to hardening the sandbox
A side-by-side editorial comparison of Bonsai and Resource Guru — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Bonsai | Resource Guru |
|---|---|---|
| Sector | PM | PM |
| Velocity score | 5.0 | 6.3 |
| Sparks · 30d | 0 | 1 |
| Top themes | crm, notes, email-sync, api | resource-scheduling, mcp, custom-fields, integrations |
| Last editorial update | 1h ago | 4d ago |
| Website | — | Visit → |
Bonsai is assembling a real CRM underneath the freelancer billing tools
Bonsai's recent work is system-of-record plumbing: a Notes section spanning contacts, companies and projects, an activity feed per company, and Gmail/Microsoft sync that files email and calendar events against the right record. Alongside it sit a self-serve API key and an MCP connector. Billing is no longer the centre of gravity.
An MCP server opens the schedule to AI tools; custom fields become the organizing spine.
Resource Guru ships small, frequent changes to its scheduling surface rather than large releases. The recent product updates cluster on two fronts: custom fields graduating from stored metadata into a way of organizing the Schedule and Projects views, and a widening set of intake integrations, with Trello and ClickUp both landing in the last six weeks. On July 30 it added an MCP server that lets AI tools query account data in plain English. The same feed carries SEO articles on capacity planning and software reviews, which are marketing output rather than product movement.
Bonsai's recent work is system-of-record plumbing: a Notes section spanning contacts, companies and projects, an activity feed per company, and Gmail/Microsoft sync that files email and calendar events against the right record. Alongside it sit a self-serve API key and an MCP connector. Billing is no longer the centre of gravity.
The pieces landing are the ones a CRM needs before it can be trusted as the single place client history lives — cross-record linking, per-object permissions, automatic contact capture. The API and MCP connector point the same data outward, reachable from outside the app. Documents was rebuilt on that footing, folding proposals and contracts into one editor.
Expect the per-object permissions introduced with Notes to spread to the other record types, and the API surface to widen now that a key can be generated self-serve.
Resource Guru ships small, frequent changes to its scheduling surface rather than large releases. The recent product updates cluster on two fronts: custom fields graduating from stored metadata into a way of organizing the Schedule and Projects views, and a widening set of intake integrations, with Trello and ClickUp both landing in the last six weeks. On July 30 it added an MCP server that lets AI tools query account data in plain English. The same feed carries SEO articles on capacity planning and software reviews, which are marketing output rather than product movement.
The custom-field work is compounding: colour-coding bookings by field value and choosing and reordering Projects columns are the same idea applied to two different views, which points to custom fields becoming the primary axis teams slice schedules by. Integrations are being treated as intake pipes rather than parity features, converting Trello cards and ClickUp tasks into bookings and positioning Resource Guru as the scheduling layer underneath other teams' task tools instead of a replacement for them. The MCP server extends that posture from writing data in to reading it back out, moving the account data outside the product's own interface.
The most likely next step is MCP moving from querying to acting, letting an assistant create or amend bookings rather than only report on them, alongside custom fields reaching the remaining views and reporting. The entries describe the server only in terms of getting insights out, so whether write access is planned is not visible here.
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 Resource Guru.
After a mandatory Action Gateway, the RC train is back to hardening the sandbox
The changelog turned into a how-to blog — capability news now arrives disguised as tutorials.
Governance and cross-workspace plumbing, not new AI surface
Two release lines, weekly tags, and not one line of release notes in the feed.
Elle stops being Aha's assistant and becomes where teams encode their own standards.
Every surface is being rebuilt around agents, and the shareholder letter says it is paying.
See all Bonsai alternatives → · See all Resource Guru alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — mcp — within PM. Resource Guru is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 editorial sparks in the last 30 days against 0. 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. Resource Guru is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 editorial sparks in the last 30 days against 0. 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 Resource Guru alternatives in PM are ranked by recent ship velocity. Browse the "Resource Guru alternatives" section above for the current picks, or visit /alternatives/resourceguru for the full list with editorial commentary on each.