Product

People Platform
one identity, end to end

The full employment lifecycle on one backend — public careers site, applicant tracking, offers, onboarding and employee self-service — so a candidate becomes an employee without a second login or a re-keyed record.

The problem

The handoffs are where people are lost

Most organizations run a careers page, an applicant tracker, an offer tool and an HR system that were never designed to speak to each other. A candidate is typed in four times, their record splits, and the person who applied is not obviously the person who was hired. Every seam is a place to lose data, lose the audit trail, or lose the candidate.

One record

No re-keying

Application, interview, offer, onboarding and employment are stages of one identity, not four systems agreeing by coincidence.

One boundary

Access that narrows

Recruiting history is preserved with HR-only access rather than copied into the employee file where a manager can read it.

One audit

Decisions on the record

Who reviewed, who scored, who approved and when — retained because hiring decisions are the kind that get asked about years later.

Modules

Six modules on one backend

Careers

Public careers site

A public careers API — openings, structured job metadata, applications with a token-secured status page — and a hosted careers portal that lists an organization's published roles and takes applications against them.

Pipeline

Applicant tracking

Internal pipeline stages mapped to a simpler status the candidate actually sees. Structured interview scorecards against criteria set on the requisition, so a decision rests on comparable evidence. Reviewers who can score without gaining access to the rest of a candidate's file.

Offers

Offers and e-signature

Offers generated from an approved template, routed for approval, signed or declined in place — and acceptance launches the correct pre-employment checklist automatically rather than by someone remembering to.

Identity

Candidate to employee

One identity throughout the transition. Recruiting records become history with a narrower access boundary; nothing is duplicated into the employee file, so there is never a second version of the truth to reconcile.

Onboarding

Onboarding

Task, training and equipment templates assigned by organization, job and department — with the manager's tasks and IT's tasks tracked alongside the new hire's, because those are the ones that get forgotten.

Self-service

Employee self-service

Time off, HR cases and the employee directory, on an employee record HR activates on day one, places on leave and closes with a last day — with a hard boundary around payroll and banking data, which this platform does not hold.

What it is not. The People Platform is not a payroll system and does not process pay, tax filings or bank details. Where those are needed it hands off to a payroll provider rather than pretending to be one.
Architecture

The same foundation as the revenue platform

This is not a second product built by a second team on a second stack. It runs on the platform already carrying claims and remittance data, which sets the floor for how employee data is handled.

Multi-tenant

Isolation enforced server-side on every query, not by a filter someone remembered to add.

Configured, never forked

One build for every organization. What differs between tenants is configuration on the tenant record; the careers portal itself is served in the platform's own presentation.

Role-based access

Recruiter, hiring manager, interviewer, HR and employee see genuinely different records.

Audited

Access and decisions recorded in an append-only audit trail.

Training content is credential-scoped: what a person can see is determined by what they are, and internal commercial material is never reachable from a customer organization. That boundary is enforced by the platform, not by which link someone is given.
See it

Request a demonstration

A walkthrough of the platform end to end: the live careers experience, the candidate-to-employee data model, and how the modules fit together. Roughly thirty minutes.

You will see

  • The live careers site, including how it behaves with no open roles
  • Structured job metadata and how a role is published
  • The candidate-to-employee identity model
  • Role-based access across recruiter, manager and HR
  • Credential-scoped training and where its boundary sits

You will also learn

  • How each organization's data is isolated from every other
  • How the candidate portal's token model keeps applications private
  • How offer approval separates the drafter from the approver
  • Where the payroll, tax and banking boundary sits

Email reaches a person directly. There is no form here that quietly goes nowhere.