Skip to main content

Purpose

Gradientflo is released in stages, sequenced by readiness rather than by date. This page states the order and what gates each step.
Status: Upcoming. Nothing described here is available today. We state sequence and readiness, not dates, and this page is updated as stages complete.

The sequence

1

Candidate Success — the first 90 days

The first release. A new joiner signs in on day one — with Workday, Darwinbox, Microsoft Entra or a company email — and sees the people they work with, the project they joined, and what day 30, 60 and 90 require, assembled from your HR system and project tools or entered directly when none is connected. Notice comes first and gates everything else: no check-in and no AI suggestion runs before the joiner has been told what is observed and why. Structured check-ins at each milestone are reviewed by a human; a below-bar result triggers support, never an automatic outcome.
2

Core loop — companion and role fit

The onboarding companion answering from your own material, ramp risk signals, and role-fit re-evaluation at day 60 and 90 against the original hiring criteria.
3

Development

Structured development planning from an identified gap, and connection to the learning your organization already licenses.
4

Operate at scale

Administrative agents, manager-facing insight, and reach through the channels a new hire actually has on day one.
5

Adaptive

Coaching prompts and pace personalization driven by accumulated signals, and cross-organization benchmarking in anonymized form.

What gates the sequence

Transparency before assessment

Notice and attestation ship before any agent evaluates an employee in the background. This is a hard ordering constraint, not a preference.

Evidence before judgment

Role-fit re-evaluation requires the onboarding companion to have run first — without interaction evidence, a re-evaluation is a guess.

Security review before write access

The first agent that writes to your systems is the one most likely to fail a security review. It ships behind permission scoping and human confirmation on every write, not ahead of them.

Customer demand

Within a stage, sequence follows what customers are asking for.

Availability language

Every Gradientflo page uses these two labels. Everything on them is Upcoming.