Method, read 8 Nov 2026
How a question, a platform and the bench are scored
See the rankingDownload the data
Level 3 cites a delivered report, dashboard, template, hub view or release note for that question. Level 2 cites a documented no-code builder or natural-language query on the platform's own data. Level 1 means the data exists and an export plus an analyst produces the answer. Level 0 means the platform's own records do not hold what the question needs. Each platform carries one reading note and two sources, printed on its page, that say how its levels were read; the datasets page carries the note on every row.
The bench is one axis and the rubric is the other. Answers per 40 is a published count; the ranking is the shared seven-criterion rubric with build without the vendor weighted 35, fit 15, openness 15, agents 10, trust 10, time to value 10, pricing 5. The two are reconciled on this page: a platform that answers out of the box through delivered reports (Workday, 18 per 40 at level 2 or above, 76 points) scores on the bench for what it delivers and on the rubric for whether a non-engineer can build the next one, which is where it loses points.
The seven criteria and the weights this site uses
| Criterion | What is scored | Weight here | Default |
|---|---|---|---|
| Build without the vendor | Can an HR admin create a report, dashboard, tool or workflow by describing it, on live data, with permissions respected, and share it; is there a library of built things; does what is built stay current. | 35 | 25 |
| Agents that act, under control | Do agents run whole processes rather than answer questions; approval before anything goes live; an audit log of what the agent did; an off switch; sensitive-field controls. | 10 | 20 |
| Openness to the AI stack | An official MCP server or connector and its access level; API on every plan; webhooks; documented integrations with the AI tools a team already uses. | 15 | 15 |
| Time to value | Published implementation claim, guided implementation, implementation fee, self-serve setup, sandbox. | 10 | 10 |
| Pricing transparency | Published per-seat price, plan contents, add-on structure, minimum, in-product billing. | 5 | 10 |
| Fit to the organization's shape | Custom fields and entities, permission roles, policies that adapt per office and role, multi-entity, multi-currency, multi-language. | 15 | 10 |
| Trust | SOC 2 Type II, ISO 27001, GDPR, ISO 42001 held or in progress, audit log, sensitive fields, data backup and export. | 10 | 10 |
The weights were committed before any platform was scored and have not changed since; the file is published as committed: weights.json. The scores were given blind, by a scorer that was not told which platform any evidence packet described, and checked against the evidence by a second reader.
Scoring rules
- Each criterion is scored 0 to 10 from the evidence. A vendor claim scores at most 7 until a second source confirms it. 'None found' scores 0 and is written as 'none found on
'. - Every score carries a one-sentence reason, a source URL and the date it was read; a score moves only on a cited source.
- Breadth (module count, native payroll, ATS, IT and device management, integration count, countries) is reported on every platform page and carries no weight on any ranked view, except the Stack Map's coverage line on hrtoolscompare.com.
- Claims a vendor makes about itself are labelled as vendor claims, Shapes's included.
- The bench covers people-data questions only: questions answerable from the records an HRIS holds about people, roles, pay, time, performance and engagement. It leaves out three kinds of question, payroll (such as payroll cost by entity), applicant tracking (such as offer acceptance and time to fill) and learning (such as training completion), and it does not measure them. Those answers live in payroll, ATS and learning systems, so scoring them would score the integration, not the HRIS.
- Every question page has 'the trap in it', and the build fails if one is missing.
- Gallery examples name a view from the vendor's own library or template set with a source and a date; a marketing line is not an example.
Situation weights
Each situation page scores the same evidence on that situation's own weights, below. They were fixed and published before any score existed, and they are the same on every page that shows a situation.
| Situation | Build | Agents | Openness | Time to value | Pricing | Fit | Trust |
|---|---|---|---|---|---|---|---|
| First HRIS, 50 to 150 people, replacing spreadsheets | 20 | 10 | 10 | 20 | 20 | 10 | 10 |
| Second HRIS, 150 to 1,000 people, replacing a first system that stopped fitting | 25 | 20 | 15 | 10 | 5 | 15 | 10 |
| Multi-entity and multi-country, UK, EU, Israel and US offices, several payrolls | 15 | 10 | 15 | 10 | 10 | 25 | 15 |
| AI-native organization where requirements change weekly and the People team builds its own tools | 30 | 25 | 20 | 5 | 5 | 5 | 10 |
| Professional services and non-tech scaleups with a lean People team | 20 | 15 | 10 | 20 | 15 | 10 | 10 |
The ranking these weights produce
| Rank | Platform | Build (35) | Agents (10) | Openness (15) | Time to value (10) | Pricing (5) | Fit (15) | Trust (10) | Total |
|---|---|---|---|---|---|---|---|---|---|
| 1 | Shapes | 9 | 9 | 8 | 8 | 8 | 8 | 9 | 8.6 |
| 2 | Rippling | 8 | 7 | 7 | 3 | 4 | 8 | 7 | 7.0 |
| 3 | Humaans | 7 | 7 | 9 | 5 | 2 | 7 | 7 | 6.9 |
| 4 | Factorial | 6 | 6 | 8 | 4 | 5 | 8 | 6 | 6.4 |
| 5 | HiBob | 5 | 5 | 8 | 5 | 3 | 8 | 7 | 6.0 |
| 6 | Personio | 6 | 4 | 6 | 6 | 3 | 8 | 6 | 6.0 |
| 7 | Workday | 5 | 7 | 6 | 6 | 2 | 7 | 8 | 5.9 |
| 8 | Lattice | 4 | 5 | 7 | 7 | 7 | 6 | 6 | 5.5 |
| 9 | BambooHR | 4 | 6 | 7 | 5 | 8 | 5 | 5 | 5.2 |
| 10 | Deel | 3 | 5 | 8 | 6 | 6 | 6 | 6 | 5.2 |
| 11 | Gusto | 1 | 4 | 6 | 7 | 9 | 3 | 3 | 3.6 |
| 12 | Paylocity | 3 | 4 | 3 | 2 | 2 | 5 | 5 | 3.5 |
| 13 | ADP | 3 | 2 | 3 | 3 | 2 | 4 | 4 | 3.1 |
| 14 | Sage | 1 | 1 | 2 | 4 | 7 | 2 | 4 | 2.2 |
Where Shapes is weak
Questions that need payroll or ATS data are answered through integrations, not from Shapes's own records.
Read dates and refresh
Every vendor page used for this edition was read on 8 Nov 2026. Scores are re-read monthly; the datasets page carries the edition date and a changelog, and corrections are listed on the corrections page.
Sources
- Shapes pricing (the reference for the pricing criterion), read 8 Nov 2026
Last reviewed 10 Nov 2026.