Technology for Africa
Technology for Africa's next chapter.
We design and build digital systems for the institutions shaping the continent — schools, leaders, and the enterprises around them.
Africa doesn't need more software. It needs systems that fit.
Too much technology arrives fully formed — designed for another market, another institution, another reality. We start from the opposite direction: with the people, workflows and constraints that define how Africa actually works.
Then we design and build software that earns its place: useful on day one, resilient over time, and owned by the institutions it serves.
02 / What we build
Platforms with a point of view.
Lumen and Kilele are our current platforms. Our custom engineering practice builds what comes next for your institution, and for our own roadmap.
See all capabilitiesEvery school. One clear view.
A multi-tenant school management system that gives groups one operating system — admissions, attendance, assessment, fees and reporting — without erasing the identity of each school.
Explore LumenLeadership, at altitude.
A training platform for leaders who learn by doing. Cohorts, facilitated sessions, reflection and evidence of growth in one deliberate journey.
Explore KileleBuilt from first principles.
When the market has no answer, we design one. Product strategy, experience design and engineering for institutions with a problem worth solving properly.
Start a project03 / How we think
Context before code. Craft before speed.
We are not interested in shipping more software. We are interested in building systems that hold up — in the school office, in the boardroom, and in the places where the work actually happens.
Context is a design material.
We spend time inside the institution before we write a line of software. The best architecture starts with how people actually work.
Systems, not features.
We design the whole: data, roles, workflows, reporting, support. Features are easy to add. Coherence is not.
Ownership, not dependency.
We build for handover. Clear documentation, sensible technology choices, and a team that stays accountable after launch.
African by default.
Mixed connectivity, mobile-first users, multi-language institutions, real budget constraints. These are not edge cases. They are the brief.
04 / How we work
A deliberate path from problem to product.
No black boxes. No hand-off cliffs. You see working software early, and you understand every decision that gets us there.
Listen
We map the institution: people, workflows, constraints and existing systems. We leave with a shared definition of the problem.
Architect
We translate that into product and technical architecture, with a clear scope and a plan for what comes first.
Build
Design and engineering move together in short, visible cycles. Working software, not status theatre.
Steward
Launch is a beginning. We support, refine and train the team that will carry the system forward.
05 / Where we work
Institutions that shape everyday life.
Our work sits close to the systems people depend on: how children learn, how leaders are formed, how organisations serve the public.
The point of view
“Africa is not a market to be entered. It is a place to build from.”
Start a project
Have a problem worth building for?
Tell us what you're trying to change. We'll tell you how we'd approach it — honestly, and with a clear sense of what it takes.