How we review HR software

Our review process

1. Name the buyer scenario: the role, the company size, and the systems already in place.
2. List the tools that still sell that job, and leave out products that do not serve the scenario.
3. Read the vendor's product page, pricing page, and the help or security pages the claim depends on.
4. Keep the fit in the words the page uses, such as growing companies, SMB, mid-market, or enterprise.
5. Copy the price, the seat minimum, and the account floor from the pricing page, and say when that page asks for a quote instead.
6. Add the caveat and two questions for the demo. A second read checks the sentence, the source, and the link before the page goes up.
7. Change the page when the price, the plan, or the cited feature changes.

What we evaluate

The criteria change with the category. A learning system and an engagement survey answer different buying jobs, so they are not judged on the same list.

Employee engagement

• Surveys the page describes: engagement, pulse, and eNPS.
• The segment or situation the page names.
• Anonymity and response thresholds, when the page states them.
• Price, seat minimum, and any account floor on the pricing page.
• Whether recognition, performance, or a wider suite sits in the same plan.

See this in employee engagement.

Performance

• Review workflows the page describes, including self reviews, manager reviews, and cycles.
• Whether goals or calibration are in the product being shown, or a module added later.
• The company size or situation the page names.
• Price and plan limits.

See this in performance.

HRIS

• The employee record the page describes as a system of record.
• Payroll or benefits, when the page says they are in the product or an add-on.
• Price, when the page publishes one, and what has to be live before the first payroll run.

See this in HRIS.

Employer of record

• The page says the provider legally employs the person for the customer.
• The country, and whether the page says the provider owns the entity.
• The price, when the page publishes one.
• Contractor payment is a different job. It does not put a product on this list by itself.

See this in employer of record.

Learning and development

• Whether the page calls the product a learning system or an LMS.
• Who it trains: employees, partners, customers, or all three.
• Whether authoring and skills tracking are in the plan or added later.
• Price, when the page publishes one.

See this in learning and development.

360 feedback

• Named rater groups on the cited page: peers, direct reports, upward feedback, or co-workers.
• Which plan includes that survey, and whether the pricing page names a separate price.

See this in 360 feedback.

1:1s

• A shared agenda, notes, or action items that carry forward, on the cited page.
• Which plan includes that meeting, or a plain statement that the pricing page does not say.

See this in 1:1 software.

How a name gets on the list

A place on a list is a fit for a scenario. A tool that suits a growing company can sit in a different place, or not at all, on a list for a large enterprise. The order is a way to read the scenario. It is not a single winner for every company.

The same product can appear in more than one category when a public page supports each job. It stays off a category when the opened page does not describe that job. FeedbackPulse is filed in employee engagement, in performance, and in 360 feedback. It stays off HRIS, off employer of record, off the 1:1 guide, and off learning and development, because the pages opened for those jobs do not describe an HR system of record, employment in another country, a shared 1:1 agenda, or a learning system.

Sources we use

Preferred

The vendor's own product page, pricing page, plan limits, and the help or security page the sentence depends on.

Used with care

A figure that is not printed on the vendor page can appear only when the entry names the other source. A screenshot shows the page the price came from. The caption does not claim the image shows a number the page left off.

Not used as the fact

Another site's ranking, a star average on its own, and a claim with no page behind it. User comments can shape a demo question. They do not replace the vendor page.

How we check prices and hidden costs

A price on a guide is the price on the vendor's pricing page: per employee, per year, a seat minimum, or a request for a quote. The engagement guide also shows a screenshot of that page. Plan limits that change the bill are written next to the rate, including annual billing, a module sold separately, and a custom enterprise schedule.

When the public page lists no dollar amount, the entry says so. An account floor is the minimum that page states before a new customer can open the product.

How we keep pages current

A page is updated when the cited price, plan, or feature changes, when a reader reports an error, and when a tool enters or leaves a category. The sentence and the link move together.

What this method does not do

• It does not report a hands-on product test. This is not a testing lab.
• It does not invent a headcount the vendor page did not give.
• It does not treat a review form as a learning system, or a directory as payroll.
• It does not file a survey or review product as HRIS software, or as an employer of record.

Inclusion

A name goes up after the vendor page supports the sentence, and it comes off when that page no longer does.