Skip to content

UI/UX Design

Interfaces that turn first-time users into repeat customers.

Research-backed product design, from flows and wireframes to polished, accessible UI that ships without guesswork.

Book a discovery callBuild your plan
  • Dubai head office, GCC-wide delivery
  • Arabic and English throughout
  • Written scope and fixed timeline before you commit

You walk away with

  • Product design
  • Design systems
  • Prototyping
  • Usability testing

Typical timeline

4–10 weeks

Typical engagements start around

AED 15,000 per project

What good looks like

users in a round of moderated testing
5–8users in a round of moderated testing
accessibility standard designed to
WCAG 2.2 AAaccessibility standard designed to
component library, not a folder of screens
1component library, not a folder of screens

The problem this solves

Design reviews turn into opinion contests. The prettiest version wins, ships, and quietly underperforms — because nobody watched a real person try to use it before it was built.

Where this usually hurts

  • Design is decided by whoever is loudest

    Without research, the decision goes to seniority or taste. Six months later nobody can explain why the flow works the way it does.

  • The handover loses the intent

    Engineers get static screens with no states, no error cases and no responsive behaviour, so a hundred small decisions get made in code by accident.

  • Every screen is slightly different

    No component library means the same button exists eleven times with eleven paddings, and the product feels assembled rather than designed.

  • Accessibility is a launch-week panic

    Contrast, focus order and labels get audited at the end, when fixing them means redesigning rather than adjusting.

We design products by watching people use them. Every engagement opens with five to eight moderated sessions on the current experience or a rough prototype, because an hour of watching someone struggle settles arguments that a month of reviews will not.

Research that fits in a sprint

This is not a six-month ethnography. Five sessions reliably surface about 80% of usability problems, and they can run inside a single week. The output is a ranked list of what is actually costing you conversions — not a deck.

2.1x

Onboarding completion after one round of research on a fintech product

On that project the fix was not visual at all. People abandoned at the address step because it asked for a document they did not have to hand; moving the upload to the end of the flow accounted for most of the improvement.

Every state, not just the happy path

Most design files show the screen with perfect data. Real products spend their time empty, loading, offline, or in error. We design those states too, because otherwise an engineer invents them at 5pm on a Friday.

  • Empty, loading, partial, error and success for every meaningful view
  • Focus order and keyboard paths defined, not left to the DOM
  • Contrast checked as the design is drawn, not audited afterwards
  • Motion specified with a reduced-motion alternative

A system, not a stack of screens

The deliverable is tokens, components, states and the rules for combining them, handed over in a form engineers implement without interpretation. We sit in build reviews specifically to catch the gap between what was drawn and what got made.

The best compliment I get is an engineer telling me there was nothing to ask about.
— Marco Bellini, Design Director

What is included

  • Discovery and research

    Five to eight moderated sessions, synthesised into a ranked list of problems worth fixing.

  • Information architecture

    Flows, navigation and the content model that has to hold them together.

  • Interface design

    Every screen and every state, at the breakpoints your traffic actually uses.

  • Design system

    Tokens, components and usage rules your engineers can build from directly.

  • Prototypes

    Clickable enough to test with real users before anyone writes production code.

  • Build support

    Weekly reviews of the built UI against the design for the life of the project.

What we build with

  • Design

    • Figma
    • Design tokens
    • Variable fonts

  • Research

    • Moderated testing
    • Analytics review
    • Session replay

  • Handover

    • Storybook
    • Annotated specs
    • Accessibility audit

How engagements are sized

Three sizes, so the scope matches the problem rather than the budget matching a template. Every tier is a starting point — the number moves with what we find in discovery, and you see the revised figure before anything is signed.

  • Essential

    One clear problem, scoped tightly and shipped.

    From

    AED 15,000

    per project

    One flow that is measurably losing people — onboarding, checkout, a form.

    • Focused research
    • Redesigned flow
    • Prototype for testing
    Get a firm number

  • Growth

    The full engagement, with measurement and iteration built in.

    From

    AED 45,000

    per project

    A full product or site, with a component library your team keeps using.

    • End-to-end research
    • Full component library
    • Moderated user testing
    Get a firm number

  • Enterprise

    Multi-entity, regulated, or integrated across several systems.

    From

    AED 110,000

    per project

    A design system serving several products or teams, with governance.

    • Multi-product tokens
    • Contribution guidelines
    • Design ops and training
    Get a firm number

