Skip to main content
Start projectENFR

People and education / Recruitment and learning

Digital systems for business school businesses

Operloom builds the operating system behind a business school: how an enrolment enquiry arrives, how it becomes a enrolment, and how anyone can tell afterwards what actually happened.

SMERecruitment and learningScheduled workOnline payment

Demand arrives from two sides at once, with clients and candidates needing different journeys. The system has to be ready for it in the same shape it arrives in.

Primary conversion: Enquiry, campus visit, assessment or enrolment

01B2B SME

The business reality

These are the recurring constraints for a business school. Each one has a system consequence, which is what the implementation is scoped against.

Long application cycles

It tends to hold until volume rises. At that point the informal version stops working and nothing has replaced it.

Manual document collection

None of this is unusual for a business school, which is exactly why it goes unaddressed for so long.

Fragmented communications

Students tend to notice this before the business does, even if nobody inside would describe it as a problem yet.

Weak attribution

The cost is rarely dramatic. It is a small amount of lost time and lost context on every enrolment, repeated all year.

02B2B SME

CRM, pipeline and lead routing

The CRM holds prospects, learners, parents, employers, programmes, applications and enrolment stages. Configured around how the work is actually run, rather than around the default pipeline the platform ships with.

Records

Each student exists once, with the history attached rather than scattered across inboxes.

Lifecycle

A lifecycle short enough that people update it, which is the only kind that stays accurate.

Pipeline

A pipeline you can read in a minute, because the fields that nobody maintains are not on it.

Lead source

Source captured on the first touch, because reconstructing it later is guesswork.

Ownership

Somebody is responsible for every open enrolment, and the system knows who.

Tasks and follow up

The next action carried by the system rather than by memory.

Reporting

The measures a business school is run on, drawn from the same records the team works in.

Permissions

Role-based access, reviewed when people join and when they leave.

03B2B SME

The buying journey

The primary conversion for a business school is enquiry, campus visit, assessment or enrolment. Everything below is arranged around getting there without losing people, and around knowing afterwards where they went.

  1. 01

    Discovery

    A student finds the business from two sides at once, with clients and candidates needing different journeys.

  2. 02

    Evaluation

    They check whether this is the right business for them. This is what sector specialism, speed and the quality of the shortlist is for.

  3. 03

    Enquiry

    They send an enrolment enquiry. The form asks the questions that decide whether it can be scoped, and nothing else.

  4. 04

    Qualification

    The enrolment enquiry is routed and qualified against the criteria that actually predict a good enrolment.

  5. 05

    Booking

    A meeting is committed to a real slot, with the buffers and the preparation the work genuinely needs.

  6. 06

    Quote

    An estimate goes out with the scope written down, and its status is visible without anyone chasing it.

  7. 07

    Delivery

    The enrolment is delivered. What happened is recorded against the student, not in a separate note.

  8. 08

    Invoice

    An invoice is raised from the same record, so what was agreed and what was billed cannot drift apart.

  9. 09

    Repeat

    The next enrolment is prompted deliberately, on the cycle this kind of work actually runs on.

04B2B SME

Demand generation

Where attention comes from decides where effort goes. For a business school demand arrives from two sides at once, with clients and candidates needing different journeys.

Technical SEO

The foundations: crawlability, speed, structure and the markup that describes what this business is

Service search

Programme, subject, level, outcome, location and question led content

Local search

Core for physical campuses, schools, nurseries and training centres

Content

Answering what a student needs to know before they will make contact

Social

Student life, outcomes, faculty expertise and campaign content

Paid media

Search and social campaigns for programmes, intakes and open days

Reviews

Student, parent and employer reviews with appropriate consent

Landing pages

Campaign pages built from the same components, so they are fast to ship and consistent to measure

05B2B SME

Positioning, service and sector pages

For a business school the site is a working part of the system rather than a brochure in front of it. That changes what gets built.

ProgrammesAdmissionsSchedulesFacultyOutcomesFeesEventsResources and enquiry forms

06B2B SME

