Founding institutional partner programme
Founding Partners do not receive a generic beta account. We establish a baseline, deploy around one measurable operational bottleneck, validate the result with your team, and use that evidence to decide what should scale next.
Measured pilot · Founder-led implementation · No compulsory rip-and-replace
What a founding pilot is
One measurable bottleneck, a written baseline, and a decision taken against evidence.
The programme, precisely
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 two positions
Once both positions are allocated, the Founding Institutional Partner programme closes permanently.
What a Founding Partner receives, under the executed agreement
What founding status is not
What founding status changes
Three pillars, not a wall of feature cards. Each one is bounded by the executed agreement.
01
The implementation is run, not handed over.
02
The commercial structure is agreed up front and holds.
03
The institution's operating reality reaches the roadmap.
The managed digital campus
Where it is part of the agreed scope, Fairhelm can design, build and operate the institution's group website, campus websites and admissions microsites—connecting enquiries and forms to SquareCampus instead of leaving them in disconnected inboxes.
Site count, design system, page migration, traffic, storage and change allowances are defined in the proposal. The programme is not an unlimited creative-services retainer.
Partnership path
Four stages. Each one has to produce something the next stage can be judged against.
01
Choose one operating bottleneck whose current cost, delay or ownership problem can be observed.
02
Write down the workflow, accountable owners, starting position and one success measure before implementation begins.
03
Deploy one campus or one agreed workflow bundle for 60–90 days, with named counterparts and parallel validation where needed.
04
Convert, extend or stop against the agreed measure. If it works, expand through the protected founding-partner commercial structure.
The same sequencing, migration discipline and parallel validation described on the rollout page, run with founder-level involvement.
Founding pilots are paid, scoped commercial engagements. Scope, success measures, fees and conversion terms are agreed in writing before implementation begins.
The university position
The same 60–90 day evidence model applies, but the wedge is usually an exception queue between systems that already exist — admissions-to-enrolment, payment-to-ERP reconciliation, interdepartmental approvals — rather than a school's day-to-day operations.
Who should apply
Founding partnership asks for something from the institution as well. These are the signals that a pilot will produce usable evidence.
Good-fit signals
What founding status is not
Founding status does not create exclusivity, ownership of SquareCampus intellectual property, veto rights, product or architectural control, or an unlimited bespoke-engineering commitment. SquareCampus retains final product, architecture, security and engineering authority unless a signed agreement explicitly states otherwise. Exact entitlements are governed by the executed agreement.
Before you commit
None of these have flattering answers, so here are the accurate ones.
You would not — not at first. A pilot is scoped to one campus or one workflow bundle, runs alongside the system you already have, and is judged against a measure written down before it starts. The institution keeps its existing system throughout, and keeps its data in standard export formats regardless of what it decides at the end.
You stop. Convert, extend and stop are the three published outcomes, and stopping is not a failure state we argue you out of — it is the reason the baseline is written down first. You leave with the measurement, the process documentation and your data.
Neither can the pilot. Sequencing around admissions, fee deadlines, examinations and results is part of the rollout method, not an accommodation. Critical workflows run in parallel until finance and academic teams trust the numbers.
A named counterpart, with founder-level involvement in discovery and implementation. That is a consequence of there being only two founding positions, and it is one of the things a Founding Partner is trading for.
The institution does, throughout. Access is role-scoped and every approval and override lands on an audit timeline while you operate — and complete exports in standard formats are available if you decide to leave. That is the same posture the platform runs on, not a concession made for pilots.
Scope, success measure and commercial terms are agreed in writing before any work begins, so the cost is known before you commit rather than discovered afterwards. The first conversation is a 30-minute diagnosis and costs nothing.
Under the executed agreement: defined roadmap influence, a protected 40% discount on Enterprise commercial terms, white-labelled mobile apps without the standard white-label charge, and any other privileges explicitly agreed. Roadmap influence is structured input, not a veto or control over the product, its architecture or its intellectual property.
The first conversation
Tell us where visibility arrives late, ownership becomes unclear, or staff rebuild the same truth by hand. We will determine whether it belongs in a Founding Institutional Partner pilot.
No commitment · 30-minute institutional diagnosis
