While preparing our BioJapan materials, we revisited an excellent guide from JETRO—the Japan External Trade Organization, a government‑related body that promotes trade and investment and equips foreign firms with practical playbooks for operating in Japan. Building on those fundamentals, this article reframes the insights specifically for CDMOs and platform biotechs who need to turn interest into execution.
In a previous post we noted Japan’s low English proficiency. Here’s the harder truth: even perfectly fluent Japanese won’t land a deal if you miss Japan’s operating expectations. The clearest window into this is how “small” details are treated. What many overseas teams would call cosmetic or minor routinely decide go/no‑go in Japan—whether in quality documentation, meeting follow‑through, or even how risks are logged. Language helps, but expectation alignment wins.
1) Decisions are consensus‑first (nemawashi → ringi), not quick “yes/no”
What it looks like. Alignment is built informally (nemawashi) before a formal approval (ringi). Pushing for a commitment in meeting #1 yields polite deflection rather than a decision. Technical voices (QA/QC, manufacturing, supply) often outweigh commercial enthusiasm.
How to respond.
- Map all stakeholders early (BD, QA/QC, site operations, medical, procurement) and pre‑align outside the big meeting.
- Send bilingual minutes with a one‑page Approval Brief (why now, risk/benefit, resources), designed to circulate internally.
- Offer a phased pathway (intro → document exchange → remote audit → pilot lot) that can be approved step by step.
2) Quality isn’t simply “strict”—it’s uniquely Japanese
What it looks like. Saying “Japan is strict” is imprecise. The reality is a distinct quality emphasis. This expectation extends far beyond manufacturing into the whole business and BD cycle: how decisions are documented, how risks are surfaced, how timelines and responsibilities are tracked, and how follow‑through is evidenced.
- From packaging to process. Packaging standards are a visible proxy for Japan’s mindset: appearance matters. Apply the same rigor to business development and deal execution, where so‑called cosmetic issues become process and communication defects that quietly stall ringi.
BD‑process translation (apply quality standards to deals).
- Co‑create a Decision & Communication Standard: a bilingual MoM/decision template with required fields (objective, risks, owners, dates), a “signal glossary,” tolerances for scope change, and an agreed “AQL” for unresolved questions before moving to the next gate.
- Pre‑alignment pilot: test pre‑reads and Q&A with 2–3 key functions, validate response SLAs, and lock the format stakeholders will circulate internally.
- 100% checkpoints: ensure data completeness, updated risk register, resource availability, and explicit go/no‑go criteria.
- Handoff & logistics validation: calendar discipline (JST coverage), version control, and clarity on who “presses send.”
- Evidence expectations: define screenshots, metrics, and rationales required in MoMs; how issues/rework are logged; and what closure looks like before escalation.
3) Presence is a seriousness test, not a courtesy
What it looks like. The fly‑in/fly‑out vendor pattern erodes confidence. Counterparties look for proof you’ll be responsive when issues arise and that you can “sit between teams” to close gaps quickly.
How to respond.
- Put named points of contact with JST coverage on slide 2 of your deck and in every MoM.
- Offer aftercare commitments (response windows in JST, incident triage protocol) and schedule quarterly reviews.
- Start with a paid feasibility or pilot so both sides experience the working cadence and escalation path before scaling.
4) Contracting culture: relationship‑first in Japan vs. contract‑first in Europe
What it looks like. In much of Europe—especially in consulting‑heavy contexts—the norm is contract‑first: a short free discovery, then no further discussion without a signed agreement. In Japan, that stance often backfires. The expectation is relationship‑first: more generous pre‑contract discovery, small unpaid work to show intent, and trust‑building before contract. Cutting the free period too quickly can stall momentum.
How to respond.
- Define a no‑fee discovery scope up front (call + short bilingual memo + high‑level feasibility checklist). Make clear that deeper analysis triggers a micro‑SOW.
- Offer micro‑engagement ladders: discovery → low‑fee diagnostic → paid pilot/workshop → full SOW.
- Use reciprocity framing: pair each free deliverable with a small ask (assign counterpart, unlock sample data, agree decision date).
- Set boundary conditions in writing: in MoMs, state what is free, what triggers fee, and when you will pause.
- Provide sample packs or a Letter of Engagement to bridge discovery and full contract.
- Avoid the freebie trap: cap hours; convert to a micro‑SOW when reached.
Field note. We have seen deals stall when the overseas side ended the free discovery too early. Relationship‑first sequencing wins: give just enough value to enable internal advocacy, then formalize with a micro‑SOW.
5) Signals are indirect; “yes” rarely means “yes‑as‑you‑mean‑it”
What it looks like. Honne/Tatemae and face‑saving norms surface objections as softer signals—“chotto muzukashii,” topic changes, or silence. Email minutes matter more than charismatic calls; LinkedIn is underused; execution teams may prefer Japanese even when BD speaks English.
How to respond.
- Treat silence as “not yet convinced,” and polite agreement as conditional. Ask, “What would need to be true to proceed?”
- Always send bilingual MoMs with owners and dates. Use checklists and remove ambiguity.
- Coach teams on JP meeting hygiene (pre‑reads, seating, turn‑taking). Escalate privately—never in‑room.
About JETRO (for readers new to Japan)
JETRO (Japan External Trade Organization) is a government‑related organization that promotes mutual trade and investment between Japan and the world. Their guides are an excellent primer. This article builds on those fundamentals and focuses on how CDMOs/biotechs can operationalize them in day‑to‑day work. When we setup join ventures with German companies, we asked for their help as well.