Why Japanese Customers Won't Agree to a Case Study (And How to Get One Anyway)

You asked your best Japanese customer for a case study. They went quiet.

You finally have a Japanese customer who loves the product. Renewal is healthy, usage is up, the champion inside the account says good things in every call. So you ask the obvious next thing: would they be willing to be a case study? A logo, a quote, maybe a short interview.

And then it gets strange. The warm champion suddenly hedges. "Let me check internally." Weeks pass. The answer, when it comes, is a soft no — or worse, a polite silence you're left to interpret. You're confused, because nothing about the relationship changed. The customer is happy. They just won't say so in public, with their name attached.

If you're running marketing for an overseas company entering Japan, this is one of the most disorienting things you'll hit. Back home, a happy customer who agrees to a reference is routine. Here, the happiest customers are sometimes the most reluctant to be named — and the reason has almost nothing to do with how they feel about you. This article explains why that happens, gives you the actual Japanese script to ask in a way that works, and shows you the asset that lets you publish a persuasive case study even when the customer's name stays off the page.

'No' usually means 'careful', not 'never'

The first thing to fix is your interpretation. When a Japanese customer declines to be named, an overseas marketer tends to read it as a verdict on the relationship: they must not be that happy, or they don't trust us yet. That reading is usually wrong, and acting on it — backing off, assuming the door is closed — is how you lose a case study you could have gotten.

In Japanese business, a soft "no" to a public-facing request is frequently not a rejection of you. It's a default posture of caution toward exposure. The customer is a happy customer and a careful organization at the same time, and those two facts don't conflict the way they would in a Western frame. The champion who loves your product may genuinely want to help and still be unable to hand you a public endorsement, because the decision isn't theirs alone and the institutional reflex is to avoid standing out.

So the practical move is to stop hearing "never" and start hearing "not in this form, not without these conditions." Almost every Japanese "no" to a case study has a "yes, if" hiding inside it. Your job is to find the conditions under which yes becomes possible — and most of those conditions are about control and exposure, not about whether they like you. The rest of this article is about lowering the exposure until the yes can surface.

