Home / Partner Onboarding
For resellers, SaaS operators and implementation teams

Plan Your School ERP Partnership

Choose a business model, agree the license scope, and prepare your first school deployment with clear responsibilities.

Designed for

Smarter day-to-day school management

Best for
Schools that want one connected system
InstiKit dashboard preview

Why schools choose InstiKit

A practical platform for school leaders and operators

Platform overview

How InstiKit supports everyday school management

Explore how InstiKit helps schools organize academics, administration, fee collection, communication, and parent engagement through one connected platform.

1. Describe Your Business and Target Market

Tell the team where you operate, the schools you serve, your existing customer network and whether you plan to resell a branded product, run a subscription service or provide implementation and customization. These models have different technical and support needs.

Use the partner application to share your country and target market. The team will discuss availability and the fit for your proposed model. Application does not grant a license or exclusive territory.

2. Confirm the Package and License Scope

Review the white-label reseller edition, SaaS Business Edition and Developer Edition. Before purchase, confirm the included source code, mobile applications, branding, number of clients or campuses, and permitted resale, SaaS or distribution rights in the applicable agreement.

Request a written breakdown of license costs, hosting, installation, updates, support, optional work and renewal terms. School per-student subscription prices are not a quotation for a reseller or developer license.

3. Prepare Your Deployment and Support Plan

For a self-hosted offering, identify who will operate the server, handle backups, maintain security, deploy updates and support your school customers. Discuss the technical prerequisites and any installation assistance before committing to a launch date.

Plan which language, terminology, payment and communication integrations your market needs. Your team should verify the supported configuration and the scope of any development work; local requirements should not be assumed to be included automatically.

4. Review the Workflows With Your First School

Prepare the school's admission, fee, attendance and communication requirements. Agree a pilot scope, data preparation, user roles, branding assets and training responsibilities. A demonstration helps your team identify what can be configured and what needs customization before rollout.

5. Agree How Ongoing Questions Will Be Handled

Define the boundary between your first-line customer support and InstiKit's package support. Confirm how to raise issues, which updates are included and how optional services are quoted. Review the first deployment before adding more customers.

Ready to Discuss the Next Step?

Apply as an InstiKit partner with your country, business model and expected client scope. The team will discuss the suitable license and onboarding requirements for your business.

Core modules

Run every major workflow from one connected system

Product screens

See how InstiKit looks across daily school workflows

Use cases

Useful for teams across the entire institution

Frequently asked questions

Answers decision-makers usually need before they switch

Next step

Tell us how you plan to serve schools

Share your country, target market, business model and expected client scope so we can discuss the appropriate package.