Customer success in Japan: a practical guide for enterprise accounts

Most customer success playbooks assume the customer reads English, decides in the meeting and buys whenever the value is clear. Large Japanese companies do none of those reliably. I work with them from Osaka, for a company headquartered in San Francisco, and this is what I do differently, roughly in the order the work happens.

Work in Japanese, and in writing

Engineers in Japan read English documentation all day, so it’s tempting to run the account in English. The problem is everyone else. Your champion (usually the engineer who chose you) has to explain you to a manager, the IT department, security and procurement, all of whom work in Japanese. Every English email you send is homework for your champion.

So the default is Japanese, and mostly written. Send the agenda the day before and the minutes, gijiroku (議事録), the same day: decisions, open questions, owners, dates. Meetings in Japan rarely end with a clear verbal yes. The minutes are where agreement shows up, because people correct them when they disagree.

Make the teirei worth attending

Most enterprise accounts settle into a teirei (定例), a standing meeting every week or two. It’s the backbone of the relationship, and very easy to waste on thirty minutes of status updates that everyone could have read.

Start each one from a shared issue list, kadai kanri-hyō (課題管理表), with one owner and one due date per line. Send the material the day before, so the meeting is for decisions and questions. Leave room for the customer’s topics; if your roadmap fills every slot, they stop bringing you problems. And when a technical item is open, put the engineer who can answer it in the room instead of promising to follow up.

Weekly makes sense during a migration. The same slot a year later, with nothing on the list, trains everyone to skip it.

Write a success plan the customer can forward

A success plan in Japan has two readers: the champion who helped write it and the manager who approves next year’s budget. Write it for the second one.

Keep it to a page. Start with the customer’s goal in their own terms (release frequency, fewer incidents, a launch date they’ve already promised internally), then the phases, an owner on each side for every phase, and dates mapped onto their fiscal calendar instead of yours. Write it in Japanese and keep it wherever they keep documents. If that’s Excel, it’s Excel.

“Roll out feature X” is your goal, so leave it out of the headline. Theirs is whatever their boss asked for.

Executive business reviews in Japanese

An executive business review in Japan is rarely where anything gets decided. The decision happens before, through nemawashi (根回し, quiet one-on-one alignment ahead of a meeting), and the review confirms it in front of the people who need to see it confirmed.

That changes the preparation. Walk your champion through the whole deck a week ahead and ask what their executive will push back on, then take out anything that would surprise them in front of their boss. Put the explanation on the slides, because decks get forwarded to people who weren’t in the room. End with a proposal the executive can accept on the spot, like the next phase or a joint review in six months.

Map the people behind the account

The engineers who use your product are a small part of the account. The rest usually looks like this:

Who	What they care about	What they need from you
Business unit (jigyōbu, 事業部)	Launches, revenue, the project their boss is watching	Outcomes in their terms, a plan that hits their dates
IT department (jōshisu, 情シス)	Internal standards, operations, the vendor list	Architecture documents, SSO, logs, a clear support path
Security	Risk, audits, where data lives	Complete answers to their checklist, on time
Procurement (kōbai, 購買)	Contract terms, vendor registration, the budget line	Paperwork in the format they use, or a partner to buy via

The business unit usually brings you in; 情シス often decides whether you stay. Meet IT early, before they’re asked to approve something they’ve never heard of.

Expect a long security checklist (セキュリティチェックシート) too, usually in Excel and in Japanese. Its deadline is part of the sales cycle.

Escalations, incident reports and apologies

When something breaks, expect a request for a written incident report, a shōgai hōkokusho (障害報告書), often within a few days. Your champion needs it for their own management, so once again you’re writing for someone who wasn’t there.

A structure that works:

件名: 【障害報告】<service> <date>

1. 概要          Summary
2. 発生日時      Start and end time, in JST
3. 影響範囲      What was affected, and for whom
4. 原因          Root cause
5. 対応内容      What we did, with timestamps
6. 再発防止策    What changes to prevent a repeat, with dates

The apology comes first, and early. In Japan it’s an apology for the trouble caused (ご迷惑をおかけし申し訳ございません), and nobody reads it as a legal admission of fault; legal teams abroad sometimes need that explained. A report without one reads as not taking the problem seriously, which costs more trust than the outage did.

Accountability lives in section 6. Customers read the saihatsu bōshi-saku (再発防止策, recurrence prevention) more closely than anything else, so only write measures your engineering team has actually committed to, with dates. A vague “we will strengthen monitoring” comes back with questions.

Osaka is 16 or 17 hours ahead of San Francisco, so the report often gets written from the global team’s notes while they sleep. Put every timestamp in JST.

Time renewals to the April fiscal year

Most large Japanese companies run their fiscal year from April to March and draft the next year’s budget months before it starts, usually in the autumn and winter. Spending above a threshold also needs a ringi (稟議), a written proposal that collects approvals up the chain.

So if you bring an expansion proposal a month before renewal, the budget for it was locked half a year ago. Work backwards from their calendar:

1. During onboarding, ask when budgeting starts and who writes the ringi.
2. Hold a review with real numbers before that date, so the champion has evidence for the proposal.
3. Give them the material in Japanese, in the shape the ringi needs.
4. Where you can, line the contract term up with their fiscal year, so the renewal matches a budget line that already exists.

Consumption pricing adds a twist. A Japanese budget is a fixed number approved once a year, and going over it means another round of approvals nobody enjoys. So usage planning is part of the job: forecast with the customer, check the trend monthly, and warn them early if they’re heading past the budget line.

Treat SIers and partners as part of the account

Many Japanese enterprises build through SIers (system integrators). The integrator’s engineers often write most of the code, know the system better than the customer does, and have a relationship years older than yours.

Don’t go around them. Invite them to the teirei, train their engineers as seriously as the customer’s, and let them lead where they’re stronger. Some customers also prefer to buy through a partner they already have a contract with, which saves everyone a vendor registration.

Partners also reach teams you’d never meet one account at a time. In October 2025 I gave the Vercel session of a hands-on workshop with AWS Japan and Classmethod at AWS Startup Loft Tokyo.

Enablement in Japanese, and community

English documentation covers the product, but not the questions a Japanese team won’t ask in English. Run enablement sessions in Japanese, hands-on rather than slides, and record them for whoever joins the team next year. Don’t end with “any questions?” and a silent room; I wrote about what to do instead in what teaching Japanese taught me about onboarding.

Community does the rest. Japanese engineers trust other engineers more than any vendor, and study sessions (benkyōkai, 勉強会), meetups and hackathons build that trust. I’ve been on stage at Vercel meetups in Tokyo, one of them with our CEO Guillermo Rauch, and co-organized the Tokyo AI Hackathon with Anthropic, Raycast and Supabase. The full list is on the speaking page.