Guide, 8 Nov 2026, read 8 Nov 2026
Connecting people data to the CRM and project tools
The questions that cross
- Revenue or pipeline per salesperson by tenure band and manager (CRM plus HRIS).
- Hours logged per team against headcount and plan (project tool plus HRIS).
- Accounts and projects owned by people leaving this month (CRM and project tool plus the leaver list).
- Time to productivity for sales hires, measured as months to first closed deal (CRM plus start date).
- Cost of the People team per employee served (HRIS plus the finance ledger).
The three doors
| Door | What it is | Who publishes it |
|---|---|---|
| MCP server | An AI client reads the HRIS and the CRM through their servers and joins them in the answer | Shapes (read-only, 35 tools), HiBob, Rippling, Workday, Gusto, Lattice, Humaans live; BambooHR beta; Personio announced |
| API | A developer or a BI tool joins the records | Shapes on every plan; Personio from CorePro; Humaans from Growth; most others on a standard plan |
| Export | CSV from each system into a spreadsheet or a warehouse | Everyone, with the Migration Ledger on the network's switching site grading the formats |
What Shapes's views do
Shapes describes Vibe Views as cross-referenced with the CRM and project tools: a view can hold the HRIS record and the connected system's fields in one place, on live data, with permissions respected. That is the built form of the first door; the bench scores it under openness and build, and the Shapes platform page says which questions it reaches.
Sources
- Shapes Vibe Views, read 8 Nov 2026
- Shapes MCP server, read 8 Nov 2026
- Humaans API and webhooks by plan, read 8 Nov 2026
Last reviewed 8 Nov 2026.