NetHunt CRM
NetHunt publishes CRM explainers on a steady cadence; the product stays off the feed
A side-by-side editorial comparison of Phorest and Twenty — release velocity, themes, recent moves, and the top alternatives to consider.
Phorest keeps shipping front-desk friction fixes, now reaching staff attendance on mobile.
Phorest is working through a queue of small, concrete improvements, most of them customer-requested and most landing in the Phorest Go mobile app. The newest adds geofenced clock in/out, drawing a boundary around a branch so staff can clock hours from their phones. Around it sit client search on the diary itself, sales transaction history in the mobile client card, voice-to-text notes, pop-up client notes at booking, and locally formatted phone numbers.
Twenty is spending its release cycles on auth hardening, not CRM features.
The last six releases are dominated by security and platform work: CVE-driven dependency bumps flagged by container image scanning, a migration of web auth off localStorage token pairs onto httpOnly cookie sessions, captcha and throttling on password reset, and per-user enforcement of OAuth application authorizations. Product-visible change is thin by comparison — an admin panel chat list and a handful of default-value corrections.
Phorest is working through a queue of small, concrete improvements, most of them customer-requested and most landing in the Phorest Go mobile app. The newest adds geofenced clock in/out, drawing a boundary around a branch so staff can clock hours from their phones. Around it sit client search on the diary itself, sales transaction history in the mobile client card, voice-to-text notes, pop-up client notes at booking, and locally formatted phone numbers.
Two directions run consistently through the window. Phorest Go is being brought toward parity with the desktop product, with transactions, notes, and now attendance all moving onto the phone, while the desktop diary is being made searchable rather than scannable. The roadmap is visibly vote-driven, with several entries thanking customers for votes on the idea. Geofencing is the first item here that governs staff behaviour rather than easing a task, which is a different kind of feature for this product.
Expect more desktop capabilities to land in Phorest Go, and expect geofencing to gain reporting or exception handling once salons hit the cases of staff clocking in just outside the boundary.
The last six releases are dominated by security and platform work: CVE-driven dependency bumps flagged by container image scanning, a migration of web auth off localStorage token pairs onto httpOnly cookie sessions, captcha and throttling on password reset, and per-user enforcement of OAuth application authorizations. Product-visible change is thin by comparison — an admin panel chat list and a handful of default-value corrections.
This is what a project looks like when it starts preparing for scrutiny it did not previously face. Moving session tokens out of JavaScript-reachable storage and recording OAuth grants per user are compliance-shaped changes, not feature work. Worth noting for anyone reading the cadence: the release train publishes each version twice, once under a twenty/ tag and once under sdk/, so the apparent volume is roughly double the actual release count.
The hardening streak points toward enterprise readiness — audit logging or SSO is the natural next item, given that per-user OAuth authorization and cookie-based sessions are already in place.
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 Phorest or Twenty.
NetHunt publishes CRM explainers on a steady cadence; the product stays off the feed
Recruiterflow's feed is a content-marketing engine, not a changelog
Cognism's feed carries a content-marketing engine, not a product changelog.
The tracked feed is agency marketing content, so Vendasta's actual shipping stays invisible here
Membrain's crawled feed is sales-methodology content marketing, not a product changelog.
Affinity is wiring deal data into outside AI tools while rebuilding its core list views.
See all Phorest alternatives → · See all Twenty alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Twenty is currently shipping more aggressively (velocity 7.5 vs 5.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 5.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 Phorest alternatives in CRM are ranked by recent ship velocity. Browse the "Phorest alternatives" section above for the current picks, or visit /alternatives/phorest 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.