Choosing a Software or IT Company in Somalia: 10 Questions to Ask Before You Sign

Why the choice matters more than the price

A software or IT project shapes how your organization works for years. A good partner leaves you with systems your team understands, can maintain and fully owns. A poor one can leave you with half-finished software, data you cannot get out, and accounts registered in someone else’s name.

The questions below help you compare IT companies in Somalia on what really determines success: how they deliver, what you will own, and what happens after launch.

Checklist

• Write down what the project must achieve before talking to any company.
• Speak to at least three companies so you can compare answers.
• Ask every company the same questions, in writing.

Questions about delivery

1. Can we see live systems you have built? Ask to use real, working software or websites, not only screenshots or slides.

2. Who will actually do the work? Find out who leads the project day to day and whether parts will be subcontracted.

3. How will we see progress? Prefer short milestones with working pieces you can test over a single delivery at the end.

4. How do you handle changes? Requirements change. A clear, written process for changes avoids disputes later.

Checklist

• Test at least two live systems the company built.
• Get the names and roles of the people on your project.
• Agree milestones you can review and test.

Questions about ownership

5. Who owns the code, the data and the accounts? Your organization should own the source code it paid for, its data, the domain, hosting and every third-party account.

6. What documentation will we receive? Ask for system documentation, access records and instructions for common tasks, so another team could take over if needed.

Checklist

• Put ownership of code, data, domain and accounts in the contract.
• Make documentation and handover part of the final milestone.
• Keep company-controlled admin access to every system from day one.

Questions about security and reliability

7. How do you protect our systems and data? Look for individual accounts, two-step sign-in, access by role, updates and encrypted connections as standard, not extras.

8. How are backups and recovery handled? Ask where backups are stored, how often they run and when a restore was last tested.

Checklist

• Ask for the company’s security basics in writing.
• Confirm backups are separate from the main system and tested.
• Check how quickly they respond to a security problem.

Questions about support

9. What happens after launch? Agree what support includes, how to report problems and how quickly they are handled.

10. Can our team run the system day to day? Training and simple admin tools let your staff handle routine changes without calling the developer every time.

Checklist

• Get support terms and response times in writing.
• Include staff training in the project.
• Ask what ongoing maintenance the system needs.

Red flags to watch for

Be careful with companies that promise everything quickly without asking about your processes, refuse to put ownership in writing, register domains or hosting in their own name, or cannot show live work. A partner who explains trade-offs and says no to unrealistic requests is usually the safer choice.

Choosing well takes a little longer at the start, but it is far cheaper than rebuilding a failed system later.

Checklist

• Walk away if ownership of code or accounts is unclear.
• Be cautious of very fast timelines with no discovery phase.
• Prefer partners who ask detailed questions about how you work.

Frequently asked questions

Should we choose a local IT company or one abroad?

A local company understands mobile money, connectivity, language and business practice in Somalia, and can meet in person. What matters most is the quality of delivery, ownership terms and support, wherever the team is based.

What should a software contract include?

Scope, milestones, acceptance testing, ownership of code and data, handover and documentation, support terms, and how changes are priced and approved.

How do we compare quotes from different companies?

Make sure each quote covers the same written scope, including integrations, content, testing, training and support. Quotes that look cheap often leave out the parts that are expensive to add later.