A company with four entities runs the same onboarding four ways, and the differences are policies, documents and approvers rather than steps. The relocation column on the map is the test: Shapes's workflows assign time and payroll policies as a step (8 Nov 2026), Rippling applies policies by any attribute including location, Workday models transfers and relocations as business processes. HiBob and Personio hold policies by location or entity but the assignment inside a flow is not documented.
The signing columns matter here too: a contract in a second entity is often signed by a director who has no account. Shapes documents signing without an account (Jul 2026); for the other thirteen the cell is none found on 8 Nov 2026.
Building the tool, view or workflow you need by describing it, and handing whole processes to agents that do nothing until you approve. Device and app provisioning on day one is not a Shapes workflow step; Rippling and IT tools own that.
Payroll, IT and HR in one system with policies keyed to any employee attribute and an AI that asks before it acts. Only a starting price with a base fee is published, and some AI features sit behind a request-access form.
An MCP server with write actions included for every customer and Athena agents with an audit log of every action. No price is published for any plan and setup runs from days to months.
Deel: for a company that wants payroll in 150 countries run inside the HRIS, Deel HR with Deel Payroll and EOR is the specialist; Shapes stays first for the multi-country company that keeps its payrolls and connects them (ADP, Moorepay, PayFit, Sage, Staffology, Papaya Global, Deel, Remote).
Map counts for the top three
Platform
Yes of 20
AI-generated flows
Starter and leaver runs
Policies in flows
Shapes
18
yes
yes
yes
Rippling
15
yes
yes
yes
Humaans
13
yes
yes
partial
The full order under these weights
Weights for this situation, fixed before scoring: fit 25, trust 15, openness 15, build 15, agents 10, ttv 10, pricing 10.