Skip to content

Technology × Product × Business

MohammedAlakel

I build products, systems and businesses.

I work across the whole arc of a product — the strategy that justifies it, the architecture that holds it up, the interface people actually touch, and the operation that keeps it running. My work spans web platforms and SaaS, AI and automation, marketplaces, games, and 3D / interactive experiences.

Scroll

01 / Identity

I don’t fit into
one title.

The through-line is systems: understanding a domain well enough to model it, then building something that survives contact with real users and real operations.

  • Technology Leader
  • Product Builder
  • Solution Architect
  • AI & Automation Builder
  • Business & Technology Strategist

Technology × Product × Business

02 / Selected work

Things I have built, and what they had to solve.

01

Marketplace

V-Store

A marketplace for 3D assets, built for creators on both sides of the transaction.

VStore
Status
Ongoing
Domain
Marketplace, 3D, Platform

Problem

A marketplace has to solve both sides at once, and it has to solve them before either side has a reason to be there. Catalogue quality, licensing clarity and the operational cost of moderation are the real constraints — not the storefront.

Approach

A two-sided catalogue covering free and paid distribution, creator publishing, and the marketplace operations underneath it: listings, categorisation, transactions, and the review workflow that keeps the catalogue worth browsing.

02

AI

AreebAI

An adaptive AI learning and training platform with multilingual, metered access.

AreebAI
Status
Ongoing
Domain
AI, SaaS, EdTech

Problem

Learner experience and unit economics pull in opposite directions. Generous AI interaction is what makes the product work; uncapped AI interaction is what makes it unaffordable. The platform has to hold both.

Approach

An adaptive learner experience with a multilingual surface, backed by subscription tiers, token controls, and payment and invoicing flows — plus a distinct administrative experience for the people running the programmes.

03

AI

Al-Mufatish

Inspection and document control, with AI-assisted monitoring on top.

AI / Operations / Platform

Inspection and document control, with AI-assisted monitoring on top.

Status
Ongoing
Domain
AI, Operations, Platform

Problem

Inspection and document control fail in the gaps: an observation captured in one place and filed in another, a revision nobody propagated, a finding with no chain of custody. Automated monitoring only helps if it lands inside that record.

Approach

Inspection workflows and document tracking held in one controlled record, with AI and computer-vision monitoring feeding the same system rather than sitting beside it.

04

Games

Skidz

A Unity mobile multiplayer game built on real-time networked competition.

Games / Mobile

A Unity mobile multiplayer game built on real-time networked competition.

Status
Shipped
Domain
Games, Mobile

Problem

Competitive play needs players to agree on what just happened. On mobile networks they frequently do not. Matchmaking, state synchronisation and reconnection have to be designed as gameplay features, not infrastructure.

Approach

Real-time multiplayer built on Photon, with competitive modes and the mobile game systems — session flow, synchronisation, progression — that hold them together.

05

Games

MARS

A gamified learning experience where the game mechanics carry the teaching.

Games / EdTech / Mobile

A gamified learning experience where the game mechanics carry the teaching.

Status
Shipped
Domain
Games, EdTech, Mobile

Problem

If the mechanic and the learning objective are separable, players optimise the mechanic and skip the learning. The teaching has to be the thing the player is actually doing.

Approach

A mobile game whose mechanics carry the educational content directly, built to work across languages rather than translated after the fact.

06

Operations

Mithar

A business and inspection-oriented web system.

Operations / Web

A business and inspection-oriented web system.

Domain
Operations, Web

03 / Project universe

The wider body of work.

Platforms & Marketplaces

08

04 / Capabilities

Four disciplines that have to agree before anything ships.

Strategy

Decide what is worth building, and what the system will refuse to do.

  • Technology strategy and platform direction
  • Opportunity framing and scope definition
  • Build / buy / integrate decisions
  • Technical due diligence on an existing codebase
  • Roadmap sequencing against real constraints

Product

Turn a domain into a product people can actually operate.

  • Product definition and requirement modelling
  • Information architecture and user flows
  • Interface and interaction design direction
  • Prioritisation under delivery pressure
  • Release planning and iteration loops

Engineering

Design the architecture, then build the thing that has to hold up.

  • Solution and system architecture
  • Full-stack web platform and SaaS development
  • AI and automation integration
  • Game systems and real-time multiplayer
  • 3D and interactive experience engineering
  • Data modelling and API design

Business

Make the product survive outside the demo.

  • Business development and partner-facing delivery
  • Commercial modelling for metered and subscription products
  • Operations design and process automation
  • Stakeholder and client communication
  • Team coordination across disciplines

05 / Technology

The ecosystem I work inside.

A taxonomy, not a badge wall. These are the places I have actually spent time — grouped by the kind of problem they solve rather than by logo.

WebProduct surfaces and the platforms behind them.
  • TypeScript
  • React
  • Next.js
  • Node.js
  • Tailwind CSS
  • GSAP
  • REST & API design
  • PostgreSQL
AIApplied, inside a product — not as a demo.
  • LLM application design
  • Prompt & context engineering
  • Retrieval-augmented generation
  • Computer vision
  • Workflow automation
  • Usage metering & token control
GamesReal-time systems where latency is a design problem.
  • Unity
  • C#
  • Photon
  • Multiplayer networking
  • Gameplay systems
  • Mobile builds
3DAssets, pipelines and interactive presentation.
  • Real-time 3D
  • Asset pipelines
  • WebGL / Three.js
  • Blender
  • Interactive scenes
Cloud & DeliveryGetting it in front of people and keeping it there.
  • Vercel
  • CI/CD
  • Git & code review
  • Environment management
  • Observability
DataThe model underneath the interface.
  • Relational modelling
  • Analytics instrumentation
  • Reporting surfaces
  • Integrations

06 / Method

How a thing gets built.

  1. 01

    Understand

    Learn the domain until the constraints are obvious, not the features.

  2. 02

    Validate

    Find the cheapest evidence that the problem is real and worth the build.

  3. 03

    Architect

    Decide the model, the boundaries, and what the system will never do.

  4. 04

    Design

    Shape the interface around the decision the user is actually making.

  5. 05

    Build

    Ship in slices that each stand on their own in production.

  6. 06

    Measure

    Instrument the few signals that would change what happens next.

  7. 07

    Iterate

    Cut what did not earn its place. Deepen what did.

  8. 08

    Scale

    Harden the operation before the volume arrives, not after.

07 / Résumé

The short version.

I work across the whole arc of a product — the strategy that justifies it, the architecture that holds it up, the interface people actually touch, and the operation that keeps it running. My work spans web platforms and SaaS, AI and automation, marketplaces, games, and 3D / interactive experiences.

Full experience, education and certifications are on the résumé page and in the CV.

08 / Philosophy

Good systems are opinionated about the few things that matter.

Most product failures are not engineering failures. They are failures to decide — to name the user, to name the constraint, to name the thing the system will refuse to do. I spend the expensive part of a project there.

The rest is craft: choose boring infrastructure for the parts that must not break, spend the innovation budget where it is visible to the user, and keep the model simple enough that the next person can hold it in their head.

Held interests

  • Systems design
  • Marketplace mechanics
  • Applied AI
  • Game feel
  • Real-time 3D
  • Typography
  • Operations & process
  • Interactive narrative

09 / Contact

Let’s build something.

If you are hiring for a role that spans technology, product and business — or you have a system that needs designing before it needs building — tell me what you are working on.

Your message and address are used to reply, nothing else.