Automation

Each workflow below states what starts it, what has to be true, what it does, where a person stays in the loop and where the result lands. Automation without those five is just an undocumented side effect.

01Enquiry capture and routing
TriggerA student submits an enrolment enquiry on any page of the site
ConditionsThe submission passes validation and spam checks, and carries the page, campaign and referral it came from
ActionsCreate or match the student record, attach the source, apply the qualifying answers, assign an owner and start the response clock
Human reviewA person reads every enrolment enquiry before it is answered. Routing decides who, not what they say
DestinationCRM, with an internal notification to the assigned owner
Why it helpsNo enrolment enquiry sits unowned, and the source that produced it survives into the reporting
02Response and follow up
TriggerAn enrolment enquiry has been owned for longer than the agreed response window
ConditionsNo reply has been logged and the record is still open
ActionsEscalate to a second owner, raise a task and flag it on the daily view
Human reviewEscalation notifies a person. It never sends anything to the student on its own
DestinationTask queue and internal alert
Why it helpsSlow replies surface the same day rather than at the end of the month
03Payment and receipt
TriggerA payment succeeds or fails
ConditionsThe payment is matched to an open enrolment or order
ActionsUpdate the status, issue the receipt, release the next step and raise a task on failure
Human reviewFailed payments are worked by a person, not retried silently
DestinationPayment platform, finance system and CRM
Why it helpsPayment status is on the record rather than in a separate inbox
04Review request
TriggerA enrolment is marked complete
ConditionsThe enrolment completed without an open complaint, and the student has not been asked recently
ActionsWait the interval that suits this kind of work, then send a single request with a direct link
Human reviewSuppression rules are set by a person and applied automatically
DestinationReview platform and student record
Why it helpsReviews are requested consistently rather than when somebody remembers
05Confirmation and reminder sequence
TriggerA meeting is booked or rescheduled
ConditionsThe student has a valid contact method and has not opted out of operational messages
ActionsSend confirmation immediately, then reminders on the schedule this kind of meeting needs, each with reschedule and cancel links
Human reviewTemplates are approved once. Individual sends are automatic
DestinationEmail and messaging, logged against the student record
Why it helpsFewer missed meetings, and a cancellation that arrives early enough for the slot to be refilled
06Reporting refresh
TriggerThe reporting period rolls over
ConditionsSource data has loaded and reconciled
ActionsRefresh the dashboard, recalculate the measures that matter to a business school, and flag anything that moved beyond its usual range
Human reviewCommentary is written by a person. The numbers are not
DestinationDashboard and scheduled summary
Why it helpsThe same numbers every time, assembled the same way, so a change means something
07Quote to invoice
TriggerA quote is approved by the student
ConditionsScope and price are agreed and recorded on the enrolment
ActionsRaise the invoice from the agreed scope, set the payment terms, send it and track its status against the same record
Human reviewAnything outside the standard scope or discount range goes to a person first
DestinationFinance system and CRM
Why it helpsWhat was agreed and what was billed stay the same document

07B2B SME

Email and communication

The communication a business school sends is mostly operational rather than promotional, which is exactly why deliverability has to be right first.

Admissions nurtureRemindersLearner communicationsRenewals and alumni campaigns

08B2B SME

Proposals and invoicing

Money moves through the same records as the work. That is the whole point: what was agreed and what was billed cannot drift apart if they are the same document.

Request a quote

A student asks for pricing with enough detail attached to answer properly.

Approve an estimate

Approval is recorded against the scope it approved.

Pay a deposit

Where a deposit is how the work is committed, it is taken at that point.

Receive an invoice

Raised from the agreed scope, not retyped from it.

Pay online

Without a phone call, and reconciled automatically.

Access receipts

Available to the student rather than requested from you.

View payment status

Visible on the record, so chasing is informed.

09B2B SME

Booking and scheduling

The diary is the constraint. tours, interviews, assessments, consultations, lessons and events, and the system is built around protecting it.

Availability

Read from the real calendar, so double booking is not possible rather than unlikely.

