— Guide · Sales
B2B sales in Japan: how Japanese enterprises actually buy.
Foreign companies do not lose in Japan because the product is wrong. They lose because they sell to the wrong person, at the wrong time, with the wrong document — and then give up two months before the buyer was ready. This page explains the mechanism: who decides, how long it takes, what the calendar does to your pipeline, and what to change.
— Short answer
Japanese enterprises buy by bottom-up consensus. A mid-level manager writes an internal approval document (the ringi-sho) that circulates upward for sign-off; the executives ratify what has already been agreed. The cycle runs 12–18 months for enterprise deals, most of it invisible to you, and it moves on a fiscal calendar that fixes budgets between October and December. Selling here means equipping the person who writes that document — in Japanese, with references, security evidence and a small pilot that has a pre-agreed path to contract — and getting introduced rather than found.
By Yuki Kishi · Updated September 21, 2026 · 10 min read
— The buyer
Who actually decides: the buyer unit, not the buyer.
The first mental model to discard is the executive sponsor. In a Japanese company the decision to buy is assembled from below. The person in charge of the evaluation — often a manager in their thirties — writes the ringi-sho, the written proposal that travels up through the section manager, the department head and every adjacent division that has a stake, collecting approval seals as it goes. By the time it reaches an executive, saying no would mean overruling the organisation.
Before the document is even written, the same manager has done nemawashi: the quiet round of one-to-one conversations that secures informal agreement so that the formal process contains no surprises. Roughly two-thirds of the sales cycle is spent here, and you will see none of it.
| Layer | Role in the decision | What they need from you |
|---|---|---|
| Tanto (担当者) — the person in charge | Runs the evaluation, writes the ringi-sho, presents you internally | Everything they will be asked, answered in Japanese before they are asked it |
| Kacho (課長) — section manager | First approval; owns the team that will use the product | A one-page summary they can forward without translating, and a reference they can call |
| Bucho (部長) — department head | Budget owner; decides whether it goes to the fiscal-year plan | Total cost of ownership in yen, vendor stability, what happens if you leave Japan |
| Adjacent divisions — IT, security, legal, procurement | Each signs the ringi-sho or blocks it | ISO 27001 / ISMS evidence, APPI data handling, a contract they have seen before |
| Executives | Ratify what has been agreed below | Almost nothing — by the time it reaches them the decision is made |
The practical consequence is that your real customer for most of the cycle is the tanto or kacho who will defend your proposal in rooms you are not in. Every material you produce should be written for that person to forward, not for you to present.
— The cycle
How long B2B sales take in Japan, and why.
12–18 mo
First introduction to first annual enterprise contract
~2/3
Share of the cycle spent on internal consensus you cannot see
Oct–Dec
When next year’s budgets are fixed inside most Japanese companies
| Buyer type | Typical cycle | What moves it |
|---|---|---|
| Mid-market SaaS, digital-native buyer | 3–6 months | Product and API quality; a Japanese-speaking counterpart |
| Large enterprise (manufacturing, retail, services) | 9–18 months | A champion, a reference, the October–December budget window |
| Banks, insurers, regulated buyers | 12–18+ months | Security review, an SIer relationship, regulatory clarity |
| Anything sold through a trading company or distributor | 3–9 months to sign the partner, then their calendar | Margin, exclusivity terms, enablement |
Ranges from YKBridge engagements and published operator surveys for foreign B2B software and services companies; individual deals vary with urgency and with whether a reference customer exists.
Two features of the calendar do most of the damage to foreign pipelines. Budgets for the fiscal year beginning in April are fixed between October and December, so a deal that is not a line item by December waits until the following spring however enthusiastic the champion is. And personnel rotate in April and October: the manager who loved your product in February may be running a different department by May. Start conversations in spring to be in an autumn budget, and re-confirm every champion after each rotation.
The month-by-month version of this cycle — what happens in months one to twelve and what to do in each — is in our Japan market entry timeline.
— Channels
Direct, system integrator, trading company: who sells for you.
Japan has one of the deepest channel ecosystems in the world. General trading companies (sogo shosha) and specialist distributors carry products into accounts they already serve. System integrators — NTT Data, Fujitsu, Hitachi, NRI, NEC and hundreds of smaller ones — are the route through which most large enterprises buy and implement technology, and for anything that touches core or channel systems, vendor status with an SIer is often the precondition for the deal rather than an alternative to it.
The trade-off is the same in every channel. The partner brings accounts and local credibility, takes 20–40% of the margin, sells on its own calendar, and sits between you and the customer conversations that should be shaping your product for Japan. For software and services aimed at a handful of enterprise accounts, the usual sequence is direct sales first with a senior bilingual person on the ground, then partners once demand exists and coverage is the constraint. For hardware, or anything needing local stock and support, the partner comes first.
Whichever route you take, the introduction still matters more than the channel. Cold outreach to Japanese enterprises is close to useless; warm introductions through a customer, an industry association, an investor, an SIer or a Country Manager who already has the relationship are how first meetings happen.
— What to change
Six changes that fix a half-size Japan pipeline.
- 01
Localise the deck; do not translate it
A Japanese enterprise deck runs about 40% longer than the US version because it answers the questions the ringi-sho will raise: company history, financial stability, customer logos that mean something in Japan, support model, security posture, exit provisions. Reviewed by a native speaker who has sold, not by a translation agency.
- 02
Put the founder in the room
A CEO who flies to Tokyo for a discovery meeting signals that Japan is a strategic market, not an experiment. Japanese buyers read commitment as a proxy for vendor risk. Two trips in the first six months is normal; none is a red flag.
- 03
Equip the champion, not the executive
The mid-level person who writes the approval document is your real customer in months three to nine. Give them a Japanese summary, a security questionnaire already filled in, a reference customer who will take their call, and a pricing table with no surprises.
- 04
Write the path from pilot to contract before the pilot
Most Japanese pilots never become contracts because success was never defined. Agree in writing, before day one, which three metrics decide it and what happens on each outcome. Keep the pilot small: one team, ninety days, minimal integration.
- 05
Respect the calendar
Budgets are fixed between October and December for the fiscal year that starts in April. Staff rotate in April and October. A deal that is not a budget line item by December waits a year; a champion who rotates in April may take your deal with them or leave it behind. Re-confirm champions in November and May.
- 06
Sell the way they buy
Yen pricing, annual invoicing, bilingual contracts with Japanese prevailing, month-end closing and payment at the end of the following month, credit and anti-social-forces checks, a company seal. None of it is negotiable in practice, and a vendor who arrives already set up for it removes a month from the cycle.
— Reading the room
What the buyer is telling you, and what to do about it.
| What you hear or see | What it usually means | What to do |
|---|---|---|
| "Very interesting" from a manager with no budget | Polite acknowledgement | Ask who else should be in the next conversation |
| "We will discuss internally" from a department head | Nemawashi is starting | Send a Japanese one-pager they can circulate; then wait |
| Silence for four to eight weeks after a good meeting | Consensus being built out of sight | One useful follow-up every two to three weeks; never "any update?" |
| A new, more senior name on the thread | The ringi is moving up | Prepare the formal proposal and pilot structure now |
| A request for a security questionnaire or Japanese contract | Procurement has been told to expect you | Answer within a week, in Japanese, completely |
| Increasing vagueness and slower replies after month seven | The process is dying | Ask the champion directly what changed; accept the answer |
The one rule
Japanese buyers almost never say no directly, and they almost never say yes early. Foreign companies fail in the gap between those two facts: they hear "very interesting" as a yes in month three and silence as a no in month six, when the truth was the reverse. A senior person who can read the language of the room in Japanese — and who has the relationships to ask what is really happening — is not a nice-to-have in this market. It is the difference between a pipeline and a list of meetings.
— Who does the selling
The person on the ground is the strategy.
Everything above assumes someone senior, bilingual and present in Tokyo is doing the work: securing introductions, sitting in the discovery meetings, producing the Japanese materials the champion needs, reading the silences, and steering the pilot toward a contract. The options are a full-time Country Manager (right once there is a pipeline to manage), a distributor or SIer (right when the product needs one), or a fractional Country Manager who joins your team under your email domain for 16–32 hours a month and builds the pipeline before you commit to either.
That last model is what YKBridge does — $300 an hour, month-to-month, backed by a 60+ bilingual specialist network — and the first ninety days of it follow the phases on this page: ICP and introductions in month one, first meetings in month two, a qualified pipeline and an honest go / hold / exit verdict in month three.
— Questions founders ask
B2B sales in Japan, answered.
Twelve to eighteen months from first introduction to a first annual contract is normal for enterprise deals; mid-market SaaS deals close in three to six months; payment companies and digital-native platforms buy closer to a Western cycle. Roughly two-thirds of the time is spent on internal consensus-building (nemawashi) that you never see. Plan for a paid pilot in six to nine months and a first contract in twelve to eighteen.
— Go deeper
- We Launched in Japan but Sales Are Half of Other Regions — Why, and What to DoThe consensus machine in detail, with the four fixes.
- Japan Market Entry Timeline: What Actually Happens in Months 1–12 (and When Deals Close)The month-by-month version of the cycle described above.
- Why Your Japanese Pilot Never Became a ContractHow to structure a pilot with a pre-agreed path to signature.
- Why Japanese Buyers Go Quiet on Your Pitch Deck (and Why It Needs to Be 40% Longer)What the Japanese deck has to contain.
- Autumn Is Japan’s Real Budget Season. Your Q4 Pipeline Is Already Too Late.The October–December budget cycle every deal has to survive.
- Hire a Japan Country Manager, go fractional, or use an agency?Who should be doing the selling described on this page.
— Ready when you are
Japan can be your next chapter.
Start with a 30-minute fit call. We'll listen to your Japan ambitions and tell you, honestly, whether we're the right partner — or not.
Available within 48 hours · Tokyo & Amsterdam time zones