Pricing that scales with the institution — not with software complexity.

The licensing model is published on the pricing page; figures are issued in a written proposal after institutional discovery. One published figure would be wrong for most institutions, in both directions.

Enterprise is selected by governance requirement, not by enrolment or module count. Advanced institutional governance, cross-campus command, analytics, integrations, expanded audit controls and specialised deployment or support requirements are assessed during discovery and documented against available capabilities. Every plan includes the complete generally available core operational platform. Essential school operations are not unlocked by upgrading from Starter to Pro or Enterprise. The institution owns its institutional data in every plan. We earn continued adoption through operational value, with supported data exports and documented offboarding rather than artificial lock-in. Export scope, available formats, access arrangements and assistance are confirmed for the deployment; retention and deletion follow the agreement, the DPA and applicable obligations. Export formats and timing are established before commitment.

Usually not. SquareCampus is priced for institutions that want governance, workflow ownership, exception management, visibility and auditability. To one that needs only the cheapest attendance, fees and report-card product it will look expensive — and that reading is correct.

Yes. A pilot covers one campus or one workflow bundle, and your ERP keeps running and stays authoritative. Replacing anything is a later decision, taken on evidence.

Data migration is included in Pro and Enterprise, and quoted on Starter. We move everything your current system can export in usable form. If it lacks data SquareCampus needs, or is too fragmented to reconcile, we show you what cannot move before go-live instead of guessing.

Reporting is self-serve in every plan: staff filter, group, total and chart their tables, save views for the team and export to Excel, CSV or PDF. A fixed-format document made only for your institution, such as your own report-card layout, is quoted; a format many schools need becomes a standard report at no charge.

Nothing extra. Implementation and support are included in every plan, and every institution gets the same rollout: there is no paid fast track. SquareCampus is designed to need little or no training. Only a custom SLA, such as 24×7 cover or guaranteed response times, is quoted.

Not by surprise. Everything optional is priced in the proposal before you sign, and usage beyond the allowance is prepaid, so the proposal you sign is the bill you get. Enrolment growth is reconciled through the agreed true-up.

Not today. Enterprise can scope a dedicated deployment on AWS, in a private cloud or on premises, with responsibilities set out before implementation.

Secure authentication and role-based access are baseline requirements in every plan. SquareCampus-managed sign-in is included in the baseline plan scope; supported sign-in methods and deployment readiness are confirmed before activation. Additional verification for privileged roles is established during technical onboarding. Institutions on Starter, Pro or Enterprise may request optional single sign-on with Microsoft Entra ID as a separately quoted enhancement, subject to technical onboarding. Once configured, staff use their institutional accounts under the institution's own MFA, Conditional Access and user-assignment policies, while SquareCampus governs authorisation. Availability and commercial terms are confirmed before activation. Enterprise: Enterprise is differentiated by identity governance rather than by having SSO. Identity requirements across several campuses or directories, directory-group to role mappings, SSO enforcement policy, joiner-mover-leaver lifecycle controls, identity migration and identity audit controls are scoped as Enterprise requirements during technical discovery.

No. Entra ID sign-in authenticates identity only; no access to email, files, Teams or SharePoint is needed.

No. Single sign-on authenticates. Automated provisioning and joiner-mover-leaver controls are identity governance, part of Enterprise and established during technical discovery.

Quoted commercial figures are exclusive of applicable taxes unless the proposal states otherwise. Applicable Indian taxes are shown on the order form and on tax invoices issued by Fairhelm Systems (OPC) Private Limited under GSTIN 29AAHCF1819L1ZA.

Not included in Starter; in Pro when the proposal includes it; in Enterprise within an agreed monthly allowance. Usage beyond the allowance is prepaid, so it never becomes a surprise bill.

Starter, Pro and Enterprise support multi-campus operations with campus-level administration and role-aware workflows. Advanced centralised institutional governance is a separate dimension; campus count alone does not require an upgrade. A trust-level agreement can cover agreed campuses; advanced central policy and governance requirements are scoped separately.

There are exactly two Founding Institutional Partner positions, ever: one school or eligible school institution, and one university. Once both positions are allocated, the programme closes permanently. A Founding Institutional Partner is not an ordinary customer. The position involves a strategic capital commitment under a separately executed agreement, material participation in product validation, and structured roadmap input.

Every plan includes the complete generally available core operational platform. Essential school operations are not unlocked by upgrading from Starter to Pro or Enterprise. Starter, Pro and Enterprise support multi-campus operations with campus-level administration and role-aware workflows. Advanced centralised institutional governance is a separate dimension; campus count alone does not require an upgrade. Available modules, workflows and deployment scope are confirmed before activation. A plan entitlement does not imply that an unreleased capability is available.

Institutions on Starter, Pro or Enterprise may request optional single sign-on with Microsoft Entra ID as a separately quoted enhancement, subject to technical onboarding. Once configured, staff use their institutional accounts under the institution's own MFA, Conditional Access and user-assignment policies, while SquareCampus governs authorisation. Availability and commercial terms are confirmed before activation.

Tenant isolation, secure authentication, role-based authorisation, protection of institutional records, essential security logging and privacy safeguards are baseline requirements in every plan. Advanced identity governance and expanded audit controls are separately scoped; fundamental security is not a premium feature. The institution owns its institutional data in every plan. We earn continued adoption through operational value, with supported data exports and documented offboarding rather than artificial lock-in. Export scope, available formats, access arrangements and assistance are confirmed for the deployment; retention and deletion follow the agreement, the DPA and applicable obligations. Export formats and timing are established before commitment.

Eligible, approved launch institutions may join a 90-day complimentary pilot. The platform subscription, standard onboarding and reasonable operational support are included for the agreed pilot scope. Participation requires institutional approval and an agreed scope; submitting an enquiry does not activate a pilot. This is a selected launch programme, not an unrestricted global free trial. Messaging, AI, storage, integrations and external-service consumption have defined boundaries agreed before activation. Custom development, bespoke integrations and unrestricted engineering support are not included. Any separately chargeable work or consumption must be agreed in writing. Subscription pricing is communicated before pilot activation, with a commercial review before the 90-day pilot expires. At completion, the institution chooses to subscribe or discontinue. The complimentary launch pilot is separate from the standard paid subscription and from the Founding Institutional Partner programme. Launch-pilot participation does not confer founding status or its negotiated privileges.

Initial launch outreach focuses on Kotdwara and surrounding areas. Enquiries are reviewed individually; this outreach focus is not a published geographic eligibility restriction.

Yes, where the capability and commercial eligibility are confirmed. Institutions on Starter, Pro or Enterprise may request optional single sign-on with Microsoft Entra ID as a separately quoted enhancement, subject to technical onboarding. Once configured, staff use their institutional accounts under the institution's own MFA, Conditional Access and user-assignment policies, while SquareCampus governs authorisation. Availability and commercial terms are confirmed before activation. Other enhancements, consumption and professional services are assessed and quoted separately; their availability is not implied by appearing in a scoping discussion.