Flagship case study
OnSync
I built OnSync to give WhatsApp-first teams one place to manage customer conversations. The case study shows how I sequenced the foundation, handled provider constraints, and divided the product between web and mobile.
Hi, I'm Abdulaziz.I learned productby building it.
I've spent years working across customer problems, product decisions, and engineering. Now I want to bring that experience into a team.
View selected workSelected work · 01
What I built, why I built it, and what I learned.
Read the decisions
Three decisions I made while building OnSync.
Each one changed the product and what I chose to build next.
Foundation before channels.
I defined organization ownership and team access before connecting the inbox, so every later workflow inherited the right boundaries.
One inbox, different rules.
I used shared conversation models for consistency while keeping each messaging provider’s constraints explicit.
A focused mobile product.
I limited mobile to triage, replies, and notifications instead of copying configuration-heavy web workflows.
Career arc
I started by building for clients. Then I started owning the product decisions too.
Worked directly with clients to turn rough requests into clear scopes, websites, and applications.
Led client delivery, shaped requirements, made technical decisions, and managed the work from scope to release.
Owned the product from planning and system design through web, mobile, integrations, testing, and launch.
I want to bring what I have learned from building independently into a team and contribute at a larger scale.