Why Japanese enterprises guard their name (and what they'll allow)

To negotiate the conditions, you need to understand what's actually behind the caution. It is not secrecy for its own sake, and it is not distrust of your product. There are concrete, rational forces pushing a Japanese enterprise to keep its name off your marketing.

Standing out is a risk, not a reward. In many Japanese organizations, being publicly first or loudest about a vendor invites scrutiny — from competitors, from within the company, from a culture that prizes not drawing undue attention. A glowing named case study can read, internally, as "we made a conspicuous bet." The downside if anything goes wrong later is borne by the person who approved the exposure. So the safe institutional choice is to stay quiet, even about a vendor they're thrilled with.

Approval is collective, and the request multiplies the people who must sign off. A reference isn't one person's call. Naming the company in your marketing typically pulls in 広報 (PR/comms), 法務 (legal), procurement, and the executive whose name sits above the function — often through 稟議, the formal ringi approval process. Each of those gatekeepers can only lose by saying yes and can't be blamed for saying no. The more public and specific the ask, the more of them you've activated, and the more likely the request quietly dies in committee.

Vendor relationships are treated as confidential by default. Many Japanese enterprises simply don't disclose who their vendors are, as a standing policy. It's not personal; it's posture. Some are bound by internal rules or industry norms that make any named endorsement a genuine exception requiring real effort to grant.

Here's the useful part: each of these forces weakens dramatically when you remove the name. A nameless story doesn't make the customer conspicuous. It activates fewer gatekeepers — often you can clear it with the champion and one approver instead of the full 稟議 chain. It doesn't violate a no-disclosure policy. What Japanese enterprises will allow is far more than "named, on the record." They'll often allow their results, their workflow, their before-and-after — the entire substance of a case study — as long as they can't be personally identified. That gap, between what they refuse and what they'll permit, is exactly where a usable asset lives.

The anonymous case study that still persuades: keep the specifics

Now the objection you're probably forming: an anonymous case study is worthless. No logo, no name, no proof. Why would a Japanese buyer believe a faceless story?

This is the most important reframe in the article, so sit with it. The persuasive power of a case study to a Japanese B2B buyer does not come primarily from the logo. It comes from recognition — "a company like ours, with our problem, in our market, got a result we want." A Japanese enterprise reader evaluating you is asking 「うちと同じような会社が、同じ課題で、本当にうまくいったのか」 — did a company like us, with the same problem, actually succeed? That question is answered by specificity, not by a name.

What makes an anonymous case study persuasive is everything except the identity:

• The industry and company shape — "a mid-sized domestic manufacturer," "a Japanese subsidiary of a foreign SaaS company," "a regional financial institution." Specific enough to recognize, not enough to identify.
• The concrete problem, in real terms — not "improved efficiency" but the actual situation: the manual process, the failed prior attempt, the internal friction, what was breaking.
• The mechanism — what you actually did, step by step, so a reader can map it onto their own org.
• Real, bounded numbers where they exist — and an honest qualitative account where they don't. (Never invent figures to compensate for the missing name; a fabricated result is far more damaging to trust than a missing logo, and Japanese buyers are unusually good at smelling marketing math.)

The version that fails is the one that strips out the name and then, nervously, strips out everything else too — until you're left with "A leading company in the industry achieved significant results with our solution." That's not anonymous; it's empty, and emptiness is what Japanese readers distrust, not anonymity. The discipline is the opposite of your instinct: when you lose the name, you must add specificity everywhere else to carry the weight the logo used to carry. (We rebuild exactly this kind of flat, empty story into a persuasive one in the Teardown gallery.)

Done this way, an anonymous case study can out-persuade a named one from a foreign market, because relevance beats recognition for a cautious domestic buyer. One detailed, anonymous story about a company that looks like the reader's own does more than a wall of global logos they discount on sight.

How to ask — a real 打診 script

Most overseas teams lose the case study at the moment of asking, because they ask the Western way: big, public, all-or-nothing, up front. "Would you be a case study? We'd feature your logo and a quote on our site." To a Japanese champion, that ask is maximally exposing — you've handed them the version that triggers every gatekeeper at once. They have to say no, or kick it to 稟議 where it dies.

The fix is a graduated 打診 (sounding-out approach) that starts small, gives the customer control, and offers the anonymous option before they have to refuse the named one. Here is a script you can hand to your Japanese champion or send directly. It's written in calm, professional です・ます — an invitation, not a request for a favor.

The soft open (frame it as their control, not your need):

Notice what this does: it leads with the anonymous option as a normal, offered path, not a fallback you grudgingly allow when they balk. That removes the exposure objection before it forms. It hands them control explicitly (公開範囲は御社にすべてお決めいただけます). And it asks to discuss, not to approve — a far lower bar for a champion who then has to carry it internally.

Lower the barrier on what you need from them:

The two non-negotiable trust signals in any Japanese reference ask are right here: approval before publication (掲載前に必ず御社のご確認) and a veto that never expires (御社が「これなら出せる」と思える内容になるまで公開しない). A Japanese customer's deepest fear is losing control of how they're represented. Guarantee control, in writing, and you remove the reason most of them say no.

Give the champion an internal-sales tool. The champion has to sell this inside their own org, often through 稟議. Make that easy: offer to write a short Japanese summary of exactly what would be published and how it's anonymized, in a format they can attach to an internal approval request. You're not asking them to advocate from memory; you're handing them the document that gets it approved.

When approval stalls in 稟議: what to do instead

Sometimes you do everything right and it still stalls. The champion is on board, but the request entered 稟議 and went silent. Don't read the silence as a no, and don't keep pushing the full named version into a process that's already choking on it. Step the ask down instead.

Step down the public-ness until something clears. There is a ladder here, and each rung is easier to approve than the one above:

1. Named, public case study — logo, company name, full story. Highest exposure, hardest 稟議.
2. Anonymous case study, full specifics — industry, problem, mechanism, results; no identifying name. Clears far more often.
3. Anonymous, results-light, mechanism-heavy — focus on what you did and the situation, lighter on numbers if results disclosure is the sticking point.
4. Quote-only, anonymized — a single attributed-to-a-role line ("情報システム部 部長") with no company name.
5. Private reference — they won't go public at all, but will take a confidential call from a serious prospect. This still has marketing value: you can say "we can arrange a reference call with a comparable company" without naming anyone.

When 稟議 stalls, propose the next rung down explicitly: "実名が難しければ、匿名事例という形でも大変参考になります" (if naming is difficult, an anonymous case study would still be very valuable). You're not retreating — you're handing the gatekeepers a version they can approve without anyone owning the exposure risk.

Build proof that doesn't depend on any single customer's yes. The strategic answer to "Japanese customers are slow to approve references" is to not let any one approval be load-bearing. Compose your domestic proof from multiple anonymous stories, role-level quotes, and aggregate patterns, so your case for the Japanese market holds even while individual named studies grind through approval. The named ones, when they finally clear, become the cherry on top — not the foundation you were waiting on.

Teardown: a flat anonymous story rebuilt to convince

Here's the difference between an anonymous case study that works and one that's just empty. This is an illustrative composite — no real company, no real customer, and the Japanese below is original writing representative of common patterns, not anyone's actual copy. The "before" is the version teams default to when they get an anonymous yes and then panic about how little they're allowed to say.

Same constraint — no name allowed. One version is empty; the other could close a deal. The difference isn't the anonymity. It's whether you kept the specifics.

What it costs to produce one this way

A case study built like the "after" above isn't a logo and a quote you paste in an afternoon. The work is the interview that surfaces the scar, the draft that earns the customer's 「これなら出せる」, and the bilingual judgment to keep it recognizable without making it identifying. Knowing the rough cost of that work helps you decide whether to build it in-house or bring in help.

A few indicative reference points for the Japanese market, to anchor your planning:

• Per-case production, done by a Japanese B2B specialist: commonly cited in the ¥100,000–300,000 per case range (indicative; based on Japanese production rates). That covers the interview, drafting, the approval back-and-forth, and the anonymization.
• A bilingual agency on retainer: roughly ¥800,000–2,000,000+ per month (≈$5,500–14,000), typically with 6–12 month minimums. Powerful if you need a full program, heavy if you only need a handful of proof assets.
• Hiring a bilingual marketer in-house to own it: ¥7,000,000+ per year (≈$48,000+) fully loaded — sensible once volume justifies it, slow if you need proof this quarter.

Where Foothold fits is between "expensive retainer" and "no one to do it": month-to-month engagements that produce proof assets — anonymous case studies included — without a long lock-in. The Sprint engagement is $1,400/month, Growth is $2,900/month, and Embedded is $4,800+/month, all month-to-month. The point isn't the line items; it's that you can produce one persuasive anonymous case study at a time, prove the market, and scale the proof from there — rather than waiting on a single named approval that may never clear 稟議.

Keep going

• Start with the bigger picture: The first marketer in Japan: building proof in a market that resists it
• Run the interview that gets this kind of story: The customer reference interview process for Japan
• What a case study actually costs to produce here: Japanese case study production cost and the broader What Japan content costs
• See it in practice: more flat Japanese pages rebuilt to convince, in the Teardown gallery
• Not sure which proof asset to build first? Take the 60-second diagnostic, or see how a first marketer in Japan puts an anonymous case study to work.