









(Key features)08 modules
01Employee managementProfiles, onboarding, documents, role-based access control and employee archiving.
02Attendance & leavePunch in/out, attendance tracking, leave requests, approval workflows and attendance reports.
03ProjectsProject assignments, client and vendor management, and employee work tracking.
04Finance & payrollSalary management, expense tracking, reimbursements, invoices and TDS.
05PerformanceEmployee KRAs, performance evaluations and question banks.
06Visitor managementA reception module for clients, vendors, guests and deliveries.
07Reports & analyticsAttendance, project, leave, salary and employee performance reports.
08Mobile appA Flutter app for attendance, leave and essential employee workflows.
(What I did)07
- Developed and maintained the web platform with Next.js, React and TypeScript.
- Built backend features in Node.js and MongoDB, exposed through REST APIs.
- Implemented role-based access control across the platform’s modules.
- Built attendance, leave and approval workflows.
- Built finance, payroll, performance and visitor management modules.
- Built reporting across attendance, projects, leave, salary and performance.
- Developed the Flutter mobile app for attendance, leave and core employee workflows.
(Architecture)One backend, two clients
- Node.js REST APIsBusiness logic & workflows
- Web appNext.js · React · TypeScript
- Mobile appFlutter
- MongoDBRecords for every module
- Access controlPermissions by role
(Challenges & solutions)04
Many modules, one product
- Challenge
- HR, attendance, projects, finance, performance and reception each have their own workflows, yet they all concern the same people and organisation.
- Solution
- Each area is built as a module on one shared stack, with reports that span attendance, projects, leave, salary and performance.
Who sees what
- Challenge
- HR and salary data is sensitive, and every role needs a different view of it.
- Solution
- Role-based access control governs what each user can see and do across modules.
Workflows, not just records
- Challenge
- Leave and attendance move through requests and approvals rather than sitting as static records.
- Solution
- Punch in/out, leave requests and approval workflows, feeding attendance and leave reports.
Work happens off the desk
- Challenge
- Employees need to punch in and apply for leave from wherever they are.
- Solution
- A Flutter app focused on attendance, leave and essential employee workflows, alongside the web platform.


