PeoplanceLive

One in-house platform for HR, hiring, payroll, and finance — web, mobile, and API

The HR and operations platform Innovaxel runs on every working day: people, leave, attendance, hiring, onboarding, payroll, invoicing, IT assets, and an internal CRM on one permission model. A Django API behind a React web app and a React Native mobile app.

Peoplance: Peoplance sign-in on web and mobile.
Peoplance sign-in on web and mobile.
Industry
HR & People Operations
Market
Pakistan & UAE
Platform
Web & Mobile
Engagement
In-house product

The short version

The problem

Leave, hiring, payroll, invoicing and approvals were spread across separate tools and chat threads.

What we built

One platform for HR, hiring, payroll, finance, IT assets and CRM, on a single permission model across web, mobile and API.

Where it is now

Live and used across the company every working day. Multi-tenant support is next.

The challenge

Every hand-off between tools was a place for a request to stall

The client

Peoplance is our own platform, and we're the client. We built it to run Innovaxel itself, with the same engineers, process, and production bar our clients get. The whole company works in it every day, so any shortcut we take shows up the next morning.

The problem

Like most growing companies, our people operations had spread across separate tools: one for leave, another for hiring, spreadsheets for payroll, an invoicing app, and chat threads for approvals. Every hand-off between them was somewhere a request could stall, data could drift, or a sensitive record could land in the wrong inbox. Off-the-shelf HR software covered part of the job and could only be configured to approximate how we work, not match it.

The approach

Small releases to colleagues who use it the next day

  • Privacy from the start

    Sensitive values stay masked until someone asks to see them, and erasing data needs typed confirmation.

  • The API enforces access

    Every permission is checked by the API, not by hiding buttons.

  • The company keeps running

    Every release went straight to colleagues who’d use it the next day.

How we worked

Continuous delivery since December 2025: small versioned releases with a changelog, staging before production, and automated tests and linting on every merge. Each product rule is decided once and carried into the API, web, and mobile apps together, so a leave policy or approval step behaves the same on every surface.

What shipped

Four things we shipped

  1. Peoplance: Every module, on one permission model.

    1One system of record

    HR, hiring, payroll, finance, IT assets, and CRM unified into one system with a single source of truth

  2. Peoplance: Role scopes, from self up to the whole organization.

    217 scoped roles

    17 responsibility roles, each with an explicit boundary, scoped to self, direct reports, department, or the whole organization and enforced by the API

  3. Peoplance: One API behind the web app, mobile app, Slack and innovaxel.com.

    3One API, every surface

    Web app, native mobile app, and Slack integration all running on one Django API, which also publishes the careers and blog pages on innovaxel.com

  4. 4600+ commits in ten months

    600+ API commits shipped to production in ten months, with the whole company using it every working day

Stack & services

What it runs on

Frontend

  • React
  • Tailwind CSS

Mobile

  • React Native

Backend

  • Django REST Framework
  • PostgreSQL
  • Celery
  • Redis

Delivery

  • Docker

What we did

  • Product Design
  • Web application development
  • Mobile application development
  • Access control architecture
  • Slack & Google Workspace integrations
  • Testing/QA
  • CI/CD
Where it is now

What happens next

Live and in daily use across the company. Multi-tenant support is next on the roadmap. If you're deciding between building an internal platform and stitching more tools together, this is the build we'd show you first.

Try it live
Your project

Stitching together HR and operations tools?

Tell us which tools you’d replace first. We’ll reply with a one-page build plan within 48 hours.

What to expect
  1. 1We review your brief
  2. 2You get a call confirmation
  3. 3Walk away with a 1-page build plan
No sales pitch — just a clear build plan.
···