Technology & digital transformation

Software Development: web, mobile and enterprise systems built around your work

We build software that supports real workflows: web and mobile applications, internal enterprise systems, portals for customers or citizens, and APIs that connect systems. We also take over and improve existing systems when that makes more sense than replacing them.

Send a project request WhatsApp

What we offer

Every project starts with understanding the work before writing code: who uses the system, which processes it supports, what data it handles and which other systems it must connect to. We turn this into a requirements document and screen prototypes that your team reviews and approves, then develop in short phases that can each be tested on their own.

Our scope covers administrative web applications and dashboards, mobile apps for Android and iOS, enterprise systems such as request, inventory and resource management, multilingual portals with full Arabic and right-to-left support, and APIs and integration layers between systems. Access rights, audit logs, data protection and maintainability are designed in from the start.

Where you already have a system, we begin with a technical review of the code, architecture and database and propose a gradual improvement plan: fixing recurring faults, adding missing functions, improving performance and updating outdated components without stopping day-to-day operations. In all cases we hand over source code and documentation as agreed in the contract.

Who it is for

Ministries and public institutionsNeed internal systems or Arabic-language service portals with multiple roles and formal approval paths.
Hospitals and healthcare organisationsNeed administrative and operational software that integrates with existing systems and protects sensitive data.
Commercial and industrial companiesWant to replace spreadsheets and paperwork with one system for orders, inventory or sales.
Investors and new businesses in SyriaNeed a digital platform for a new operation, built in phases according to budget and priorities.
Organisations with legacy softwareDepend on a system that is no longer maintained and need someone to understand and develop it safely.

Problems we address

Processes run through spreadsheets and scattered messages, so information is lost and nobody can see who did what and when.
A legacy system that handles Arabic poorly, does not run on current devices, or stalled because the original developer is gone.
Separate systems that do not exchange data, so the same information is entered several times.
A need for a portal or mobile app so customers or citizens can use services without visiting in person.
Earlier software projects that failed because requirements were unclear or testing and documentation were missing.
Unreliable reporting because data is unstructured or incomplete.

Tasks and deliverables

Requirements analysis and scope document: A written description of users, processes, data and integrations, approved before development and used as the shared reference.
Screen prototypes: Interactive designs of the main screens in Arabic and English that users can try before coding, reducing costly changes later.
Web application or enterprise system: A browser-based system with user roles, audit log, dashboards and reports within the agreed scope.
Mobile application: An Android and iOS app or a responsive web app, connected to the back end and prepared for store publication where needed.
APIs and integrations: Documented APIs to connect with other systems such as accounting, payment gateways or public-sector systems, as far as those owners allow.
Further development of an existing system: A written technical review of the current system and a prioritised improvement plan, then delivered in tested increments.
Testing and handover: Functional tests and a user acceptance phase with your team, followed by handover of source code, user guide and technical operations guide.

Who does what

What IAG does

Analyse requirements with stakeholders and write the scope document.
Design the architecture, database and user experience.
Develop, test and manage releases in phases.
Prepare technical documentation and user guides and train the team.
Coordinate with hosting providers or owners of other systems for integration.
Provide post-launch support and further development under a written agreement.

What specialists, partners and authorities do

The client names a project owner, provides information and approves requirements and acceptance test results.
Owners of other systems enable integration and provide technical documentation and the necessary access.
Any sector-specific regulatory requirements, such as data protection rules, are defined by the competent authority or the client's legal adviser.

Practical example

Illustrative scenario

Maintenance request system for a multi-branch company

A company with several branches receives equipment maintenance requests by phone and messaging, and management cannot see how many requests are open or how long they take.

Short workshops with branch managers and the maintenance team to document the current request path.
Prototype of the request form, the technician view and the management dashboard.
First version developed and piloted in one branch for a defined period.
System adjusted based on user feedback, then rolled out to other branches.
Mobile app added so technicians can update request status on site.
User training, documentation handover and agreement on the support level.

This is an illustrative scenario to explain our approach, not a client reference.

How we work together

Discovery
We learn your goals, processes and current systems and define what the first version must include and what can wait.
Analysis and design
We write the requirements, design prototypes and architecture, and approve them with you before coding.
Phased development
We develop in short increments and present each one to your team for testing and feedback.
Testing and acceptance
We run functional, performance and permission tests, then your team performs acceptance testing on real scenarios.
Launch and training
We deploy to the agreed environment, migrate data where needed and train users.
Support and continuous development
We monitor operation, handle feedback and plan further releases under the support agreement.

Intended results

Consistent, traceable processes instead of information scattered across files and messages.
Structured data that supports clearer reports for decision-making.
A documented system that your team or any later technical provider can understand and maintain.
A technical foundation that can grow with new functions or integrations in phases.

What we need from you

A project owner with authority to make decisions and approve phases.
An explanation of current processes, forms and reports in use today.
Participation of actual users in workshops and acceptance testing.
Documentation of existing systems and integration access, shared through agreed secure channels, not via the public website.
Test or anonymised sample data where needed.
Preferred hosting environment and any internal security or data protection requirements.

Basis for cost and timeline

Cost and duration depend on the size of the scope, the number of roles and screens, the number of integrations, multilingual and mobile requirements, and the condition of any existing system. For well-defined projects we agree a fixed price for a fixed scope; larger projects are split into phases, each priced once its requirements are approved; ongoing development and support are agreed as a monthly or annual retainer. We provide a written quote after the discovery session.

Frequently asked questions

Can you develop a system that another developer built?

In many cases, yes. We start with a technical review of the code and architecture and tell you honestly whether gradual development is feasible or whether rebuilding some parts makes more sense.

Who owns the source code after handover?

Ownership and usage rights are defined in the contract. Our usual approach is to hand over source code and documentation to the client when the agreed phases are completed.

Do your systems fully support Arabic?

Yes. Interfaces are designed from the start for Arabic and right-to-left layout, with English or other languages added as required.

Can we start small and expand later?

That is usually what we recommend. We define a first version covering the most important process, then add functions in phases after real-world use.

Where is the system hosted?

That depends on your requirements: a cloud provider, a private environment or servers inside your organisation. We can handle setup and operation through our hosting service.

Request this service