Recruiterflow
Staking the AI-native ATS claim in editorial while shipping nothing visible.
A side-by-side editorial comparison of Act and Phorest — release velocity, themes, recent moves, and the top alternatives to consider.
Act! pivots from CRM-only to payment processor while modernizing its Cloud UX.
Act! is in the middle of a methodical Cloud modernization, rebuilding list views, navigation, and notifications to match the consistency users expect from modern CRMs. Alongside that polish work, Act! has just shipped Act! Payments via Propelr — turning the CRM into a place where credit card transactions close, not just leads. The product is still recognizably a small-business CRM, but its surface area is widening.
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.
Act! is in the middle of a methodical Cloud modernization, rebuilding list views, navigation, and notifications to match the consistency users expect from modern CRMs. Alongside that polish work, Act! has just shipped Act! Payments via Propelr — turning the CRM into a place where credit card transactions close, not just leads. The product is still recognizably a small-business CRM, but its surface area is widening.
The release cadence shows two parallel tracks: weekly UX rationalization (notification center, list parity, faster task editing) and category expansion through embedded financial services. Act! is following the same playbook HubSpot and Pipedrive have run — keep the legacy users happy with quality-of-life work while quietly bolting on revenue-bearing features that compete with Stripe-adjacent SMB tools. Payments is the most directional move in years.
Expect deeper payments integration next — recurring billing tied to opportunities, dunning workflows from the contact record, and likely a payments-driven pricing tier that monetizes transaction volume rather than seats.
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 Act 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.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Act is currently shipping more aggressively (velocity 6.3 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. Act is currently shipping more aggressively (velocity 6.3 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 Act alternatives in CRM are ranked by recent ship velocity. Browse the "Act alternatives" section above for the current picks, or visit /alternatives/act 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.