Phorest
Phorest lets salons price the stylist, not just the service
A side-by-side editorial comparison of CRM-service and Twenty — release velocity, themes, recent moves, and the top alternatives to consider.
A steady, unflashy CRM grinding out monthly quality-of-life features across campaigns and billing.
This CRM ships disciplined monthly release notes, each a bundle of incremental feature and workflow improvements rather than headline launches. Recent work centers on campaign logic (AND/OR condition groups, relative date conditions), record management (inline related-entity editing, duplicate merging), and billing automation (invoice payment status).
Twenty's ORM v2 migration is down to permission and repository edge cases
The two newest tags are single-line fixes on the ORM v2 rewrite: an orphaned mirrored-field permission blocking relation field updates, and findAndCount missing from the ORM v2 workspace repository. They follow the same-day cluster pattern this feed always shows, where the version tag carries a one-line title and the substance sits in the referenced PR.
This CRM ships disciplined monthly release notes, each a bundle of incremental feature and workflow improvements rather than headline launches. Recent work centers on campaign logic (AND/OR condition groups, relative date conditions), record management (inline related-entity editing, duplicate merging), and billing automation (invoice payment status).
The product is maturing along predictable CRM lines: richer segmentation and campaign conditions, less context-switching in the record view, and automation of routine back-office tasks like invoicing and deduplication. There is no directional pivot here — it is consistent breadth-filling that closes gaps against larger CRMs one month at a time.
Expect continued campaign-logic depth and record-management convenience features, with more billing and data-hygiene automation following the invoice-status and duplicate-merge work.
The two newest tags are single-line fixes on the ORM v2 rewrite: an orphaned mirrored-field permission blocking relation field updates, and findAndCount missing from the ORM v2 workspace repository. They follow the same-day cluster pattern this feed always shows, where the version tag carries a one-line title and the substance sits in the referenced PR.
Nearly every tag in this window traces back to the ORM v2 migration — relation-keyed where clauses, quoted aliases, dropped validator specs, repository methods being backfilled as callers hit them. That is the signature of a rewrite in its long tail: the shape is settled and what remains is discovering which methods and permission paths were missed.
On this pattern the ORM v2 fixes keep arriving one missing method or permission path at a time until the callers stop finding gaps; no new feature surface is visible in the release stream.
Other CRM 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 CRM-service or Twenty.
Phorest lets salons price the stylist, not just the service
Woodpecker's public feed is an SEO content engine, not a changelog.
A daily SEO blog pitching AI service lines to agencies, with no product releases in it.
Two weeks after the platform relaunch, Thryv's feed is all demand generation for it.
Staking the AI-native ATS claim in editorial while shipping nothing visible.
NetHunt's feed is evaluation-stage SEO content, with no product releases visible in it.
See all CRM-service alternatives → · See all Twenty alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — crm — within CRM. Twenty is currently shipping more aggressively (velocity 7.5 vs 0.0), with 0 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. Twenty is currently shipping more aggressively (velocity 7.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other CRM products to evaluate alongside.
Top CRM-service alternatives in CRM are ranked by recent ship velocity. Browse the "CRM-service alternatives" section above for the current picks, or visit /alternatives/crm-service for the full list with editorial commentary on each.
Top Twenty alternatives in CRM are ranked by recent ship velocity. Browse the "Twenty alternatives" section above for the current picks, or visit /alternatives/twenty for the full list with editorial commentary on each.