Prices are in AED excluding 5% VAT. Other currencies on the pricing page.

How delivery actually runs

The phases below are what a typical engagement moves through, with the durations we plan against. You always know which phase you are in and what leaves it.

See the full process
  1. 1

    Research

    1–2 weeks

    Interviews with real users, a look at the analytics you already have, and a walkthrough of the current experience with the people who support it.

  2. 2

    Structure

    1–2 weeks

    Information architecture and flows agreed before any visual design, because moving a box in a flow diagram is free and moving it in a build is not.

  3. 3

    Interface and system

    2–5 weeks

    Visual design built as a component library with states, breakpoints and tokens, so what engineering receives is a system rather than pictures.

  4. 4

    Validate and hand over

    1–2 weeks

    Moderated testing on the prototype, fixes to what it exposes, then a working session with the engineers who will build it.

  • Research · You get

    • Interview findings
    • Current-state friction map
    • Prioritised problem list

  • Structure · You get

    • Flow diagrams
    • Wireframes
    • Content requirements

  • Interface and system · You get

    • Component library
    • Design tokens
    • Interactive prototype

  • Validate and hand over · You get

    • Test findings and revisions
    • Annotated specs
    • Engineering walkthrough

Built for the UAE

What working with a Dubai partner actually changes

Most of what follows is invisible until it goes wrong — a supplier who cannot keep data in-country, an invoice the FTA rejects, a support rota that is asleep for half of your working day. These are the questions we answer before they become findings.

Designing for both Arabic and English is a structural constraint, not a styling one: layouts have to mirror, icons that imply direction have to flip, numerals and dates need a policy, and Arabic type needs its own scale. We design RTL alongside LTR from the first wireframe rather than mirroring at the end.

  • Data residency, decided up front

    AWS me-central-1, Azure UAE North and OCI Dubai are all in scope. We map the whole data path — backups, logs, metrics and support access — rather than the primary database alone, and put the result in writing.

  • PDPL, and the free zones

    Federal Decree-Law No. 45 of 2021 governs most of the mainland; DIFC and ADGM entities fall under their own data protection laws instead. We establish which applies to your entity before we design anything that touches personal data.

  • VAT and e-invoicing that pass

    Five per cent VAT, FTA-compliant tax invoices, the audit file the authority can request, and readiness for e-invoicing as the mandate phases in. Configured in the build, not patched after the first filing is rejected.

  • Your hours, your languages

    Delivery runs on Gulf hours with real overlap with your team, in Arabic and English. Customer-facing interfaces, documents and training are produced in both where you need them, with RTL treated as a design requirement rather than a translation step.

Sectors we do this in most

Not the only sectors we work in — the ones where we have shipped this service enough times to know the regulatory edges and the usual traps.

  • Fintech

    Onboarding, KYC and dashboards that build trust and convert.

  • B2B SaaS

    Marketing sites and product UX that feed qualified pipeline.

  • Healthcare

    Compliant, accessible experiences patients actually use.

In-house, generalist agency, or us

An honest comparison, including where the other two options are the better call.

Hiring in-houseWorking with us
Time to first outputThree to five months to source, notice-period and onboard, in a market where senior specialists are scarce and expensive.Two to three weeks from signature, with people who have shipped this before.
Cost shapeFixed monthly cost plus visa, insurance, end-of-service and equipment, whether or not there is a full workload.Scoped to the work. Costs stop when the work does.
Breadth of skillOne or two specialisms per hire. Anything outside them gets improvised or outsourced anyway.Design, engineering, security and growth from the same team, without a handoff between vendors.
Institutional knowledgeStays in the building — which is the real advantage, and the reason to hire eventually.Documented and handed over. We write runbooks so you can take it back in-house.
When it is the wrong choiceRarely, once the workload is genuinely full-time and permanent.If you need someone in your standups every day for years, hire. We will say so.

Related work

Questions people ask before starting

For usability problems, yes — five users surface roughly 80% of them, and the sixth mostly repeats the first five. Sizing a market or validating pricing needs a different, larger study, and we will say so rather than pretending five interviews answer it.

Services that pair with this

Most engagements use two or three together.

Ready to talk about UI/UX Design?

Tell us what you are building and where it is stuck. We will come back with a scope, a timeline and a number — usually within two working days.

Step 1 of 3 · What you need

Which services are you interested in?