Buffers

Preparation and turnaround built into the slot, because a meeting is not only the time with the student.

Qualification

The questions that decide whether the slot is right, asked before it is taken.

Reminders

On the interval this kind of work needs, each one carrying a reschedule link.

Rescheduling

A student can move a meeting without a phone call, which is how you find out early.

Cancellation

A clear policy applied consistently, with the slot released for rebooking.

Routing

To the right person and the right location, using rules rather than judgement.

Time zones

Handled properly wherever the work crosses them.

10B2B SME

The recommended operating system

Every one of these already exists in some form, usually as a tool somebody chose alone. The build is mostly about the lines between them.

The systems a business school connects, and where they meet. Every node is listed beside the diagram.
  1. 01
    Discovery Search, maps and campaigns

    Where a student first finds the business.

  2. 02
    Website Programme and enrolment website

    The pages a student reads before deciding to make contact.

  3. 03
    Forms Enrolment enquiry capture

    Qualifying questions asked once, at the point of enquiry.

  4. 04
    CRM Records and pipeline

    Every student, every enrolment and who owns it.

  5. 05
    Calendar Availability and buffers

    Real availability for a enrolment, with the preparation time it needs.

  6. 06
    Invoicing Quotes and invoices

    Estimates and invoices raised from the agreed scope.

  7. 07
    Payments Online payment

    Payment taken and reconciled against the record.

  8. 08
    Email Authenticated sending

    Operational and lifecycle messages that arrive and are logged.

  9. 09
    Automation Workflows and routing

    The rules that move work between systems, with human review where it matters.

  10. 10
    Portal Self service

    What a student can see and do without contacting anyone.

  11. 11
    Advertising Paid campaigns

    Campaigns tracked through to the record they produced.

  12. 12
    Analytics Measurement

    The measures a business school is actually run on.

  13. 13
    Internal alerts Ownership

    Who is told, when, and what they are expected to do about it.

11B2B SME

What Operloom builds

Scope is decided by what the operating model requires, not by what is available. Core is structural for a business school. Recommended follows shortly after. Optional depends on the year you are having.

16Core services
13Recommended
5Optional

Digital presence

2
  • Website build or redesigncore

    Website build or redesign supports business school businesses by helping to increase qualified enrolment

  • Service and landing pagescore

    Service and landing pages supports business school businesses by helping to increase qualified enrolment

Revenue operations

3
  • CRM setup and data modelcore

    CRM setup and data model supports business school businesses by helping to increase qualified enrolment

  • Pipeline and lifecycle designcore

    Pipeline and lifecycle design supports business school businesses by helping to increase qualified enrolment

  • Lead routing, scoring and follow uprecommended

Operations

2
  • Booking and appointment systemcore

    Booking and appointment system supports business school businesses by helping to increase qualified enrolment

  • Documents, forms and e signaturecore

    Documents, forms and e signature supports business school businesses by helping to increase qualified enrolment

Email

2
  • Email infrastructure and deliverabilitycore

    Email infrastructure and deliverability supports business school businesses by helping to increase qualified enrolment

  • Email campaigns, nurture and reminderscore

    Email campaigns, nurture and reminders supports business school businesses by helping to increase qualified enrolment

Measurement

2
  • Analytics and conversion trackingcore

    Analytics and conversion tracking supports business school businesses by helping to increase qualified enrolment

  • Dashboards and attributioncore

    Dashboards and attribution supports business school businesses by helping to increase qualified enrolment

Brand

2
  • Brand identity systemcore

    Brand identity system supports business school businesses by helping to increase qualified enrolment

  • Sales and marketing materialsoptional

Discovery

2
  • Technical and on page SEOcore

    Technical and on page SEO supports business school businesses by helping to increase qualified enrolment

  • Local SEO and Google Business Profilerecommended

Content

1
  • Content strategy and copywritingcore

    Content strategy and copywriting supports business school businesses by helping to increase qualified enrolment

Commerce

