---
title: "Founding Institutional Partners | SquareCampus"
description: "A measured, founder-led programme for schools, school groups and education trusts that want to shape SquareCampus against a real operating bottleneck."
canonical: https://squarecampus.com/launch-partners/
describedby: https://squarecampus.com/llms.txt
---

Founding institutional partner programme

# Build the School OS with us—against a real institutional problem.

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.

[Discuss founding partnership](https://squarecampus.com/demo/?intent=founding-partner) See the 60–90 day pilot

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.

**Positions**

Two, ever: one school, one university

**Window**

60–90 days

**Scope**

One campus or one workflow bundle

**Close**

Convert, extend or stop

The programme, precisely

## Two Founding Institutional Partner positions. Then the programme closes.

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

1. One school or eligible school institution

2. One university

Once both positions are allocated, the Founding Institutional Partner programme closes permanently.

What a Founding Partner receives, under the executed agreement

**Defined roadmap influence**

Structured, written consideration of the partner's operating requirements in roadmap planning, as defined in the executed agreement.

**Protected 40% Enterprise discount**

A protected 40% discount on Enterprise commercial terms, as set out in the executed agreement.

**White-labelled mobile apps**

The SquareCampus parent and staff apps published under the institution's own branding and store listings, without the standard white-label charge.

**Other agreed founding privileges**

Any further privileges are those explicitly agreed in the executed agreement, and no others.

What founding status is not

- Roadmap influence is not a veto, ownership of the roadmap, product or architectural control, ownership of intellectual property, or an entitlement to unlimited custom development.

- SquareCampus retains final product, architecture, security and engineering authority unless a signed agreement explicitly states otherwise.

- Founding status does not create exclusivity or territory rights.

- Entitlements are governed by the executed agreement. This page describes the programme; it is not an offer.

What founding status changes

## Ordinary customers buy the platform. Founding Partners help shape how it reaches the institution.

Three pillars, not a wall of feature cards. Each one is bounded by the executed agreement.

### Better execution

The implementation is run, not handed over.

- Founder-led institutional discovery

- A named implementation counterpart

- Parallel validation with current systems

- Scoped migration and integration planning

- Peak-cycle capacity planning and escalation

### Better economics

The commercial structure is agreed up front and holds.

- A protected 40% discount on Enterprise commercial terms under the executed agreement

- White-labelled Android and iOS apps under the institution's own branding, without the standard white-label charge

- Clearly bounded implementation and digital-campus allowances

- No hidden module wall or surprise pass-through markup

### Better influence

The institution's operating reality reaches the roadmap.

- Defined roadmap influence under the executed agreement

- Material participation in product validation

- Early access to selected capabilities

- Written consideration of major workflow proposals

- Direct operating feedback with Fairhelm leadership

The managed digital campus

## Your public digital estate can run with the same operational discipline.

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.

- Group and campus websites

- Admissions and campaign microsites

- Enquiry forms connected to institutional workflows

- Managed hosting, SSL, CDN and backups

- Role-controlled publishing for campus teams

- English/Hindi content support where required

- Analytics, performance and accessibility foundations

- Domain and institutional content ownership retained by the school

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

## Start with evidence. Expand only when it earns the right.

Four stages. Each one has to produce something the next stage can be judged against.

### Diagnose

Choose one operating bottleneck whose current cost, delay or ownership problem can be observed.

### Baseline

Write down the workflow, accountable owners, starting position and one success measure before implementation begins.

### Run the pilot

Deploy one campus or one agreed workflow bundle for 60–90 days, with named counterparts and parallel validation where needed.

### Decide on evidence

Convert, extend or stop against the agreed measure. If it works, expand through the protected founding-partner commercial structure.

60–90 day pilot

The same sequencing, migration discipline and parallel validation described on the [rollout page](https://squarecampus.com/rollout/), run with founder-level involvement.

Paid, scoped engagement

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 second Founding Partner position is reserved for a university.

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.

[Read the higher-education lane](https://squarecampus.com/launch-partners/higher-education/)

Who should apply

## Designed for institutions willing to participate, not merely observe.

Founding partnership asks for something from the institution as well. These are the signals that a pilot will produce usable evidence.

Good-fit signals

- A principal, trustee, director or group leader will act as executive sponsor

- There is a real workflow bottleneck that leadership wants to measure

- Campus teams can participate in discovery and weekly implementation reviews

- The institution can provide legitimate exports or process documentation needed for the agreed scope

- Leadership wants a multi-year operating relationship if the pilot succeeds

- The institution is prepared to make a strategic capital commitment under a separately executed agreement

- The institution values governance, accountability and cross-campus visibility—not merely a cheaper attendance app

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.

[How the licence is composed](https://squarecampus.com/pricing/) · [Review the trust posture](https://squarecampus.com/security/)

Before you commit

## The questions a board asks before it says yes.

None of these have flattering answers, so here are the accurate ones.

### You are a new company. Why would we depend on you?

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.

### What happens if the pilot fails?

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.

### We cannot afford disruption during admissions or fee cycles.

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.

### Who actually does the work?

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.

### Who owns the data, and can we get it out?

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.

### What does it cost to find out?

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.

### What does a Founding Partner actually receive?

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

## Bring one bottleneck. We will map the operating path around it.

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

[Discuss founding partnership](https://squarecampus.com/demo/?intent=founding-partner) · [Review rollout and trust](https://squarecampus.com/rollout/)
