- Company sizes or stages where this product may not be appropriate
- Very small teams (for example, fewer than ~25 employees) that primarily need basic timesheets and do not face material time-fraud risks may find the biometric-oriented approach and a sales-led procurement process to be disproportionate.
- Industries or use cases where competitors may be superior
- Highly regulated enterprises that require published, standardized security/compliance attestations (SOC 2, ISO) as part of vendor onboarding, unless the vendor can provide those attestations.
- Organizations that require a full HCM + payroll consolidation may prefer vendors that provide a broader integrated stack.
- Technical requirements that the product may not meet without validation
- If SAML/SCIM/SSO, detailed audit log export, customer-managed keys, or strict data residency are required, buyers should validate that these are available and meet their controls.
- Budget constraints
- If procurement requires clear, month-to-month published pricing and predictable small-SMB cost structures, SMB-focused solutions with public pricing may be a better fit.
- Specific workflow or integration needs
- Buyers that require extensive bespoke reporting included in the base price should confirm cost and scope, as some reviewers have reported additional charges for custom reports/fixes.
- Red flags to watch for during procurement
- On-site vendor metrics that appear to be placeholders or lack methodology should be clarified with customer references and explained by the vendor before being relied upon in a business case.
- Vendor-acknowledged limitations
- Public documentation focused on feature descriptions; explicit vendor-maintained limitations pages were not identified in the material reviewed.
- Features on the roadmap
- No public product roadmap with estimated delivery dates was identified in the sources accessed.
- Scale considerations
- Public materials did not include documented scale limits or load testing outcomes; buyers should request scalability references for deployments at relevant size thresholds.
- Security and compliance gaps
- No public SOC 2 or ISO attestation statements were identified in the documentation reviewed. The biometric and location tracking approach increases privacy and legal exposure; buyers should require clear retention, deletion, consent, and alternative workflows.
- Technical debt and product maturity indicators
- Some reviewers reported workflows that required workarounds or additional development; these comments suggest areas where feature maturity may lag enterprise expectations.
- API and integration constraints
- Integration availability is indicated (for example, ADP connector), but API surface, rate limits, and detailed integration behavior were not clearly documented in the public material reviewed.