The Friction
A hire finishes onboarding on day one — and lands in a void on day two. Attendance lived in registers, leaves in verbal approvals, tasks in chat threads, KRAs nowhere at all. For teams of five to fifty running without HR software, day-one systems were rich and day-two systems were absent. And the economics were backwards: onboarding is a one-time engagement, but employment never stops recurring.
The Catalyst
The seam was visible from the previous build: TalentArc’s lifecycle ends at hired/check-in, and the operating model that already ran the agency day to day — KRAs, a task manager, an automated end-of-day report — existed only as habit. Productizing that habit closes the lifecycle gap and converts it: a one-time onboarding engagement becomes recurring per-seat accounts. The architecture decision was locked the same day: fully standalone — own repo, own database, own OAuth, own brand — with a thin one-way bridge from TalentArc, never a module of it.
The Resolution
A per-tenant branded employee workspace and HR console. Attendance with check-in and worked hours, tasks with comments and attachments, leave balances with a single approval level, a KRA and KPI engine, versioned policy documents, announcements, an HR help desk, and reports — with three roles: employee, manager, HR admin. Logins run through Google, hires arrive either through the TalentArc provisioning bridge or manual creation, each tenant wears its own color from the database. The v1 fence is deliberate: no payroll, no biometrics, single-level approvals.
The Pipeline
Phases, not ambitions: scaffold and auth, then people, then the daily core of attendance and tasks and leaves, then KRAs and policies and helpdesk, then reports and the bridge — seven to nine build slots to go-live, on the same stack as TalentArc so proven library patterns port instead of get rewritten. Gates were written before work started: an intake score before the first build slot, a committed external tenant before go-live — with kill criteria recorded at intake, not invented after.
The Horizon
The first client go-live graduates it from candidate to product, and the bridge keeps it fed: every new TalentArc client is a warm Operance lead. The KRA engine doubles as the engine for the agency’s own operating model — the discipline it sells is the discipline it runs on. Long-term, the pairing completes a market: TalentArc owns the one-time relationship to hire, Operance owns the recurring relationship after it.