Pricing
School software pricing should match the size and operating reality of your institution, not force every school into the same package.
Pricing is shaped around student strength, campuses and required modules.
Plan data preparation, configuration and team training before launch.
Understand which workflows and services are included before you decide.
A useful quote considers the number of students, number of campuses, modules required, existing data, implementation support and any specialised workflow. This prevents a misleading headline price from becoming an expensive rollout later.
Common questions
A 200-student school and a multi-campus network have very different configuration, migration and support requirements. A scoped quote is more transparent.
Yes. Request a demonstration so the conversation starts with your actual workflows and priorities.
Bring your approximate student count, campus count, priority modules, current tools and preferred implementation timeline.
See the workflow, not just a feature list
Book a focused demonstration around your team’s priorities.