Can a Cultural Product Built for One Country Work Globally?
I have been building a small web product around a concept that is immediately familiar to many people in Japan but difficult to explain in a single sentence to someone outside the country.
The product is based on 恋みくじ—Japanese love fortunes inspired by the omikuji traditionally found at shrines and temples.
In Japan, most people already understand the basic ritual. You think about something important, draw one fortune, read the message, and consider how it relates to your current situation.
The product does not need a long onboarding process because the culture has already taught users how to use it.
But what happens when the same product is introduced to people who have never encountered an omikuji?
That is the question I am currently trying to answer.
A product that grew through cultural familiarity
I launched the Japanese version in 2023.
The experience is deliberately simple. A visitor thinks about their current romantic situation, draws one 恋みくじ, and receives a short message for the day.
There is no registration, no email address, and no personal information required.
The product currently includes a daily love fortune and a situation-based version for concerns such as unrequited love, reconciliation, unanswered messages, and long-distance relationships.
Together, the two versions have generated more than 4.9 million draws.
The existing product is [Ichizendo Koi Mikuji] 一禅堂.
Its growth has made me consider an English version. However, the more I think about localization, the less it feels like a translation project.
It feels like a product-design problem.
The words can be translated, but can the ritual?
The most obvious option would be to translate 恋みくじ as “love fortune.”
That translation is understandable, but it loses some of the original context.
For a Japanese user, “omikuji” is not simply a random prediction. It is connected to a familiar ritual: visiting a shrine, drawing a numbered stick or paper, unfolding the result, and reflecting on what it may mean.
Some people take the result seriously. Others enjoy it casually. Many do both at the same time.
That balance is important.
The experience can feel meaningful without requiring the user to believe that every sentence is a literal prediction of the future.
When the product is described only as a “love fortune generator,” an English-speaking visitor may imagine something very different:
* A novelty random-text tool
* An astrology or horoscope website
* A dating compatibility quiz
* An AI relationship adviser
* A game with random romantic predictions
None of those descriptions is completely wrong, but none captures the original experience either.
The interface can be translated in a few hours. The cultural expectation behind the interface cannot.
Should the Japanese name be preserved?
One possibility is to keep the name “Koi Mikuji.”
This preserves the identity of the product and gives users an opportunity to discover something specifically Japanese.
However, an unfamiliar name creates friction.
Someone seeing “Koi Mikuji” for the first time may not know:
* What the product does
* Whether it is a game or a serious service
* What “koi” means
* What “mikuji” means
* Why they should draw only once per day
A descriptive subtitle could solve part of this problem:
> Koi Mikuji — A Japanese Love Fortune for Daily Reflection
This approach keeps the original cultural name while immediately explaining the function.
The alternative would be to remove the Japanese term and use a fully localized name such as “Daily Love Fortune.”
That would be easier to understand, but it would also make the product look similar to many generic fortune and horoscope websites.
The Japanese context is not decoration added to the product. It is the reason the product exists.
Removing it may improve immediate comprehension while weakening the product’s identity.
Literal translation can change the emotional tone
The messages inside a 恋みくじ are short. That makes their tone especially important.
A long article has space to explain itself. A short fortune may have only one or two sentences.
In Japanese, a message can feel gentle, indirect, and emotionally open. A literal English translation may sound vague, awkward, overly dramatic, or even cold.
For example, a Japanese message may suggest waiting without directly commanding the reader to wait. It may imply that someone should reconsider a relationship without explicitly saying, “You should leave.”
This indirectness gives the user room to connect the message to their own situation.
English product copy often values clarity and directness. But if every message becomes too direct, the experience may start to feel like advice rather than reflection.
There is also a question of emotional responsibility.
People often open a love fortune when they are already uncertain. They may be waiting for a reply, thinking about an ex, or wondering whether someone shares their feelings.
A message should not promise that a person will return, guarantee that a relationship will succeed, or make an important decision on the user’s behalf.
The Japanese product presents each result as a prompt for self-reflection rather than a fixed prediction.
That principle needs to survive localization, even if the wording changes completely.
Three possible approaches
I currently see three ways to bring the product to an international audience.
1. Translate the existing product directly
This is the fastest approach.
The interface, explanations, and existing fortune messages would be translated into English. The product structure would remain almost identical to the Japanese version.
Advantages:
* Faster to launch
* Lower development cost
* Easier to maintain
* Preserves the existing product experience
Risks:
* Messages may feel translated rather than naturally written
* Cultural meaning may be lost
* The product may require more explanation than expected
* Japanese romantic situations may not map perfectly to other cultures
This approach would test whether the core interaction works globally, but a weak translation could produce a false negative. Users might reject the wording rather than the concept.
2. Rebuild the experience for English-speaking users
Instead of translating existing fortunes, I could treat the English version as a related but separate product.
The core ritual would remain: think about a romantic concern, draw once, and reflect on the result.
However, the messages, categories, examples, and explanations would be written specifically for English-speaking users.
Advantages:
* More natural language
* Better cultural fit
* Greater freedom to test new categories
* A clearer experience for first-time users
Risks:
* More expensive and time-consuming
* Harder to maintain two content systems
* Greater chance of losing the original Japanese identity
* The result may become a generic relationship-advice product
This could create a better localized product, but it raises a difficult question: at what point does adaptation become a different product?
3. Keep the Japanese ritual and teach users how to experience it
The third approach is to preserve 恋みくじ as a Japanese cultural experience.
Instead of hiding the unfamiliar parts, the product would explain them.
A short introduction could tell users:
* What omikuji is
* What “koi” means
* Why the product recommends one draw per day
* Why the result is not a guaranteed prediction
* How to reflect on the message
* How the online version relates to the traditional ritual
Advantages:
* Stronger differentiation
* Preserves the product’s origin
* Gives users a reason to remember and share it
* Creates a cultural experience rather than another generic fortune tool
Risks:
* More onboarding friction
* Some users may leave before drawing
* Cultural explanations can become too long
* The experience could feel educational rather than emotional
This is the approach I find most interesting, but it requires careful design. The explanation must provide context without standing between the user and the main action.
What should remain universal?
Although the product is culturally specific, the emotional situations behind it are not.
People everywhere experience uncertainty in relationships.
They wait for replies. They wonder whether to confess their feelings. They think about reconnecting with someone. They struggle with distance, timing, and unspoken expectations.
The language and customs may change, but the underlying emotions are recognizable.
This may be the bridge between the Japanese product and a global version.
Instead of translating every cultural detail, the product could preserve the ritual while rewriting the messages around universal emotional moments.
The experience would remain Japanese in origin but would not require users to behave or communicate exactly like Japanese users.
How I am thinking about testing it
Rather than translating the entire product immediately, I am considering a smaller experiment.
The first version could include:
* A short English landing page explaining Koi Mikuji
* A limited collection of messages written directly in English
* Three or four universal relationship situations
* No registration or personal-data requirements
* One draw per day
* A simple way to save and share the result
* A short feedback question after the experience
The first goal would not be revenue.
It would be to understand whether users outside Japan find the ritual meaningful, confusing, entertaining, or emotionally useful.
I would want to learn:
* Do users understand the product before drawing?
* Does the Japanese name create interest or confusion?
* Do they interpret the result as reflection, entertainment, or prediction?
* Does the once-per-day recommendation make the experience feel meaningful or unnecessarily limited?
* Which relationship situations feel universal?
* How much cultural explanation is useful?
* Would users return without notifications?
These answers would help determine whether the product needs translation, adaptation, or a completely different global experience.
The risk of making a cultural product too universal
There is a common temptation in localization: remove everything unfamiliar so that the product becomes easy for everyone to understand.
But unfamiliarity can also be valuable.
People travel, read, watch films, and try new products partly because they want to experience something outside their own culture.
If every Japanese element is replaced with a familiar Western equivalent, the product may become easier to understand but less interesting.
The goal may not be to make Koi Mikuji feel as if it originated everywhere.
The goal may be to make its Japanese origin understandable and welcoming to people everywhere.
That is a different design objective.
I would like to hear how other founders approach this
Many Indie Hackers build products for global audiences from the beginning. Others start with a local market and expand only after finding product-market fit.
Cultural products create an additional challenge because localization affects more than menus, currencies, and date formats. It can change the meaning of the product itself.
I would appreciate the community’s perspective:
1. Would you keep the name “Koi Mikuji,” or replace it with a descriptive English name?
2. Would you translate the existing messages or write a completely new English collection?
3. How much cultural explanation would you include before the user’s first interaction?
4. Is the Japanese origin the product’s strongest advantage, or a barrier to global adoption?
5. Have you ever localized a product built around a tradition, habit, or emotional behavior specific to one country?
6. How did you decide which parts to preserve and which parts to redesign?
I am especially interested in examples where a culturally specific product succeeded internationally without becoming a generic version of itself.
Can a product built for one country work globally?
I believe it can—but only if localization protects the reason people cared about the original product in the first place.
