Ethiopia · software studio
Software for businesses and for individuals — the thing that runs the work, not a brochure about it. We are based in Ethiopia and we build for the conditions here: modest budgets, shared devices, and a connection that comes and goes.
01 What we build
Whole systems, from the database to the thing a person actually touches. Built to be handed over and maintained, not to be rebuilt in two years.
The spreadsheet that has outgrown itself: rosters, payments, approvals, records. Multi-tenant where it needs to be, with the rules enforced by the database rather than by everyone remembering.
Applications that install to a phone and keep working with no signal, then catch up when there is one. This is a requirement here, not a feature.
Telebirr, CBE, bank transfer, cash — with receipts checked and recorded properly. Payment flows that match how money actually moves in Ethiopia.
02 Work
Our own product · live
A digital yearbook for Ethiopian schools and universities. A class builds it together — everyone gets a page, and everyone signs each other's pages by hand, on their own phone. It installs to the phone and opens with no connection at all.
Underneath it is a multi-tenant platform: a school's roster imported from a spreadsheet, portraits matched to names automatically, seats paid for by bank transfer with receipts verified by hand, and every school's data separated by the database itself rather than by application code.
Android app
Spontaneous plans with people nearby. Things happening near you appear as pins on a map — pickup football, a study session, coffee. Join one and you are put in a small group chat to agree where to meet, and when a group fills up the next person opens a new one, so a popular plan becomes several small groups rather than one crowded chat. Afterwards everyone rates each other, so a reputation is earned rather than claimed.
The rules live in the database: who can read a chat, who can message whom, and who can rate whom and when. Joining locks the event, so two people can never take the same last place in a group.
03 How we work
Not a specification — the work it has to carry, who has to use it, and what happens today when it goes wrong. A message on Telegram is enough to start.
What we would build, what we would deliberately leave out, and what it costs. If we think somebody else is better placed to build it, we say so here rather than after you have paid.
Working software you can open, from early on, not a demonstration at the end. The expensive decisions — who can see what, what happens with no signal, how money is recorded — are settled first, because those are the ones that are painful to change late.
The code, the database and the accounts are yours, with a written account of why each decision was made. We stay available because you want us to be, not because you are stuck with us.
04 Work with us
We will tell you honestly whether we are the right people to build it.
@Makense_org on Telegram — the only way in, and it is answered.