Buyer’s checklist
HowtochooseasoftwaredevelopmentcompanyinEthiopia
The questions to ask, the red flags, and the local constraints to test for when hiring a software development company in Ethiopia. Names no companies.
Judge an Ethiopian software firm on four things: production software you can see being used by non-developers, a named maintenance path with a price attached, demonstrated handling of local constraints - connectivity, Amharic script, the Ethiopian calendar, mobile money, e-invoicing - and verifiable third-party reviews. Ask what they would refuse to build.
Last reviewed
A sequence that works
- Write down the problem, not the solutionArrive with "approvals take eleven days and we lose track of them", not "we need a workflow system". A firm worth hiring will interrogate the problem; a firm that just quotes your proposed solution back is not adding anything.
- Ask to see production software in useNot a portfolio screenshot - something running, being used daily by someone who is not a developer. Ask to speak to that person if you can.
- Establish who maintains it, and what that costsGet the annual maintenance figure before you compare build quotes. A cheap build with no maintenance path is reliably the expensive option, and this is the single most common way Ethiopian software projects end up abandoned.
- Test them on local constraintsAsk how they handle intermittent connectivity, Amharic and Ethiopic script, the Ethiopian calendar, mobile-money payments and the new e-invoicing directive. Specific answers mean they have hit these problems. Vague ones mean you will be the project where they first do.
- Meet the people who will do the workNot the founder who pitched. Ask who is actually assigned, and whether they are on other projects simultaneously.
- Check third-party profilesClutch, TechBehemoths, GoodFirms, The Manifest and Sortlist maintain Ethiopia listings with client review histories. A firm with no third-party footprint at all is not disqualified, but it is unverified.
- Start with something small and realA paid, scoped first phase that delivers something usable beats a discovery document. You learn more about how a firm works from four weeks of delivery than from any amount of diligence.
Red flags
| Signal | Why it matters |
|---|---|
| No street address or local phone number | Several firms ranking for Ethiopian search terms have no presence in the country. Ask to visit. |
| Says yes to everything | A firm with no opinion about what it should not build has no expertise to sell you. |
| Quotes a fixed price before understanding the process | Either the price is padded to cover the unknown, or it will be revised upward later. |
| Cannot name who will maintain it | Maintenance is where most of the total cost lives. Silence here is the most expensive silence in the process. |
| "HIPAA certified", "GDPR certified" | Neither certification exists. It signals either carelessness or a willingness to overstate. |
| Percentage improvement claims with no methodology | "Cut costs 40%" with no explanation of what was measured is a number chosen for effect. |
| Portfolio of designs, not systems | A firm whose evidence is all visual may not have shipped much that has to keep working. |
| Reluctant to let you talk to a past client | The most informative fifteen minutes available to you, and the easiest thing for a good firm to arrange. |
Match the kind of firm to the kind of problem
Ethiopian technology firms are not interchangeable, and a mismatch of *kind* does more damage than a mismatch of quality. Before comparing firms, work out which of these you actually need.
| You need | Hire | Not |
|---|---|---|
| A mature system, configured to you | A product company with its own platform | A custom house - you will pay to rebuild what exists |
| A system fitted to an unusual process | A custom software house | A product company - you will bend your process to their product |
| A hard research problem | An AI research lab | A general software house |
| ERP selection and rollout | An ERP consultancy | A web development shop |
| Developers you will manage yourself | A talent marketplace | A project firm - you would be paying twice for management |
| A process run as well as built | A firm that does software and operations | A pure software house that hands over and leaves |
Questions people ask
Any figure quoted without scope is marketing. A more useful approach: ask three firms to price the same written scope, and treat a quote far below the others as a signal that something has been left out rather than as a bargain.
A local firm understands connectivity, script, calendar, payment rails and the e-invoicing directive, and can be in the room. An offshore firm may have deeper specialist capability. If you go offshore, establish who is accountable during your working hours.
Source code ownership and access, a defined maintenance scope and price, who holds credentials and hosting, and what happens to your data if the relationship ends. Sort those before scope; they are much harder to renegotiate later.
Clutch, TechBehemoths, GoodFirms, The Manifest and Sortlist all publish Ethiopia listings with review histories. Read the reviews rather than the score - the detail tells you what the firm is actually like to work with.
Not disqualifying - several capable Ethiopian firms were founded in the last five years. It shifts what you should ask for: a smaller first phase, closer review, and clearer exit terms if it does not work.
Use this checklist on us
Every question above is one we would rather be asked than not. Bring the problem and the checklist, and if the honest answer is that a different kind of firm fits better, we will say so.