For Institutions

After-hours help for every student on your roll

One pooled token budget, your branding, your identity provider, and dashboards that show teachers where a cohort is failing before the test does.

Why institutions choose it

Built for a cohort, not a single learner

  • Every student gets after-hours help

    One pooled token budget covers the whole cohort, so support doesn't stop when the timetable does.

  • Built for school data rules

    Role-based access, regional data residency, retention controls and a signed DPA on request.

  • Drops into what you already run

    SSO with Google Workspace or Microsoft Entra, LTI 1.3 into your LMS, and rostering via CSV or API.

  • Visibility for teachers

    Class-level dashboards showing which topics the cohort is failing before the test tells you.

  • Your name on it

    Custom subdomain, your logo and colours, and lesson templates matched to your syllabus.

  • A real person on the account

    Onboarding for staff, a dedicated success manager, and an uptime SLA in the contract.

Budgets

One pooled budget, spent where it's needed

Institutions don't buy per-seat allowances. You buy a pooled token budget for the cohort. Students draw from the same shared balance according to need instead of leaving fixed individual allowances unused.

  • One shared token balance across the whole cohort
  • Per-class or per-year-group caps so one cohort can't drain the pool
  • Usage reporting by class, subject and topic, exportable each term
  • Top the pool up mid-term, or roll unused budget into next term

Worked example

A 200-student prep centre

  • Students200
  • Illustrative monthly token budget30,000 tokens
  • Average starting allocation150 tokens per student
  • Billing structureOne shared pool

In practice usage is uneven: roughly a third of students use most of the pool. We size the first term from your own numbers and adjust at the termly review, so you aren't prepaying for identical per-seat allocations that nobody uses.

Rollout

From first call to full deployment

Most institutions go live within four to six weeks, starting with a single department.

  1. 1

    Scoping call

    We size your cohort, subjects and expected usage, then propose a pooled token budget.

  2. 2

    Pilot with one department

    A four-week pilot with a single class or faculty, with usage and outcome reporting at the end.

  3. 3

    Roll out

    SSO, rostering and branding configured, staff trained, students onboarded in a single session.

  4. 4

    Review each term

    Termly review of usage, mastery movement and budget with your success manager.

From the field

What partners say

  • We run a 200-student prep centre. Pooled tokens meant we could give every student after-hours help without hiring six more tutors.

    TATunde A.Director, Crestpoint Prep
  • I homeschool three children at three levels. The weekly report tells me exactly where each one is stuck, which is the thing I was always guessing at before.

    MHMrs. Halima B.Homeschooling parent
  • The replay is the part I didn't expect to need. Two weeks before mocks I went back through eleven saved boards instead of re-reading notes I didn't understand the first time.

    ENEmeka N.A-Level student, Abuja

Book a scoping call

Tell us the size of the cohort and the subjects that matter, and we'll come back with a token budget, a pilot plan and a price, usually within two business days.

  • 30 minutes, no deck
  • A four-week pilot proposal you can say no to
  • Signed DPA and sub-processor list on request

Prefer email? institutions@santitutor.com

We'll only use these details to respond to your enquiry. See our Privacy Policy.

Give the whole cohort a tutor

Pooled budgets, your branding, and a success manager who knows your timetable.