Workable
Workable is localizing hard while its hiring agent quietly gets adjustable.
A side-by-side editorial comparison of Lattice and Workyard — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Lattice | Workyard |
|---|---|---|
| Sector | HR | HR |
| Velocity score | 0.0 | 7.5 |
| Sparks · 30d | 0 | 1 |
| Top themes | ai-agent, mcp, performance-reviews, compensation | ai-assistant, time-tracking, payroll-export, job-costing |
| Last editorial update | 9d ago | 8d ago |
| Website | Visit → | — |
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.
Workyard's Time Assistant now does the pre-payroll cleanup a bookkeeper used to do by hand.
Workyard is building on two fronts. The AI Time Assistant has moved from fixing clock times and breaks to reading worker notes, proposing exact edits, reallocating hours across projects and cost codes from a plain-language request, and is now delegated down to managers scoped to their own crews. Separately, the back-office edge keeps widening: Acumatica sync, time off in QuickBooks Online exports, expense transaction exports to NetSuite and QuickBooks Desktop, and auto top-up for expense card funding.
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.
Workyard is building on two fronts. The AI Time Assistant has moved from fixing clock times and breaks to reading worker notes, proposing exact edits, reallocating hours across projects and cost codes from a plain-language request, and is now delegated down to managers scoped to their own crews. Separately, the back-office edge keeps widening: Acumatica sync, time off in QuickBooks Online exports, expense transaction exports to NetSuite and QuickBooks Desktop, and auto top-up for expense card funding.
The assistant is being positioned as the pre-payroll review layer, where every change is a proposal the approver accepts rather than an automated write. Note-reading and cost-code reallocation together cover most of what made timecard cleanup a manual pass. Meanwhile the integration work is aimed at the same outcome from the other side: getting GPS-verified field hours into payroll and accounting systems without re-keying, which is what makes accurate job costing worth anything.
Time Assistant should reach the mobile app for managers and admins next, as the manager release states, and the approval-with-diff pattern is the likely template for any further automation Workyard applies to timecards.
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 Workyard.
Workable is localizing hard while its hiring agent quietly gets adjustable.
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.
See all Lattice alternatives → · See all Workyard alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Workyard is currently shipping more aggressively (velocity 7.5 vs 0.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. Workyard is currently shipping more aggressively (velocity 7.5 vs 0.0), with 1 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 Workyard alternatives in HR are ranked by recent ship velocity. Browse the "Workyard alternatives" section above for the current picks, or visit /alternatives/workyard for the full list with editorial commentary on each.