Student applications were managed in spreadsheets with no shared source of truth.
Case Study Details
Project Overview
A Bangladesh-based education consultancy operating across multiple branches needed one system to replace spreadsheets, chat threads, and disconnected document storage.
Counsellors, documentation officers, branch managers, and finance staff all interacted with the same student journey but followed inconsistent processes.
Xorin Lab scoped and delivered a centralized platform with role-based access, workflow automation, and reporting designed for day-to-day branch operations.
The Challenge
Documents were scattered across drives, email, and chat apps.
Application status was difficult to track across teams and branches.
Multiple branches followed different operational processes.
Management lacked real-time visibility into pipeline and performance.
Staff permissions were hard to control as the team grew.
Project Objectives
Centralized application management across branches
Multi-branch access with controlled visibility
Role-based permissions for every team type
Structured document management per application
Payment tracking linked to student records
Automated status workflow with audit history
Reporting dashboard for management decisions
Client communication tied to application progress
Our Solution
Solution step
We designed a multi-tenant architecture where each organization operates in an isolated workspace while sharing a scalable platform foundation.
Solution step
Application workflows were mapped to real branch operations, with configurable stages, ownership, and escalation rules.
Solution step
A client-facing portal lets students and applicants upload documents, track status, and receive notifications without manual follow-up.
Solution step
Admin dashboards give leadership branch-level and organization-level reporting without exporting data manually.
Key Features
Multi-Tenant Architecture
Each organization runs in a dedicated workspace with isolated data, configurable branding, and scalable infrastructure.
Role-Based Access Control
Each branch, department, and team member receives access based on their responsibilities, helping protect sensitive data and reduce operational mistakes.
Application Workflow
Configurable stages guide each application from intake to completion with clear ownership and status history.
Document Management
All files stay attached to the correct application with version context, reducing lost documents and duplicate uploads.
Payment Tracking
Finance teams can reconcile payments against application records without maintaining separate spreadsheets.
Reporting Dashboard
Branch and organization leaders review pipeline health, team workload, and conversion trends in one place.
User Roles
Permission model
7 roles defined for this platform
Super Admin
Platform-wide configuration and tenant management.
Organization Admin
Organization settings, branches, and user governance.
Branch Manager
Branch operations, team oversight, and reporting.
Counsellor
Student guidance, application progress, and communication.
Documentation Officer
Document review, verification, and compliance checks.
Finance Team
Payment recording, reconciliation, and financial reporting.
Student / Client
Portal access for submissions, updates, and notifications.
Development Process
Discovery
We interviewed branch teams, counsellors, and leadership to map how applications, documents, payments, and reporting actually work day to day. This phase uncovered bottlenecks, permission gaps, and branch-level process differences that had to be reflected in the platform.
Requirements Mapping
We turned discovery findings into a clear module map covering applications, documents, CRM, payments, and dashboards. Roles, approval paths, workflow statuses, and reporting requirements were documented so development stayed aligned with real operations.
Wireframing
We structured key journeys for admins, counsellors, documentation officers, finance teams, and students. Wireframes validated navigation, task priority, and information density before visual design began.
UI/UX Design
We designed interfaces optimized for high-volume daily use — clear status visibility, fast document review, and branch-aware dashboards. The design system kept workflows consistent across admin and client portal screens.
Development
We built the platform in phased releases so stakeholders could validate applications, documents, payments, and notifications early. Core modules shipped incrementally with role-based access and configurable workflow stages.
Quality Assurance
We tested permissions, multi-branch access, document workflows, payment status updates, and edge cases across roles. QA focused on operational reliability so teams could trust the system under real workload.
Deployment
We launched branch-by-branch with guided onboarding, data migration support where needed, and live training for counsellors and admins. Rollout sequencing reduced risk while keeping operations running.
Ongoing Support
After launch we monitored adoption, gathered branch feedback, and shipped iterative improvements to workflows, reporting, and usability. Support covered maintenance, enhancements, and operational refinements as the consultancy scaled.
Technical Architecture
Frontend
Next.js, TypeScript, Tailwind CSS
Backend
Node.js, NestJS REST APIs
Database
PostgreSQL with Prisma ORM
Cache
Redis for sessions and hot data
Queue
BullMQ background job processing
Storage
S3-compatible object storage for documents
Docker
Docker Compose multi-service deployment
Infrastructure
Nginx reverse proxy on cloud VPS
Auth
JWT auth with role-based access control
Transactional email for status and reminders
SMS
Optional SMS alerts for critical updates
Payments
Payment gateway for fee tracking integration
Realtime
WebSocket updates for operational dashboards
Monitoring
Application logs, uptime, and error tracking
Why this stack
This stack supports modular SaaS delivery with strong role-based security, reliable document handling, and background processing for notifications and reports. Redis, queues, and object storage keep the platform responsive under multi-branch operational load.
Challenges During Development
Problem & Resolution
Challenge
Complex permission boundaries across branches and departments
Solution
Implemented granular role templates with branch-scoped data access.
Problem & Resolution
Challenge
Large document uploads during peak intake periods
Solution
Added resilient upload handling and object storage with progress feedback.
Problem & Resolution
Challenge
Workflow history needed for accountability
Solution
Built immutable status history and audit logs for every application action.
Gallery
Screenshots and Gallery
Centralized application operations across branches
Reduced manual coordination between counsellors and documentation teams
Faster application tracking with clear ownership
Improved management reporting without spreadsheet exports
Better staff accountability through workflow history
More secure document handling for student records
Planning a Similar Platform?
Tell us about your users, workflows, and current operational challenges.
