Building From Jordan Is a Feature, Not a Footnote
Being based in Amman is not a constraint. It is the reason the team builds the way it does.
The question underneath the question
Most first calls with a new client from London, New York or the Gulf eventually hit the same beat. The polite version goes "tell us about your timezone overlap" or "how do you handle communication." The less polite version is "is the work the same quality."
I have learned to hear what the question is actually asking. Can you be trusted with something important.
The answer is yes. And the question itself sits on top of a flawed premise.
What building here actually means
Jordan sits at the seam of Europe, the Gulf and Africa. Our clients are headquartered in London, Dubai, Nairobi and New York. We work across their timezones, across regulatory environments that span six jurisdictions, and across user bases that range from English-first SaaS buyers to Arabic-first mobile users opening a smartphone for the first time.
That breadth was not a concession we made for global clients. It is a capability the market here forced on us. You cannot ship a product in this region without designing for variance. Variance in language. Variance in payment rails. Variance in connectivity. Variance in regulation. Once you can do that, the rest of the world feels easier, not harder.
Multilingual by default, not by patch
Most Western product studios build in English and localize later. The result is RTL layouts that fall apart at the edges, translated copy that ignores cultural register, and mobile flows that assume the kind of network nobody outside a few cities actually has.
Arabic is a first-class language at WTM. RTL is part of how we design components, not a CSS afterthought. When we localize a product, we do it with native speakers in the room. Not with machine translation and a character count.
That is not a pitch line. It is the only way to ship in a market where your first user might open the product in Arabic on a 3G connection and never tolerate it loading slowly.
On cost
Yes, our rates beat London or New York for the same caliber of work. That is true. It is also not the reason clients stay.
Clients who come to us because we are cheaper end up renewing because the output is better. Cost gets us in the room. Quality keeps us in it.
I have stopped leading with the cost line entirely. It attracts the wrong buyer. The buyer I want is the one who reads the work and understands why a senior engineering team that ships in weeks is worth more than a body shop that ships in quarters.
The studio I wanted to build
I have been writing software since I was ten. I spent years inside MENA's developer community, including running Meta for Developers' regional program for tens of thousands of engineers. I have seen what the talent here can actually do when it is given real work and a high bar.
We did not build WTM to look like a San Francisco studio. We built it to be useful to ambitious teams anywhere in the world, from one of the most demanding multilingual, multi-market environments on the planet.
The Jordan address is not a footnote in the pitch. It is part of why the work is good.