weight.
Kavod is a technology company in Addis Ababa. We design, build and run the systems organisations depend on, and we build them to carry load for years.
Why Kavod.
Kavod (ካቮድ) comes from an ancient word for weight. Over time it came to mean what weight earns: honour, and respect.
Something with kavod is substantial. It carries load, holds its shape under pressure, and is trusted for it. That is the standard we hold our work to. The systems we build sit under payrolls, patient records, loans, deliveries and public services. They have to carry weight every single day.
- 01 Two forms meet Your organisation and the technology under it, designed together instead of bolted on.
- 02 Two pillars carry the load The part nobody sees: architecture, security, backups and support that hold everything above them.
- 03 One point Everything resolves to one place: one system, one version of every number, one team that answers.
Why Kavod exists
systems that carry the load, built here, by people who answer when you call.
Serious software within reach
Make the kind of systems large institutions run on affordable and achievable for growing companies, not only the largest.
People who can run it
Train the people behind every system we build, in their own language, so the system is theirs from the first day.
A home for great engineers
Build one of the strongest engineering and design teams in Addis Ababa, doing work that the region relies on.
- 2024
Kavod starts in Addis Ababa
Building websites and systems for organisations in the city.
- 2026
Platforms in two countries
A staff workspace with its own mail, a student platform, an offline point of sale that recognises products by photo, and a data platform for a conservation charity in Uganda go live.
- 2027
Sector platforms in production
Operations, lending, healthcare and education platforms running for organisations across Ethiopia’s regions.
Goal - 2030
The systems a region runs on
Kavod systems behind the daily work of organisations across Ethiopia and East Africa.
Goal
Founder
Tsion founded Kavod on a simple conviction: organisations here deserve technology with real weight, built close to them, by people who answer when they call.
She trained as an engineer, with a degree from Hindustan University in Chennai, India, and has worked in applied research and systems documentation in Addis Ababa. She has spent years making complex technology understandable to non-specialists, including as the host of a science programme on Ethiopian television.
At Kavod she leads the relationship with every client: understanding the organisation, shaping what should be built first, and making sure what we deliver is what was needed. Clients work with her directly, from the first conversation to go-live and after.
The people on your project.
Every project gets the same six roles, from the first workshop to support. You always know who is doing what, and you always have one person to call.
-
Project lead
Your one point of contact from the first call to go-live, and after.
-
Solution architect
Designs how the system fits together and with what you already have.
-
Product designer
Makes complex work feel simple for the people at the counter.
-
Engineers
Build, test and secure every part, in two-week phases you can click through.
-
Data and AI
Automation, reporting and AI that work from your own records.
-
Support
Monitoring, backups, updates and a person who answers.
What we hold to.
- 01
Weight over noise
Fewer, heavier things, done properly. A system that works every day beats ten features nobody trusts.
- 02
Prove it
A working link every week instead of a status report, and nothing claimed that we cannot show.
- 03
Yours, completely
Your code, your data, your domain, documented so you are never dependent on us.
- 04
Built for here
The payments, languages, networks and habits of the people who will use it come first.
How a project runs.
A typical system project, week by week. Smaller projects move faster; larger ones repeat the build phase. The shape never changes.
Weeks 1–2
Discover
We sit with the people who do the work, map how things run today, and agree what to build first: the part that pays back fastest.
What you receive
- A map of your current process
- Priorities, agreed in writing
- A plan and timeline you sign off
In the room
Your team leads, our project lead and solution architect
Weeks 2–4
Design
You click through the screens before a line of production code exists, and change your mind while it is still cheap.
What you receive
- A clickable prototype
- The data model and integrations plan
- Screens approved by the people who will use them
In the room
Your users, our product designer and architect
Weeks 4–13
Build
Two-week phases, each ending in something that works. Every week you get a link to the real system, not a status report.
What you receive
- A working link every week
- Modules released phase by phase
- Tests and a security review
In the room
Our engineers, with your project owner every week
Weeks 13–16
Launch
Your data comes across and is reconciled against your own totals. Your people are trained in their language. We are on site for go-live.
What you receive
- Data migrated and reconciled
- Training for every role
- Go-live support in person
In the room
Everyone, including the people at the counter
From then on
Run
We stay. The system is monitored, backed up and improved, with response times written into the agreement.
What you receive
- Monitoring and nightly backups
- Updates and improvements
- Support with agreed response times
In the room
Our support team and your project lead
- A named project lead
- A working link every week
- A written plan and timeline
- Your code, your data
- Training in your language
Built to pass your IT, finance and legal review.
The questions serious organisations ask before they sign, answered before they ask them.
-
You own everything
Source code, data, domains and accounts are in your organisation’s name from day one. No lock-in.
-
Security by default
Role-based access, two-step sign-in, encryption, audit logs on every change, and security review before launch.
-
Documented and handed over
Architecture, operating guides and training for your team, in English and Amharic.
-
Agreed service levels
Monitoring, backups and response times written into a care agreement, not promised in conversation.
-
Built to be audited
Every transaction traceable to a person and a time, with exports your auditors can work with.
-
Data protection
Personal data handled in line with Ethiopia’s Personal Data Protection Proclamation, collected only where needed.
Where we work.
From Addis Ababa, with organisations across Ethiopia’s regions, in East Africa, and with diaspora-led companies abroad. We start in person and work remotely after, on a schedule that suits you.
- Office
- Addis Ababa, Ethiopia
- Local time
- EAT (GMT+3)
- Hours
- Monday to Saturday, 8:30 to 18:00 (East Africa Time)
- hello@kavod.et
- New projects
- projects@kavod.et
- Careers
- Work with us
that slows you down.
Tell us how things run today. We reply within one working day with what we would build first and how long it would take.