Meeting Read サンプル

1. What was said

Attendees: your CEO and BD lead; their side, four people: General Manager (led the meeting), two section managers, and a director who joined 10 minutes late and spoke once. Your CEO presented the platform for 18 minutes. Their questions, in order: company history (founded when, headcount), current Japan clients (none yet), funding and shareholders, then two product questions on data residency and Japanese-language support. Your BD lead proposed a pilot in two schools by October. The GM answered that the timeline would be discussed internally. Closing line from the GM: 前向きに検討させていただきます (we will consider this positively). No concrete commitments were made by either side, except your promise to send the security whitepaper.

2. What was meant

The closing line (前向きに). Read: mildly positive, not a yes. Evidence: it came from the GM, not the director, and was not paired with any process question (who signs, what steps, when). When this phrase is a real yes, it usually arrives with a date or a named next step. Confidence: likely.

The question sequence. Seven of their nine questions were about your company, not your product. Read: they are still deciding whether EduNova is safe to be seen with, which is the pre-evaluation stage in a large Japanese organization. Product interest is real but secondary for now. Confidence: likely.

The silent director. He arrived late, apologized twice, asked one question (which other Asian markets you operate in), and took notes during the funding discussion. Read: he is either the internal sponsor testing the room, or risk oversight. The regional question suggests sponsor: he is imagining the internal pitch. Confidence: possible; verify in the next meeting by addressing regional expansion directly and watching who follows up.

What was avoided. Your BD lead asked twice about budget cycles. Both times the GM redirected to process generalities. Read: either the budget is not theirs to discuss, or the fiscal-year window you are assuming (April) is wrong for this division. Do not assume April. Confidence: uncertain, and worth one direct question in writing.

3. Risks I flagged

R1 (high). The October pilot proposal was made mid-meeting, before their internal alignment exists. To them this can read as pressure. Mitigation: in your follow-up, reframe October as "an example timeline, shaped around your internal schedule."

R2 (medium). No one on their side committed to anything. If your next email only says "looking forward," this deal drifts. Mitigation: give them one small, easy yes (see next moves).

R3 (low). Your CEO's joke about Japanese meetings being formal received polite laughter only from the juniors. No repair needed, but do not repeat the genre.

4. Your next moves

Within 48 hours: send the security whitepaper you promised, with a two-line cover note. Suggested wording: "Please find the whitepaper as promised. If helpful for your internal review, we can prepare a one-page Japanese summary." The offer of a Japanese summary is the small yes: easy to accept, and it tells you whether an internal review is actually happening.

By next Friday: one question, in writing, to the GM: "So that we can align with your planning, could you share how your division usually schedules new pilot evaluations?" This tests the budget-cycle read without pressure.

Before the second meeting: prepare one slide on your Southeast Asia footprint. It is for the director. If he engages with it, you have found your sponsor.

Do not: propose dates again until a process question comes from their side.

This is negotiation advisory, not legal advice. Confidential to the client. MIKATA03 works one side per deal, ever.