How to sell B2B software in Japan without a local sales team

Ask a Japanese enterprise buyer why they did not proceed with a foreign software vendor and the answer is rarely about the product. It is some version of: there was nobody here.

Not "nobody here" in the sense of a sales office. Nobody who could be summoned to a meeting, held responsible when something breaks, or produce a contract in Japanese under Japanese law. Procurement and legal treat a vendor with no local presence as a risk to be justified, and mid-level champions rarely have the standing to carry that justification through.

The usual conclusion is that you have to hire. That conclusion is wrong, or at least premature. What the buyer needs is presence, and presence is separable from headcount.

What the buyer is actually checking

Strip the politeness away and the objection decomposes into five concrete things:

1. Can we contract in Japanese, under Japanese law, with a Japanese counterparty?
2. If this breaks at 3pm on a Tuesday, who answers in Japanese, and how fast?
3. Who is accountable — a name, a title, an address?
4. Can we pay by bank transfer against an invoice, on our closing cycle?
5. Has any Japanese company already taken this risk?

None of these five require you to employ anyone in Japan. All of them require someone in Japan to be answerable on your behalf.

Three structures that create presence without headcount

Reseller with a services wrap

A Japanese systems integrator or reseller contracts with the customer and buys from you. They handle contracting, first-line support and invoicing on domestic terms.

This solves all five checks at once, which is why it is the default route for enterprise software into Japan. The costs are real: margin (frequently 20–40%), loss of direct customer contact, and dependence on their sales priorities. It also tends to concentrate your Japanese revenue in one relationship, which becomes a governance problem at scale.

Best when your product needs implementation work that a partner can profitably deliver.

Outsourced local sales and support

A local team sells, supports and contracts under your direction, using their entity. You keep the customer relationship, the pricing and the roadmap; they provide the Japanese-facing presence and the operational answer to all five checks.

The difference from a reseller is control and data. You see every lost deal and every objection, which is the thing you most need in the first year and the thing a reseller structurally will not give you.

Best when you are still learning what the Japanese version of your offer is — which is most companies in their first two years.

Product-led entry with an enterprise ceiling

Self-serve signup, Japanese-language product and documentation, credit card billing. This genuinely works, and it works faster than either structure above — for SMB, individual developers and teams buying below the procurement threshold.

It has a hard ceiling. The moment a deal crosses into procurement review, all five checks reappear and the self-serve motion cannot answer them. Companies that treat product-led entry as the whole strategy typically plateau at a revenue level well below what the market supports.

Best as a demand-generation layer beneath one of the other two, not as a replacement for them.

What to actually do in the first ninety days

A sequence that has worked repeatedly:

Weeks 1–4 — establish that anyone wants it. Twenty to thirty structured conversations with target-profile companies, conducted in Japanese by someone who can read the room. The output is not leads. It is the list of objections, the language buyers actually use for the problem, and a read on price sensitivity.

Weeks 5–8 — build the minimum credible presence. Japanese landing page and one-pager written from the objection list, not translated from English. A Japanese point of contact with a name and a phone number. A contract template reviewed under Japanese law. Bank transfer invoicing.

Weeks 9–12 — close one reference customer, on bad terms if necessary. Discount it. Over-service it. Write the case study before you sign. The first named Japanese logo changes the conversion rate of every conversation after it by more than any other single action available to you.

Then decide. If those twelve weeks produce a reference customer and a pipeline that behaves, the case for permanent local headcount is now evidenced rather than assumed. If they do not, you have spent one quarter instead of two years.

The part people skip

Most failed Japan launches we are asked to diagnose skipped step one. They built the Japanese website first, because it is the visible, budgetable, schedulable task. Then they discovered that the positioning was wrong, and the website was an expensive statement of the wrong thing.

Twenty conversations in Japanese, before anything is built, is the highest-return activity available in a Japan launch. It is also the one that most requires someone local, which is why it gets skipped.

If you want those conversations run for you, that is a thing we do.