0→1 / B2B / SAAS / PRODUCT DESIGN / SYSTEMS DESIGN
Campus Management System
Designing a fully modular institutional platform to manage students, staff, and daily campus operations from scratch.
// PROJECT OVERVIEW
A modular institutional platform designed to manage students, staff, and daily operations for schools, colleges, and universities. Built to replace manual workflows with a system, administrators would actually want to use.
Schools and universities were trapped between inefficient manual processes and rigid, expensive ERPs with poor usability. The CMS was designed to fill that gap. Affordable, flexible, and built for the people who actually run campus operations.
// THE PROBLEM
Institutions were stuck between pen-and-paper chaos and rigid software they couldn't afford or use.
Existing ERPs were expensive, inflexible, and built for IT teams, not for the middle-aged administrators who actually run campus operations. Most institutions defaulted to Excel sheets, WhatsApp groups, and manual registers.
The market needed a solution that was complete enough to handle every operational need, yet simple enough for non-technical staff to adopt without training.
// RESEARCH
With no formal user research access, I relied on three methods to understand the problem space before designing anything.
Sales team interviews
The sales team had been calling institutions and gathering direct feedback. I sourced pain points from their conversations: existing systems were too costly, too rigid, had poor customer support, and left institutions locked into software they weren't comfortable using.
Competitive ERP analysis
I went through existing ERP systems used by institutions to understand what they got right and where they failed. Most were feature-heavy but unusable for non-technical administrators.
Collective campus experience
I spoke with my developer team about their own campus experiences, how things worked at their institutions, what processes were frustrating, and where daily friction lived. This gave me first-hand perspective on real campus pain points.
// MY ROLE
Sole product designer working end-to-end across system architecture, workflow design, and UI, collaborating directly with developers over five months. No PM, limited research, and an evolving scope.
15+
Interconnected modules designed
0
Product managers on the team
5 months
Design to deployment
// APPROACH
The system was designed around how institutions operate on a daily basis, not the other way around. Every decision prioritized real-world workflows over conventional SaaS patterns.
The foundational decision was the Academic Structure module, a flexible system that lets any institution define how they organize students. Every other module references this structure automatically.
For high-stakes modules like fees and attendance, I prioritized audit trails, preview screens, and explicit confirmations. Reliability over speed. Conservative design for operations where mistakes don't stay isolated.
// IMPACT
A complete institutional management system designed for reliability and trust, now operational across early adopter institutions. 6 institutions onboarded and using the CMS for daily campus management.
The system replaced fragmented manual processes with a single platform that administrators trust for high-stakes operations: attendance, fees, alerts, results, and timetables.
