Paper → structured data
Forms with validation, mandatory fields and barcode/QR input — entered once at the source, formatted correctly. No retyping, no "which version is right?".
Service — Business Automation AppsCairo, Egypt — open to remote
Automate the manual work with a mobile app
Somewhere in your business, work still moves on paper and WhatsApp: inventory counted by hand and retyped into Excel, forms duplicated into a system, approvals waiting on someone's presence. A well-built internal app removes those loops — data is entered once, validated at the source, and every stakeholder sees the same numbers.
This is the operational sibling of a business app: less about your customers, more about your inventory, field teams, workflows and the hours your staff lose to data entry. It has to work in basements and warehouses where the network doesn't — which is exactly where my experience lives.
3+ yrsprofessional experience
10+production apps today
EG · LB · AEclients served
What gets built:
Inventory & asset tracking
Stock counts, movements and audits from the phone — RFID and NFC where hardware exists (readers via native channels), barcode scanning where it doesn't.
Offline-first field work
Reps and warehouse staff keep working with no signal; everything queues and syncs when connectivity returns, with conflict rules decided up front.
Workflows & approvals
Requests that route themselves — roles, permissions, approvals and notifications, with an audit trail of who did what, when.
Live numbers
Dashboards and exports your managers actually check — stock levels, task status, team output — updated as the work happens, not at month-end.
- Field teams
Sales reps, technicians, collectors — people whose work happens away from a desk and a stable connection.
- Warehouses & retail ops
Counting, receiving, transfers and audits — high-volume data entry where minutes per scan decide the shift.
- Multi-branch businesses
Head office wants the numbers; branches want simple screens. One app, role-based views, one source of truth.
How it ships:
01Map the real process
I shadow the workflow as it actually runs — including the spreadsheet nobody admitted to. We automate what's real, not the org chart.
02Design for speed
Screens designed around gloves, glare and one-handed use: big targets, few taps, offline states visible at a glance.
03Build & pilot
One branch or team pilots on weekly builds; sync conflicts and edge cases surface at small scale, not company-wide.
04Roll out & measure
Phased rollout with training; adoption and time saved are measured against the paper baseline it replaced.
- Offline-first sync
Unilever field-sales and warehouse apps I built run through intermittent networks and reconcile when the signal returns — the hard part is the conflict rules, and those are designed, not hoped for.
- Large datasets, fast UI
Catalogs and stock files in the thousands stay responsive — isolates, pagination and local storage tuned so reps spend seconds per screen.
- Hardware when it helps
RFID/NFC readers, barcode scanners and printers through native platform channels — the phone as a tool, not a toy.
- Integrations, guarded
REST/SOAP into ERP or accounting with OAuth2/JWT — automation that writes into your existing systems, not another island.
Shipped at scale: Unilever's sales-management and warehouse-inventory suite (offline-first, huge catalogs, long shifts) and RFID access/inventory systems for Alexandria Sporting Club, Arab Open University and Export Development Bank of Egypt.
See the selected work on the main page →
Show me the spreadsheet you hate.
Send the process that hurts most — a form, a count, a handoff — and you'll get a straight answer on what an app would change and what it wouldn't.