Skip to content
HuloolX IT

Projects and concepts

What we delivered, and how we think

One platform in production, then three concepts that show how we would approach a problem. The concepts are labelled as such; none involves a client.

Delivered projectGovernment · Import and export licensing platform

Iraq's electronic import and export licensing platform

Client: Iraqi General Company for Fairs and Commercial Services · ecor.iq

Context
The company issues importer and exporter identities, import and export licences and shipping licences for Iraq. Applications, document checks, multi-stage approvals, fees, printed IDs and licence verification ran as separate steps. It needed one system that applicants and every kind of government staff could work in, in Arabic first.
What we built
The whole platform, live at ecor.iq. A bilingual, Arabic-first web application where businesses register, apply, pay and track their requests. A back office of twelve role-specific dashboards, from licence examiners, auditors and compliance checkers to sectoral entities, customs officers, finance and reporting. A .NET back end with multi-stage approval and return workflows, two-phase fees through a payment-gateway integration, scheduled expiry and renewal, QR-verifiable licences and printable IDs, blacklist screening with Arabic fuzzy matching, audit trails and financial reports. An AI assistant, deployed as a separate service. HuloolX IT delivered it end to end as the development partner of the prime contractor.
Today
In production, serving applicants and government staff in Arabic and English. 164 screens and 12 staff roles run on one front-end codebase, with monitoring and error tracking built in from launch.

Capabilities: Web platform · Backend development · System integration · Payment integration · AI assistant · Deployment and monitoring

Built with: Next.js · TypeScript · .NET 8 · SQL Server · OpenTelemetry

Related services

The public home page of ecor.iq in Arabic: the platform's headline over an aerial photograph of an aircraft, with sign-in and registration actions.
The services grid on ecor.iq: importer and exporter identity, import and export licence requests, establishment registration and COR-G certificates.
The sign-in page of ecor.iq: email and password fields on a card over a photograph of a container ship.
Public pages of the live platform, captured in September 2026.

ConceptLogistics · Operations platform

One system for orders, fleet and exceptions

Scenario
Imagine orders, dispatch and customer updates living in three tools that never agree. Dispatchers re-key details between them, nobody sees a late delivery until the customer calls, and every exception becomes a phone call.
Proposed solution
One operations platform over the systems already in place: the ERP stays the system of record, telematics and the support inbox arrive through an integration layer, and a shared data model feeds role-based workflows for dispatch and support, so an exception carries its whole history from detection to resolution.
Intended benefits
Exceptions would surface in one queue before the customer notices them, dispatch would work from a single screen instead of three, and support would answer from the same record dispatch is working on.

Capabilities: System integration · Backend development · Web platform · Cloud architecture

Related services

Concept interface — illustrative data
Integration mapArchitecture sketch — illustrative

ConceptFinancial services · AI document processing

Customer onboarding without the paperwork queue

Scenario
Imagine customer onboarding stalling on manual document review: files arrive in every format, and checks are repeated because nobody can see what has already been verified.
Proposed solution
A document pipeline that extracts and validates submitted files, an AI agent that raises mismatches to a human reviewer, and an audit trail behind every automated decision.
Intended benefits
Reviewers would spend their time on the cases the system flags, and every automated decision could be explained after the fact.

Capabilities: AI solutions · Workflow automation · API development · Deployment

Related services

Automation sequenceArchitecture sketch — illustrative

ConceptRetail · Commerce platform and mobile app

A storefront and an app that share one catalogue

Scenario
Imagine a web store and a mobile app built separately, so pricing, stock and content drift apart and every campaign has to be set up twice.
Proposed solution
A headless commerce backend, meaning the storefront is separated from the system that manages products and orders, with one catalogue and one pricing service, a rebuilt storefront, and a React Native app consuming the same APIs.
Intended benefits
Campaigns would be configured once and appear in both channels, and the app could ship on the same release cadence as the site.

Capabilities: Web platform · Mobile development · API development · Product design

Related services

Shared servicesArchitecture sketch — illustrative

In the three concepts, all records, figures and names shown are sample data.

Next step

Let's build the system your business needs next.

Tell us what you're trying to change. We'll tell you what it takes: the scope, the order of work and the constraints we can see.

Start a project

Or write to us directly
hello@huloolx.com

Replies come from the people who would do the work.