Software Development

Geexar is a software company in Saudi Arabia that builds custom business systems: the internal platforms, portals, dashboards and integrations that off-the-shelf products cannot cover. Founded in 2018, head office in Riyadh, production team in El Mansoura, Egypt.

Custom software is worth building in three situations, and we will tell you if yours is not one of them. First, when your process is your advantage and forcing it into a packaged product would flatten it. Second, when your data lives in three systems that do not talk to each other and the reconciliation is being done by a person with a spreadsheet. Third, when you are paying per-seat licences for a fraction of a product’s features and the arithmetic has stopped working. If a configured off-the-shelf platform would genuinely serve you better, that is the recommendation you will get from us.

Typical deliverables: web-based business platforms, admin dashboards and reporting, customer and supplier portals, workflow and approval systems, API integrations between existing systems, and the Arabic/English bilingual interfaces most Saudi organisations need. Request a quote and we will scope it before pricing it.

Six phases, each with a defined output you sign off before the next one starts.

1. Discovery and process mapping. We sit with the people who do the work today and map the current process, including the exceptions and the workarounds, because the exceptions are where custom software either earns its money or fails. Output: a process map, a requirements document, and a scope split into phase one and later phases.
2. Solution architecture. Data model, module breakdown, roles and permissions, integration contracts, hosting and backup plan, and the security model. Output: a technical specification your own IT team can review before a line of code is written.
3. Design and prototyping. Interface design in Figma for every role in the system, in Arabic and English with RTL layouts designed properly. Output: a clickable prototype and a component library.
4. Development in sprints. Built in two-week increments against the specification, with a staging environment available to you throughout so your team can use the system as it grows rather than seeing it at the end.
5. Testing, UAT and data migration. Functional, performance and security testing, then user acceptance with your own staff on real data. Where you are replacing an existing system we plan and rehearse the data migration rather than doing it on go-live night. Output: test reports, a migration plan, sign-off.
6. Deployment, training and support. Production deployment, monitoring and backups configured, training sessions for each user role, and written documentation. Output: a live system, trained users, and a support agreement.

Timelines are committed in the proposal once phase-one scope is agreed.

We build on a small, mainstream stack on purpose. It keeps our team interchangeable across projects and it means you can hire developers for your system later without hunting for a rare skill set.

• Laravel and PHP for application logic, business rules, roles and permissions, queues and scheduled jobs, and REST APIs.
• MySQL as the primary database, with a documented schema, migrations in version control, and indexing reviewed against your real query patterns rather than left to defaults.
• React and Next.js for dashboards and interactive front ends, and TypeScript where type safety pays for itself.
• Flutter (Dart) when the system needs a mobile client as well as a web interface.
• Figma for design systems and role-by-role interface design.
• GitHub for version control, code review and deployment pipelines — in a repository you own.

Integrations we build routinely: payment gateways, SMS and OTP, email, accounting and ERP systems over REST, government and banking APIs where they are available, single sign-on, and file and document storage.

A digital platform for a consulting firm serving multiple sectors and industries with a diverse team of consultants, whose stated experience runs to more than 25 years. The build had to present that depth clearly and support a stronger digital presence and audience engagement — the platform is the front door to a professional services business, so structure and credibility were the design constraints. See the Mostazed case study.

A digital wallet handling money movement between users, built with a security model following current standards for data and transaction protection, instant operations with as few steps as possible, and an advanced dashboard that lets users track every detail of their account. Performance had to be stable and fast enough for daily use. See the Zidcash case study.

A platform for a medical supplies business covering a wide catalogue — products for seniors, orthopaedics, sports, daily care, medical shoes, mother and child, comfort and massage tools — plus a dedicated wholesale section serving a different kind of buyer with different pricing and ordering behaviour. Two commercial models in one system, with a clear policy framework and continuous performance and speed work. See the Al-Joud Med case study.

More of our work is on the projects page.

From our Riyadh head office at 4171 Al Mashtal St, Al Hazm, we deliver software projects across the Kingdom. Riyadh engagements are typically internal business systems — ERP-adjacent tools, dashboards, portals and integrations with existing accounting or HR platforms. In Jeddah we see more commerce and logistics systems: order management, inventory, and platforms that connect a warehouse to a storefront. In Dammam and the Eastern Province the work leans industrial: operations reporting, maintenance and inspection systems, contractor and supplier portals. We deliver these remotely with scheduled on-site workshops in your city for discovery, user acceptance testing and handover training, so you get the same senior team regardless of where your offices are. Arabic and English interfaces are treated as first-class requirements, not an afterthought, and RTL layouts are built into the design system from day one.

We price custom software after discovery, not before, and we say so plainly rather than publishing a figure that will not survive contact with your requirements. The models we work in are: fixed-scope phases, quoted as a single figure against a signed specification and invoiced at milestones — the usual choice for a first release; a retained team, a monthly fee for an agreed team shape, for organisations that keep building after go-live; and support and maintenance, a separate monthly agreement covering hosting oversight, security updates, monitoring, backups and a fixed allowance of change hours.

If you want to reduce risk on a large project, we will usually propose a paid discovery phase first: you get the process map, the specification and a firm price for phase one, and you own those documents whether or not you continue with us. Request a quote or book a free consultation.

There is no useful average. The cost is driven by the number of user roles, the number of integrations, whether you are migrating data from an existing system, and how much of the process is exception handling. We scope in a discovery phase and then commit to a fixed price for phase one, so you are approving a number attached to a specification rather than an estimate attached to a hope.

Buy, if a configured product covers your process without you having to change how you work. Build, when the process is your competitive advantage, when your data is trapped in disconnected systems, or when licence costs have outgrown the value you get. We will give you that assessment in discovery even when the answer costs us the project.

You own both. Development happens in a repository under your account, and the handover package includes source code, database schema, API documentation, deployment instructions and infrastructure access. You can move the system to another vendor or in-house at any point.

Usually. If the system exposes an API or a database we can integrate with it, and we agree the integration contract during architecture rather than discovering the limits mid-build. Where a system has no API we look at scheduled file exchange or a middleware layer, and we tell you honestly if the integration will be fragile.

Yes, as standard. Bilingual Arabic/English is the normal requirement for Saudi organisations, so RTL layouts, Arabic typography, and Arabic number, date and currency formats are designed into the system from the start rather than patched on. Terminology is reviewed by native Arabic speakers on our team.

A support and maintenance agreement covers security patching, dependency and framework updates, monitoring, backup verification and a fixed number of change hours each month. Larger changes are quoted as phases. Systems that are not maintained become security liabilities, so we would rather you had a plan for that in the contract.