Give Japanese Buyers an ROI Model They Can Edit Themselves
The Japan team reports that the demos go well. The prospect nods through the ROI slide.
Then the deal sits for weeks, and the champion comes back with one line: they cannot explain the cost-effectiveness internally.
Headquarters usually hears this as a weak value proposition.
More often the ROI was delivered in the room, and nothing the buyer can carry out of the room contains it. The person who was convinced is rarely the person who signs. They are the person who has to convince others.
Buyers get stuck on the ROI estimate before they talk to sales
IDEATECH and Hiroyasu Kitagawa (Demagen Research) surveyed people in Japan in May 2026 (fielded May 25-26, 330 valid responses, n varies by question).
Respondents had been involved, with at least one other person, in buying, replacing or renewing B2B software, SaaS or IT infrastructure and security products worth 5 million yen or more a year in the previous 12 months.
Asked what was hard to judge on their own before contacting a vendor, 56.3% named estimating the operating burden after rollout, 47.1% named feature comparison, and 41.5% named ROI estimation.
Putting numbers on effort and return was harder for buyers than comparing features.
The content they found most helpful was an ROI calculator, at 55.4%. Case studies from similar industries and sizes followed at 46.5%, slides for internal explanation at 26.8%, and support material for the approval request at 14.2%.
The content that did not affect the decision was general industry trend reports (49.5%) and feature comparison tables (46.2%).
The reasonable reading is that buyers do not want the answer you calculated. They want the means to calculate it.
Price dominates the stated criteria, and ROI may sit inside it
In the same survey, the top criterion for choosing a vendor (up to three answers) was price and cost at 58.5%. The persuasiveness of ROI was cited by 11.1%.
Read at face value, ROI carries little weight when the vendor is chosen.
Yet in the same survey, the most helpful content was an ROI calculator. Both facts stand side by side.
Our hypothesis for connecting them, which the survey did not test: buyers do not weigh ROI as a criterion separate from price. They use it to check whether the price can be justified internally, so it shows up as price.
That would explain why “persuasive ROI” is rarely named while a calculator the buyer can run is valued. If the hypothesis holds, material for justifying beats a better argument.
A model the buyer owns travels through the approval chain
Approval in Japan involves several readers. In the earlier IDEATECH and Kitagawa survey (April 2026, n=307, respondents involved with others in purchases of 3 million yen or more), over 80% reported two or more layers of approval.
Your champion’s account of what your rep said reaches the next layer as hearsay.
Compare two sentences. “Sales told us it saves about this much.” And: “With our numbers, it comes to this.”
The second can be questioned and answered by the person who brought it. That difference is what survives a ringi meeting.
Giving the buyer what they need to convince everyone else, not just convincing the buyer, is the core of this. An editable ROI model is the clearest form it takes.
Three rules for building it for Japan
It does not need to be a tool. One spreadsheet is enough. Three rules matter.
Keep inputs to five or fewer, and ask only for numbers the buyer has to hand: monthly hours, headcount, unit cost.
If an input is hard to find, add one line saying where to look. A long form will not be finished.
Show the assumptions on screen and let the buyer overwrite them.
If you hide the savings rate, the output has the same standing as your rep’s claim, and the champion cannot answer “where does this number come from?” in a meeting you are not in.
When the buyer can correct an assumption to fit their own business, the result becomes a number they own.
Show three cases, not one: optimistic, standard and conservative.
Approval discussions in Japan tend to test the worst case, and a conservative figure your team publishes first is one the champion can use as it stands.
What the Japan team can do this week
Ask the Japan team to recall three recent deals and find the moment a buyer asked, “What would this come to for us?”
If the rep answered by calculating on the spot, that calculation is your material. While it stays in the rep’s head, the buyer has nothing to use in a ringi.
Turn it into a sheet with five inputs or fewer. Decide later whether to publish it or hand it over after the second meeting.
Building it usually shows that each rep has been using different assumptions, which is worth knowing before HQ sees the pipeline.
If you want to use a real customer’s figures, get their permission first. If you cannot, a blank sheet with the assumptions filled in is enough.
Keep the sheet after you hand it over. When the buyer returns it with their own numbers, attach it to the deal, the same way the approval draft is attached rather than turned into new fields.
The conservative-case annual benefit in particular becomes the baseline for checking value after go-live and for the renewal, when the same question gets asked again.
Put that number in the handoff note; What your Japan handoff drops is the reason the contract was approved explains what usually goes missing there.
One caution on the data. The survey was run through IDEATECH’s own survey PR service as an online panel.
Read the percentages as orders of magnitude and rankings, and do not mix them with the earlier survey, which used a different amount threshold and different questions.
Related reading
Once the model is in the buyer’s hands, the next gap is the internal approval document itself, which your champion usually cannot write. We covered that in Help the Japan buyer prepare a draft business case
Other notes on the same problem are collected under Demand generation.