← All verticals

People operations

The employee side: joining, absence, time and objectives.

What the workspace opens with

recruitingonboardingleavetimesheetexpensesconsultant-self-serviceokrworkflows

Plus the core every workspace carries — support, notifications, documents, analytics — because a tenant with no documents, no notifications and no analytics is not a smaller product, it is a broken one.

What that lets you do end to end

From a gap on a project to somebody working on it

  1. A project reports a gap — A staffing request names the role, the skills and the dates. Until somebody is allocated it sits in the capacity view as an unmet need, not as a note in a spreadsheet. (needs the staffing module, which this vertical does not enable by default)
  2. The gap becomes an opening — The opening remembers the request it came from, so the pipeline is answerable to the project that asked. Candidates carry their consent date and a retention deadline from the moment they are created.
  3. Interviews, kept separate — Each interviewer files their own evaluation. A split panel is shown as a split panel rather than averaged into a number that hides the disagreement.
  4. The hire becomes a person on the payroll — Marking a candidate hired writes the consultant record. The database refuses the state otherwise: an application cannot claim a hire that produced nobody. (needs the contractor-portal module, which this vertical does not enable by default)
  5. And an onboarding that already exists — The same action instantiates a checklist from a template, one row per item, with due dates counted from the start date rather than from today.
  6. Then the hours start arriving — The new consultant files time against the project that raised the request. The loop closes where it opened.

From work done to money received

  1. Hours are approved, not just entered — An entry passes an internal approval, and — where the contract says so — a client approval through a tokenised link that needs no account.
  2. The project knows what it has burned — Budget burn is computed from the approved hours, and crossing 80% or 100% raises a digest rather than being noticed at the end of the quarter. (needs the projects module, which this vertical does not enable by default)
  3. The invoice is generated from those hours — Line items come from the approved entries. Nothing is retyped, so nothing can disagree. (needs the invoicing module, which this vertical does not enable by default)
  4. And transmitted where the law requires it — Italian e-invoicing goes to the SDI with its receipts tracked as states, not as an email somebody remembers sending. (needs the invoicing module, which this vertical does not enable by default)

See it with data in it

A demo workspace set up for people operations, seeded and yours for 14 days.

Start one