Fair warning: this post is about one of our own products, the BenStay AI concierge. I’ll spend the first half on the problem, because I think it’s worth understanding even if you never use what we built.
The problem is simple. A guest lands at Narita at 11pm, their phone is on 4% battery, and they want to know how to get into the building. They don’t want a ticket number or “we’ll reply within 24 hours”. They want the door code and the right exit from the station, in a language they can read.
Every few weeks a guest at one of our properties asks some version of the same question: “Where can we get good craft beer tonight?” It sounds like a simple ask. It isn’t, and after fielding it enough times as a guesthouse operator, we ended up building something to solve it properly.
Every time I’ve talked to another operator or a developer building something for Japanese hospitality, the same complaint comes up: accommodation tax math. Not the concept — everyone understands “some cities tax overnight stays.” It’s the fact that local governments calculate it differently, and there is no single official, machine-readable national table that developers can safely drop into booking software without checking each local government’s ordinance and guidance.
Last year I got three quotes for repainting and re-tiling a bathroom in one of our units. The totals were ¥480,000, ¥610,000, and ¥720,000. My first reaction was “just take the cheapest one.” My second reaction, after actually reading all three line by line, was that I had no idea if I was comparing the same job three times or three different jobs that happened to share a bathroom.
That gap between “the totals look comparable” and “the scopes are actually comparable” is where a lot of property owners in Japan lose money — either by overpaying, or by picking the cheap quote and then getting hit with change orders once work starts.
Every listing I’ve seen for a small hotel or guesthouse in Japan leads with the same number: gross yield. Annual revenue divided by price, presented like it’s the whole story. It isn’t, and if you’ve bought property here before you already know that. But if you’re evaluating your first deal, that gap between the headline number and what actually lands in your pocket is where a lot of buyers get burned.
Before BenStay was a software company, it was one guesthouse in Kyoto that I was running myself — answering the same questions at midnight, adjusting prices by hand, and copy-pasting the same listing update across multiple OTAs. The automation we now offer other operators started as tools we built to keep our own operation from burning us out.
A few years into running guesthouses in Tokyo, I noticed something that should have been obvious sooner: I was answering the same questions over and over, just from different people. “How do I get in?” “Where’s the nearest station exit?” “Can I leave my bag before check-in?” Different guests, same script, every single day.
Operating furnished rentals and guesthouse properties in Japan, including Tokyo, for the past few years, one of the most common things our guests ask us about isn’t the sights everyone already knows — it’s where to eat and drink like someone who actually lives here. Craft beer comes up a lot, and it’s a genuinely great scene: dozens of small breweries and taprooms scattered across the city, many of them with limited English signage or menus and no obvious way for a first-time visitor to find them.
Every few months I get the same message from another operator: “wait, how much accommodation tax am I supposed to be charging in [city]?” And every time, the honest answer is “it depends which city, which band, and whether you’re calculating off the room rate or the total price.” That inconsistency across Japan is annoying enough that we ended up writing code to solve it for ourselves — and then decided to open-source it.
If you’ve ever tried to compare three renovation quotes in Japan and ended up more confused than when you started, you’re not alone. The problem usually isn’t that contractors are being dishonest — it’s that the format of Japanese 見積書 makes genuine like-for-like comparison structurally difficult.
A listing comes across your feed: “Tokyo guesthouse, ¥35M, gross yield 8%.” That number sounds reasonable — maybe even good by Japanese real estate standards. You start running mental math.
Here is the problem: gross yield is almost always the wrong number to base a decision on.
Before October 2023, managing receipts as a Japanese sole proprietor was already annoying. After the invoice system (インボイス制度) kicked in, it became genuinely complicated. Most freelancers I talk to are still figuring out exactly what they need to keep — and why the rules changed in ways that aren’t obvious from the headlines.
This post is partly useful background on Japanese receipt compliance, and partly an honest look at Reshito (https://reshito.jp), the AI receipt scanner we built to tackle this specific problem.