AI training for teams
Your team, faster at the work they already do.
Most AI training teaches tools. That is why nothing changes on Monday. We start from your team’s actual week, and shorten it.
Based in Kigali, working with organisations globally. Live online, or in person where arranged.
What changes
The same week, shorter.
A client deck takes two days
An afternoon
The monthly report is typed by hand
Drafted in minutes, checked by a human
Small features wait weeks on engineering
Shipped the same week
Research spread across twenty tabs
One answer, with its sources
Security is whatever your vendor tool catches
Your own engineers catch what it misses
One person knows the AI tools
The whole team does
What your team gets
Built around your work, not ours.
- A curriculum scoped to your team's real tasks
- Seats you assign as people join and leave
- A dashboard of who finished and who stalled
- A private space, separate from the public community
- Certificates your people show, and you verify
I am a polymath. In practice that means building across several fields at once: software for large organisations in Nigeria and across Africa, fintech and security products, and advanced AI platforms.
One of my live platforms is Oystar, a clinical referral system used in Rwanda. It carries a patient’s case from a frontline clinic to the right specialist, and brings the answer back.
Creovine Academy is the training arm of Creovine, the studio I co-founded. The same team builds Lira, an AI support platform running in production today.
I teach what I actually use. Book thirty minutes and tell me what slows your team’s week down.
Yerins AbrahamCo-Founder, Creovine Academy
The programme
What we actually do.
Every engagement is scoped to one organisation, so no two are the same shape. This is the work underneath all of them.
- 01
We learn how the team actually works
Sessions with the people doing the work, not only the person buying the training. What a week contains, where it stalls, and which tools are already in the building.
- 02
We pick the workflows worth changing
Not everything benefits. We choose the few tasks that are frequent, slow, and repeatable enough that a change compounds, and we say which ones we are leaving alone.
- 03
We design the training around those roles
An analyst, a marketer and an engineer do not need the same session. The curriculum is built per role against the workflows above.
- 04
The team trains on its own work
Real documents, real reports, real tickets, handled under supervision. People leave a session with something finished, not with notes about a demo.
- 05
We stay through adoption
The weeks after training are where most of it is lost. Follow-up sessions, a place to ask questions, and help fixing what does not survive contact with a real deadline.
- 06
We write down what changed
Agreed with you at the start: which tasks, measured how. Where a number is not honestly measurable we say so rather than producing one.
How it works
Four steps. The first one is free.
We talk
Thirty minutes on what your team does and where the week slows down.
We scope it
The format, the people on it, the timeline. In writing, before anything is agreed.
We agree the terms
One invoice, in your currency, on your terms.
They start
Seats issued, progress visible to you throughout.
Start here
Thirty minutes, and you will know if this fits.
No deck and no pitch. You tell us what your team spends the week on, we tell you what we would change and whether it is worth doing.
Book a 30 minute callPick a time that suits you. Nothing is committed on the call.
Rather not book yet?
Send four details and we reply by email within a day.