Skip to main content
CASE STUDYEnterprise ERP System

Khan Hub ERP

Centralized multi-role operational ERP managing 16+ departments across 5 connected web properties with granular access control, financial logging, and LLM automation.

ROLESole Developer
TIMELINE2025 – Present
STACKNext.js, TypeScript, Tailwind CSS
STATUS
Internal
Privacy Note:Screenshots and record displays use blurred or sample data to protect patient, staff, student, and donor confidentiality.
Khan Hub ERP Cover Specimen
(01)The Problem
Context & Operational Friction

A hospital, rehab centre, college and welfare departments each ran on separate physical registers and spreadsheets. Fees, staff, salaries and departmental reports could not be tracked or audited in one place, causing operational delays and reconciliation friction.

(02)What I Built
Granular Deliverables • 11 Milestones
  1. (01)One Next.js + TypeScript + Firebase system with separate logins and dedicated operational screens for 16+ departments.
  2. (02)Role-based access control (admin, cashier, staff) enforced through strict Firestore security rules and approval steps.
  3. (03)Comprehensive audit log recording every transaction, cashier submission, and record update with timestamps and user IDs.
  4. (04)Finance and cashier screens paired with interactive Recharts dashboards for revenue tracking.
  5. (05)Firebase Cloud Messaging (FCM) push notifications and Progressive Web App (PWA) installation support for staff devices.
  6. (06)Digital student admission system for the college with document verification gates.
  7. (07)Centralized donor register for the welfare division with receipt generation.
  8. (08)A 10-slide architectural proposal for a unified billing and medicine-stock system, starting as an active hospital trial.
  9. (09)Head-office AI voice assistant using Groq and Llama 3.3 70B with tool-calling, self-describing Firestore schemas, and two-tier memory.
  10. (10)Five connected websites integrated into the centralized ecosystem, including JobReel.
  11. (11)Hardware-level biometric fingerprint and facial recognition attendance integration (currently in progress).
(03)Decisions that mattered
Architectural Reasoning & Tradeoffs
DECISION 01

Managed backend (Firebase) over custom Node servers.

Selected Firebase Auth, Firestore, and Security Rules so one developer can ship, secure, and maintain 16+ departments alone without running and babysitting custom server infrastructure.

DECISION 02

Role-based access designed first, screens second.

Defined permission matrices and Firestore security rules before building UI screens, preventing cross-department data leakage and unauthorized cashier overrides.

DECISION 03

Resolved production Cross-Origin-Opener-Policy (COOP) edge case.

A browser security header misconfiguration broke Firebase popup sign-in in production. Isolated the origin policy conflict, corrected server response headers, and documented the root cause.

DECISION 04

AI coding agents used to speed delivery while I review and own every change.

Used AI coding workflows to accelerate component scaffolding while personally reviewing, validating, and owning every line of architectural logic and security rule.

(04)Screenshot Gallery
Interface Records • Captured Specimen
4 Exhibits
Khan Hub ERP - Exhibit 01
[01]Centralized multi-department dashboard with role-based routing and live status metrics
Khan Hub ERP - Exhibit 02
[02]Cashier ledger interface with fee categorization and balancing audit
Khan Hub ERP - Exhibit 03
[03]Executive AI voice assistant with Groq + Llama 3.3 70B tool-calling schema
Khan Hub ERP - Exhibit 04
[04]Immutable system audit trail detailing user actions, cashier submissions, and department approvals
(05)Production Outcome
Verifiable Daily Utility

Sole developer who unified 16+ departments and 5 connected websites into a single operational system.

Eliminated paper registers and disconnected spreadsheets across hospital, college, and head-office divisions.

Staff and cashiers now balance daily collections through verified, role-segregated audit trails (TODO_REAL_VALUE daily active records handled).

NEXT CASE STUDY →JobReel
Short-Video Hiring Platform•2026Read Case Study →