Something rare is loading.

0% · summoning #001

Back to the collection

#004 · Financial Strategist · Rare · March 2026 to present

Oumla

Primary designer across Oumla's product suite: product UX, design systems and marketing material, delivered bilingually in English and Arabic RTL.

Lead Product Designer (part-time contract) · OumlaLead Product Designer, part-time contract since March 2026. Three products, three design systems from scratch built with AI and agents, website pages, booth materials, sales and partnership decks, and templates for the business team.

StatusOngoing engagement. Screens stay private while the contract runs; scope and products are listed below.

#004Financial Strategist
Rare

Oumla

Primary designer across a tokenized finance suite: three design systems, three products, English and Arabic RTL.

March 2026 to presentTames tokenized finance
View case study
Status

The card carries what can be shared today. Ask me about the rest.

The challenge

Loose, inconsistent product files across a suite of tokenized finance products, with regulatory weight, institutional users and Arabic RTL as a hard requirement.

What I led

All product design across the suite: product UX, design systems and marketing material, bilingual in English and Arabic RTL.

What shipped

Three design systems from scratch (TFM, Dashboard and Bahith), built with AI and agents, RTL as a first-class deliverable, website pages for the revamp, booth materials, sales and key-partnership decks, and templates for the business team: slides, documents and official documents.

01 · Product leadership

Leading design across Oumla's products.

From complex financial workflows to shared product foundations.

As Lead Product Designer I lead design across Oumla's tokenized finance products: product UX, the design systems underneath them, and the marketing and communication material around them, delivered in English and Arabic RTL. Three of the products are below; the role spans the whole ecosystem.

TFM

Tokenized Fund Marketplace

Secondary market trading for tokenized funds, as a white-label platform and a bespoke client version.

My contribution
  • Led the marketplace design
  • Secondary market trading, approval and settlement flows
  • TFM Design System, built from scratch
Dashboard

Oumla Dashboard

Oumla's dashboard, where roles, permissions and members are managed.

My contribution
  • Role-based access control: roles, permissions matrix, member management
  • Dashboard Design System derived from the product, then governed
Bahith

Blockchain explorer

Oumla's blockchain explorer.

My contribution
  • Design system rebuilt from tokens up
  • Declared complete this month

Interface screens stay private while the contract runs.

02 · Design systems

Three design systems. Built from scratch.

Loose, inconsistent product files became systems engineers build against, each produced with AI and the agents I set up, each approved by me before anything was published.

  1. 01

    TFM Design System

    From scratch, for the marketplace.

    In use
  2. 02

    Dashboard Design System

    The product had no system and inconsistent screens; components and tokens were derived from the designs, then governed.

    In use
  3. 03

    Bahith Design System

    Same approach: derived from inconsistent designs, rebuilt from tokens up.

    Complete
What every system carries
Tokens
Color, type, spacing and radius, bound to components rather than hardcoded.
Components
Variants and interaction states, named and approved before the library is built.
RTL and LTR
Direction decided per element during production, so Arabic is designed in, not mirrored later.
Compliance
Sweeps across files so the product matches the system after every change.
03 · Beyond the product

From product interfaces to the bigger picture.

The same identity and the same two writing directions carried into everything around the products.

Business and investor materials are shown on request.

04 · AI-native workflow

AI-assisted production. Designer-led decisions.

Claude, through the Figma MCP and Claude Code, does the production-heavy work. I set the direction, approve every decision that shapes the product, and validate what ships.

  1. 01ReadAgents

    Product screens are audited into spec cards: what exists, what repeats, what conflicts.

  2. 02DecideMe

    I approve variants, names and tokens. Nothing is built until this is signed off.

  3. 03BuildAgents

    The library is built in Figma to the approved spec: tokens bound, components assembled, screens converted to RTL, decks laid out.

  4. 04DeliverMe

    Compliance sweeps across files, a final review, then the system, screens and decks ship to engineering and the business.

Agents and tools assist with
Building and binding tokens and components; converting screens to RTL; laying out multi-slide decks; running compliance sweeps. Galley, my own Figma plugin, serves the copywriters; published Claude artifacts prototype interactive website concepts.
Decisions I make
Scope and priorities; variants, names and tokens; what counts as consistent; what is good enough to ship.
How designs are validated
Spec cards checked against the product before building; compliance sweeps after; review with engineering and the business before release.
The impact

What changed.

3Design systems from scratch, built with AI and agents

TFM, Dashboard and Bahith; two of them derived from inconsistent designs with no system.

DeliveryArabic/RTL as a first-class deliverable

Across products and documentation, designed in rather than patched on.

MaterialsDecks and templates the business team reuses

Booth materials, the sales deck and key-partnership decks, and templates for slides, documents and official documents.

The takeaway

A repeatable AI-assisted production process lets one designer cover the output of a much larger team, with design decisions kept firmly in my hands.

Let's talk

Let's make
it happen.

For product leadership, ambitious projects, and interesting collaborations.