Wagepoint
Wagepoint put AI at the payroll approval gate, then spent a week arguing about where else it belongs.
A side-by-side editorial comparison of Lattice and Workable — release velocity, themes, recent moves, and the top alternatives to consider.
Lattice built an AI agent worth visiting, then handed its data to everyone else's.
Lattice runs AI Agent as its own changelog category alongside Performance, Compensation, and Analytics, and the June work built it into something worth opening: the Agent attends 1:1s and captures summaries, action items, and coaching insights, answers data questions with charts rather than prose, and takes voice input. July then pointed the same capability outward. An MCP server exposes Lattice to Claude, OpenAI, and Slack, and AI review drafts are assembled from a person's own 1:1s, feedback, goals, and updates with cited sources. Underneath both, the performance and compensation machinery keeps absorbing manual setup — calibration groups generated from the org chart, approved promotions carried from a review cycle into a comp cycle.
Workable is localizing hard while its hiring agent quietly gets adjustable.
Two threads dominate. Localization is being pushed on both sides at once: the interface now ships in French, Canadian French, Danish and Dutch, and candidate-facing language kits expanded from five languages to nine. The other thread is the Workable Agent, generally available in June to run sourcing, screening and qualification against an ideal candidate profile, and now editable — teams can rewrite criteria, add or remove must-haves, and re-evaluate an existing pipeline against the revised profile at one credit per candidate.
Lattice runs AI Agent as its own changelog category alongside Performance, Compensation, and Analytics, and the June work built it into something worth opening: the Agent attends 1:1s and captures summaries, action items, and coaching insights, answers data questions with charts rather than prose, and takes voice input. July then pointed the same capability outward. An MCP server exposes Lattice to Claude, OpenAI, and Slack, and AI review drafts are assembled from a person's own 1:1s, feedback, goals, and updates with cited sources. Underneath both, the performance and compensation machinery keeps absorbing manual setup — calibration groups generated from the org chart, approved promotions carried from a review cycle into a comp cycle.
The interesting move is that Lattice stopped assuming it wins by being the app you open. June made the Agent a destination; July made Lattice reachable from Claude, ChatGPT, and Slack instead, which is a bet that being the HR data layer beats owning the chat surface. Review drafts show what that data layer is being accumulated for: the meeting capture, feedback, and goals the Agent has been collecting are now the raw material for the review itself, with citations as the trust mechanism. Compensation is on a slower and more procedural track, closing loops — sending recommendations back for revision, exporting with HRIS IDs attached — rather than adding AI.
Expect the review-drafting work and the MCP surface to converge, so a manager can draft an evidence-cited review from Claude or Slack without opening Lattice. Whether compensation gets the same treatment is genuinely unclear from these entries — that area is still being hardened procedurally, and approval chains carry consequences that make an AI draft a harder sell.
Two threads dominate. Localization is being pushed on both sides at once: the interface now ships in French, Canadian French, Danish and Dutch, and candidate-facing language kits expanded from five languages to nine. The other thread is the Workable Agent, generally available in June to run sourcing, screening and qualification against an ideal candidate profile, and now editable — teams can rewrite criteria, add or remove must-haves, and re-evaluate an existing pipeline against the revised profile at one credit per candidate.
The Agent has moved from launch to operability in two months: the interesting release was not making it autonomous but letting a recruiter change its mind and replay the pipeline. That, plus credit-metered re-evaluation, tells you Workable is selling agent output as something to be corrected rather than trusted outright. Around it the platform keeps widening past the ATS — employee surveys, headcount reporting, entity-scoped HR admin — which is the HRIS build-out competing for the same seat. Localization serves both, and is the cheapest way to reach markets where an English-only ATS was disqualifying.
Mobile app localization is stated as coming, and the language-kit and interface lists will likely converge. On the Agent, per-criterion transparency — why a candidate scored as they did — is the natural follow-on to letting teams edit the criteria.
Other HR 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 Lattice or Workable.
Wagepoint put AI at the payroll approval gate, then spent a week arguing about where else it belongs.
Eightfold has moved from screening candidates to running the interview loop itself.
Gauzy's React rewrite becomes a tenant-level switch, and its AI chat learns to listen
Miter added accounts payable and opened a free API — it's no longer just construction payroll.
Tanda starts encoding state statute into the roster itself, not just the pay run.
Crelate's public feed is a recruiting podcast plus search-craft essays; the changelog lives elsewhere.
See all Lattice alternatives → · See all Workable alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Workable is currently shipping more aggressively (velocity 5.0 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. Workable is currently shipping more aggressively (velocity 5.0 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 HR products to evaluate alongside.
Top Lattice alternatives in HR are ranked by recent ship velocity. Browse the "Lattice alternatives" section above for the current picks, or visit /alternatives/lattice for the full list with editorial commentary on each.
Top Workable alternatives in HR are ranked by recent ship velocity. Browse the "Workable alternatives" section above for the current picks, or visit /alternatives/workable for the full list with editorial commentary on each.