Technource ERP
Designing clarity into enterprise complexity.
An internal ERP built as a single-page React application. Eight modules, eight roles, one component library — and a permission model that had to be legible to the people using it, not just correct in the database.
- Modules
- User roles
- Architecture
- Realtime
1440 × 900
1440 × 900
- 01Kanban · drag & drop · sprint sync · filtering
- 02HR scoring
- 03LiveBiometric · realtime over WebSockets
- 04
- 05Dashboards
- ··Eight modules in total
- 01The problem
Eight modules that had to feel like one product.
Projects, HRMS, Attendance, Recruitment and Reporting each arrived with their own vocabulary and their own idea of what a table should look like. The work was not adding features. It was finding the small set of patterns that every module could be expressed in, then holding the line on them.
- 02Access
Eight roles, one interface.
Role-based access control across eight user roles. Rather than branching the interface per role, permissions resolve into the same layout — actions and modules appear, disappear or explain themselves, so nobody learns a different product because of their job title.
- 03Workflow
A Kanban board that behaves like the one people already know.
A Jira-style board with drag-and-drop task movement, sprint synchronisation and filtering. Familiarity was the requirement: the fastest interface to learn is the one that matches the mental model people brought with them.
- 04Realtime
Attendance that is true right now.
Real-time biometric attendance over WebSockets, feeding HR scoring and reporting dashboards. Live data changes the design problem — the interface has to stay readable while the numbers underneath it move.
- 05The system
A component library, not a stylesheet.
A reusable Tailwind component library underpins all eight modules. Designed in Figma, implemented in React, then used as the actual constraint on what new screens could look like. That loop is the reason the product stayed coherent.
- Category
- Year
- Role
- Built with