INVENTORY · ASSET TRACKING · DUBAI
I'm Emad Yahya — a systems engineer in Dubai who builds custom inventory and asset management systems: stock, equipment and IT hardware tracked in one platform your company owns. No per-user subscriptions, no monthly fees — a system shaped to how your stock actually moves, replacing the spreadsheet that is always one missed update from wrong.
This is in production, not a pitch: my IT Asset Manager tracks 150+ company devices for a Dubai real estate firm — zero untracked assets since deployment — and my Arabic-first pharmacy POS keeps sales and inventory in one system, so stock moves the moment the counter sells.
The IT Asset Manager exists because asset tracking was my own problem: I run the IT estate for a Dubai real estate firm, and device tracking lived in an error-prone spreadsheet — no assignment history, no liability records, no audit trail, and assets went missing. The system replaced it entirely: every assignment, transfer and return recorded per employee, liability agreements and maintenance logs attached to each device, and audit trails generated automatically. The result: 150+ devices under continuous audit and zero untracked assets since deployment.
The pharmacy POS proves the stock side: sales flow through the same system that watches inventory, so the owner's stock dashboards describe the same reality the counter just created — no separate reconciliation step, no spreadsheet drifting out of date the day after it was updated.
Subscription inventory and asset tools charge per user, per month, forever — and most force your workflow into their template. What I build is priced once, as a project: no seat licenses, no monthly fees, and you own everything — code, database, hosting and accounts, all registered in your name.
An honest note from running one of these systems myself: the software is the easier half. A tracking system only works if it is the sole path stock and devices travel through — a single handover outside it quietly reintroduces the spreadsheet problem. So the build includes the process side: your existing sheets migrated in, staff onboarded, and workflows kept simple enough that people actually use them.
Scope drives it. Counting stock at a single store is a different build from tracking assigned assets across departments and sites, and stock counts, adjustment approvals and reporting each add work on top. I price the whole build once, against the feature list we agree on, and that number reaches you in writing within 24 hours of your brief. Nothing is charged per seat or per month after launch — the system is yours.
Yes, and that is where the system came from: I ran device tracking for a Dubai real estate firm on a shared sheet where anyone could overwrite a quantity and nobody could prove who did. What replaced it keeps the data and changes the rules — each item becomes a record rather than a row, only the roles you authorise can adjust a quantity or reassign an asset, and every change carries the person and the time behind it. Your current sheet is imported at the start, so the history you already have comes with you.
Yes — barcode-driven workflows are proven in my pharmacy POS, where the scanner is the primary input at the counter: scan, price, sell. The same approach applies to receiving stock, issuing assets and running counts.
Yes — that is precisely what my IT Asset Manager does in production: every assignment, transfer and return recorded per employee, liability agreements and maintenance logs attached to each device, and dashboards showing deployment status across departments. 150+ devices, zero untracked since deployment.
Honest answer: if your needs are tiny and standard, a subscription tool is a fine start. The math changes as users and locations grow — subscription pricing is per user per month forever, while a custom build is priced once and owned. Custom also wins when your workflow never quite fits the templates: approval chains, handover agreements and reports built around how you actually operate.
A single-site tracker covering the core movements — receiving, issuing, counting, returning — takes 2–4 weeks. Bring in several locations, adjustment approvals and department-level reporting and it runs 4–8 weeks. Those windows come from builds already running in Dubai, not from an estimating sheet.
Yes — a storekeeper can receive stock, run a count or adjust a quantity entirely in Arabic, on screens laid out right-to-left rather than flipped. I wrote the interface language myself for a pharmacy POS that was Arabic-first from its first screen, and the same standard applies here: no machine-translated labels sitting on top of an English system.
Emad Yahya — portfolio · emaadyahya4@gmail.com · WhatsApp +971 566 392 647