I build products fromreal operational problems.
I turn fragmented workflows into software systems, test ideas in the market, and build products people genuinely use.
One connected flow.
Built around the business.
Information everywhere. A system nowhere.
Inventory, hospitality, property and workshop work showed me the same pattern: people spending their day manually joining information that already existed.
Invoice
No. 001842
The workshop stopped living in people's heads.
TeraMotors began inside a real auto-repair operation. Customers, vehicles, jobs, parts and payments needed one dependable place to move through the business.
Used in
Daily operations
Context
Saudi Arabia
Languages
Arabic + English
Role
Product + engineering
Built around the workshop's actual sequence—not a generic dashboard template.
Then I learned that building was the easy part.
VantLaunch began as a way to replace operational chaos with custom software. It became a practical education in positioning, outreach, validation and distribution.
Logistics
via Email
Workshops
via WhatsApp
Property
via DM
Recruitment
via Landing page
Hospitality
via Call
Security
via Ad
Hundreds of messages. Rewritten offers. Tested niches. Plenty of silence.
The result was not a neat success story. It was better judgment: attention, trust and demand are product problems too.
Products can create their own signals.
SpeakBill converts spoken work into structured invoices. More importantly, it showed a different kind of traction: people could discover, enter and explore the product without a direct conversation first.
New invoice
SpeakBill / listening
The workbench.
Different places.
Same curiosity.
Born in Sudan and raised across Saudi Arabia, Sudan, Türkiye and Malaysia. I study Information Systems at Universiti Malaya and learn fastest by building things that have to work outside a classroom.
Sudan
Origin
Saudi Arabia
Operations
Türkiye
Growing up
Kuala Lumpur
Building now
Archival map: Library of Congress, Geography and Map Division · 1900
A few rules earned through doing.
Observe before designing
The useful details usually live inside the work, not the brief.
Validate before building
A technically good product can still solve the wrong market problem.
Own the whole outcome
Interfaces, workflows, adoption and distribution are one connected system.
Ship, watch, improve
Reality gives better feedback than another week of speculation.