Arvenson Group · Manifesto
We Are Building Tools for the Students Africa Has Not Yet Heard Of
A personal essay on why technology must serve the classroom before it serves the boardroom, and why Arvenson exists to make that happen.
There is a student somewhere in a secondary school in Kisumu, or Kakamega, or Garissa, who is extraordinarily talented. She is good with numbers. She asks the kind of questions that make her teachers pause. She has never had a career counsellor sit with her, never used a well-designed piece of software in a classroom, and has no reliable way of knowing which subjects she is studying today will matter most to her future. Nobody has told her. Not because people do not care, but because the tools to tell her simply do not exist at scale in her world.
That student is not an edge case. She is the rule. And she is the reason Arvenson Group exists.
I want to be careful here. I am not writing this to present a problem that needs a foreign solution. I am writing this because I am Kenyan, I grew up inside this system, I sat in classrooms that ran on spreadsheet timetables that nobody could explain, and I became a technologist precisely because I believe we can build our way forward. This is not charity. This is conviction.

When we started building Tabbbly, our first product, the trigger was almost embarrassingly simple. A school administrator — a man who had spent thirty years in education — showed me a printed timetable that had taken him three weeks to produce by hand. Three weeks. He had a spreadsheet open on one screen and a list of teacher availabilities on a notepad beside him. He had started over four times. And he was proud of it, as he should have been, because completing that puzzle manually is genuinely impressive.
But three weeks is also three weeks in which that same person was not doing the hundred other things a school needs. Three weeks in which teachers did not know their schedules. Three weeks in which students were uncertain. We built Tabbbly to make that process take seconds. Not because we wanted to replace the administrator — we wanted to give him three weeks of his life back every term.
"The best technology for a school is the kind that disappears into the background and lets teachers teach."
That principle has guided every decision we have made since. The best technology for a school is the kind that disappears into the background and lets teachers teach, lets administrators administrate, and lets students focus entirely on learning. Software that demands to be noticed has failed at its job. We do not want Tabbbly to be the most interesting thing in a school. We want it to be the most reliable.
The same thinking drove Edubora. Kenya's CBE curriculum reform is one of the most ambitious educational restructurings this country has attempted. It shifts the emphasis from rote memorization toward competency-based learning, toward helping students discover where their strengths actually lie. But that shift requires a kind of individual guidance at scale that most schools simply cannot provide with existing resources. A career counsellor serving eight hundred students has, mathematically, very little time per student. Edubora is our attempt to make that guidance available to all eight hundred, simultaneously, at a quality that does not degrade with volume.

I have heard the scepticism. It usually sounds like this: Africa does not need more apps, it needs better infrastructure. It needs more teachers, better pay, more books. All of that is true, and none of it is an argument against software. Those are arguments for more investment across the board, and I agree with every one of them. But they are not a reason to wait.
The mobile phone proved something important about this continent: when technology is designed for the actual conditions on the ground, it gets adopted faster than anyone predicts. M-PESA did not wait for every Kenyan to have a bank account before it became indispensable. It met people where they were. That is the model we are following. Not "this technology will work here eventually" but "we are building this specifically for here, right now, for these schools, these curricula, these constraints."
"We are not building tools for Africa in the abstract. We are building tools for specific schools, with specific curricula, on specific infrastructure."
That specificity matters more than anything else we do. Generic SaaS products built for American or European schools do not map onto the CBE. They do not understand what a Junior Secondary School is, or what it means to allocate learning areas rather than subjects, or why a bell schedule in a Kenyan school looks the way it does. We do. We were educated here. We built for here. And that is a genuine competitive advantage that no amount of venture capital can buy for a company that has never sat inside a Kenyan classroom.

We believe that education technology has a responsibility that most other categories of software do not. When a consumer app fails, someone has a slightly worse day. When education technology fails, a student loses time they cannot get back, a teacher loses trust in tools that were meant to help them, and a school loses confidence in the promise of digital transformation. The stakes are higher. The standards must be higher.
We believe that affordability is not a concession but a design constraint. If our products cannot be used by a school in a rural county, they are not solving the problem we set out to solve. They are solving the problem for the schools that already have the most resources, which is the opposite of what this continent needs. Every pricing and infrastructure decision we make is filtered through this question: does this work for the school that needs it most, not just the school that can pay the most?
We believe that local ownership of this technology matters enormously. Not for nationalistic reasons, but for practical ones. A company that is accountable to the communities it serves makes better decisions than one that is not. When the people building the product are also the people who could be affected by it — who have relatives in these schools, who studied under this curriculum — the feedback loop is shorter and the motivation is different in kind, not just in degree.
"Affordability is not a concession. It is a design constraint. If our products cannot reach the school that needs them most, we have not solved the problem."
We believe in building slowly and correctly rather than quickly and incorrectly. This is harder than it sounds in an era that celebrates speed above almost everything else. But education is one of the domains where moving fast and breaking things is genuinely dangerous. A broken timetable affects every student and teacher in a school for an entire term. A flawed career recommendation can send a student down a path that does not suit them. We take that weight seriously.

We are two products into what we intend to be a much longer body of work. Tabbbly and Edubora are proof of concept — proof that this kind of software can be built here, by people from here, and that schools will use it. But they are also a beginning, not a destination.
The problems that remain are large. School performance data is fragmented and inaccessible in ways that prevent good decision-making at every level of the system. Teacher professional development happens inconsistently and without the kind of data feedback that would make it more effective. Parents, particularly in rural areas, are often entirely disconnected from their children"s academic journey in real time. Students make subject choices at critical junctures with very little structured information.
Each of these is a solvable problem. Not easily, not cheaply, not quickly — but solvable. And solving them, one at a time, with the same discipline and specificity we have brought to timetabling and career guidance, is exactly what we intend to do.
"We are two products into what we intend to be a much longer body of work. This is a beginning, not a destination."
I want to say something directly to the schools and educators who are reading this. We know that technology fatigue is real. We know you have been promised solutions before that did not deliver, that required training you did not have time for, that were abandoned when the funding cycle ended. We are aware of that history and we take it seriously. Our job is not to convince you that technology works in the abstract. Our job is to earn your trust one school at a time, one timetable at a time, one student whose path becomes a little clearer because of something we built.
That is the work. It is not glamorous in the way that technology is sometimes made to sound. It is detailed, iterative, accountable work. It is also, I genuinely believe, some of the most important work being done in this country right now.

I started this essay with a student in Kisumu I have never met. I want to end with her too.
By the time she finishes secondary school, I want Edubora to have given her a clear picture of what her strengths are and where they could take her. I want the school she attended to have run smoothly enough — because Tabbbly handled the scheduling — that her teachers had more time to notice her. I want the tools her institution used to have been reliable enough that she never had to think about them at all.
I want her to move into the world with the same advantages that students in better-resourced systems have always taken for granted — not because the world suddenly became fair, but because we built something that made it fractionally more so.
That is why Arvenson exists. That is why we come to work.
Vincent Eliezer
Co-Founder, Arvenson
Nairobi, Kenya