Shortening your Japan contact form lifts submissions and nothing else

A global form gets localised for Japan. Someone trims it to work email and company name. Submissions rise.

Pipeline does not. Two quarters later the read at headquarters is that Japanese inbound does not convert, and the budget moves to paid reach.

The form is not the problem because it is too long or too short. It is the problem because it was designed for a buyer who starts an evaluation alone.

The global form assumes a buyer who arrives by themselves

Most demand-gen forms are built on one premise. The person filling it in can decide to look at your product, and later can decide to buy it.

In Japanese enterprise deals that premise breaks early. A joint survey by IDEATECH and Hiroyasu Kitagawa of Demagen Research (published 9 June 2026, fielded 25 to 26 May 2026, n=325, limited to people who took part with at least one colleague in a Japanese purchase of business software or IT infrastructure worth 5 million yen or more per year; a vendor-run survey-as-PR exercise, so read it for order of magnitude) found 58.5% of those deals involved seven or more people. The functions in the room were IT at 42.2%, finance and accounting at 38.2%, and legal at 33.2%.

Your form is filled in by one of them. Often before the others know the project exists.

You cannot tell an early submitter from a late one, and both get the same email

Someone who has not yet raised the topic internally and someone whose evaluation is already circulating between departments land in your CRM as the same record.

With nothing on the form to separate them, the rep sends one sequence to both. Too early for the first, too late for the second. A quarter of that produces the sentence every Japan team eventually hears from sales, which is that the leads are low quality, and the usual response is to buy more traffic.

Cut the fields your reps can recover, keep the one they cannot

The test is a single question. After the form is submitted, can a rep fill this in without asking?

Company name gives you industry, headcount and location. Department and job title arrive in the email signature. A phone number takes one reply to get. Delete all of it. Keeping those fields adds friction without adding information.

What cannot be recovered is what the person was reading and trying to solve at the moment they clicked. Call them the next day and they will have rewritten it into something tidy and general. The specific version only exists at submit time.

So keep one optional free-text question. Something close to “in one line, what are you looking at right now.” Whether it is answered at all is your only usable signal for splitting the traffic you just increased.

One Japan-specific caution on the fields you do keep. Japanese company names arrive with 株式会社 before or after the name, in full-width or half-width characters, sometimes under a former name, so matching a submission to an existing account fails more often than it does in other regions. That is a list preparation problem, not a form problem, and shortening the form does not fix it.

Change what the submit button leads to, not only the number of fields

In the same survey, the things Japanese buyers said were hardest to judge before talking to a vendor were the operational load after go-live at 56.3%, feature comparison at 47.1%, and calculating ROI at 41.5%. The content they found most useful was an ROI calculator at 55.4%, followed by case studies from a similar industry and company size at 46.5%, and slides they could use to explain the purchase internally at 26.8%.

The same respondents said general industry trend reports at 49.5% and feature comparison tables at 46.2% had no influence on the decision.

Read those together and the Japanese submitter is doing something specific. They are assembling an internal case, on their own, before the group exists. If the only next step your form offers is booking a call, you are routing every one of them into the one action that requires the group to exist first.

Delete the fields a rep can recover. Keep the one question only the submitter can answer, and put something behind the submit button that helps them build their case without you.

Common mistakes

• Treating field count as the whole design. Fields are the cost of submitting. What you ask, and what happens next, decide who submits and whether anything follows.
• Enriching your way out of it. Enrichment recovers firmographics. It cannot recover intent, and Japanese name matching makes it less reliable here than the global average anyway.
• Reading flat pipeline as low intent. Japanese submitters are frequently early by design, because the internal case gets built before the group is convened. Early is not the same as unqualified.

Related reading

Where to draw the handover line once you can tell the two groups apart is covered in changing the handover rule from lead score to buying behaviour. The free-text answer from the form is usable as that trigger.

Other notes on the same problem are collected under Demand generation.