The questions organizations ask us, answered plainly.

We design, build and operate software for organizations: custom systems, institutional information systems, enterprise applications, web and mobile products, integrations and digital platforms. We also build and run our own digital products, which is where our operating experience comes from.

Government and public institutions, NGOs and development programmes, businesses of every size, startups, and licensed gaming operators. The industries page describes each in detail, including what is proven on our own products and what is offered as a prospective service.

Our engineers work from Europe and Ethiopia, and GeezSoft Technologies is registered in Ethiopia. We deliver remotely by default, in your time zone, with staging demos you can open on your phone, and we come on site for discovery, training and onboarding wherever the engagement needs it. Our products run in Ethiopia today; the same engineering, payment integration and multilingual work applies to any market.

You do. Client code lives in your repository from the first commit, systems run in accounts you control, and handover includes documentation and a recorded walkthrough. For platforms hosted on our infrastructure, your data is exportable at any time and source-code escrow is available on enterprise terms.

Custom work is a fixed price per scope with milestone payments, quoted in writing after discovery. Long-term partnerships run on a monthly retainer or a support contract. Branded gaming platforms are a setup fee plus revenue share. No hourly billing. The pricing page explains each model.

It depends on the scope, so we give a written timeline with the proposal rather than a guess on this page. Discovery usually settles the phases; a first version that does the essentials well is sequenced before the wish list.

Every week you get a short written update and a demo on a staging environment. Every milestone has an acceptance checklist agreed in advance. You talk to the engineers doing the work, not an account manager.

Yes. Integration with existing systems, payment providers, SMS, identity and reporting platforms is a core part of most engagements. We prefer to connect systems that work rather than replace them.

A support arrangement with response times by severity, maintenance windows, a reviewed backlog of improvements and periodic service reviews. You can also take the system in-house with the documentation and training we hand over.

Email customer-support@geezsoft.org. Requests are handled within the response times in your support agreement, and a severe incident is escalated to the engineers who built the system. New project inquiries go to info@geezsoft.org, so nothing gets lost between the two.

In cloud accounts you own, or on in-country infrastructure where regulation or policy requires it. We are added as operators to your accounts rather than hosting your system in ours, unless you choose a platform we run.

Yes. We work in Amharic and English, and we have shipped interfaces in Amharic, Afaan Oromoo, Tigrinya and English on our own products.

Yes. We provide written proposals with scope, architecture, milestones, acceptance criteria and price in the format your process requires, and we supply company documents on request. The procurement checklist in our resources lists exactly what we provide.

No, and we say so rather than imply otherwise. The security page describes the practices that are live, the designs in progress and one mistake we made and fixed, so your reviewers can check our work instead of taking it on trust.

Send a short inquiry from the contact page, or message us directly. If you want to prepare first, the guide on how to brief a software project and the digital-readiness check in our resources take a few minutes each.

No. Custom work is quoted as a fixed price per scope with milestone payments. If scope changes, we re-quote in writing before doing the work. Retained teams are priced monthly.

Yes. We provide written proposals with scope, architecture, milestones, acceptance criteria and price in the format your process requires.

A one-time setup fee, then a percentage of gross gaming revenue (bets minus winnings) computed from the platform ledger. Player deposits and withdrawals settle against a prepaid credit balance you top up.

Payment-provider fees are passed through at cost and shown in your reconciliation reports.

Custom development: none beyond the project. Support contracts and retainers: an initial term we agree, then month-to-month. Your data is exportable at any time.

Case by case. If we believe in the product and the market, we are open to sharing risk instead of charging a full build fee.

It depends on scope, which we only know after discovery. We prefer a focused first release that replaces one painful process early, then extend it with real users in the loop. Timelines are written into the proposal, not promised on the first call.

You do. Code lives in your repository and runs in accounts you control unless you ask us to host it. Handover includes documentation and training.

Usually, yes. We start with a technical review of the code, data and hosting, and tell you honestly whether extending or replacing is the better path.

Yes. We deploy to servers or cloud accounts the institution controls, and we document the environment so your IT team can operate it. Managed hosting by GeezSoft is an option, not a requirement.

We provide written proposals with scope, architecture, milestones, acceptance criteria and price, and we can work within a formal tender or RFP process. We do not claim certifications or approvals we do not hold.

Interfaces are designed for the least experienced user group first: few screens, clear language, large targets, and training sessions with printed guides as part of handover.

Yes. Indicator frameworks, disaggregation and reporting periods are configured per donor, and reports are exported in the template you need. We ask for the real templates during discovery.

Yes. Mobile forms store entries on the device and synchronize when a connection is available, with conflict handling and a record of who collected what, where and when.

Wherever your policy requires: your own cloud account, a region you choose, or servers you manage. We document the environment and hand over the keys.

If a package fits your processes well, buy it — we will say so. Build when your workflow, pricing, branch structure or integrations are specific enough that a package needs constant workarounds.

Yes. We design for low bandwidth and intermittent connections: small pages, local caching and sync, and clear status when a device is offline.

Each branch has its own users, stock and cash position; management sees everything consolidated. Permissions and reports are defined per branch and per role.

If your users already live in a messaging app and you want distribution without a store, an in-chat app ships fastest. An installable web app suits most customer-facing products. Native makes sense for hardware access or store presence. We recommend one on the scoping call.

Yes. Our products ship with Ethiopic-ready typography and we design for Amharic and English interfaces.

Yes — we design the API and data model together with the app, and we can integrate with an existing backend if you have one.

Mobile money and bank transfer run in production on our own products. Other rails are integrated per project against the provider's official interface.

Yes. We work through its official API, its database or its exports — whichever is supported — and add the reconciliation and logging around it.

Dry runs with validation reports, a parallel-running period, a rehearsed cut-over plan and a rollback path. Nothing is switched off until the new system has been proven with real data.

Yes, within a support contract: agreed response times by severity, maintenance windows and reporting. We do not advertise availability percentages we cannot prove for your specific environment.

Yes. Handover includes runbooks and documentation, and we can train your team to run day-to-day operations while we remain available for escalation.

After a technical review, usually yes. We will tell you what we found and what it would take to support it responsibly.

No. Operators are responsible for licensing in their jurisdiction. We can share what we know about the landscape and build the compliance controls the licence requires.

Yes. Branded platforms are how we work with operators; see pricing for the setup-fee plus revenue-share model.

On the compliance page, which covers licensing responsibility, KYC and AML, age verification, responsible-gambling tools and data protection.