Twenty
Twenty's ORM v2 migration is down to permission and repository edge cases
A side-by-side editorial comparison of Folk and Phorest — release velocity, themes, recent moves, and the top alternatives to consider.
folk is unbundling its CRM into surfaces: an agent, a phone, and now an API.
folk spent April automating data upkeep inside the app, then spent three weeks in July adding three new ways to reach the same contact data: an MCP server, a native mobile app, and an Interactions API beta. The CRM workspace itself has changed little; what changed is who and what can address it. The changelog entries are one-line teasers with no release detail, so the depth of each launch is hard to verify from the feed alone.
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.
folk spent April automating data upkeep inside the app, then spent three weeks in July adding three new ways to reach the same contact data: an MCP server, a native mobile app, and an Interactions API beta. The CRM workspace itself has changed little; what changed is who and what can address it. The changelog entries are one-line teasers with no release detail, so the depth of each launch is hard to verify from the feed alone.
The pattern here is access, not features. MCP made the records agent-addressable, the mobile app made them capturable away from a desk, and the Interactions API opens the highest-value slice of the dataset to outside builders. folk is positioning itself as a contact graph that other tools read and write, rather than a destination app users are expected to sit in.
Expect the Interactions API to exit beta with pricing attached, and the mobile app to keep absorbing capture features the way the business card scanner did two weeks after launch.
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 Folk or Phorest.
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.
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 Folk 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. Folk is currently shipping more aggressively (velocity 8.8 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. Folk is currently shipping more aggressively (velocity 8.8 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 CRM products to evaluate alongside.
Top Folk alternatives in CRM are ranked by recent ship velocity. Browse the "Folk alternatives" section above for the current picks, or visit /alternatives/folk 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.