Universities,
engineered across the estate.
Student information systems, admissions and enrolment, research administration, campus life and institutional analytics, integrated across faculties that have each bought their own software for twenty years.
What a university platform is held to.
Universities are judged on recruitment, retention and research income, and every one of those depends on systems that were bought separately. These are the numbers we design against.
- 10–20%
- Retention uplift
- Clearing-grade
- Peak load
- 6–10
- Weeks
- GDPR + FERPA
- Native
Typical outcome on well-evaluated early-alert and support programmes
Engineered for the few days that decide an intake
To first release on a scoped admissions or student-journey slice
Student and research data governance engineered from day one
The institutions we build for.
A research-intensive university, a teaching-led college and a multi-campus group are different operating models with different constraints. We tailor the work to the one you run.
Research-intensive universities
Research administration, grant lifecycle, costing, compliance and output reporting alongside the student estate.
Teaching-led universities & colleges
Recruitment, progression and employability as the central concerns, with lean professional-services capacity.
Multi-campus & federated groups
Shared spine with local autonomy, across campuses that may sit in different jurisdictions and funding regimes.
Business & professional schools
Executive education, cohort management, corporate relationships and distinct admissions economics.
Medical & health faculties
Placement management, clinical partnerships and regulated programme requirements with their own data duties.
Online & distance provision
Fully remote delivery where the platform is the campus, engineered for scale and for engagement at distance.
Services we deliver into higher education.
University engagements usually begin with one visible problem and quickly become an integration problem. These are the practices we most often deploy, each linked to its dedicated page.
The university estate we engineer end to end.
The institutions that pull ahead stop treating admissions, teaching, research and advancement as four unrelated software estates and start running them against one model of a person.
- 01Student information & records
- Enrolment, programme structure, module registration, grading, progression and transcripts as the institutional spine.
- 02Admissions & enrolment
- Prospect through to enrolled student as one connected journey, with CRM, communications, offers and yield analytics.
- 03Learning & assessment
- LMS surfaces, assessment, academic integrity and outcome reporting integrated with the record rather than beside it.
- 04Research administration
- Grant lifecycle, costing and pricing, ethics, outputs and compliance reporting engineered as a connected system.
- 05Campus life & student support
- Timetabling, accommodation, wellbeing, library and support services on surfaces students will actually open.
- 06Advancement & alumni
- Alumni records, giving, events and engagement built on the same person model as the student estate.
Programmes delivered in this sector.
What clients ask us first
01Our faculties have all bought different systems. Where do we start?
Not with a consolidation programme. Start by agreeing one authoritative model of a student and one of a staff member, then integrate the highest-value faculty systems against it while leaving the rest alone. That gives the institution reliable reporting within months rather than years, and it turns later consolidation into an optional commercial decision rather than a prerequisite. Big-bang estate replacement is where university IT budgets go to die.
02Modernise the SIS or replace it?
By institution, on evidence. Modernisation wins where the incumbent holds the record dependably and the constraint is agility: APIs, modern surfaces and analytics land value in months. Replacement wins where the incumbent has drifted from how the institution now operates, or where a merger warrants a single spine. Either way cutovers are rolling, reconciled and reversible. We will give you the honest read before you commit.
03How do you handle clearing and enrolment peaks?
As an engineering problem with a known date. Load profiles are modelled on your actual historic traffic, not on a generic curve. The system is tested against them well before the window. Error budgets tighten for clearing and results days, and we agree in advance what degrades gracefully if the ceiling is hit. Institutions that trade cleanly through clearing are the ones that engineered for it in spring.
04Where does AI genuinely earn its place?
In early-alert and progression models where the signal is real and the evaluation is honest, in student-support assistants grounded in your own regulations and content, in feedback and marking assistance with staff in the loop, and in admissions triage. Model governance and human oversight are engineered in every case, because this is a domain where a confident wrong answer affects someone's degree or their visa status.
05How do you handle research data governance?
Separately from student data, because the obligations are different. Research data carries funder conditions, ethics approvals, embargo periods, export-control considerations and in some cases patient-level confidentiality. Those controls are modelled explicitly rather than folded into a general permissions scheme, and the evidence a funder or auditor asks for is generated by the system rather than assembled by hand afterwards.
Let's discuss your university programme.
Tell us about the institution, the systems you run and the outcome you are chasing, whether that is recruitment, retention or getting one reliable set of numbers. We will arrange a conversation with the relevant practice leadership.