Operating in Complex B2B Systems
How I built and contributed to high-scale B2B products across telecom, marketplaces, and operational platforms
B2B Systems
Complexity
UX Craft
Living inside B2B systems
Throughout my career, I have consistently operated in B2B environments, where products are not just used by individuals, but by businesses managing money, operations, and large-scale decisions.
These environments are defined by:
High financial stakes
Multiple stakeholders
Complex workflows
Interconnected systems
The challenge is not just building interfaces. It is designing systems that businesses depend on.
Example 1: Rakuten Mobile – International Business (Japan)
At Rakuten Mobile’s International Business division, I worked on products that support global telecom operations.
This environment involves:
Partnerships with mobile operators and enterprises
Cross-border business operations
High-value transactions and large-scale deployments
Within this context, I contributed to building:
eSIM management dashboards for enterprise clients
Pricing intelligence layer for market positioning
AI-driven concepts such as roaming optimization
Supporting systems for voice and data transit businesses
These are not consumer tools.
They are operational platforms used by businesses to run telecom services.
The complexity comes from:
Handling large datasets (e.g. ICCIDs, plans, regions)
Supporting multiple business models
Aligning technical systems with commercial strategies
Example 2: Sary – B2B Marketplace (Saudi Arabia)
At Sary, I worked within a wholesale marketplace connecting businesses to suppliers across Saudi Arabia.
This ecosystem included multiple interconnected products:
Customer app (for business buyers)
Lighthouse (internal operations tool)
ARK (wholesale business interface)
Driver applications (last-mile logistics)
One business model, multiple products, each serving a different role in the system.
My role required:
Aligning experiences across all platforms
Designing workflows that connect operations, logistics, and commerce
Supporting internal and external users simultaneously
This created a deeply interconnected system where:
A single decision in one interface affects multiple actors across the chain.
Example 3: Suppy – End-to-End Retail & Grocery Platform
In Suppy, I worked on a platform that enables grocery retailers, supermarkets, and convenience stores to digitize their entire operations.
This is not a single product. It is a full ecosystem that includes:
Customer mobile applications (for end users)
Picker and fulfillment systems
Driver applications for last-mile delivery
Admin portals for operations and business intelligence
My role focused on:
Strategic communication and positioning
Translating complex product capabilities into clear business value
Enabling sales and growth through structured narratives and content systems
The challenge was not building features, but making a complex system understandable and sellable.
This required deep understanding of:
Retail operations
Inventory and pricing dynamics
Fulfillment and delivery workflows
The outcome:
Enabling businesses to move from fragmented operations to a fully integrated digital retail system.
Example 4: Noon Academy – Fintech & Education Systems
At Noon Academy, I worked within a fintech-focused initiative aimed at enabling tutoring businesses across multiple regions (Saudi Arabia, Pakistan, India).
The goal was to support:
Tutoring centers
Teachers
Students
Through systems that manage:
Courses and payments
Student enrollment
Teacher coordination
This required:
Aligning multiple stakeholders in one system
Structuring financial and operational flows
Designing scalable solutions across markets
I operate where multiple businesses interact
Across these experiences, a consistent pattern emerges:
I operate in systems where multiple businesses interact
I design for workflows, not just screens
I align technical, operational, and commercial layers
B2B products are not about simplicity. They are about clarity within complexity.
Reflection
Working across these B2B environments shaped how I think:
A B2B product is not defined by its interface.
It is defined by how many moving parts it can align without breaking.
© Ahmed Ramadan 2026
