How to choose a software development company in Ethiopia

A seven-point rubric, the red flags we have learned to watch for, and an honest scoring of ourselves against it — including where we lose.

Meron Desta

Product Manager, Lattice Technologies

Choosing a software partner in Ethiopia is harder than choosing one in London or Austin — not because the talent is weaker, but because the signals are noisier. Directory rankings are thin, most company websites say the same three things, and quotes for the same project can differ by five times.

This is the rubric we would use if we were buying instead of selling. Score every candidate one to five on each point; anything below 25 out of 35, keep looking.

The seven-point rubric

1. Can you use something they built, today?

Not screenshots. A URL, an app store listing, or a demo login. A company that cannot produce one within 24 hours is selling capacity it does not have.

2. Will they name the engineers on your project?

The chronic failure of outsourcing is the bait-and-switch: senior engineers in the sales call, juniors on the delivery. Ask for names, roles, and whether those people attend your kickoff.

3. Do they own the full cycle?

Design, architecture, development, deployment, maintenance. Firms that subcontract any core stage add a failure point you cannot see. Ask it plainly: who writes the code, and who answers when production goes down at two in the morning?

4. Have they shipped inside your industry's constraints?

Healthcare data, school administration, e-commerce payments, ERP integration — each carries baggage that only shows up in month three. Prior work in your vertical is worth more than general headcount.

5. How do they estimate?

Vague quotes produce disputed invoices. The strongest signal of a mature firm is a written scope with assumptions, exclusions and a change process, produced before you have paid anything. Insist on the artefact whoever you choose.

6. Can they work in your time zone and contract framework?

Ethiopia is UTC+3: all morning with Europe, afternoons with US Eastern. But time zone is the easy part — ask where the contract is signed and under which jurisdiction. A US or European contracting entity is a meaningful de-risk.

7. What happens after launch?

Ask for standard maintenance terms, response-time commitments, and exactly what the handover package contains: repository access, infrastructure credentials, documentation. If the answer is improvised, so is their maintenance.

Red flags

What it costs, honestly

Rates in this market commonly sit 50–70% below US and Western Europe for comparable seniority. Be suspicious of both ends: quotes far below market mean junior delivery or scope games, and quotes at Western rates from a local shop mean you are paying for someone's sales trip.

Our own published figures, based on a $28 blended hourly rate and a 20% lead-and-design allocation. Other firms will quote differently; ask each of them to show the arithmetic.

Where Lattice lands on its own rubric

We wrote the rubric, so you should make us answer it first.

Where we are not the cheapest: a freelancer will beat our price on a brochure site. We are built for systems that have to keep working.

And where we are not the right firm at all: embedded systems, telecom BSS, and hundred-engineer staff augmentation. We will say that on the first call rather than in month two.

Frequently asked questions