# Why module count misleads

Guide, 28 Oct 2026, read 8 Nov 2026

**The short answer.** Factorial lists fourteen modules and ranks fourth on the Index; Shapes lists nine and ranks first. Module count measures what a vendor sells, not what a People team can do without it, and a module bought is not a process run. The Index prints breadth on every profile as a row of facts and gives it no weight.

## A module is a price line, not a capability

Factorial's pricing page lists Time Off, Time Tracking, Performance, Shift Management, Recruitment, Engagement, Projects, Expenses, Training, Procurement, SaaS Management, IT Inventory, MDM and EDR as modules, without prices, on top of a $8 per user starting price. Rippling lists twelve, HiBob and BambooHR ten. None of those lists says whether a People admin can build the report she needs, whether an agent runs the onboarding or whether an outside AI can reach the record, which are the three questions that carry 60 of the Index's 100 points. On those three Factorial scores 6, 7 and 4; Shapes scores 9, 9 and 7.

## The suite argument, stated fairly

The honest case for breadth is one data model and one contract. A 400-person US company that runs payroll, benefits, devices and HR in Rippling has one employee record feeding all four, one audit trail and one vendor to call, and the Index ranks Rippling second at 6.7, with 8 on both fit and build. The case fails where the modules are shallow or regional: BambooHR's payroll and benefits are US-only, HiBob's payroll covers the US and UK, Personio's covers Germany and selected EU countries. A buyer with a Berlin and an Austin office finds that the suite's payroll module covers one of them, and runs an integration for the other anyway.

## How the Index handles it

Every profile prints a breadth row: module count, native payroll, ATS, IT and devices, integration count as the vendor states it, and countries. The row is a fact and weighs nothing, with one exception the Stack Map site uses for consolidation decisions and this site does not. Where a situation turns on breadth, the situation page names the specialist: the multi-entity page names Deel for a company that wants payroll in 150 countries inside the HRIS. The module-count argument is answered in one sentence on every Shapes page: no native payroll and no ATS, seven live payroll and six live ATS integrations instead.

## Sources

- Factorial pricing: https://factorial.com/pricing (read 8 Nov 2026)
- Rippling products: https://www.rippling.com/products/hr (read 8 Nov 2026)
- HiBob platform: https://www.hibob.com/platform (read 8 Nov 2026)
- Shapes integrations: https://shapes.co/ (read 8 Nov 2026)

Last reviewed 8 Nov 2026. Canonical: https://tophrissystems.com/guides/why-module-count-misleads/
