Negotiation Preparation Brief: US Software Vendor — Japanese Manufacturing Customer Renewal 1. Situation Snapshot Supplied facts First renewal discussion following a completed pilot deployment US vendor: account director and solutions engineer Customer attendees: plant operations lead, procurement manager, IT security representative Vendor objective: 12-month renewal and phased expansion Customer stated wants: reliability evidence, clear support path, price predictability Meeting format: online, 75 minutes Customer requested agenda and implementation data in advance Interpreter may be available; not confirmed Assumptions to test That the three customer attendees collectively represent the decision-making unit for this renewal That the pilot metrics exist in a form the vendor can present That IT security review and commercial terms can proceed in parallel That the interpreter, if present, has the technical vocabulary to handle deployment and SLA terminology accurately Unknowns Who holds final budget approval and whether that person is attending Whether pilot performance meets the operations lead's standards Whether IT security review must formally close before commercial terms can be discussed or signed Interpreter availability, scope, and whether they have received materials in advance Whether additional stakeholders such as finance or senior management will review terms before any decision 2. Stakeholder and Decision Map Party Role Decision Authority Stated Interests Missing Information Account Director (US) Commercial relationship lead Can likely propose terms; confirm authorization to finalize or commit to exceptions Renewal and phased expansion Internal approval chain for non-standard terms Solutions Engineer (US) Technical and reliability evidence Advisory Demonstrate pilot outcomes Which specific metrics the customer prioritizes Plant Operations Lead Operational evaluator and daily user Not confirmed; do not infer from title Reliability, uptime, support responsiveness Satisfaction level with pilot; role in budget sign-off Procurement Manager Contract and pricing interface Possibly co-approver; confirm Price predictability, contract terms Procurement process steps and approval layers IT Security Representative Security compliance reviewer May hold gating authority over commercial timeline; confirm Security assurance and risk mitigation Whether security sign-off is a formal prerequisite before commercial terms proceed 3. Communication Design Meeting format: Online, 75 minutes. Confirm before the meeting whether all customer participants will join on video or audio only, and whether screen sharing for data review is technically supported on the customer's end. Pre-distributed materials: The customer already requested agenda and implementation data. Send both at least 48 hours before the meeting. Confirm the preferred format — slides, spreadsheet, or narrative summary — and whether a bilingual version is needed. Interpreter: Ask the customer directly and before the meeting whether an interpreter will be present. If so, confirm that the interpreter has received materials in advance, allow extended time per agenda item, avoid idiomatic or jargon-heavy language, and prepare a technical glossary of key terms as a backup reference. Pacing: After presenting each data section, pause and allow space before asking for a response. Avoid filling silence. Build in a midpoint summary check to confirm shared understanding before advancing. Turn-taking: Assign one speaker per topic on the US side to avoid cross-talk. When inviting customer input, address each representative by role rather than directing open questions to the room. Documentation: Offer to send written notes and confirmed next steps within 24 hours of the meeting. Ask in advance whether the customer prefers a formal meeting summary or a concise action-item list. Escalation: Confirm at the start of the meeting who on each side is the named contact for any question that cannot be resolved during the session and requires follow-up. 4. Negotiation Agenda # Item Purpose Owner Desired Output Transition 1 Welcome and role confirmations (5 min) Confirm attendance, roles, and shared objectives for the session Account Director Confirmation of who is present and in what capacity "Let's confirm our shared agenda for the next 70 minutes." 2 Pilot performance review (20 min) Present reliability and support data; invite the customer to assess against their expectations Solutions Engineer + Operations Lead Customer's view on whether pilot metrics meet their standards "Based on what you've shared, may we move to the support continuity question?" 3 Support and service path (15 min) Walk through support tiers, escalation paths, and SLA terms Account Director Customer questions on the support model answered and noted "With service continuity outlined, we'd like to address security readiness." 4 IT security status (10 min) Understand where the security review stands and how it affects the commercial timeline IT Security Representative + Account Director Clarity on whether security review is a precondition for commercial discussion "Thank you — that helps us sequence the next steps accurately." 5 Renewal and expansion concept (15 min) Introduce the 12-month renewal and phased expansion idea; no commitment sought Account Director Customer reaction and questions noted; open items captured "We'd like to understand your preferred path forward from here." 6 Next steps and timeline (10 min) Align on owner, action item, and date for each open question Account Director Written list of agreed next steps confirmed before close "We will send a written summary within 24 hours for your review and correction." 5. Trade-off Map Vendor Priority Customer Priority Potential Area to Explore Non-negotiable (if stated) Questions Before Proposing 12-month renewal commitment Price predictability Multi-year pricing stability in exchange for a longer commitment term None stated What contract duration does procurement prefer? Phased expansion Reliability evidence first Condition expansion milestones on agreed performance thresholds rather than time-based triggers None stated What reliability metric would satisfy the operations lead for expansion approval? Speed to renewal Security review completion Phased commercial agreement with a security-gate built into the expansion milestone None stated Must security review formally close before any commercial signature is possible? Expanded scope Clear support path Enhanced SLA or dedicated support contact included in the renewal as a structural element None stated What does "clear support path" mean specifically to the operations lead? Do not propose specific pricing structures, concession packages, or expansion timelines until budget authority, security gate status, and pilot satisfaction are clarified. 6. Clarification Questions Who holds authority to approve a renewal contract, and is that person available to review terms after this meeting? What specific metrics or outcomes from the pilot would constitute success from the operations team's perspective? Is the IT security review a formal prerequisite before commercial terms can proceed, or can both tracks run in parallel? Will an interpreter be present, and if so, should materials be provided in translated or bilingual format in advance? What is the customer's preferred timeline for completing a renewal, given any internal approval steps required? When you asked for "price predictability," does that refer to fixed annual pricing, multi-year locked rates, or something else? Are there additional stakeholders — for example in finance or senior management — who will need to review terms before a decision can be confirmed? What format works best for follow-up: a formal written proposal, a revised contract draft, or a summary of key terms first? 7. Risk and Repair Plan Risk Early Signal Repair Move Security review blocks commercial progress without either side naming it IT security representative is passive or defers questions during the renewal discussion Explicitly invite the security representative to name any conditions that would affect timing before commercial terms are explored Pilot metrics are below expectations but this is not stated directly Qualified or vague language from the operations lead; questions deferred rather than answered Pause the data review and ask: "Are there areas of performance you'd like us to address more specifically?" Budget approver is absent; meeting ends without authority on next steps Procurement manager indicates decisions require further internal review without naming a timeline or contact Ask: "What does the internal review process look like, and who should we address our follow-up to?" Interpreter is absent unexpectedly Customer asks to slow down or responses are delayed and shorter than usual Reduce pace, simplify language, and confirm after each section that the key points landed as intended US team speaks over each other or presents too quickly Customer becomes passive or stops asking questions Designate one speaker per section; build a pause after each and explicitly invite the customer to respond before moving on Customer hears "phased expansion" as commercial pressure Procurement manager raises cost concerns before reliability questions are answered Reframe expansion explicitly as optional and milestone-gated; clarify that no expansion commitment is being sought in this meeting 8. Preparation Checklist Before the meeting Send agenda and implementation data to all named customer contacts at least 48 hours in advance Confirm interpreter availability; if confirmed, share a technical glossary and allow added time per section Align internally on which data sections each US team member presents Agree on which commercial terms the account director is authorized to discuss versus escalate Prepare a clean reliability summary — uptime, support response times, incident log — in a screen-shareable format Draft a next-step template to fill in during agenda item 6 During the meeting Confirm attendance and roles at the opening; note any unexpected participants Invite each customer representative to respond after their relevant agenda section Monitor language and pacing signals and adjust in real time Do not propose specific pricing or expansion commitments before security and authority questions are clarified Record open questions with assigned owners as they arise After the meeting Send a written summary and action-item list within 24 hours for customer review Address unanswered security or performance questions with supporting documentation Debrief internally on budget authority, security gate status, and customer sentiment Communicate a proposed follow-up contact date to the customer Use this as a preparation framework and confirm material commercial, legal, regulatory, and relationship decisions with the appropriate stakeholders.