Skip to main content

Purpose

Smaya is horizontal: one Agent OS, one governance model, one integration layer. What sits on top of it is vertical: applications that carry the deep expertise of a single business function. Depth is what makes an application useful. The shared foundation keeps governance, identity and audit consistent.

The applications

Exterview — Agentic Talent Intelligence

Available. Everything up to the hiring decision: role design, resume screening and matching, AI phone screens and interviews, panel and HR rounds, ranking and decision support. Upcoming: sourcing, outreach campaigns and offers. 26 specialized agents. Live and transactable on the Microsoft Marketplace.

Gradientflo — Post-hire

Upcoming. Everything after the hire: onboarding, role fit and performance, career and mobility. See Upcoming.

The boundary between them

A single cut across the employee lifecycle, at the moment of hire. Solid lines are Available today. Dotted lines are Upcoming.

What holds them together

The Talent Graph — the shared language of skills, evidence and outcomes. A role states a requirement as a skill. Exterview evaluates a candidate against that skill. Gradientflo checks the same person’s role fit against the same skill, and reviews them against it later. One vocabulary, one evidence standard, across the whole employee lifecycle. This is the reason the two products are one platform rather than two tools that share a login.

What we do not build

Stated plainly, because it is a question every CIO asks. The test we apply: if the output is a record, it belongs in your HR system and we do not build it. If the output is a judgment backed by evidence, it is ours.

FAQs

No. Most organizations start with one. The platform is the same underneath, so adding the second is a configuration and commercial step rather than a new implementation.
Because governance, identity, approvals, audit, integration and evaluation are the same problem in every business function, and the expertise is not. Sharing the first and specializing the second is what makes both good.
The exit is a post-hire event, so it belongs to Gradientflo. The interview itself runs on Exterview’s interviewing capability. One deliberate crossing, rather than a second interview engine.