Reading a Vendor Claim

The vocabulary here is loose in specific, repeatable ways. Translating it is most of the evaluation.

"Fully configurable"

Usually means: settings exist for the common cases.

Ask: show me this rule configured, in the product, now. Give them one of your awkward rules.

A vendor who needs a call with engineering to answer has told you it is a customisation.

"Integrates with your payroll"

Usually means: a CSV export exists.

Ask: which payroll systems, by name and version, with which method — API, file, connector? Who maintains it? What happens when the payroll vendor changes their format?

A file export is not an integration. It is a manual step with an owner and a failure mode.

"Compliant"

Compliance is a property of your deployment, not of a product. A vendor cannot make your configuration lawful.

Ask: which jurisdictions the rule library covers, how it is updated when law changes, and whether that update is included or chargeable.

"Real-time"

Ask: real-time to what? A clock-in visible to a supervisor within seconds is different from payroll data available immediately, which almost never is.

"Unlimited users"

Ask: what is metered instead. Entries, projects, storage, API calls. Something is, and it is the thing that grows.

"Enterprise-grade"

Means nothing measurable.

Ask: uptime commitment in the contract, with a remedy. Support response times by severity. Where data is processed and stored.

"AI-powered"

Ask: what specifically is learned, and what happens when it is wrong. In this category the answer is usually suggestion of project codes, which is useful and low-risk — or it is activity inference, which is the thing the exclusions cover.

"Trusted by N companies"

Ask for two references at your size, in your sector, using the module you need, and speak to an administrator rather than the sponsor.

A vendor unable to offer a comparable reference is telling you something about the deployment base for that module.

The general test

Any claim without a name, a number or a demonstrable screen is a description of intent.

Convert each one into a question that has a checkable answer, and ask it in writing. Sales answers given in writing are noticeably more careful than the same answers given in a meeting.

Ask in writing

The difference between a sales answer and a commitment.

Send the questions by email rather than asking in a meeting.

Ask for the answers to be attached to the contract.

Sales answers given in writing are noticeably more careful than the same answers given aloud, and that carefulness is itself the information.

Where a claim matters — processing location, no training on your data, export completeness — it belongs in a term rather than a slide.

Checking the underlying product

When a shortlist reaches vendor validation, compare claims with the provider’s official website and record the page, plan and date supporting each mandatory requirement.