Getting generative-AI dev tools adopted in large Japanese companies

I've spent the last couple of years helping large Japanese companies adopt generative-AI development tools, starting with some of the first enterprise rollouts of v0, Vercel's AI app builder, in Japan. The pattern is consistent enough that it's worth writing down.

The short version: the product is almost never the problem.

The question isn't "is it good?"

Show an engineer a working app generated from a plain-language prompt and you don't need to convince them of anything. The questions that decide whether a company adopts it come from other people:

Where do prompts and code go, and are they used for training? Who owns the generated code? How does it pass the security checklist (セキュリティチェックシート), which at a large company can run to a few hundred questions? Who is accountable when generated code ships a bug?

These questions have good answers. The mistake is waiting to be asked. I prepare them in Japanese, in writing, before the first demo, because they will be asked, and the person asking usually isn't in the demo.

Pilots need a deadline

A pilot with no deadline is a free trial that expires quietly. The pilots that turned into rollouts had a team with a real internal tool or prototype due, a date, and one person responsible for reporting back.

What to measure is simple and convincing: how long it took to get to a first working version, and how many people outside engineering could contribute to it. The second number is usually the one that gets attention.

Hackathons are an adoption tool

I used to think of hackathons as community events. They are also the fastest way to teach a company how to work with these tools.

People learn prompting by doing it with a deadline and an audience. The demo at the end produces what a rollout actually needs: a few internal champions, working examples in the company's own context, and screenshots that end up in the approval document. The Tokyo AI Hackathon we ran with Anthropic, Raycast and Supabase worked the same way for the wider community: teams built Claude-powered Raycast extensions and MCP integrations in a single day.

Seats and consumption are different conversations

v0 is sold per seat. The Vercel platform underneath is billed by usage. Japanese procurement strongly prefers a predictable annual number, so the two need different explanations.

Seats are easy: count the people. Usage needs a forecast, spend limits and a clear owner for the monthly review, otherwise the first unexpected bill becomes the reason to stop. I'd rather spend an hour building that forecast with the customer than a week explaining an invoice.

Let people prompt in Japanese

Teams work best when they prompt in the language they think in, and current models handle Japanese well. What still needs a human is the output that users will read. Generated interface copy needs a review for register (keigo is easy to get slightly wrong), and Japanese text needs proper line breaking. If you ship Japanese UI, word-break: auto-phrase in CSS is worth knowing about.

Where rollouts stall

After a successful pilot, the most common failure is that nobody owns the tool. The champion goes back to their day job, usage drifts down, and a year later the renewal conversation starts from zero.

Name an owner before the pilot ends. Give them a monthly review with the vendor and a small budget for internal events. It sounds bureaucratic, and in a large Japanese company that is exactly why it works.