Why Your Japanese Pilot Never Became a Contract

The pilot everyone was happy with

Six months ago you signed a pilot with a Japanese enterprise. Maybe a manufacturer, maybe a bank. The team on their side was serious. They joined every call, sent detailed feedback, and tested your product against internal data more rigorously than any customer in your home market. The final review went well. Someone said the word "excellent" out loud.

Then the replies got slower. A reorganisation was mentioned. Your champion is still friendly, still answers, still says the project is alive.

There is still no contract.

We hear a version of this story most months. The company changes, the product changes, the ending is the same.

A pilot is not a purchase decision. It is risk removal.

In most Western markets, a pilot is a stage in a buying process. Budget is loosely allocated, the pilot tests fit, and success moves the deal forward. The pilot is the deal in miniature.

In a Japanese enterprise, it is usually something else. A pilot is the mechanism by which one person inside the organisation removes personal risk from an idea they already like. They cannot walk an unproven foreign vendor into the room where spending gets approved. They can walk in a completed evaluation with results.

So a successful pilot does not create a reason to buy. It creates material that makes buying defensible. Those are not the same thing, and the distance between them is where a lot of foreign startups lose a year.

Who paid for the pilot tells you almost everything

Free pilots feel like a way to lower friction. In Japan they are more useful as a diagnostic.

If your pilot was unpaid, think about what that means. No budget line existed. Nobody had to justify a spend, which means nobody has yet made the internal argument that you are worth money. You were given access without commitment, which was generous, and which is also why nothing happened afterwards.

A paid pilot behaves differently, even at a small number. Someone had to raise a purchase order and get it through. That person's name is the answer to the question you actually care about.

The fix: charge something. Even a token fee forces someone to own the line item, and that person is the one who can buy.

The budget cycle nobody told you about

Most Japanese companies run an April to March fiscal year. Budgets for the coming year take shape between October and December, get argued through January, and are locked well before March. By February, money for the year starting in April is already committed.

Now go back and look at when your pilot ended.

If it wrapped up in February or March, you were probably not rejected. You arrived after the window closed. The soft language you got back, that they would like to continue the discussion, that this could be picked up next time, was often literal. It meant a wait of twelve months rather than two weeks. Nobody said that part out loud because inside their world it was obvious.

We have watched strong pilots die on this alone. The product worked. The timing was wrong by about six weeks.

Your champion had authority to test, not to buy

The person running your pilot is often a section manager. They can start an evaluation, direct their team's time, and request a small amount of money. They cannot approve a multi-year contract.

That approval moves through ringi, a document that circulates for consensus before it reaches anyone with signing authority. By the time it is formally reviewed, the real persuasion has already happened privately, in the nemawashi conversations your champion had with counterparts in finance, legal, IT security, and the business unit that would actually use your product.

You were in none of those rooms. Your champion carried you into them alone, using whatever your pilot produced, translated into a form his colleagues expect to see.

If you never asked who those people were, you handed the most important part of your sale to someone who does not sell for a living.

The fix: before the pilot starts, ask who signs if it works. If nobody can answer, you are running a science experiment, not a sales process.

How to design a pilot that converts

The changes are small, and almost all of them happen before anything begins.

Agree the success criteria in writing, with numbers, before day one. Not because Japanese companies are unusually rigid, but because a vague success is impossible to defend on paper. Your champion needs a sentence he can put in a box.

Charge for it. Small is fine. Free is expensive.

Identify the budget holder by name and title, then ask what that person needs to see. This question is not rude. Asked plainly, it reads as competence, and it is one of the fastest ways to find out whether a deal exists at all.

Build the internal materials with your champion rather than for him. Sit down together and produce the comparison table, the cost case, the security answers. He knows the format his company expects. You know the product. Done separately, the result satisfies neither side.

Then finish early. If you want money in the fiscal year starting in April, target an October or November completion. That gives your champion the winter to fight for you, and winter is when the fighting happens.

Map the schedule backwards from March, not forwards from today.

The test you did not know you were taking

Foreign teams treat the pilot as a technical exam. They optimise for performance, uptime, integration speed, a clean set of numbers at the end.

Their Japanese counterpart is sitting a different exam. His question is whether recommending an unknown overseas vendor will damage his standing if something goes wrong three years from now. Every request for one more data point, one more reference, one more security document, is that exam being taken in front of you.

A pilot in Japan does not answer the question "does this work." It answers the question "can I defend this internally." Design for the second one, and the first takes care of itself.