Services
I work with founders, business owners and teams who need a product built properly rather than quickly. Below is what that looks like in practice.
- 01
Product discovery & technical planning
Who it is for: Founders and business owners with an idea, a spreadsheet, or a broken process.
What it solves
You know what the business needs but not what should be built, in what order, or what it will cost you technically.
How I work
I start with how the business runs today, not with technology. The output is a plan you could hand to another engineer.
Typical deliverables
- Product scope and module breakdown
- User flows and role model
- System architecture and data model outline
- Task plan and delivery milestones
Proof
Client productIMMAR - 02
Full-stack SaaS & web application delivery
Who it is for: Businesses that need a real product, not a prototype that stalls at 80%.
What it solves
You need one person accountable from data model to interface, who will finish it and deploy it.
How I work
Vertical slices — each one shippable — so you see working software throughout rather than at the end.
Typical deliverables
- Complete web application, frontend and backend
- Authentication, roles and permissions
- Deployment, environments and handover documentation
Proof
Founder productSendy - 03
Backend systems & API architecture
Who it is for: Teams with a frontend, a mobile app, or a partner integration that needs a solid API behind it.
What it solves
Your business rules are scattered, duplicated across clients, or impossible to audit.
How I work
All business rules live in one place. Clients render and validate for the user — they never become a second source of truth.
Typical deliverables
- REST API with validated contracts
- Clean Architecture / layered structure
- Database design, migrations and seed data
- Auth, RBAC and audit logging
Proof
Independent buildVirtual Banking API - 04
Dashboards & operational platforms
Who it is for: Operations teams drowning in spreadsheets, WhatsApp groups and paper.
What it solves
The information exists but nobody can see all of it at once, and nothing reconciles.
How I work
Designed for the person who uses it eight hours a day, which is a different problem from designing for a demo.
Typical deliverables
- Role-based operational dashboard
- Data tables with filtering, pagination and bulk action
- Reporting and export surfaces
- Complete loading, empty and error states
Proof
Client productAl-Tafawuq School System - 05
Arabic/English bilingual product implementation
Who it is for: Products serving Iraqi and regional users alongside international ones.
What it solves
Your product was built LTR and the Arabic version is a mirrored afterthought that breaks on every dense screen.
How I work
Both directions are designed, not derived. This is structural work, and it is much cheaper to do early.
Typical deliverables
- Logical-property layout system
- Authored RTL behaviour for navigation, tables, dates and forms
- LTR isolation for technical and numeric tokens
- Localised validation, metadata and accessibility labels
Proof
Founder productSendy - 06
AI integrations & workflow automation
Who it is for: Businesses with a manual, repetitive information-handling step.
What it solves
Someone is retyping, re-checking or re-routing information that a system could handle.
How I work
The interface matters as much as the model. An output nobody can verify is not a result.
Typical deliverables
- Inference or extraction pipeline
- Service interface over the model
- A verification UI so results can be trusted or corrected
Proof
Hackathon projectNANO - 07
Production hardening, debugging & deployment support
Who it is for: Teams with something built that is not reliable, not deployed, or not maintainable.
What it solves
It works on a developer machine, breaks in production, and nobody is sure why.
How I work
I find the smallest root cause rather than the fastest patch, and I document what I changed.
Typical deliverables
- Environment configuration, domains and DNS
- Deployment on Railway, DigitalOcean or similar
- Error handling, audit logging and failure recovery
- Handover documentation and seed/test data
Proof
Client productAl-Tafawuq School System
Scope, timeline and budget
I do not publish fixed prices, because a number quoted before understanding a product is a guess dressed as a commitment. Tell me what you are building and what is blocking it, and we will discuss scope, timeline and budget once the shape of the work is clear. If the project is not a fit for me, I will say so early.