NureCampus is an EdTech SaaS platform that consolidates student management, attendance, grading, fees, communication, and faculty workflows. At 3i Infotech, I owned the end-to-end product design — from problem framing and user research to a shipped design system and engineering handoff.
Mid-sized colleges and institutes in India typically run on a stack of disconnected tools: spreadsheets for grades, WhatsApp groups for announcements, paper attendance registers, a 10-year-old fees module, and a website nobody updates. Three audiences (admin, faculty, students/parents) live in three universes that rarely meet.
NureCampus's brief was to consolidate this into one platform. The challenge wasn't building modules — it was making them feel like one product to three different audiences with very different mental models.
"Our admin team uses keyboard shortcuts and dense tables. Our faculty uses one screen between classes. Our students live on phones. The same product can't look the same to all of them — but it has to feel like the same product." — Founder & CEO, kickoff workshop
Core problems:
We spent the first three weeks inside the campus — shadowing the admin office, sitting in faculty rooms between classes, and following students through a normal day. Workshop-only research would have missed the truth: faculty don't use computers between classes; they use their phone, in 90 seconds, while walking to the next room.
We synthesised the field data into three job-to-be-done maps — one per audience — and defined the cross-cutting design principles that would unify them:
Admin gets keyboard shortcuts and 8-row tables. Faculty gets a phone-sized attendance grid with offline queue. Students get conversational cards with one CTA.
Underneath: identical color tokens, identical motion library, identical accessibility contract. Density and copy do the work, not separate codebases.
The system uses a 3-mode density variable applied at the page root that ripples through
spacing, type scale, and component padding. Engineering swaps a single attribute on
<html>; the entire UI re-densifies for the audience.
EdTech is sensitive — academic decisions on autonomous AI are a non-starter for institutions and parents. We picked 3 surfaces where AI helped operations without touching graded outcomes.
Flags students whose attendance pattern, late-marks, and grade dip together suggest disengagement. Mentor reaches out — not the system.
Parent/student inbox auto-summarises the week's announcements into one digest with read-receipts. Reduces 30+ messages to one.
Pre-fills term-end remarks with phrasing rooted in attendance, performance trend, and past comments. Faculty edits and signs.
"Show me Class IX students with fee due and 3+ absences this month" → filtered list with one-click actions.
Illustrative numbers — I'll swap in verified figures before publishing.
Field research before workshop research. Three weeks on campus rewrote half our assumptions about faculty behaviour. Workshops would have produced a different (worse) product.
One token tree, three densities. Cheaper to maintain than three codebases, and the brand stayed coherent across very different audiences.
Never let AI make academic decisions. Keeping it advisory removed political risk and made adoption frictionless.
Pushed back harder on scope. The 14-week MVP attempted three portals; two would have shipped sharper.
Built parent-side onboarding earlier. Faculty & admin had clear flows; parents kept getting designed last and shipped roughest.
Offline-first isn't a feature — it's the contract. Every late bug we shipped traced back to a flow that hadn't been thought through for "queue → reconcile → conflict UI" from day one.