Certificates piling up in a folder
Every course that finishes leaves a stack of certificates to generate, personalise, and send. Someone loses theirs six months later and asks you to redo it by hand.
Built by a teacher who also builds automations — not the other way around.
Automation for training academies, built by someone who runs classes too.
I teach. I also build n8n and AI automations. When I look at your enrolment forms, your certificate backlog, or your attendance spreadsheet, I'm not guessing what matters — I've filled out the same forms. I build the automations a training organisation actually needs, not a generic CRM template with your logo on it.
Book a free 20-min automation auditThe problem
Training academies lose hours to work that has nothing to do with teaching
Enrolment paperwork before day one
A new student signs up and then you're chasing ID copies, signed agreements, and payment confirmation across three separate tools before they can start.
Students who go quiet mid-course
Attendance drops, nobody notices until week six, and by then the student has already decided to quit. No one flagged it because no one was watching the register in real time.
What I build
Workflows that fit how a course actually runs
01
Audit call
We walk through how a student actually moves through your academy — enrolment, attendance, certification, renewal — and I map where the manual work sits. I've done this walk myself, from the classroom side, so I ask about the steps most vendors skip: the make-up class, the partial refund, the certificate reissue.
02
Build sprint
I build the automations in n8n, connected to the tools you already use — Notion for student records, WhatsApp or Telegram for reminders, Stripe for payment tracking. A student finishing a course triggers a certificate, a payment confirmation triggers an enrolment update, three missed sessions trigger an alert to you instead of silence.
03
Handover & support
You get the workflows running on your own accounts, documentation on what each one does, and a walkthrough call. Nothing lives in a black box you have to call me to open.
Why it's different
Why a teacher builds this differently
Most automation agencies map your processes from the outside. They ask what your CRM looks like, what fields you track, what triggers a notification. That gets you a workflow that matches your org chart. It doesn't get you a workflow that matches how a course actually runs.
I teach. I've sat on the other side of the enrolment form, the attendance register, and the certificate request. I know that "student completes course" isn't one event — it's a messy sequence of last-minute makeup sessions, a grade that comes in late, an admin who has to manually confirm attendance before anyone can issue a certificate. I know that compliance reporting deadlines don't map neatly onto your billing cycle, and that the student who "goes quiet" usually gave three small signals before they actually dropped out: skipped one class, stopped replying to the WhatsApp group, paid late.
That's the difference between an automation that technically works and one that actually holds up under how your academy runs in practice. A generic vendor builds the workflow you describe to them. I build the workflow I'd have wanted when I was the one running the register.
This also means I know where automation should stop. Not every conversation with a struggling student should be handled by a bot. Not every certificate should go out without a human glance first, especially early on. Part of the audit call is deciding which decisions stay yours and which ones I can safely take off your plate. I'd rather build three automations that free up real hours than ten that need constant babysitting.
See a real academy example:a language school that stopped chasing certificates.
Ready to see where your hours are going?
I'll walk through your enrolment, attendance, and certification process and show you exactly what can run without you. One week, fixed price, credited toward your build if you move forward.
Book your audit call