There are two pieces of software almost every university buys. The first is the management system, applications, offers, enrolment, records, fees, transcripts. The second is the learning platform, courses, lessons, assignments, quizzes, discussions, gradebooks. For at least two decades the industry has treated these as separate procurements, separate vendors, separate contracts, and separate teams to call when something breaks.
It is not a small seam. The student lives in one system, the course they are enrolled in lives in another, the grade for that course is captured in a third, the transcript that publishes the grade is generated by a fourth. So a number, a grade, a credit, a status, has to travel between systems every time it changes. The standard answer is an integration project. Sometimes it ships, often it does not, almost always it is brittle. We have replaced enough of those projects to be confident the seam is the source of the cost.
What the seam actually costs
When you treat the management spine and the learning platform as one product, three lines on the operational P&L collapse into nothing.
- › Integration maintenance, typically a permanent half-FTE plus an outside contractor every renewal cycle.
- › Two procurement cycles, two security reviews, two vendor renewals, twice the audit, half the leverage.
- › A category of bugs that lives only in the gap (mismatched gradebooks, mis-enrolled cohorts, transcripts that disagree with the registry).
"The seam between your management system and your learning platform is the most expensive twenty centimetres of fibre you will ever own."
A registrar we know
What "one product" actually means
It is not a single page tree. It is a single data model with two surfaces, the registrar's desk and the lecturer's gradebook, and a single team responsible for both. The implementation is uninteresting; the consequence is everything. A grade entered in the gradebook lands on the transcript live. A withdrawal from a course updates the official record live. The financial statement, the regulatory return, and the academic transcript all draw from one source.
The objection we hear most
Procurement officers ask, fairly, whether buying the two together creates lock-in. We separate the management contract from the learning contract on paper, even though it is one codebase. Either half can be replaced without ripping out the other. The integration tax does not come back when one half changes; it never returns at all, because there is nothing to integrate.
What we will publish next
Over the next quarter we will write about the deployment story, the multilingual rollout (multi-locale is a content problem, not a translation one), and the procurement cycle itself (five clauses that decide what your next five years feel like). The throughline is the same: the most expensive part of higher-ed software is the part nobody knew they were paying for.