The Launch Path.

We begin with a structured conversation to identify the people involved in the pilot, including the coordinating team, selected teachers and students, and the key contacts who will work with us throughout the pilot. We also establish the pilot timeline, responsibilities, and communication process.

We begin by setting up the institution’s co-branded experience with its name, logo, colors, and other required branding elements. The mobile and web applications are then configured for the pilot environment.

We provide beta access to the co-branded mobile and web applications. For Android, the beta application is provided through an AAB-based installation process rather than being published on the Google Play Store during the pilot.

We provide access to the pilot group of 50 students, 5 teachers, and 1 admin, enabling them to use the configured platform and experience the relevant learning, communication, and administrative features.

During the two-week pilot period, we observe platform usage, gather feedback, and fine-tune app settings where needed. This helps validate the setup and prepare the institution for the full launch.

We set up the institution’s no-login communication pages based on the information and achievements it wants to showcase, while configuring student, teacher, and admin accounts along with teacher classes and authorizations.

We securely migrate relevant historical academic data, including past attendance, results, and subject notes, and validate the migrated information as part of the launch preparation.

We publish the approved mobile applications on the Apple App Store and Google Play Store, provide campus-wide installation and onboarding guidance, and support the institution through the transition to full platform usage.