Forward-deployed engineering
A GEERD engineer sits with your team, and stays until it runs in production.
Not a specification sent from a distance, not software delivered and left there. An engineer comes to your institution, watches how admissions, payments, academic life or reporting are actually done, writes down what is missing, builds it on your systems and your data, and puts it to work with your team. They leave when the team no longer needs them. That is how we have worked with Moroccan institutions for eight years; we do it, in French and in English, for those who call us from elsewhere.
Last updated · September 2026
- years alongside institutions
- 8years alongside institutions
- institutions worked with
- 11institutions worked with
- platforms that came out of the work
- 3platforms that came out of the work
- working languages
- FR · ENworking languages
Why on site
The process that matters is not the one that is written down.
Every institution has an admissions procedure, a chasing procedure, a closing procedure. And each one has, alongside, the way it is actually done: the spreadsheet one person keeps, the exception granted every year to the same kind of file, the chasing done by hand because the software does not know how, the document asked for three times. A system built on the written procedure meets reality on the first Monday.
That is why the engineer comes. They sit beside the admissions, registry or accounts team while the work is being done. They see the exceptions before writing code, and they see what the software will have to refuse to do. What they write afterwards is short, and it is right.
We measure what teams use, not what is deployed. An engineer on site is the only way we know of keeping that rule.
How it runs
Five stages, always in this order.
The same sequence whether or not an agent is involved: the diagnostic says first whether there is anything to build.
01Observe
A few days in the institution, on the chosen process. We note how the work is done, including the steps nobody has documented, and we locate the source of every piece of information: the file, the payment schedule, the calendar, the spreadsheet.
02Write
The perimeter (what the system will do, what it will not, where it stops and whom it warns), and the list of systems it will read and write, field by field. Read by you, signed before a line of code. The price is set on that document.
03Build on your data
Not on a sample file: on your real records, your real exceptions, inside your existing systems: the student-records software, the ERP, the accounts, the messaging. Our platforms are among them when you run them; they are not a condition.
04Put to work under supervision
The system runs under real conditions, with the team reading before anything goes out, and measurable targets written in advance. The engineer is there. What has to be corrected is corrected within the week, not next term.
05Hand over
Your team is trained until it owns the system; the documentation and the access are theirs. We do not keep the keys. What was built (the connectors, the perimeter, the checks) serves the next process, which goes faster than the first.
What the engineer builds
Four kinds of work, one method.
The diagnostic decides which. Often, it is the smallest.
An agent for one process
Chasing an instalment, answering families, preparing the returns the ministry expects, getting back in touch with graduates. Written with its limits, wired to its source, checked on every action. One agent runs in production today in admissions; the others are built the same way.
A connector between two systems
Your student-records software and your accounts do not talk to each other; neither do your training platform and your client’s HR system. We connect the two through existing interfaces where they exist, through a connector written for you where they do not.
A platform when no product exists
A written-examination environment for an entrance exam, a training platform for executive programmes: software written for a single institution because its need had no product. Rarely, and only when configuring and standardising are not enough.
Deploying our own platforms
BrightStep, EasyClass or AlmaHub, installed with the same method: your data migrated, set up on your programmes or your year groups, training, and an engineer present until the use is real.
Already delivered this way
What deployed engineers have built.
- The executive-programme platform of Africa Business School (UM6P), connected to the HR system and the attendance tool of Groupe OCP, its first industrial client: enrolments, attendance and results reach the client directly.
- The written entrance-exam platform of EMINES – UM6P, an engineering school that sits its entrance exam on site.
- Enro, BrightStep’s admissions agent, in production: it answers families, records interest, opens tasks, and stops where its perimeter stops.
- The institutional website and connected assistant of HEC Rabat, a research data platform, a seminar and podcast platform.
In Morocco, and elsewhere
Based in Casablanca. We travel.
GEERD was born in Casablanca and has worked there for eight years, with international schools, business and engineering schools, universities and executive programmes. That is where our clients are today, and where the method was proven.
An education group, a university or a school network that calls us from another country finds the same team and the same sequence. The first conversation and the diagnostic can happen remotely, in your working language: French or English; observation and go-live happen at your institution, and the engineer stays reachable between visits. Data is hosted in France with OVHcloud, and the processing agreement is signed before go-live.
We do not promise to be everywhere. We promise to be at your institution when it matters, and not to keep the keys when we leave.
How this is billed
The diagnostic is free and ends with a written report. The work that follows is priced on the signed perimeter, before the first line of code. The rules (what is included, what is not, what is credited) are written on the Our approach page.
If it is an agent you have in mind
The agentic-AI page says what an agent actually does in an institution, process by process, how we write it before wiring it, and what it will never decide.
On the same subject
Read next.
- HEC Rabat−70% in daily requests to leadership. ×4 Executive Education enrolments.→
- ESFPP40% of the team’s administrative time recovered, as measured by the school.→
- Seven questions to ask before letting an AI talk to your applicantsNone is about the model. All are about what is written, what stops, and what can be read back.→
- BrightStepAdmissions→
Start with the diagnostic.
Half a day, at your institution or remotely, a written report. You leave with a reading of your situation and, if there is something to build, the perimeter to start with.