Founding institutional partners · Higher education
Private universities and multi-school groups rarely lack software. They run an ERP, an LMS, one or more payment portals, an identity provider and several communication channels — and lose weeks in the gaps between them, where a case is stalled, unowned, and visible to nobody until someone escalates. SquareCampus is the governed layer across that space.
Runs alongside your existing ERP, LMS, payment and identity systems · One bounded workflow · Paid, scoped pilot
The 60–90 day evidence model
One bounded workflow, a written baseline, and a decision taken against evidence.
What this is, precisely
It is worth being exact about this before anything else, because the wrong expectation wastes both sides' time.
What it is not
What it is
Where a pilot starts
Each one is bounded, already measurable today, and does not require switching off anything the institution depends on.
01
Applications that clear one stage and stall at the next — document verification, fee confirmation, seat allocation, registration. The exception gets an owner and a position instead of living in an inbox.
02
Payments that succeed at the gateway and do not land cleanly against the record. The mismatch is raised as an exception, routed, and closed with a recorded reason rather than reconciled by hand at month end.
03
Requests that cross academic, finance, registry and administrative boundaries and lose their owner at each handover. Latency becomes visible while it is still recoverable.
04
A current view of one workflow — what is open, who owns it, what is overdue and what was decided — without a department preparing a deck for it.
05
Administrative and operational workflows outside clinical and hospital systems, where a decision needs a recorded reason and an auditable close.
Explicitly out of scope
Clinical and hospital information systems are outside the suggested pilot scope. Where an institution operates a teaching hospital, the pilot is scoped to non-clinical administrative workflows only, and SquareCampus makes no medical, patient-care, accreditation or regulatory claim.
How it sits
During the pilot the institution's ERP, LMS, payment portals, forms and identity provider stay exactly where they are and stay authoritative. SquareCampus governs the workflow that runs across them.
The ERP or SIS remains the record. SquareCampus does not ask to become it, and does not require a migration to start.
A case is tracked from the event that starts it to the decision that closes it, regardless of how many systems it touches on the way.
Every open exception has a named accountable owner and a position. Nothing sits in a shared mailbox waiting to be noticed.
Approvals, overrides and refusals land on an append-only timeline with the reason attached, scoped to the role that took them.
A later rollout may replace selected fragmented tools, when and if the institution decides to. That is a separate decision, taken after the evidence exists — never a precondition of the pilot.
The 60–90 day evidence model
The same sequencing, migration discipline and parallel validation described on the rollout page, scoped to one university workflow.
01
One workflow, or one non-clinical constituent school or department. Not the institution, and not a phased programme dressed up as a pilot.
02
The current position — volumes, delays, ownership gaps — written down before implementation, so the result is measured rather than argued.
03
A Registrar, Dean, Finance lead, COO or CIO who owns the outcome internally and can convene the people the workflow crosses.
04
Anything finance or registry teams must trust runs alongside the existing process until the numbers agree.
05
Judged against the measure agreed at the start. Stopping is a published outcome, not a failure state we argue you out of.
Founding pilots are paid, scoped commercial engagements. Scope, success measures, fees and conversion terms are agreed in writing before implementation begins. How the licence is composed and how a rollout runs.
Who this has to convince
A pilot at a university needs several people to agree. They are not agreeing to the same thing.
President / Vice Chancellor
One bounded workflow stops arriving as an escalation and starts arriving as a current position. The pilot is small enough to stop and specific enough to judge.
Registrar
It governs the ones you already run. The registry keeps its system of record; what changes is that a stalled case has an owner and a position instead of a follow-up email.
Dean / Academic leader
No. The scope is administrative and operational workflow — where a case is, who owns it, and whether a decision was recorded. Academic decisions stay with the people who make them.
Finance leader
Mismatches between payment success and the record become routed exceptions with a recorded closure, and run in parallel with the existing process until finance trusts the numbers.
CIO / IT leader
Scoped to the workflow in the pilot, agreed in writing before implementation, and read-oriented where the existing system stays authoritative. Access is role-scoped and exports are available in standard formats throughout.
One position
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.
The first conversation
A 30-minute diagnosis of one workflow: where it stalls, who should own it, what a bounded pilot would cover, and whether the university Founding Partner position is the right fit at all.
No commitment · 30-minute institutional diagnosis
