Sales model: Quote Core Foundation for every client. Add modules 1–12 and extended modules 13–22 based on need — more can be switched on later without rebuilding the foundation.

Core Foundation (required)

Everything needed to register students, manage staff, run multi-campus structure, and give parents basic access. Implement this first. See Core implementation plan.

CapabilityMicroservice(s)Included
API gateway, security, JWTapi-gateway, auth-service
Multi-campus org, years, terms, classesorganization-service
Student registration, guardians, enrollmentstudent-service
Staff & teacher accounts, roles (RBAC)auth-service
Parent accounts linked to childrenauth-service
Student photos & document uploadsfile-service
Admin web portal (shell)React admin
Basic parent login & child listReact family portal
SMS/email infrastructure setupnotification-service✓ (config)

Core pricing guide (indicative, 500-student school)

ItemImplementation (UGX)Annual subscription (UGX)
Core Foundation8M – 12M650,000 – 850,000

Scale implementation and subscription by student count tier — see pricing guide.

Add-on modules (optional)

Each module maps to one or more microservices. Enable per client contract. Price reflects build complexity and operational value to the school.

ModuleService(s)ComplexityImpl. add-on (500 stu)Annual add-onPriority
Fees & Payments
Invoices, payment claims, defaulters
fee-service High +4M – 6M +350k – 450k Essential
Parent Portal & Documents
Library, homework, distribution
notice-service, portal High +3M – 5M +280k – 380k Essential
Attendance attendance-service Medium +1.5M – 2.5M +120k – 180k Common
Student Health Records
Parent confirm, doctor's note, nurse-only access
health-service Medium–High +2M – 3.5M +150k – 220k Boarding / welfare
Academics & Report Cards
Marks, CBC grading, reports
academic-service High +4M – 6M +320k – 420k Common
Finance & Accounting
P&L, balance sheet, reconciliation
finance-service High +3M – 5M +250k – 350k Director schools
Notice Board notice-service Low +800k – 1.2M +80k – 120k Common
Requirements Checklist student-service Low +600k – 1M +60k – 100k Optional
Stock Keeping inventory-service Medium +1.2M – 2M +100k – 150k Optional
Uniform Management inventory-service Medium +1M – 1.8M +90k – 140k Optional
Director Dashboards report-service Medium +1.5M – 2.5M +150k – 220k Multi-campus
Android App
Offline attendance, fee lookup
mobile + API High +5M – 8M +200k – 300k Phase 6

Extended add-ons (modules 13–22)

Roadmap modules — standalone with Core or integrated with other add-ons. Full integration matrix: extended modules roadmap.

#ModuleService(s)Standalone?Impl. add-on (500 stu)Phase
13Transporttransport-serviceYes+2M – 3.5M10
14Boarding & hostelboarding-serviceYes+2.5M – 4M10
15Scholarships & bursariesscholarship-serviceNeeds Fees+1M – 2M7
16Discipline & welfarewelfare-serviceYes+1.5M – 2.5M8
17Timetable & lesson planningtimetable-serviceYes+2M – 3.5M9
18Official chat & broadcastschat-serviceNeeds Portal+2.5M – 4M8
19Events & calendarcalendar-serviceYes+800k – 1.5M7
20Staff HR & payrollhr-serviceYes+3M – 5M11
21E-learningelearning-serviceNeeds Portal+3M – 6M12
22Librarylibrary-serviceYes+1.2M – 2M9

Example packages

Starter

Core + Fees + basic notices

~12M – 18M implementation

See tiers →

Standard

Starter + Parent portal + Attendance + Academics + Health records

~22M – 35M implementation

Enterprise

Modules 1–12 + extended 13–22 + dashboards + Android

~50M – 120M+ implementation

Boarding school plus

Standard + Boarding, Transport, Discipline

~30M – 48M implementation

How modules are deployed

  • Each add-on is a Docker service added to the school's compose/Kubernetes stack
  • Feature flags in gateway route to enabled services only
  • Client pays implementation once per module; annual subscription increases per active module
  • New modules connect via RabbitMQ events — no Core rebuild required

Technical detail per module: Technical module specifications