Services Work About Blog Book a call
Our work

Quantifiable results.
Humanized flows.

نتائج قابلة للقياس.
أرقام واقعية.

Selected work across banking, fintech, and transportation. Each project measured in user outcomes, not just delivered documents.

DNB bilingual banking content system
01

Banking: Building the language of trust

البنوك: بناء لغة الثقة

A GCC retail bank needed one voice across five products and four writing teams. What they had was five different dialects of the same confusion.

Client DNB · GCC Retail Bank
Industry Banking · Fintech
Service Content Systems · Style Guide
Result 1 voice · 5 products

The challenge

DNB had grown fast. Five distinct digital products: retail banking, business banking, a tablet experience, ATM interface, and corporate banking. Each built by a separate squad. None of them were talking to each other. The Arabic copy read like it had been run through a translation engine, because most of it had. The English was technically correct but tonally flat. KYC and onboarding flows were seeing drop-off that the data team flagged but nobody could explain. The answer was in the words.

Our approach

We started with a full content audit across all five products in both languages, cataloguing every point where the voice broke, where terminology conflicted, and where Arabic copy failed to match the trust-building standard users expected from a bank. From there we ran workshops with all four writing teams to define a shared content philosophy. We then built the system from the ground up: tone principles, a bilingual terminology glossary covering banking-specific language in both MSA and Gulf-calibrated Arabic, component-level writing patterns, and a KYC and onboarding flow rewrite that replaced bureaucratic copy with human-first language.

The outcome

DNB now ships content from a single source of truth. Four product squads and a five-person UX writing team, all hired and onboarded after the system was delivered, write to the same standard without needing to consult each other on every string. Onboarding completion rates improved as the copy became clearer and more culturally grounded. The content system became the foundation for all subsequent product launches, including a new communications layer across email, SMS, and push notifications.

What we built
01
Bilingual content system

A complete EN + AR writing framework covering voice, tone, grammar rules, and formatting. Built for a team, not a single writer.

02
Banking terminology glossary

200+ terms defined and approved in both languages, from KYC and IBAN to everyday microcopy like "transfer" and "recipient". No more improvised translations.

03
KYC and onboarding rewrite

Every screen from account creation to first deposit rewritten in both languages. Designed to reduce friction, build trust, and reflect MENA banking culture.

04
Comms content principles

Tone and writing rules extended beyond the app to push notifications, SMS, and email. So the bank's voice stays consistent wherever it speaks.

By the numbers
5 Digital products under one unified bilingual content system
4 Product squads writing consistently from day one of handoff
UX writing team hired and onboarded using the system as their foundation

"Before Tybo, every squad was essentially making up the rules as they went. We had five products that were all supposed to be the same bank, and none of them sounded like it. The content system they delivered didn't just fix the copy. It gave us the infrastructure to grow a writing team that actually knows what DNB sounds like."

— Design Manager · DNB · GCC Retail Bank
SWRL Cairo transportation Egyptian Arabic content
02

Transportation: Finding the Egyptian voice

النقل: بحثاً عن الصوت المصري

SWRL's app worked. But in a city of 21 million people who speak one of the world's most expressive Arabic dialects, "working" was not enough.

Client SWRL · Cairo, Egypt
Industry Transportation · Ride-hailing
Service Tone of Voice · Microcopy
Result −31% driver drop-off

The challenge

SWRL operated two parallel apps, one for riders and one for drivers, and both had the same problem: the language felt imported. The English was generic global tech copy with no Cairo texture. The Arabic was Modern Standard Arabic written by people who were not from Egypt, producing sentences that were grammatically correct and emotionally inert. In a city where language carries warmth, humour, and street-level trust, inert copy is invisible at best and alienating at worst. Driver onboarding was seeing a 31% drop-off that nobody had connected to the words on screen. Rider satisfaction scores in Arabic were consistently lower than in English for the same flows.

Our approach

We spent the first week in Cairo, not at a desk. Rider interviews, driver onboarding sessions observed in real time, and a linguistic audit of every user-facing string in both apps and both languages. What we found was that the rider app and the driver app spoke completely differently, and neither spoke like Cairo. We built an Egyptian Arabic tone of voice guide that defined how SWRL speaks: warm but efficient, street-smart but never reckless, with specific guidance on when to use Egyptian colloquial and when MSA was appropriate. Then we rewrote the critical flows: onboarding, ride request, safety moments, cancellations, and ratings, in both languages simultaneously, not sequentially.

The outcome

Driver onboarding drop-off fell 31% within six weeks of the Arabic rewrite going live. Rider satisfaction scores for Arabic-language sessions improved to match and then exceed the English baseline, a first in SWRL's Egypt data. The tone of voice guide became the hiring brief for SWRL's first in-house Egyptian Arabic content role, and the microcopy framework was adopted by the product team as the baseline for all future feature launches across both apps.

What we built
01
Egyptian Arabic tone of voice guide

A practical, Cairo-specific guide defining SWRL's voice: how it sounds in Egyptian colloquial, when to use MSA, and how to balance warmth with clarity under pressure.

02
Bilingual microcopy rewrite

Both the rider and driver apps rewritten end to end in English and Arabic, simultaneously, not translated. Every screen written for the same Cairo user, not a generic MENA average.

03
Safety and trust copy framework

A dedicated set of writing principles for high-stakes moments: cancellations, incident reporting, identity checks. Where the wrong word erodes the trust transportation apps run on.

04
Driver onboarding flow rewrite

The full driver registration and onboarding journey rewritten in Egyptian Arabic. Treating drivers as partners, not applicants, from the first screen to the first ride.

By the numbers
−31% Driver onboarding drop-off within 6 weeks of Arabic rewrite going live
2 Apps rewritten simultaneously, rider and driver, in EN + Egyptian Arabic
1st Time Arabic satisfaction scores matched and exceeded the English baseline in Egypt

"We always knew the language wasn't right, but we kept telling ourselves it was a product problem, a design problem, a retention problem. Tybo came in and showed us in the first week that it was a language problem. The before and after on the driver onboarding screens was the clearest UX case I've ever had to make to leadership. The numbers followed."

— UX Lead · SWRL · Cairo

Want results like
these for your product?

Book a call. We'll audit your current state and show you what's possible.

Chat with us