The problem we solve
Most products are structured around the database schema or the org chart rather than the job the user came to do. The symptoms are familiar: crowded screens, steps nobody can justify, forms people abandon halfway. Teams usually discover this after launch, when changes are expensive and the support queue is full of questions the interface should have answered. Arabic versions suffer most, because direction, typography and terminology get treated as a late translation task instead of a design decision. We deal with all of it while change is still cheap.
Expected outcomes
- Shorter, more obvious routes through the tasks that actually matter.
- Fewer repeat support questions caused by an unclear interface.
- Design decisions grounded in observed behaviour rather than opinion in a meeting room.
- An Arabic interface designed in Arabic, not a mirrored copy of the English one.
- One consistent visual language across screens instead of drift between them.
- A cleaner handover that reduces back-and-forth during the build.
Who this is for
- Product teams building a platform who need a design foundation before they scale.
- Companies with an internal system that works technically but staff avoid using.
- Startups wanting to validate an interface idea before spending engineering budget.
- Organisations running several products with inconsistent interfaces.
- Commercial teams seeing users drop out at a specific step without knowing why.
Use cases
- Rebuilding a crowded dashboard around the tasks people really perform.
- Simplifying a long signup, application or checkout flow that loses people midway.
- Creating a unified design system for a product that grew faster than its interface.
- Designing a proper Arabic experience for a product originally built in English.
- Validating a new product concept as a tested prototype before committing to build.
- Auditing accessibility on an existing interface and fixing what blocks people.
Deliverables
- A research summary showing what we observed and what each decision rests on.
- User flow maps for the core journeys.
- An organised design file covering mobile and desktop in both text directions.
- A clickable prototype of the pivotal flows.
- A documented design system: colour, type, spacing, components and their states.
- Approved interface copy in Arabic and English.
- A developer handover document covering behaviour, edge cases and accessibility criteria.
Project phases
Framing
A working session on core tasks, constraints, target users and how success will be judged.
Research
Interviews or usage observation, a review of the current interface and any available data, written up as findings.
Structure
Information architecture, task flows and wireframes, signed off before visual detail begins.
Design & prototype
High-fidelity screens, a component system, and a prototype covering the pivotal journeys.
Testing
Running the prototype with people from your audience, then resolving the friction we see before code is written.
Handover & support
Design system documentation, an engineering handover session, and review of built screens against the approved design.
- Estimated timeline
- 4 to 9 weeks
- An estimate that depends on scope and how quickly reviews come back — not a contractual commitment in itself.
- Pricing
- After scoping
- Cost depends on how many pivotal screens are involved, how much research is needed, and whether you want a full design system or a targeted fix to one journey. A scoped proposal follows the framing session.
Scope and working details
What is in and out of scope, how we work, and what we need from you.
What is included
- Framing sessions with your team and stakeholders to agree on core tasks and success criteria.
- Interviews or observation with real users from your audience, where the project allows.
- Review of available usage data to locate where people currently stall.
- Information architecture and task flows for the primary journeys.
- Wireframes followed by high-fidelity screens for the pivotal moments.
- A clickable prototype tested with users before development starts.
- A design system with documented components, states and usage rules.
- Interface copy in Arabic and English: labels, error messages, empty states.
- Accessibility review covering contrast, target sizes, keyboard navigation and reading order.
- Engineering handover session, with specifications and support during the build.
What is not included
- Front-end or back-end development — agreed as a separate phase or service.
- Building a brand identity from scratch; we work within yours and extend it for digital use.
- Complex motion work, illustration series or photo and video production.
- Large-scale usability studies requiring a paid participant panel, unless agreed explicitly.
- Open-ended design revisions after a phase is signed off; review rounds are agreed upfront.
How we work
We agree first on the job the user is hiring the product to do and how we will know it worked. Then we gather enough observation to design from reality rather than assumption. Work runs in short phases, each ending in something concrete you can react to — a flow map, a wireframe, a prototype. We prefer to break an idea on paper, because correcting course at that stage costs a fraction of correcting it in production. And we do not disappear at handover: we stay with engineering until the built screens match what was approved.
What we need from you
- A named decision-maker who can sign off phases and respond within agreed timeframes.
- Access to real users, or to staff who work in the system daily.
- Available brand assets and any earlier guidelines.
- Read access to the existing product and its usage data, if any exists.
- Clarity on technical and operational constraints design cannot override.
Methodology and technology
Qualitative research with users, supported by whatever usage data already exists. Design in Figma using a component library and design tokens that translate cleanly into code. Bidirectional layout planned from the outset with logical properties, and Arabic typography chosen for on-screen legibility. Accessibility reviewed against WCAG level AA as an internal working standard. Interactive prototypes tested with users before development, and a documented handover covering behaviour and edge cases.
How this connects to the rest of our work
A service rarely works alone. These come before it or alongside it, and these are the solutions it forms part of.
Services that work with it
Web Applications and SaaS Development
A web app or SaaS product built around your real process — permissions, integrations and code you own.
Digital Products and MVP Development
Idea to working product: tight scope, production-grade build, and a next round decided by real usage.
Corporate Website Design & Development
A fast bilingual corporate site that turns visitors into enquiries — and that your team can edit.
Mobile Application Development
An iOS and Android app with one coherent experience, plus accounts, code and release pipeline you own.
Part of these solutions
Frequently asked questions
Can you do the design without doing the development?
Yes, and it is common. You receive the design file, component system and handover documentation in a form any engineering team can build from — yours or another vendor. We stay reachable for developer questions during an agreed window.
How do you test a design before anything is built?
We build a clickable prototype that behaves like the real thing, then ask people from your audience to complete a specific task on it and watch where they hesitate. Direct observation surfaces what surveys miss, because people describe what they think they do rather than what they do.
What makes an Arabic interface different from a mirrored one?
Flipping a layout automatically produces something that looks Arabic and behaves English: directional icons pointing the wrong way, awkward number and date formatting, and literally translated labels nobody would say. We design each language on its own terms — direction, typography and wording together.
We already have a working product. Do we need a full redesign?
Often not. We usually begin with a diagnostic review that pinpoints where users actually struggle, and it frequently turns out that fixing one or two journeys delivers more than rebuilding everything. We present both options with their cost and let you choose.
Who owns the design files afterwards?
You do. Source files and the full design system are handed over in your company name, with nothing that prevents you continuing the work in-house or with another partner.
How many rounds of revisions are included?
Review rounds are agreed per phase before we start and written into the proposal. That protects both sides: you get room to respond properly, and the project does not drift into an open loop of edits without sign-off.