SmartRecruiters is now an SAP-owned recruiting platform that is still marketed as a standalone product. Buyers should evaluate the product available today, the priced edition, and the supported integrations separately from future integration promises around SAP SuccessFactors.

This review reflects public information checked on September 14, 2026. It corrects older descriptions that treated SmartRecruiters as an independent company or presented roadmap language as delivered capability.

Ownership changed, but standalone use continues

SAP announced an agreement to acquire SmartRecruiters on August 1, 2025. SmartRecruiters then announced completion of the acquisition on September 11, 2025.

The completion notice says standalone customers can continue using SmartRecruiters and that the platform remains interoperable with other HCM systems. It also discusses integration with SAP SuccessFactors. The completed acquisition is a verifiable event; statements about what integration will enable are company plans and should be confirmed in the buyer’s release, tenant, and contract.

For a current customer, ownership may affect the roadmap, commercial terms, identity architecture, subprocessors, and support escalation. It does not automatically require an HRIS migration. Ask for a dated product roadmap, end-of-life protections, data-portability terms, and a list of changes already delivered since the acquisition.

Current editions and published starting price

The SmartRecruiters pricing page lists Essential starting at $14,995, while Professional, High Volume, and Complete require a quote. The page associates the core SmartOS environment with ATS, CRM, onboarding, SMS, job distribution, and scheduling. It places features such as AI Hiring Agent and matching, conversational AI, high-volume screening, advanced analytics, and sandbox access in particular tiers.

These are public vendor prices and packaging observed on the checked date, not a complete contract. The page does not establish an identical cost for every employee count, geography, usage level, implementation, or integration. A proposal should separate:

  • subscription edition and user or usage assumptions;
  • candidate communication and AI consumption limits;
  • implementation, configuration, and data migration;
  • career-site and job-distribution costs;
  • HRIS, assessment, background-check, and calendar integrations;
  • sandbox, premium support, training, and renewal increases.

Do not infer that an edition name guarantees a particular feature. Put every critical capability and capacity in the order form.

AI assistance needs measurable boundaries

SmartRecruiters markets agents, matching, screening, and conversational functions across its editions. These can reduce manual coordination, but vendor labels do not reveal what data affects a recommendation, whether a candidate is automatically excluded, or how a recruiter can challenge a result.

Test the actual configured workflow with ordinary, incomplete, multilingual, and accommodation cases. Capture the candidate input, system output, reason, human action, override, and final outcome. Require change notices for models and material scoring logic. Any vendor-reported productivity or scale statistic should be treated as a claim until reproduced in the customer’s own process.

If a tool substantially assists or replaces discretionary hiring decisions for jobs in New York City, the employer should evaluate the city’s official Automated Employment Decision Tools rules. Product marketing cannot decide legal scope. The use case and configuration do.

Integration is the operational test

The platform may sit between career sites, job boards, email and messaging, assessments, background checks, and the HR system of record. A demo rarely tests the failure modes across that chain.

Before signing, define which system owns jobs, approvals, candidate identity, offers, and hires. Run duplicate candidates, reopened requisitions, rescheduled interviews, withdrawn consent, failed outbound messages, and a rejected hire export. Verify retry queues, alert ownership, field-level permissions, and an audit trail that a customer can export.

SAP ownership makes SuccessFactors connectivity strategically relevant, but non-SAP customers need equal clarity on certified connectors and continued support. A roadmap item is not an integration acceptance result.

Decision rule

SmartRecruiters is a credible option for organizations that need a dedicated recruiting operating layer and can support enterprise implementation. It should advance when the selected edition covers the required workflow, integration failures are recoverable, AI influence is observable, and the total contract is competitive.

It should pause when the business case relies on unpriced add-ons, a promised SAP integration, or company-reported automation results. Buy the tested configuration that exists, with exit and change protections, rather than the acquisition narrative.