Sales process
A Japanese pipeline reviewed on rep confidence will be wrong in a specific direction: the deals look healthy until the quarter they were supposed to close.
This category covers the mechanics that make it readable, including forecasting on approval progress rather than sentiment, what to hand a champion who has to write the internal proposal, how to record loss reasons that survive analysis, and what to ask in a first meeting when the buyer has already done the evaluation.
10 articles
In Japan, 'we'll take it back' is a handoff, not an answer
Your Japan rep closes the meeting with the buyer saying they will take it back and consider internally. HQ hears a soft yes, or a soft no, and the deal sits in the CRM as 'evaluating' for a quarter. It is neither. It is the moment the deal is handed to seven or more people your team will never meet, with no record of the handoff on either side. What to ask before leaving the room, where to put the follow-up date, and the two fields to add.
Japan pipeline grew, revenue flat: the stall is downstream
You told the Japan team to run more meetings. Meeting count and pipeline value both climbed, and bookings did not move. The usual readings are weak reps or soft demand. Neither explains it. The added deals all queued at the same point, inside the buyer's approval circuit, where meeting volume has no effect and the work that does have an effect has no field in your global CRM.
What your Japan handoff drops is the reason the contract was approved
Your Japan closed-won record is complete: contract terms, contacts, go-live date. It is still missing the one artifact that decides the renewal, which is the sentence the customer's own approval document used to justify the purchase. That sentence exists, it is in Japanese, it was half-written by your seller, and it lives in a folder you will never open. Why renewals in Japan turn into fresh approvals, and the one field to add before your next close.
Why your 30-day quote expires inside Japan's approval cycle
HQ tells the Japan team to get the quote out fast. But in Japan the quote is the number a stranger has to defend in writing, and 73.5% of large purchases run longer than planned (IDEATECH, 2026). A quote issued before requirements settle becomes a price increase later. What to send instead, and how to set the validity date.
"No budget" in Japan is a date, not a number
Your Japan rep reports no budget, HQ reads soft demand, and the response is discount approval. But Japanese IT budgets are rising: 52.6% of surveyed companies increased theirs (JUAS, n=957). The increase is pre-committed, and the fiscal year runs to March. What to ask for instead of a price cut, and the CRM fields that keep the deal alive.
Your Japan battlecard is read in a room your rep never enters
HQ localises the global comparison matrix, the Japan team sends it, and the deal still sits in evaluation. Japanese buyers finish comparing before your rep is invited, and the document that actually moves inside their company is not a battlecard but an attachment to an approval. Survey data (n=307, n=330) and the sheet to ship instead.
In Japan, the first meeting is not discovery. The shortlist already exists.
Your global first-call framework opens with pain discovery. Japanese buyers of large B2B deals have finished that work before your rep joins the call, and a two-to-three vendor shortlist is already drawn. Here is what to ask instead, and which fields the answers belong in.
Why every lost deal in Japan shows up as "price" in your CRM
Your Japan closed-lost report says price, so headquarters approves a discount policy, and nothing changes. The picklist was designed for a market where deals are lost to competitors. In Japan they are lost to an approval that stops moving, and there is no value in the field for that. Here is how to rebuild the list.
Forecast your Japan pipeline on approval progress, not rep confidence
Every deal in your Japan pipeline looks positive, yet the quarter slips again. The cause is not weak local reps. It is that confidence is set by the rep's read of a buyer who cannot approve anything. Add a second axis that tracks how far the approval has climbed, and define which deals leave the forecast before the quarter closes.
In Japan, deals are won on precedent rather than features
In Japan, approval passes on precedent, not feature superiority. The number that decides your deal is whether a similar-sized company in the same industry already uses you. Here is the data and how to build it into your sales process.
Frequently asked
- How should we forecast Japanese deals?
- On how far the buyer's internal approval has travelled, not on how the meeting felt. Because more than 80% of large Japanese purchases clear two or more approval stages (IDEATECH and Kitagawa, April 2026, n=307), a deal where only the operational owner is convinced is early regardless of how positive the conversation was. Track the two axes separately and forecast on the lower one.
- Our champion says they are preparing the paperwork and then nothing happens. Why?
- Because they are being asked to author a document they have never written for a product they have owned for weeks, with no deadline. The document, a ringi, circulates to people your reps will never meet. Writing the draft for them is a sales deliverable in Japan, not an overstep.
- What actually gets a vendor selected in Japan?
- Precedent more than features. In the same IDEATECH and Kitagawa study, the most influential factor in reaching the final selection was having a reference customer of similar size, at 44.3% (this question n=298), while the top reasons for being dropped were insufficient fit to the specific problem at 39.1% and a sense that the vendor was wrong for a company of that size at 34.5%. A global logo slide can actively work against you here.