What Tehran teaches you about building brand worlds.
Working here removes several assumptions that brand practice elsewhere treats as free. Most of them turn out to be assumptions worth losing.
A lot of brand thinking is written from markets where certain things are simply available: the typeface you licensed, the platform you planned around, the service you embedded in the checkout. Working in Tehran removes several of those assumptions.
The useful discovery is how many of them were never load-bearing.
Bilingual is a design problem, not a translation task
This is the one that changes the most.
Persian and Latin do not share proportions. They sit differently on a line, they break differently at small sizes, and Persian does not take letter spacing the way Latin does — a headline set with the tracking that flatters a Latin display face is simply wrong in Persian.
So a wordmark drawn in one script and traced into the other usually fails in the second. Both have to be drawn as first-class versions. That is slower and more expensive, and it is also a quality filter: a concept that only works in one script was probably a shallow concept.
The same applies to copy. A line that depends on English wordplay is usually the wrong line, and it is far cheaper to discover that during strategy than after the packaging is printed.
The infrastructure you assume is not always there
A great deal of standard marketing practice quietly depends on third-party services that an Iranian visitor may not be able to reach. Embedded forms, hosted analytics, foreign fonts served from a CDN, video players, payment widgets.
Each one is a place a page can silently break for the audience it was built for. Not error out visibly — just fail to appear, leaving a gap the visitor reads as carelessness.
The practical response is to shorten the dependency chain. Serve fonts from your own domain. Keep the form on your own server. Host the video yourself. Prefer what the browser already does over a library that does it more elegantly. None of that is ideological; it is the difference between a site that works here and a site that works in a case study.
Constraints improve production discipline
Location work in Iran does not come with the infrastructure that makes shooting casual. That imposes planning.
Filming on the Makran coast means a narrow usable window: direct sun near midday flattens skin tone and kills the texture of the sand, so the schedule gets built backwards from the two ends of the day. Food photography at a restaurant pass means the shot list follows the kitchen’s timing rather than the other way round, because steam reads for about forty seconds and sauce starts separating while you are still checking focus.
Neither of those is a local problem, strictly. They are universal production truths that a well-resourced shoot can paper over and a lean one cannot. Not being able to paper over them makes the work better.
The audience is not a smaller version of somewhere else
The most common failure we see is a brand built as though its audience were a regional edition of a Western consumer. The visual language is imported, the references are imported, and the whole thing reads as a translation.
Audiences notice this instantly, and it costs the brand exactly the thing it was trying to buy: credibility.
The alternative is not nostalgia or heritage pastiche. It is specificity — a brand that could only have come from here, addressed to people who live here, without the decorative folklore that treats a culture as a texture.
What travels
Everything above sounds local, and most of it is not.
Bilingual rigour is just typographic rigour. Short dependency chains are just good engineering. Production discipline under constraint is just production discipline. Refusing to treat an audience as a derivative of another audience is just respect.
Tehran teaches these more insistently than a market with fewer constraints, because here you find out immediately when you have got them wrong.