Long application cycles
Left alone it becomes a reporting problem too: the record of what happened gets assembled afterwards, from memory.
People and education / Recruitment and learning
Operloom builds the operating system behind a exam preparation centre: how an enrolment enquiry arrives, how it becomes a enrolment, and how anyone can tell afterwards what actually happened.
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
These are the recurring constraints for a exam preparation centre. Each one has a system consequence, which is what the implementation is scoped against.
Left alone it becomes a reporting problem too: the record of what happened gets assembled afterwards, from memory.
It lands on the founder / operations director first, well before it shows up in any number.
Fixing it is rarely a tooling decision. It is a question of where the work is supposed to stop and who picks it up next.
Because a two-sided pipeline where supply and demand rarely peak together, this one compounds rather than staying still.
02B2B SME
What the CRM has to carry for a exam preparation centre: prospects, learners, parents, employers, programmes, applications and enrolment stages. Everything else is optional and usually a liability.
Each student exists once, with the history attached rather than scattered across inboxes.
A lifecycle short enough that people update it, which is the only kind that stays accurate.
A pipeline you can read in a minute, because the fields that nobody maintains are not on it.
Source captured on the first touch, because reconstructing it later is guesswork.
Ownership is explicit, so "I thought you had it" stops being a category of loss.
Follow up scheduled when the enrolment is created, not when someone remembers.
Reporting out of the working system, so the numbers and the work cannot disagree.
Access matched to role, which matters as soon as more than one person is involved.
03B2B SME
This is the route a student takes. Each step is a place where the system either holds the context or drops it.
A student finds the business from two sides at once, with clients and candidates needing different journeys.
They check whether this is the right business for them. This is what sector specialism, speed and the quality of the shortlist is for.
They send an enrolment enquiry. The form asks the questions that decide whether it can be scoped, and nothing else.
The enrolment enquiry is routed and qualified against the criteria that actually predict a good enrolment.
A meeting is committed to a real slot, with the buffers and the preparation the work genuinely needs.
An estimate goes out with the scope written down, and its status is visible without anyone chasing it.
The enrolment is delivered. What happened is recorded against the student, not in a separate note.
An invoice is raised from the same record, so what was agreed and what was billed cannot drift apart.
The next enrolment is prompted deliberately, on the cycle this kind of work actually runs on.
04B2B SME
Where attention comes from decides where effort goes. For a exam preparation centre demand arrives from two sides at once, with clients and candidates needing different journeys.
The foundations: crawlability, speed, structure and the markup that describes what this business is
Programme, subject, level, outcome, location and question led content
Core for physical campuses, schools, nurseries and training centres
Answering what a student needs to know before they will make contact
Student life, outcomes, faculty expertise and campaign content
Search and social campaigns for programmes, intakes and open days
Student, parent and employer reviews with appropriate consent
Campaign pages built from the same components, so they are fast to ship and consistent to measure
05B2B SME
The recommended build is programme and enrolment website. The modules below are the ones this operating model needs, not a sitemap template.
06B2B SME
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.
07B2B SME
The communication a exam preparation centre sends is mostly operational rather than promotional, which is exactly why deliverability has to be right first.
08B2B SME
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.
A student asks for pricing with enough detail attached to answer properly.
Approval is recorded against the scope it approved.
Where a deposit is how the work is committed, it is taken at that point.
Raised from the agreed scope, not retyped from it.
Without a phone call, and reconciled automatically.
Available to the student rather than requested from you.
Visible on the record, so chasing is informed.
09B2B SME
The diary is the constraint. tours, interviews, assessments, consultations, lessons and events, and the system is built around protecting it.
Read from the real calendar, so double booking is not possible rather than unlikely.
Preparation and turnaround built into the slot, because a meeting is not only the time with the student.
The questions that decide whether the slot is right, asked before it is taken.
On the interval this kind of work needs, each one carrying a reschedule link.
A student can move a meeting without a phone call, which is how you find out early.
A clear policy applied consistently, with the slot released for rebooking.
To the right person and the right location, using rules rather than judgement.
Handled properly wherever the work crosses them.
10B2B SME
The nodes are unremarkable. What makes this an operating system rather than a stack is that each connection is deliberate, owned and documented.
Where a student first finds the business.
The pages a student reads before deciding to make contact.
Qualifying questions asked once, at the point of enquiry.
Every student, every enrolment and who owns it.
Real availability for a enrolment, with the preparation time it needs.
Estimates and invoices raised from the agreed scope.
Payment taken and reconciled against the record.
Operational and lifecycle messages that arrive and are logged.
The rules that move work between systems, with human review where it matters.
What a student can see and do without contacting anyone.
Campaigns tracked through to the record they produced.
The measures a exam preparation centre is actually run on.
Who is told, when, and what they are expected to do about it.
11B2B SME
The combination below comes from the service model rather than from a menu. Core work is what this operating model does not function without. Recommended work is what it usually needs next. Optional work is genuinely optional.
Website build or redesign supports exam preparation centre businesses by helping to increase qualified enrolment
Service and landing pages supports exam preparation centre businesses by helping to increase qualified enrolment
CRM setup and data model supports exam preparation centre businesses by helping to increase qualified enrolment
Pipeline and lifecycle design supports exam preparation centre businesses by helping to increase qualified enrolment
Booking and appointment system supports exam preparation centre businesses by helping to increase qualified enrolment
Documents, forms and e signature supports exam preparation centre businesses by helping to increase qualified enrolment
Email infrastructure and deliverability supports exam preparation centre businesses by helping to increase qualified enrolment
Email campaigns, nurture and reminders supports exam preparation centre businesses by helping to increase qualified enrolment
Analytics and conversion tracking supports exam preparation centre businesses by helping to increase qualified enrolment
Dashboards and attribution supports exam preparation centre businesses by helping to increase qualified enrolment
Brand identity system supports exam preparation centre businesses by helping to increase qualified enrolment
Technical and on page SEO supports exam preparation centre businesses by helping to increase qualified enrolment
Content strategy and copywriting supports exam preparation centre businesses by helping to increase qualified enrolment
Online payments and deposits supports exam preparation centre businesses by helping to increase qualified enrolment
Workflow automation supports exam preparation centre businesses by helping to increase qualified enrolment
Security, privacy and maintenance supports exam preparation centre businesses by helping to increase qualified enrolment
12B2B SME
The honest claim is narrow: a well built system makes certain failures much less likely and makes the rest visible. For a exam preparation centre the areas below are where that shows up first, each with the measure that would prove it.
Being findable for the terms a student actually uses, rather than the ones the business uses internally.
Measure: EnquiriesKnowing what is committed, what is quoted and what is at risk, without rebuilding the picture by hand each month.
Measure: ApplicationsTaking 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: EnrolmentsBeing able to change how the work runs without needing the person who originally set it up.
Measure: ConversionMaking the second enrolment as deliberate as the first, rather than leaving it to whoever remembers.
Measure: SourceAsking the qualifying questions at the point of enquiry, so the enrolment is scoped before anyone spends time on it.
Measure: Programme demand and retention13B2B SME
These are the measures worth reporting for a exam preparation centre. Any figures shown in charts on this site are illustrative and labelled as such: we do not publish client data.
Measured from the record rather than reconstructed at month end.
Reviewed alongside the stage it depends on, not in isolation.
Defined once and written down, so it means the same thing next quarter.
Tracked as a trend, because a single period rarely means anything.
Reviewed alongside the stage it depends on, not in isolation.
Defined once and written down, so it means the same thing next quarter.
14B2B SME
What exists now, what it costs to run, and where a enrolment currently loses time.
How an enrolment enquiry should become a enrolment, agreed and written down before anything is configured.
Delivered in stages that each stand up on their own, rather than one launch that has to go perfectly.
The handovers between Student information system, learning platform, CRM, payments, calendar and email made explicit and monitored.
Documentation aimed at whoever runs this next year, which may not be whoever commissioned it.
Measurement built in rather than added afterwards, when the baseline has already gone.
Improvement as a standing habit rather than a second project.
15B2B SME
Concrete deliverables, not projected commercial results. What each one achieves depends on how it is used after handover.
16B2B SME
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.
Core measures
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.
17B2B SME
The categories this operating model usually has to connect. Naming a category is not a claim of partnership, certification or reseller status.
18B2B SME
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
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.
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.
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.
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.
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.
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.
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.
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.
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.