Recruiterflow
Staking the AI-native ATS claim in editorial while shipping nothing visible.
A side-by-side editorial comparison of ERPNext and Phorest — release velocity, themes, recent moves, and the top alternatives to consider.
Two ERPNext lines ship minutes apart: v16 takes the features, v15 takes the same fixes
ERPNext maintains two release lines in parallel and publishes them within minutes of each other — v16.x carries features, v15.x carries backported fixes, frequently as paired PR numbers for an identical change. The last two weeks delivered an optional customer overdue-limit block on Sales Invoice submission, accounting entries for stock-related expenses, partial Pick List transfers, and a faster data source behind the General Ledger, Trial Balance, Balance Sheet and Profit and Loss reports. The notes are LLM-summarized from commits and say so at the bottom of each release.
Phorest lets salons price the stylist, not just the service
Two back-of-house releases landed the same day. Staff pricing can now be set per individual staff member per service, replacing a model where variation came only from branch price or staff category, and it carries through to booking, checkout and online. Alongside it, everything a staff member is qualified for — service, service time, development time, finish time — collapses into one table instead of several screens. Brand creation also stops requiring a support ticket.
ERPNext maintains two release lines in parallel and publishes them within minutes of each other — v16.x carries features, v15.x carries backported fixes, frequently as paired PR numbers for an identical change. The last two weeks delivered an optional customer overdue-limit block on Sales Invoice submission, accounting entries for stock-related expenses, partial Pick List transfers, and a faster data source behind the General Ledger, Trial Balance, Balance Sheet and Profit and Loss reports. The notes are LLM-summarized from commits and say so at the bottom of each release.
No new direction is visible here; this is an ERP working through the long tail of accounting correctness and warehouse edge cases — variant BOM selection, double-counted stock on same-timestamp cancellations, weekly auto-reposting of incorrect valuation entries, a revised country chart of accounts. The pattern worth tracking is the dual-line discipline itself: v15 keeps receiving fixes on the same day v16 receives features, which says the installed base has not moved and the project plans to carry both for some time.
The cadence should hold — a paired v15/v16 drop roughly weekly, features on 16 and fixes mirrored onto 15. Nothing in these entries signals a major-version push or a change in how long v15 will be supported.
Two back-of-house releases landed the same day. Staff pricing can now be set per individual staff member per service, replacing a model where variation came only from branch price or staff category, and it carries through to booking, checkout and online. Alongside it, everything a staff member is qualified for — service, service time, development time, finish time — collapses into one table instead of several screens. Brand creation also stops requiring a support ticket.
The recent run is consistently about removing steps from daily front-desk and manager work: clock-in by geofence, client lookup on the diary, transactions on the client card, voice notes, and now self-serve brands and consolidated staff setup. The direction is deepening the operational core rather than expanding into new surfaces like marketing or payments.
With pricing now granular to the individual staff member, the pressure moves to reporting — expect the analytics side to gain per-staff revenue views that make the new pricing dimension readable.
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 ERPNext or Phorest.
Staking the AI-native ATS claim in editorial while shipping nothing visible.
Twenty's ORM v2 migration is down to permission and repository edge cases
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.
NetHunt's feed is evaluation-stage SEO content, with no product releases visible in it.
See all ERPNext alternatives → · See all Phorest alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. ERPNext and Phorest are shipping at a similar cadence (velocity 5.0 vs 5.0, 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. ERPNext and Phorest are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other CRM products to evaluate alongside.
Top ERPNext alternatives in CRM are ranked by recent ship velocity. Browse the "ERPNext alternatives" section above for the current picks, or visit /alternatives/erpnext for the full list with editorial commentary on each.
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.