When systems diverge, leaders lose the thread from employee record to customer record.
|
Orgix is built for teams that want one platform for people operations and sales operations — web and mobile in sync.
Multi-tenant B2B SaaS
From directory to deal on one platform
Run people operations (HRIS) and customer/sales operations (CRM + Field Force) from one shared system — instead of spreadsheets, chat threads, and disconnected tools.
The problem
Manual workflows don't scale
Growing companies waste time, cause errors, and hide information in silos. Orgix replaces manual, error-prone processes with backend rules as the source of truth.
Scattered HR data
Employee records live in Excel, email, and paper files. Orgix gives you one directory, org chart, and reporting structure.
Manual attendance & leave chaos
Paper registers and email approval chains waste time. QR, selfie, or biometric check-in and multi-step leave approvals run in-app.
Payroll re-entry errors
Re-typing hours and leave into payroll sheets causes mistakes. Payroll runs are built from structured attendance and leave data.
Sales blind spots
Leads in notebooks with no pipeline visibility. Track leads → customers → opportunities with stage history enforced by the backend.
Field team disconnect
Reps report visits late or not at all. Visit plans, GPS check-in/out, and conveyance claims happen on mobile in real time.
Multiple logins & permission confusion
Separate tools for HR and CRM, unclear approval rights. One identity, modular SKUs, and role-based access per module.
Why Orgix
Five pillars of the platform
HRIS, CRM, and Field Force on one platform — each tenant isolated, each module gated by subscription and permission.
One employee record
Directory, org chart, documents, assets, attendance, leave, payroll, and lifecycle workflows — hire to offboard on a single profile.
Explore →People operations (HRIS)
Attendance with QR, selfie, or biometric check-in; leave policies with multi-step approvals; payroll runs built from structured HR data.
Explore →Customer & sales (CRM)
Leads → customers → opportunities with pipeline stages, activity logging, and backend-enforced transitions for consistent reporting.
Explore →Field Force
Visit plans, GPS check-in/out, route and territory planning, targets, and conveyance claims — connected to the same CRM accounts.
Explore →Built for scale
Multi-tenant isolation, modular SKUs, dual authorization (roles + permission groups), SSO, webhooks, and web ↔ mobile parity.
Explore →
Module spotlight
Representative capabilities
A rotating slice of the product map — availability and navigation depend on roles and enabled modules. See the full module map.
Core workspace
Dashboard, invitations, configurable widgets, and multi-company context.
Open solution →
Support & governance
Help center, docs hub, and workspace settings including SSO and webhooks.
Open solution →
Time & attendance
QR, selfie, or biometric check-in with rules, sessions, and history.
Open solution →
How it works
One request, no duplicate entry
Example: an employee requests leave on mobile → manager approves in app → HR sees the approved request → attendance marks ON_LEAVE → payroll reflects unpaid days. Backend rules route each step automatically.
Enable your product SKUs
Subscribe to HRIS, CRM, Field Force, or the full Suite. Each company gets only the modules they pay for — no one-size-fits-all bloat.
Invite users & assign roles
Invite by email with role assignment in one step. SUPER_ADMIN, ADMIN, HR, MANAGER, EMPLOYEE, and sales roles map to the right capabilities.
Configure policies & pipelines
Set leave policies by department or job, attendance rules, and CRM pipeline stages. Backend validation keeps workflows consistent.
Operate from web + mobile
HR and admins work on web; employees check in, request leave, and get payslips on mobile. Sales reps run visits and pipeline from either surface.
Architecture
Built for consistent behavior at scale
Orgix is delivered as web apps (People, CRM, Auth), a Flutter mobile client, and a shared REST API — each tenant isolated, each module gated by subscription and permission.
One API, one database
HRIS and CRM share tenancy and identity. Web and mobile clients expose the same capabilities — no duplicate business logic.
Details →Backend is source of truth
Validation, enums, permissions, and pipeline transitions live in the API. Clients do not re-implement rules.
Details →Modular SKU model
Companies enable only what they pay for — HRIS, CRM, Field Force, or Suite. Module access drives navigation on web and mobile.
Details →Dual authorization
Company role plus permission groups for fine-grained access. GET /auth/modules drives consistent navigation everywhere.
Details →Ready to replace manual HR and sales workflows?
Talk to us about HRIS, CRM, Field Force, or Suite packaging — or sign in if you already have access.