A serious conversation about admissions systems in schools
When a school evaluates admissions systems, they often look towards platforms that are widely used by corporates and large organisations.
On the surface, that makes sense. These platforms are powerful, proven and feature-rich.
But here’s the catch: those platforms were built for corporate sales pipelines, not schools.
And that distinction matters.
Admissions is not simply a sales pipeline. It is the formal intake into a highly structured academic institution defined by year groups, academic progression, reporting cycles, and internal coordination.
If a system does not understand that structure, the school must adapt around it. That’s where strain begins.
This article does not dismiss platforms like Salesforce or HubSpot. Both are powerful in their own domains. But we’re offering a challenge to their use within a school context.
The real question is not whether a system can manage a pipeline.
It is whether it understands how a school actually works.
Get Your ChatGPT Admissions Cheat Sheet
The structural argument: schools are not linear organisations
On paper, admissions looks linear.
Enquiry → Application → Offer → Enrolment.
That sequence maps neatly onto CRM logic. Which is why platforms like Salesforce and HubSpot are so often shortlisted.
But this framing is misleading.
The admissions journey itself is not linear.
There is constant movement back and forth. For example, parents submit documents at different stages, additional information is requested, offers are conditional, applications pause and restart, internal reviews move between departments, and decisions evolve as context changes.
In other words, admissions is iterative. It requires flexibility and structured adaptability.
And then enrolment happens, further expanding that complexity.
Students enter:
- Academic year groups
- Houses
- Classes and sets
- Pastoral systems
- Reporting frameworks
- Progression pathways
Admissions is not the end of a pipeline. It is the beginning of a student’s life inside a highly structured system.
And here is the core issue:
General CRMs are built to manage commercial pipelines. They assume forward momentum through defined stages.
Schools don’t operate that way.
They operate through cohorts, progression, layered oversight, and structured coordination across departments.
An admissions platform must therefore do two things simultaneously:
- Adapt to a non-linear journey
- Remain structurally native to the logic of a school
When a system is not designed with that dual reality in mind, schools compensate through configuration, workaround, and manual intervention.
And that gap has consequences.
Salesforce: powerful, but structurally misaligned for schools
Let’s be clear.
Salesforce is an effective platform. It is flexible, scalable, and capable of modelling almost any business process imaginable.
And for many schools, that very flexibility is what makes it attractive.
There is a natural assumption — particularly in well-resourced institutions — that complexity signals capability. That a system powerful enough to model global enterprises must surely be the most “serious” choice for admissions.
In theory, that logic holds, but in practice, it is more complicated.
Salesforce does not arrive with a view of how admissions should function inside a school. It requires the institution to define and configure that structure themselves.
In enterprise environments with dedicated CRM teams, that model can work well. Where there is in-house technical capacity and ongoing budget for configuration and optimisation, Salesforce can be shaped to fit.
But schools are not enterprises in the commercial sense. Even the largest and most prestigious international schools operate with different structural rhythms and resource realities.
What we repeatedly observe — including in conversations with some of the largest and best-resourced international day and boarding schools — is that even when budget is not the constraint, alignment is.
The admissions team becomes dependent on system administrators, external consultants, bespoke configuration, and ongoing translation between CRM logic and school logic.
And here is the critical friction point:
Salesforce is often too complex for staff on the ground.
Admissions professionals, on the whole, are not CRM architects. They are relationship managers, organisers, communicators, and coordinators.
When a system becomes heavily customised, field-heavy, permission-layered, and dependent on technical oversight, confidence begins to erode.
Adoption falters at campus level - cognitive load on frontline staff becomes too high. This fragility becomes particularly exposed when staff change. In schools with higher turnover, heavily customised systems can be difficult for new team members to navigate. What took months to configure and refine can take months to relearn.
As a result, the pattern is familiar:
- Shadow spreadsheets reappear
- Partial adoption becomes normalised
- Reliance grows on a single “Salesforce expert”
- Distance increases between system design and daily use
The system works in theory, but in practice, it becomes brittle. And brittleness, in a school environment, carries risk.
HubSpot: elegant, but built for marketing logic
HubSpot presents a different proposition. It is intuitive. It’s clean. It’s well-designed. And it’s strong on communication.
In many schools, its appeal is immediate.
Often there is someone internally — perhaps a Director of Marketing, Advancement lead, or even a senior leader who has come from a non-educational background — who has used HubSpot before and is comfortable with it. That familiarity lowers perceived risk. It feels known. It feels manageable.
And for marketing-led admissions environments, particularly where enquiry generation and communication cadence are the primary concerns, HubSpot can be highly effective.
It understands leads, lifecycle stages, campaign tracking, and communication workflows.
Where the structural tension begins to surface is further down the admissions journey.
HubSpot does not inherently understand:
- Academic intake structures
- Conditional offers
- Documentation workflows with layered review
- The internal choreography between admissions and academic leadership
As application complexity increases, schools often begin extending HubSpot beyond its natural centre of gravity.
Custom fields multiply. Pipelines become more intricate. Workflows grow longer. Internal processes are adapted to fit CRM logic rather than the other way around.
The system becomes workable.
But it requires stretching.
And the more a platform is stretched beyond its native design, the more ongoing effort is required to maintain alignment.
The compounding problem: system layering
This is where the discussion becomes strategic rather than tactical.
When a general CRM is used for admissions, and a separate MIS such as iSAMS is used for enrolled students, the school now operates across:
- A CRM for enquiries
- An MIS for academic structure
- Manual bridges between the two
Each additional layer introduces:
- Duplication risk
- Reconciliation effort
- Integration dependency
- Human workaround
That’s not to say this model cannot function. It just doesn’t function elegantly. And elegance matters in schools, because complexity compounds over time.
OpenApply: structurally native to schools
OpenApply begins from a different premise.
It assumes that admissions is not merely a sales process. It is a structured academic intake process.
It understands that:
- Admissions must reflect cohort logic
- Communication must align with institutional rhythm
- Documentation and review must be visible internally
- Enrolment is not an endpoint but a transition into school life
Because of that starting point, OpenApply requires less bending.
Less translation.
Less configuration to mimic school logic.
It is not trying to be a universal CRM. It is deliberately opinionated about admissions in schools.
And that opinionation is a strength.
It means:
- Workflows reflect educational reality
- Staff adoption is higher
- Reliance on technical specialists is lower
- System sprawl is reduced
Admissions teams can focus on families, not system architecture.
Conclusion
If this were simply a question of feature depth, Salesforce might just take the lead.
If it were purely a question of marketing elegance, HubSpot would compete strongly.
But admissions in schools is neither a generic enterprise sales function nor purely a marketing funnel.
It is a structurally embedded academic process.
And when you evaluate systems through that lens, the question changes.
It is no longer “Which platform is most powerful?”
It becomes:
Which platform understands the internal logic of a school without requiring us to recreate it ourselves?
In that conversation, OpenApply is not simply a viable option. It is the platform built for the job.
If you’re interested in how OpenApply can enhance your admissions process, schedule a demo with one of our experts today.