Your free trial won't close the deal in Japan. The approval document will.

Your self-serve motion works in every other market. In Japan, prospects take the trial, use it, say good things, and then nothing happens for three months.

HQ reads this as a product-market fit problem, or a pricing problem. It is neither.

The trial proves your product works. It does not produce anything the buyer can take into a Japanese approval process.

Same product, opposite front door

In the US, the entry point is “try it first.” In Japan, the same product usually opens with “let’s talk first.” That is not a cultural quirk; it is structural.

For systems of record such as CRM, ERP, marketing automation, and security tooling, fit cannot be judged by touching the product alone. It depends on existing integrations, workflows, who will operate it after go-live, and internal security requirements. None of that appears on a product screen or a public pricing page.

So the buyer asks a person first. Sales comes before the trial, not after it.

What the buyer is actually stuck on

HubSpot Japan’s “2026 Survey on B2B Buying in Japan” (published 16 July 2026; fielded 11 to 16 June 2026 by Macromill; 1,573 respondents at companies with 50 or more employees who were involved in comparing, selecting, or approving a B2B purchase; note that HubSpot sells CRM, so this is a vendor’s own study) found the top difficulty in moving a decision forward was “hard to explain the cost-benefit internally,” at 21.9%, excluding “nothing in particular.”

In the same survey, 46.9% of purchases involved five or more internal stakeholders including the respondent, and 50.9% took a month or more from start to decision.

Note what this is not. It is not the widely quoted “5.4 decision-makers” figure, which comes from a US CEB study of US companies. This is Japanese data, from a disclosed sample.

The buyer is not stuck on whether your product is good. They are stuck on how to explain it upward.

The approval ladder outranks the product evaluation

In a joint study by IDEATECH and Hiroyasu Kitagawa (published 16 April 2026, n=307, covering people who were involved with at least one other colleague in a B2B purchase of 3 million yen or more in annual contract value within the past 12 months; this is IDEATECH’s research-PR programme), more than 80% of deals passed through two or more approval stages before the final vendor decision, with “two stages, department head plus executive” at 60.9%.

Departments involved were IT at 45.6%, the using business unit at 37.5%, and corporate planning at 29.0%. From the start of evaluation to the final vendor decision, 63.6% of deals took three to eight months.

Only one of those parties ever opens your trial. Executives and the IT department do not look at your product screen. They read documents.

The same study shows what gets vendors dropped: “did not feel it fit our company size” at 34.5%, and “no reference customer similar to us” at 26.4%. The top factor for making the shortlist that ultimately won was “a reference customer of a similar size existed,” at 44.3% (this question only, n=298).

What is being judged is fit and precedent, not product behaviour.

How to redesign the trial for Japan

Do not remove the trial. Change what it is for. In Japan it is not an evaluation stage; it is a manufacturing stage for approval material.

1. Agree the deliverable before the trial starts. Write down who receives what, and on what date. A trial without a named approver and a submission date ends as an opinion, not a document.
2. Bring the IT department in on day one. IT is the most frequently involved department (45.6%). Deferring integration and security review until after the trial simply starts a second multi-month process.
3. Place the trial just before the final comparison, not at the top of the funnel. With 63.6% of deals running three to eight months, a 30-day trial run early is stale by the time the approval paper circulates.
4. Ship documents, not impressions. A cost-benefit calculation, the named operator and estimated effort after go-live, the integration and security review result, and a reference customer of similar size. Those four items are the contents of the approval paper.

Aim the documents at what Japanese buyers actually trust. In the HubSpot Japan survey, the highest-trust information was “clear pricing, additional costs, and contract terms” at 60.6%, “an individual explanation from the vendor’s representative” at 59.8%, and “the vendor’s customer references” at 57.0%.

What buyers most want from the sales and proposal process is “a proposal adapted to our situation” at 37.1% and “an explanation of cost-benefit and ROI” at 30.2%. Before signing, the single most requested item is clarity on support: “the contact point, hours, and scope of support are clear,” at 35.3%.

None of that is visible inside a trial account. A person has to write it down and hand it over.

This is not an argument against product-led growth. It is an argument for wrapping people around it: sales frames whether the product can actually be deployed, the trial proves the value, usage surfaces real signals, and sales then supports the internal decision.

Treating the Japanese market as one continuous revenue architecture from acquisition through retention is what tells you where in the process the trial belongs.

In Japan, a trial is not where the product gets evaluated. It is where the material that clears internal approval gets built.

Common mistakes

• Reporting Japan on trial-to-paid conversion. In a market where the trial sits late and sales comes first, that ratio measures the wrong stage. Track how many approval-ready documents a deal has produced.
• Reading a happy user as pipeline progress. “They said it was easy to use” is not progress in a two-stage approval structure. Progress is a document reaching the next approver.
• Leaving the business case to the buyer. Explaining cost-benefit internally is their single biggest difficulty. Hand over the calculation template and the assumptions, not a link to a trial.

Related reading

What actually carries an approval document internally is precedent, not features. why deals in Japan are won on precedent rather than features has the data.

Other notes on the same problem are collected under Japan market entry.