3
  • Online payments and depositscore

    Online payments and deposits supports business school businesses by helping to increase qualified enrolment

  • Memberships and subscriptionsrecommended
  • Ecommerce or online orderingoptional

Automation

2
  • Workflow automationcore

    Workflow automation supports business school businesses by helping to increase qualified enrolment

  • Practical AI assistants and workflowsoptional

Technology

2
  • Security, privacy and maintenancecore

    Security, privacy and maintenance supports business school businesses by helping to increase qualified enrolment

  • Platform integrations and APIsrecommended

Social

2
  • Social profile setuprecommended
  • Social media operationsrecommended

Acquisition

2
  • Paid search campaignsrecommended
  • Paid social campaignsrecommended

Finance operations

1
  • Quotes, estimates and invoicingrecommended

Trust

1
  • Reviews and reputation managementrecommended

Customer experience

3
  • Live chat, WhatsApp and messagingrecommended
  • Client, patient or customer portalrecommended
  • Help desk and service workflowsoptional

Events

1
  • Event, ticketing and registration systemrecommended

Scale

1
  • Multi location and franchise managementoptional

12B2B SME

Where better systems change something

Better systems do not guarantee a commercial result, and nobody should promise one. What they do is remove specific failure points. These are the ones that matter for a business school, and the measures that would show whether the change worked.

Retention

Making the second enrolment as deliberate as the first, rather than leaving it to whoever remembers.

Measure: Enquiries

Visibility

Being findable for the terms a student actually uses, rather than the ones the business uses internally.

Measure: Applications

Operational control

Being able to change how the work runs without needing the person who originally set it up.

Measure: Enrolments

Conversion

Removing the steps between interest and a committed enrolment, and making the next action obvious at every point.

Measure: Conversion

Administrative efficiency

Taking the repeatable parts of the enrolment out of somebody's head and putting them into a workflow that runs whether or not it is a busy week.

Measure: Source

Lead quality

Asking the qualifying questions at the point of enquiry, so the enrolment is scoped before anyone spends time on it.

Measure: Programme demand and retention

13B2B SME

Attribution and reporting

These are the measures worth reporting for a business school. Any figures shown in charts on this site are illustrative and labelled as such: we do not publish client data.

Enquiries

Reviewed alongside the stage it depends on, not in isolation.

Applications

Defined once and written down, so it means the same thing next quarter.

Enrolments

Tracked as a trend, because a single period rarely means anything.

Conversion

Broken down by source, so the number leads somewhere.

Source

Measured from the record rather than reconstructed at month end.

Programme demand and retention

Reviewed alongside the stage it depends on, not in isolation.

14B2B SME

How Operloom works

  1. 01

    Assess

    A short audit of the platforms, the data in them and the points where an enrolment enquiry stalls.

  2. 02

    Design

    Decisions made once, in writing, so the build is execution rather than a series of small arguments.

  3. 03

    Implement

    Built in the order that gets a business school value soonest, not the order that is tidiest to build.

  4. 04

    Connect

    Integrate the platforms so Student information system, learning platform, CRM, payments, calendar and email behave as one system.

  5. 05

    Document

    Workflow maps, field definitions, ownership and runbooks, written for the people who will use them.

  6. 06

    Measure

    Instrumented against enquiries, applications and enrolments, with the definitions agreed first.

  7. 07

    Improve

    Regular review with a small change list, judged against the baseline rather than against opinion.

15B2B SME

What you end up with

Concrete deliverables, not projected commercial results. What each one achieves depends on how it is used after handover.

Programme and enrolment websiteBrand and component system as requiredCRM configuration, pipeline and field definitionsBooking workflows, availability rules and reminder sequencesQuote and invoice templates linked to the recordPayment configuration and reconciliationAuthenticated email setup and lifecycle templatesAutomation workflows with documented review pointsTracking plan, event taxonomy and dashboardsSelf service area scoped to what is genuinely usefulIntegration configuration and failure handlingDocumentation, workflow maps and handover trainingLaunch support and an agreed review cadence

