Answers for schools, training teams, partners, and families.

AcadNest is an education platform family covering school operations, academic reporting, learning delivery, and family finance planning. The products are separate enough to solve focused problems, but connected by one broader education ecosystem story.

Use EduSphere when the main need is admissions, billing, student records, staff workflows, notices, and operational oversight. Use SiyandaTermly when the urgent need is marks capture, term reports, rankings, and parent access to reports.

EduSphere is the school operations layer. It covers admissions pipelines, student and guardian records, billing and receipts, arrears visibility, staff and HR workflows, notices, dashboard metrics, and tenant-level school administration.

SiyandaTermly covers the term-end academic workflow: schools, staff, learners, classes, grades, subjects, assessments, mark capture, percentage and ranking calculations, report exports, parent access codes, audit logs, and forecasting views.

FundisaFlow is the learning delivery product. It is for institutions, training teams, and educators who need tenant-aware courses, modules, lessons, enrolments, quizzes, learner progress, certificates, dashboards, and public certificate verification.

TuMu is for parents, guardians, and shared households. It helps families manage child profiles, track child-related expenses, set budgets, store receipts or supporting documents, invite household members, export data, and plan for milestones like a new baby or university.

AcadNest should be treated as pilot-ready. Public environments and walkthroughs can support discovery, demos, and controlled pilots, while wider production use needs final checks around hosting, backups, legal terms, support, privacy, and product-specific implementation scope.

Payment readiness depends on the product. EduSphere includes school fee and receipt workflows. TuMu tracks household spending and budgets. FundisaFlow has payment-shaped demo flows, but real payment processing and webhooks are parked for a later production phase.

EduSphere and FundisaFlow are designed around tenant-aware operation, so each school or institution can work within its own space. SiyandaTermly includes platform administration for multiple schools, and TuMu is organised around household-level workspaces.

AcadNest reviews your product area, organisation or household context, and preferred contact details. The next step is usually a short WhatsApp conversation, then a focused walkthrough shaped around your workflow.

WhatsApp is faster for early discovery because it makes it easy to clarify the product, school or household context, and next step before scheduling a formal walkthrough. Email remains available as the secondary channel.

Yes. For example, a school may start with EduSphere for operations and SiyandaTermly for reporting. A training organisation may focus on FundisaFlow. The walkthrough can cover one product or the broader ecosystem.

The current FundisaFlow codebase includes backend and frontend flows for authentication, tenant-aware courses, enrolments, learner progress, quizzes, certificate issuance, public certificate verification, and student/instructor dashboards. Production hardening is still required before broad rollout.

Yes. TuMu has a PWA baseline and Capacitor Android/iOS wrappers in the project, which means it can move toward packaged mobile app distribution once production API, release, and store requirements are finalised.

Confirm the target product, users, data to import, pilot duration, support process, privacy and legal requirements, hosting expectations, reporting needs, and the workflow that will define whether the pilot was successful.