Our approach
We start by understanding how you work. The software comes after.
Most digital projects fail for the same reason: a tool chosen first, processes forced to fit it, teams left on their own. GEERD was built to do the opposite.
Two sequences
The same intention, in the opposite order.
It is not a question of tooling, it is a question of order. What comes first decides everything else.
| Traditional | GEERD | |
|---|---|---|
| Sequence | Tools → Customisation → Adoption (maybe) | Operations → Structure → Platform activation |
| Starting point | The software, chosen first | The real processes |
| Processes | Forced to adapt | Clarified, kept simple |
| Teams | Left to themselves | Involved and guided |
| Result | Fragmented systems, limited ownership | Clear processes, strong adoption |
How we work
Three phases, always in this order.
01DiagnosticFree
Half a day with the leadership and the person who actually holds the process together. Before the session, a short questionnaire, or your DigiPulse answers. After it, a written report: findings, priorities, one recommendation, one next step. We keep it for institutions whose leadership takes part, and we run a limited number each month.
02Set-up
Together we settle the stages, the rules, the documents. Then we configure the platform so that it looks like your process, not the other way round. We migrate your data. We train your teams on their own real cases.
03Support
We stay through the first real cycle: a campaign, an intake, a semester, a deadline. A weekly check-in, one named contact, an answer within 48 hours. After that your team is autonomous. We build autonomy, not dependency.
When more is needed
The audit.
When the situation is bigger than one process (a group, a network of schools, a university, a full overhaul), we propose an audit: on site, cross-interviews with the teams, a map of the processes, and a sequenced, costed roadmap.
It is a consulting engagement, and it is invoiced. Its amount is credited against the deployment contract if that contract is signed within the agreed window.
From signature to the new academic year
What happens, in order, and who does what.
Three to five days for a guided set-up of one process; two to three weeks for full support including data migration. The sequence is the same either way.
01Scoping
One working session. GEERD writes down the stages, the rules and the list of documents from the diagnostic report; your process owner validates them. Deliverable: the configuration document, signed on both sides.
02Configuration and migration
GEERD configures the platform (programmes, stages, document templates, billing rules) and migrates your data from your spreadsheets and exports. Your team supplies the files and validates a sample before the full load. Deliverable: your institution, in the platform, with your data.
03Training
On your real cases, with your data already in place, by role: academic administration, admissions, finance, leadership. Deliverable: everyone has done at least once, in the session, what they will do when the year starts.
04Go-live and the first cycle
Your team operates; GEERD stays present through the first real cycle with a weekly check-in, a named contact and a reply within 48 hours. At the end of the cycle, a written review and autonomy.
The rules
How we charge.
The diagnostic is free. The audit, when the situation calls for one, is invoiced and credited against the deployment.
Each platform is an annual subscription, sized on your institution: the number of pupils or students for EasyClass, the number of graduates per year for AlmaHub. BrightStep is sized on your team’s seats, the modules you switch on and the communications actually sent.
Set-up (your programmes, your document templates, your stages, your data migration, the training) is invoiced once, then reused at every intake.
Alumni associations use AlmaHub free of charge up to 300 members.
After a diagnostic or a demo you get a complete written quote within 48 hours. No hidden fees, no indispensable option discovered after signature.
Your data
They stay yours, before, during and after.
The data you entrust to the platforms belongs to your institution. GEERD hosts and processes it on your behalf, in the European Union, and uses it for nothing else.
You can request a full export at any time, in open formats, with no reason required. At the end of the contract you receive that export, then the data is deleted from our systems within the period written in the contract.
The reversibility clause is in every GEERD contract. We show it before signature.
After go-live
Support, as it is.
During the first real cycle: a weekly check-in, a named contact, a reply within 48 hours. After that, the same contact remains reachable by e-mail and WhatsApp during Moroccan working hours.
Response times by severity, escalation and maintenance windows are written in the contract, not on this site: a service commitment belongs in a signed document.
What we connect to
Today, in the platforms.
The list is short because it is true. What is not on it does not exist yet, and the next section says what is coming.
Identity and sign-in
Sign-in with a Google Workspace or Microsoft 365 account, or with a one-time code sent by e-mail or WhatsApp. Roles and permissions per team in each platform.
Messages and calls
WhatsApp Business inbound and outbound, transactional e-mail, browser calls and video interviews in BrightStep, online classes in EasyClass.
Payments
Secure card payment to banking-industry standards, a payment code settled in cash at a network of agencies, and tracking of offline payments: documented bank transfer, cheque, cash.
Files
Excel and CSV import of pupils and students, contacts and lists, with row-by-row correction before loading. Excel and CSV export of every list. Your Word templates become the generated documents: invoices, receipts, certificates, student cards, timetables, as PDF.
Between our platforms
Between EasyClass and AlmaHub, graduates are invited in batches, with class year, programme and degree, through AlmaHub’s invitation API; GEERD triggers the send for each graduating class. Between BrightStep and EasyClass, GEERD carries the enrolled students over at set-up.
Your website and your tools
BrightStep exposes a documented contacts API (OpenAPI) with keys, quotas and a call log, so your website or your automations can create and update contacts. Enabled on request.
In preparation
What we build next, with no date promised.
Chosen because institutions we work with already use them and re-key today. Each leaves this list the day it is in production, not before.
- Accounting export to Sage and Odoo: invoices, payments and the customer ledger, in the layout your accountant imports.
- BrightStep interview slots pushed to the interviewer’s Google or Outlook calendar.
- EasyClass enrolments into Moodle: cohorts become course enrolments, with no re-keying.
- WhatsApp for EasyClass receipts and notices, with the approved templates BrightStep already uses.
- The contacts API extended to applications and enrolments, with outbound webhooks.
Our limits
What GEERD does not do.
- We do not run your institution for you.
- We do not hand over software on its own.
- We do not configure before we understand.
- We do not say yes when the timing is wrong.
When something has to be built
Custom work.
When a need outgrows the platforms we proceed in order: configure what exists, standardise what is repeatable, extend only when something is genuinely specific.
Then we build: a connector between two systems that do not talk, an agent for one process, a platform when no product exists, with the same method as a deployment, and in the same way: an engineer at your institution, from the diagnostic to the team standing on its own.
Already delivered
- The executive-programme platform of Africa Business School (UM6P), connected to the HR system of Groupe OCP, its first industrial client.
- The written entrance-exam platform of EMINES – UM6P.
- The institutional website and connected assistant of HEC Rabat.
- A research data platform.
- A seminar and podcast platform.
Engineers deployed at your institution
Custom work is built on site: a GEERD engineer watches the process while it is done, writes the perimeter with your team, builds on your systems and your data, and stays until production. In Morocco, and wherever we are called.
What the diagnostic covers
The situations we start with.
- Grow your admissionsFollow every applicant from first enquiry to enrolment.→
- Prepare the new academic yearRe-enrolments, payments, groups and documents before September.→
- Simplify academic lifeCourses, attendance, grades, transcripts and academic operations.→
- Track paymentsGive the right teams clear financial information.→
And where does AI fit?
In the same place as everything else: after. An AI agent answering families is only worth something if what it repeats is right, and most institutions we meet have not yet written down what it would repeat. A first agent runs in admissions, with limits written down and verified on every message; the next ones (payments, academic life, reporting) are written at the diagnostic, on your existing systems. And we say no when the diagnostic shows the problem is elsewhere.
Start with the half day.
A free diagnostic, half a day, a written report. You leave with a reading of your own situation, whether or not you work with us afterwards.