Compensation, module versus point tool, read 8 Nov 2026
Shapes compensation against Pave
| Pave | Shapes compensation | |
|---|---|---|
| Depth, as published | Benchmarks from 9,000+ companies, job architecture, comp planning, total rewards, MCP access to Pave data | native (Compensation app) |
| Price | Market Data Lite free; planning by quote | inside Core at $8 per seat; module pricing by quote |
| Replaces the other | no: a point tool needs an HRIS record to read | yes for a stack that does not need the specialist's depth |
| Keeps the record | in the HRIS, synced | in the HRIS |
The stack verdict
A company that runs one compensation cycle a year on a template keeps it in Shapes and cancels the specialist; a company whose compensation practice is the People team's main product keeps Pave and connects it. A company that wants best-of-breed depth in performance or compensation will find more in Lattice or Pave than in the Shapes apps.
Sources
- Pave, read 8 Nov 2026
- Shapes modules, read 8 Nov 2026
Last reviewed 10 Nov 2026.