Campus OS

A mid-sized university runs on five disconnected systems and a paper bridge between them: fees in one database, housing in a spreadsheet, registration queues in a hall, and deans making decisions on last semester's exports. Students queue for things a system should settle in seconds.

One student record, many services. A modular platform holds the canonical record — admissions, fees, courses, housing, results — while role-based portals serve students, lecturers, administrators and deans from the same source. Registration, fee clearance and record requests become self-service; staff consoles handle the exceptions.

• ▸Modular monolith — one deployable, strict module boundaries (records, fees, courses, housing)
• ▸Role-based access control with delegated administration per faculty
• ▸M-Pesa + bank rails for fees with instant clearance against the record
• ▸SSO integration with existing university identity systems
• ▸Reporting warehouse feeding dean-level analytics

Students get a mobile-first portal where registration is minutes, not a morning in a queue. Staff get an efficiency console — the ten tasks that eat their week, streamlined. Deans get numbers they trust without asking IT for an export.

Engagement signals feed an early-support flag list for students at risk — built as decision support with explicit governance: visible criteria, human decisions, and an audit of every intervention. No surveillance theatre.

Targets are what this design is dimensioned for — not results claimed from work we haven't done. We think you should hold us to exactly this standard of honesty.

• Design target — 40,000 student records, one source of truth
• Design target — course registration completed in under 5 minutes
• Design target — fee clearance reflected in real time