The employee lifecycle, handled in one place
Onboarding, the org chart, time off, documents, and the laptop that has to be on someone's desk on day one. People is the fourth product in the suite, and it is not finished yet.
Everything below describes what we are building, not what you can buy today. MDM, Desk, and Swift are the products that ship right now. If People is the reason you are here, tell us, because design partners shape what lands first.
Ask about early accessWhere it stands
Building against the shared platform.
Opening to design partners first.
Once early access tells us it holds up.
What we're building
Planned scope for the first release. None of it is available yet.
Onboarding and offboarding flows
A signed offer starts a single workflow, not four. Checklists are assigned, owners are named, and due dates count back from the start date rather than forward from whenever someone remembered.
Org chart and directory
One person record with reporting lines, teams, and locations, sourced from the directory sync the rest of the platform already runs on.
Time off and documents
Requests, approvals, balances, and the documents that pile up around a hire, held in the same place as the rest of the employee record.
Day-one device provisioning
The laptop is assigned and staged from MDM before the start date, because the start date is a field People already knows.
Why build it inside the suite
There is no shortage of HR portals. The reason to build another one is that the handoff between HR and IT is where onboarding actually breaks, and that handoff only disappears if both sides are reading the same record.
One person record, not four
Most companies run HR, IT, and support on separate systems that each keep their own copy of the same employee. Every copy drifts. People reads the same record MDM, Desk, and Swift already read, so there is nothing to reconcile.
Handoffs become joins
When onboarding kicks off, the laptop assignment in MDM and the account-provisioning ticket in Desk are not integrations that someone has to build and maintain. They are joins inside one data model.
One rule builder, four products
The automation that already runs device compliance and ticket routing will run onboarding workflows too. Learn it once. Rules can cross products, so a start date ten days out can order hardware without an integration project.
Three products you can use today
People will read the same person record these already share. Start with any one of them and People slots in when it is ready, with your directory and permissions already in place.