16B2B SME

Recommended package

Recommended starting scope

Education Enrolment and Operations

A starting scope rather than a fixed package. The plan page sets out who it is for, the core deliverables, the modules, the integrations and the measures.

Read the plan

Core measures

  • Enquiries
  • Applications
  • Enrolments
  • Conversion
  • Source
  • Programme demand and retention
Custom scope

Scope varies with what already exists, so we do not publish a figure. Tell us what you have and you will get a scoped proposal with the assumptions written down.

Support level
Agreed per engagement
Contract term
Agreed per engagement
Implementation
Agreed after scoping

Request a tailored proposal

17B2B SME

Typical integrations

The categories this operating model usually has to connect. Naming a category is not a claim of partnership, certification or reseller status.

Student information systemLearning platformCRMPaymentsCalendar and email

18B2B SME

Compliance, privacy and risk

Safeguarding, accessibility, consent, student data and education marketing rules.

We are implementers, not advisers. What we do is build the controls your obligations require once they are confirmed, and make them evidenceable. What we will not do is tell you what those obligations are.

19B2B SME

Frequently asked questions

Question: What does Operloom actually build for a business school?
Operloom replies:

The scope starts from how this kind of business runs rather than from a package. In practice that means programme and enrolment website, a CRM holding prospects, learners, parents, employers, programmes, applications and enrolment stages, and the booking and follow up around it. The nearest starting point in our catalogue is Education Enrolment and Operations, which is a scope to argue with rather than a fixed list.

Question: How do you handle the regulatory side?
Operloom replies:

Carefully, and within our lane. Safeguarding, accessibility, consent, student data and education marketing rules. We build to what your advisers tell us applies: consent capture, retention rules, access control, audit trails and secure handling. We implement requirements. We do not interpret them for you, and we will say so rather than guess.

Question: How does booking connect to everything else?
Operloom replies:

Availability comes from the real calendar, not a copy of it, so a enrolment cannot be booked into a slot that is already gone. Tours, interviews, assessments, consultations, lessons and events. Every booking writes back to the student record, so the diary and the pipeline are the same story.

Question: What do you need from us?
Operloom replies:

Less than most people expect, but not nothing. Access to the platforms, a decision maker who can settle scope questions in the same week they are asked, and someone who knows how the work really runs, which is rarely the same as how it is written down. Content and assets where you have them. We write what you do not.

Question: How long does an implementation take?
Operloom replies:

It depends on how much already exists and how clean it is. A build is sequenced so that something useful goes live early rather than everything landing at once: the CRM and enrolment enquiry capture first, because that is where work is lost today, then the site, then the automation, then reporting. We give a timeline after a scoping conversation, not before one.

Question: Our sales cycle is long. How do we tell whether any of this is working?
Operloom replies:

By measuring the stages rather than only the close. Source, enrolment enquiry quality, meeting rate, proposal rate and stage ageing all move long before revenue does, and they are the ones that tell you whether a change helped. Attribution is set up to survive a cycle measured in months rather than days.

Question: Can we keep the website and CRM we already have?
Operloom replies:

Often, yes, and it usually makes the project smaller. A maintainable site is better connected than replaced: enrolment enquiry capture that carries its source, tracking that survives, and a clean handover into the CRM. The CRM question is whether it can hold prospects, learners, parents, employers, programmes, applications and enrolment stages without being fought. If it can, we configure it properly. If it cannot, we say so and explain what migrating would actually cost you in time and disruption.

Question: What happens after launch?
Operloom replies:

You get the documentation, the workflow map and the training, because the point is that you own it. Ongoing support is a separate arrangement rather than an assumption: some businesses take a maintenance and improvement retainer, others take the handover and run it themselves. Both are fine, and we will tell you which one we think fits.

Talk through how this would work for your business school

The first conversation is a scoping one: what exists, what it costs to run, and what would have to be true for enquiry, campus visit, assessment or enrolment to happen more often. No obligation and no prepared deck.

Request a CRM and pipeline audit