Independent product builder. Strategy to launch.
I am Mohamed Motassem, an independent product builder based in Istanbul. I help founders and small businesses turn ideas into shipped digital products by combining product strategy, UX/UI design, AI-assisted development, full-stack implementation, and launch support.
Before working independently, I was Head of Design at webkeyz, leading UX and UI teams across product design, digital transformation, design operations, delivery governance, and AI-focused service evolution. Earlier, I designed digital experiences for large-scale media products at Al Jazeera Media Network.
My work sits between strategy and execution: define the product, design the experience, build the system, prepare the content structure, and support the launch.
One accountable owner, not a handoff chain.
I work independently because the strongest product work happens when strategy, design, and build stay in one head — instead of being split across account managers, specialists, and handoffs that lose the intent at every step.
- Fewer handoffs — one head holds strategy, design, and build.
- Ship what matters — the first serious version, not a feature museum.
- Proof over polish — promotions verified in a real browser, not a status report.
- Honest scope — a clear starting point, and a straight answer on fit.
From web craft to product leadership.
Working in digital since 2004 — the documented chapters below pick up from the first senior design roles: hands-on interface craft, then design leadership, and now end-to-end product building.
- 2012–13
ZAD Solutions — Senior Graphics Designer
Design work in Cairo, sharpening the visual craft that everything after was built on.
- 2013–18
webkeyz — Senior UI/Visual Designer → Lead UI Designer
Grew from hands-on UI craft into leading and mentoring the agency’s UI team across its product work.
- 2019–24
Al Jazeera Media Network — Senior Product Designer
Five years building and evolving a design system across six news websites and their editorial publishing interfaces — product design at large media scale.
- 2024–26
webkeyz — Head of Design
Returned to lead UX and UI teams across product design, design operations, delivery governance, and mentoring — and shaped the agency’s AI-transformation service offerings.
- May 2026
Independent Product Builder
Went fully independent, from Istanbul — product strategy, UX/UI, AI-assisted development, CMS, and launch support to take founders from idea to shipped product as one accountable owner.
Along the way, webkeyz client builds included Pfizer’s Dr. Advizer app and Microsoft’s LUIS web app.
View selected workWhat leadership said about the work.
A cornerstone of my company’s growth from a startup to a 7000% growth company … very well organized, committed … he never breaks a deadline … a unique asset to any creative company.
Clear handover, and specialist help when the work needs it.
A solo delivery model does not mean pretending every problem is the same size. Scope records what I own, what the client owns, and when specialist support is required.
I own
Product direction, UX/UI decisions, implementation, QA, and launch coordination
Clear documentation of the working system and handover steps
We agree
Content go-live, project-account access, deployment ownership, and post-launch support
Specialist engineering or infrastructure support when complexity demands it
Questions founders ask.
Can you work with an existing website or product?
Yes. Platform rebuilds and CMS migrations are a core engagement: I can audit the current structure, preserve valuable content, redesign the experience, and move the product onto a maintainable launch path.
What if I only have an idea?
Start with the Product Clarity Sprint. It turns the idea into a written first scope, prioritized user journeys, and a launch roadmap before a larger design or build commitment.
What do you need from the client?
A decision-maker, access to the current product or content, timely feedback, and a clear launch goal. Content readiness and specialist third-party accounts are confirmed before they affect the timeline.
When do you bring in specialist engineering support?
I stay hands-on when the work fits one senior owner. Complex backend systems, native apps, unusual integrations, or specialist infrastructure are identified during scoping and added as a separate, explicit requirement rather than hidden inside the estimate.
How do ownership and handover work?
The scope records who owns decisions, content go-live, project accounts, source code, and deployment access. Handover is part of launch, so the client is not left dependent on an undocumented setup.
Think we'd work well together?
If you want one accountable owner from strategy to launch, tell me about the product — I'll be honest about whether I'm the right fit.