There is a counterintuitive argument at the center of why we built Ikura, and I want to make it as directly as I can: the smaller your property, the higher the return from a multilingual guest messaging tool. Not despite your size, but because of it.
This is worth examining carefully because the intuitive assumption runs the other way. Large hotel chains have the problems that technology should solve. They have hundreds of rooms, thousands of guests per month, and the volume to justify enterprise tools. Small ryokan with 8 or 10 rooms are different. They are intimate. They are personal. They do not have "processes."
But that intuition is wrong, and I saw it being wrong repeatedly during the years I spent consulting for Japan inbound hospitality operators before founding Ikura. The language problem at a small property is not smaller than at a large hotel. In some ways it is larger, because the small property has fewer resources to absorb it.
What a large hotel has that a small inn does not
A 200-room business hotel in Tokyo has a front desk staffed by three or four people per shift. At least one of those people, often more, speaks English. The hotel has likely hired a Chinese-speaking staff member if their booking data shows significant mainland Chinese guest volume. They have a concierge desk where guests can ask questions in person and receive answers with reasonable fluency in multiple languages. They have a reservations team that handles pre-arrival messages during business hours, staffed with people who can read and respond in foreign languages.
None of this is glamorous or expensive by large-hotel standards. It is baseline operations for a property of that size. The math just works: at 200 rooms with 60 to 70 percent occupancy, you have enough revenue and enough volume to justify dedicated multilingual staffing.
A ryokan with 8 rooms operating at similar occupancy has a fraction of that revenue. The owner or a single staff member handles everything: breakfast, check-in, housekeeping coordination, and guest messages. During peak season, that person may be answering Korean messages while simultaneously setting up the dining room for the evening meal. The idea of hiring dedicated multilingual staff is not just economically impractical; it is physically impossible given the staffing model that small properties run.
The asymmetry of the problem
Here is where the asymmetry becomes clear. A large hotel with multilingual staff handles a Chinese guest's question about the onsen policy in 3 minutes. A small ryokan without that capacity handles the same question in 4 hours, if the owner remembers to check the WhatsApp inbox between other tasks, and if she can compose an accurate response in Chinese that correctly conveys the nuance of the policy without using a translation app that renders the politeness level wrong.
That 4-hour gap is not just a response time problem. It is a guest experience problem, a review problem, and sometimes a booking completion problem. Foreign guests who do not receive timely answers to pre-booking questions sometimes book elsewhere. Foreign guests who experience communication difficulty during their stay leave reviews that reflect it. Neither of those outcomes is fixable after the fact.
The large hotel does not have this problem because it has enough scale to hire its way out of it. The small ryokan cannot hire its way out of it. But it can use a tool designed specifically for this problem.
The economics are different for a small property
I want to be specific about the economics because they are often misunderstood. The value of Ikura for a 10-room ryokan is not calculated by multiplying the number of automated responses by some efficiency figure. It is calculated by asking: what does the front desk do with the time that used to go to message translation and response?
At a small property, that time goes into the hospitality experience itself. The owner who is not spending 45 minutes during the morning shift working through a message queue in Chinese and Korean has 45 minutes to prepare the breakfast presentation, check the room arrangements, or be fully present when the first guests come down. That is not an abstract benefit. It is the thing that drives the review scores that drive the bookings that make the property viable.
We are not suggesting that all properties need to automate every guest interaction, or that the personal touch of a small ryokan should be replaced by automated responses. That would be a misuse of the tool. The point is more specific: the questions that have known, factual answers (transport directions, onsen hours, meal options, check-in times) do not need a human to answer them. They need accurate, language-appropriate responses delivered in time for the guest to act on them. Automating those specific questions leaves the human interactions for the things that actually benefit from a human: the greeting, the recommendation for a local restaurant the guest would not find otherwise, the conversation over dinner.
What small properties can do that large hotels cannot
There is a real advantage that small properties have over large hotels, and a well-implemented messaging approach reinforces rather than undermines it. A guest staying at an 8-room ryokan expects a personal experience. They expect to feel that the owner knows who they are. Pre-arrival messaging that arrives in the guest's language, feels appropriately warm rather than corporate, and answers their specific questions accurately is consistent with that expectation. It is not the kind of communication that makes the experience feel automated or industrial.
A large hotel's pre-arrival messaging, regardless of how well it is written, often feels like a system output. A small ryokan's pre-arrival messaging, because the FAQ responses are written by the owner in her own voice and then delivered in multiple languages, can still feel personal. The language handling is automated; the content and warmth behind it is not.
This is the distinction that matters for small property operators who are concerned about whether a messaging tool is consistent with their hospitality philosophy. The tool does not replace what makes your property worth staying at. It removes the operational friction that currently prevents you from delivering that experience at full strength to every guest, regardless of what language they speak.
A note on where this argument has limits
Not every small property should run automated multilingual messaging. If your property has fewer than 20 percent foreign guests, the case is weaker. If you have a staff member who speaks your top two or three guest languages fluently and enjoys managing those communications, the time savings may not justify the cost. If your property operates at very low occupancy, the economics do not close.
The properties that benefit most are those with a meaningful proportion of non-Japanese-speaking guests (roughly 25 percent or more), operating at reasonable occupancy (50 percent or above), where the front desk communication burden during peak season is clearly affecting either guest experience or staff capacity. If those three conditions describe your situation, the argument I am making here applies directly.