Scale
Active enrolled students
Student volume sets the platform baseline. Larger enrolments sit in progressively better volume bands, so the marginal rate reduces as the institution grows.
Commercial model
Pricing that scales with the institution — not with software complexity.
SquareCampus is licensed annually as one institutional platform. The licence is calculated through student-volume bands and scoped according to the operational depth, governance requirements and deployment profile the institution actually needs.
No hidden module wall. No compulsory rip-and-replace. Scope, ownership and success measures agreed before deployment.
Commercial doctrine
Students price platform scale. The plan prices operational and governance depth.
Two separate dimensions, decided separately. Scale is a fact about the institution; depth is a decision about how much command it wants over daily operations.
- Licence
- Annual, institutional
- Calculated on
- Student-volume bands
- Shaped by
- Operational depth
How the licence is composed
Four inputs, agreed openly, before any number is issued.
The annual platform licence is not a module count. It is the sum of institutional scale, the depth of operational command selected, the complexity of the institution and how the platform is delivered.
The equation
Annual platform licence
One annual institutional licence, composed of four inputs that are each discussed openly during scoping. Nothing is bundled into an unstated blended rate.
- Scale
- Active enrolled students
- Depth
- Starter, Pro or Enterprise
- Complexity
- Campuses, workflows, roles and governance
- Delivery
- Migration, deployment, integrations and support
Depth
Starter, Pro or Enterprise
The plan reflects how much operational and governance control the institution needs — from connected core operations through to trust-level command.
Complexity
Campuses, workflows, roles and governance
Multiple campuses, deeper approval chains and wider role structures change the shape of the rollout and the shape of the commercial.
Delivery
Migration, deployment, integrations and support
Data migration, deployment profile, integrations and the support model are scoped explicitly rather than folded into an unstated blended rate.
Plan architecture
Three levels of institutional command, not three feature bundles.
Each plan represents progressively deeper control over how the institution runs: connected core operations, then visibility and accountability, then trust-level governance across campuses.
01
Starter
Core school operations on one connected institutional backbone.
Depth 1 of 3
The problem it solves
Records, attendance, fees and results live in separate tools, so every question needs a person to reconcile an answer by hand.
Best suited for
- Schools replacing fragmented spreadsheets and disconnected tools
- Institutions that need reliable core workflows before anything else
- Institutions beginning on managed SquareCampus Cloud
Deployment posture
Managed SquareCampus Cloud, with standard onboarding and support.
Capability themes
- Student and staff records
- Attendance workflows
- Fees and reconciliation
- Exams and reports
- Parent and staff communication
- Parent and staff mobile apps
- Role-based access
- Audit history
- Standard operational dashboards
02
Pro
Operational command for institutions that need deeper visibility and accountability.
Depth 2 of 3
The problem it solves
The core runs, but leadership still cannot see what is slipping, who owns it, or whether an exception was ever closed.
Best suited for
- Growing schools taking on more operational complexity
- Institutions that need management dashboards and workflow governance
- Institutions introducing cross-functional accountability
Deployment posture
Managed SquareCampus Cloud, with priority implementation and support options.
Capability themes
- Everything represented in Starter
- Owner command views
- Richer operational analytics
- Advanced exception routing
- Workflow SLAs
- Deeper auditability
- API and standard integration readiness
- AEGIS eligibility or controlled access
03
Enterprise
Selected by governance needTrust-level governance and institutional command across campuses.
Depth 3 of 3
The problem it solves
Central policy and local accountability pull against each other, and no single view reconciles what every campus is actually doing.
Best suited for
- Educational trusts and multi-campus groups
- Church-run school chains
- Institutions balancing central policy with local accountability
- Standalone schools with governance, identity or audit requirements
Deployment posture
Managed cloud, private-cloud or on-premises eligibility, with enterprise implementation governance and tailored support structures.
Capability themes
- Everything represented in Pro
- Trust and campus hierarchy
- Cross-campus command
- Approval and governance chains
- Advanced policy and audit controls
- Microsoft Entra ID SSO
- Governed AEGIS access within an allowance
- Advanced audit exports and data portability
Microsoft Entra ID SSO
Let staff authenticate through your institution's Microsoft identity environment while SquareCampus continues to enforce campus-aware roles, permissions and workflow boundaries.
- Institution-managed identity
- Microsoft Entra ID SSO
- Customer MFA and Conditional Access compatibility
- SquareCampus-governed authorisation
Enterprise includes Microsoft Entra ID SSO for one approved institutional tenant, available subject to technical onboarding. Automated provisioning, additional identity tenants and complex federation requirements are scoped separately.
At a glance
| Dimension | 01Starter | 02Pro | 03Enterprise |
|---|---|---|---|
| Operational scope | Connected core operations | Core operations plus workflow governance | Cross-campus operations under central policy |
| Leadership visibility | Standard operational dashboards | Owner command views and richer analytics | Trust-level command and advanced analytics |
| Accountability model | Role-based access and audit history | Exception routing, workflow SLAs, deeper auditability | Approval and governance chains, advanced policy controls |
| Institutional structure | Single campus | Single or growing campus operations | Trust and campus hierarchy |
| Sign-in and identity | SquareCampus accounts, role-based access | SquareCampus accounts, role-based access | Microsoft Entra ID SSO for one approved institutional tenant |
| Integrations | Standard configuration | API and standard integration readiness | Enterprise integrations, custom integrations |
| Mobile apps | Parent and staff apps included | Parent and staff apps included | Parent and staff apps included; white-label scoped separately |
| AEGIS intelligence | Not included | Eligibility or controlled access | Governed access within an agreed allowance |
| Chosen because | The core needs to work as one system | Leadership needs visibility and accountability | Governance, identity or audit requirements — at any enrolment |
| Deployment | Managed SquareCampus Cloud | Managed SquareCampus Cloud | Managed, private-cloud or on-premises eligibility |
| Implementation and support | Standard onboarding and support | Priority implementation and support options | Enterprise implementation governance, tailored SLA structures |
Capability themes are indicative. Final inclusions, limits and service levels are set by the proposal and the signed order form.
Small institution. Enterprise-grade control.
Enterprise control is not reserved for large institutions.
Enterprise is selected by governance requirement, not merely by enrolment. A standalone school may require institution-managed identity, advanced approvals, executive visibility, stricter auditability or governed intelligence even without operating a large campus network.
Most institutions are well served by Starter or Pro. Enterprise exists for institutions whose governance, identity or audit requirements genuinely sit above them — not as a safer version of the same product.
Reasons a single-campus school lands on Enterprise
- Institution-managed identity and Microsoft Entra ID SSO
- Deeper approval chains and configurable exception ownership
- Executive command views for a board or trustee group
- Stricter access governance and advanced audit exports
- Governed AEGIS access within an internal allowance
- Implementation governance and support escalation policy
Enterprise capabilities are institutional controls rather than open-ended service commitments. Governed AEGIS access, messaging, storage and third-party usage run within agreed allowances or on a metered basis, and implementation, migration and custom engineering are scoped as their own lines. Allowances and fair-use terms are set in the proposal and the order form.
Volume-based pricing
The marginal rate reduces as enrolment grows.
Student volume sets platform scale, and larger volumes use the shared platform foundation more efficiently. The commercial model reflects those economies rather than imposing a flat rate for every institution.
The institution benefits from its own scale
SquareCampus maintains one shared platform baseline — capacity, security, observability, workflow infrastructure and the operations behind them. That baseline does not multiply with every additional student.
Larger institutions therefore receive the benefit of platform economies of scale. The marginal rate reduces as enrolment grows, while the selected plan reflects the workflow, analytics, governance and deployment depth required. An institution is not charged the entry rate indefinitely for growing.
- 01
Platform foundation
Shared capacity, security and operations.
- 02
Greater utilisation
Larger enrolments use that foundation more fully.
- 03
Lower marginal rate
The benefit returns to the institution.
Marginal rate per student
Enrolment →
Shared platform foundation — constant across every band
Pricing uses progressive, volume-based student bands. The chart shows the direction of the marginal rate as enrolment grows — the bands themselves are set out in your proposal.
What shapes the proposal
The inputs we establish during institutional discovery.
A proposal is only useful if it reflects the institution as it actually operates. These are the dimensions mapped before commercial terms are issued.
Active student count
The billable enrolment basis for the term.
Number of campuses
Single campus, group, or trust hierarchy.
Workflows selected
Which operational areas move onto the platform.
Migration volume and data quality
How much history moves, and in what state.
Integrations
Accounting, identity, payments and existing institutional systems.
Deployment profile
Managed cloud, private cloud, or on-premises.
Support and SLA requirements
Response expectations and escalation structure.
Governance and approval depth
Approval chains, policy controls and audit expectations.
AEGIS usage
Whether governed intelligence is in scope, and at what depth.
Communication and storage requirements
Messaging volume and document retention.
Exact commercial terms are issued after a short institutional discovery.
Begin discoveryCost transparency
No hidden subsidies. No surprise implementation bill.
Some dimensions vary far too much between institutions to be averaged into a licence. They are scoped independently and quoted openly, so the annual commitment stays predictable.
Data and migration
- Legacy data migration
- Historical data cleaning
- Bespoke reporting
Engineering and deployment
- Custom integrations
- Private-cloud deployment
- On-premises deployment
- White-label Android and iOS appsOne-time
Identity and federation
- SCIM 2.0 provisioning and deprovisioning
- Additional Microsoft Entra ID tenants
- SAML or non-Microsoft identity providers
- Identity migration
Implementation and support
- Premium implementation services
- Premium support SLA
Metered third-party usage
- SMS and WhatsApp usagePassed through
- Payment-gateway chargesPassed through
- Excess storageMetered
- Unusually high AEGIS usageMetered
Each of these is quoted as a distinct line in the proposal. Metered third-party usage — messaging, payment gateways, storage — is passed through rather than marked into the licence.
The SquareCampus parent and staff mobile apps are included in every plan at no additional licence charge. Only white-labelled Android and iOS builds published under the institution's own branding carry a one-time charge.
Design-partner pilot
The lowest-risk way to establish evidence before committing.
A pilot is a measured operational exercise, not a trial account. It runs on a written baseline and closes against an agreed metric.
60–90 days
Convert, extend or stop — decided on evidence.
One campus or one workflow bundle, implemented with founder-level involvement, and closed against the baseline written down at the start.
- Scope
- One campus, or one agreed workflow bundle.
- Measure
- One agreed success metric, written down before the start.
- Ownership
- Founder-led implementation, with a written baseline.
- Close
- Measured against the baseline — then convert, extend or stop.
Procurement questions
The commercial questions institutions ask before signing.
Answers here describe how the model works. The signed order form governs the specific terms for your institution.
Why are exact prices not published?
The annual licence is calculated from student volume, the selected plan, institutional complexity and the deployment profile. A published figure would be wrong for most institutions in both directions, so SquareCampus issues a written proposal after discovery instead.
How is student count determined?
Billable enrolment is agreed in the order form using active enrolled records. Growth may be reconciled through an agreed true-up mechanism, while reductions are normally considered at renewal. The signed order form governs in every case.
Does the marginal rate decrease at larger volumes?
Yes. Pricing uses progressive, volume-based student bands, so the marginal per-student rate reduces as enrolment grows. Larger institutions receive the benefit of platform economies of scale rather than paying the entry rate indefinitely.
Can we keep our existing ERP during the pilot?
Yes. A design-partner pilot is deliberately scoped to one campus or one workflow bundle so the existing system keeps running alongside it. There is no compulsory rip-and-replace before the institution has evidence.
Is migration included?
Legacy data migration and historical data cleaning are scoped separately from the annual licence, because the effort depends entirely on how much history moves and what condition it is in. The scope and its commercial treatment are agreed in the proposal.
Can SquareCampus run in our cloud account?
Private-cloud and on-premises deployment are available under Enterprise, subject to scoping. Deployment profile is one of the inputs to the proposal, and the resulting responsibilities are set out before implementation begins.
Is the mobile app charged separately?
No. The SquareCampus parent and staff mobile apps are included in every plan at no additional licence charge. A white-labelled Android and iOS build — published under your institution's own branding and store listings — is a separately scoped one-time charge.
Does Microsoft SSO use our institution's existing accounts?
Yes. Enterprise customers can authenticate staff through their own Microsoft Entra ID tenant. Their institution continues to control identity policies such as MFA and Conditional Access, while SquareCampus controls campus, role, record and workflow permissions.
Does SquareCampus access our Outlook or Microsoft 365 data?
No. Standard Microsoft Entra ID SSO is used to authenticate identity. Access to email, files, Teams, SharePoint or other Microsoft Graph data is not required for basic sign-in.
Does SSO automatically create and remove users?
SSO authenticates users. Automated user provisioning and deprovisioning require a separately configured lifecycle-integration capability such as SCIM, which is scoped as an Enterprise service rather than included by default.
Can a trust use more than one Microsoft tenant?
Enterprise includes Microsoft Entra ID SSO for one approved institutional tenant. Multiple Entra tenants can be supported as an Enterprise federation requirement and are scoped during technical discovery.
Is GST included?
Quoted commercial figures are exclusive of applicable taxes unless the proposal states otherwise. Applicable Indian taxes are shown on the order form and invoices.
How is AEGIS usage handled?
AEGIS availability depends on the plan, and governed usage is part of the scoping conversation. Ordinary institutional use is covered by the plan; unusually high usage is treated as a separately scoped, metered dimension so it never distorts the base licence.
Can a trust contract cover multiple campuses?
Yes. Enterprise is built for trust and campus hierarchies, and a single trust-level agreement can cover multiple campuses with central policy and local accountability. Campus coverage is defined in the order form.
What happens if enrolment changes during the year?
Material growth is reconciled through the true-up mechanism agreed in the order form. Reductions are normally considered at renewal rather than mid-term, so the institution has a predictable annual commitment.
Next step
Price the institution you operate — not a generic software package.
Bring your campus structure, student volume, the workflows in scope, the migration you are carrying and the governance your board expects. We map them, then issue a written proposal against that reality.
If an institution only needs a conventional attendance, fee and report-card system, SquareCampus will look expensive. It is priced for institutions that want operational command, measurable ownership and leadership visibility.