Practical guide
How to prepare a negotiation strategy with AI
A negotiation plan should define the organization’s objectives, alternatives, issue priorities, concession logic, evidence, and decision authority before the conversation begins. AI can organize scenarios and expose inconsistent assumptions. It should not invent the counterpart’s motives or turn speculation into a fact. Preserve a clear boundary among known information, hypotheses, and walk-away.
A negotiation plan should define the organization’s objectives, alternatives, issue priorities, concession logic, evidence, and decision authority before the conversation begins. AI can organize scenarios and expose inconsistent assumptions. It should not invent the counterpart’s motives or turn speculation into a fact. Preserve a clear boundary among known information, hypotheses, and walk-away conditions.
Establish objectives and alternatives
State the desired outcome, minimum acceptable outcome, issues that can be traded, issues that require approval, and the consequence of no agreement. Build the best available alternative from actions the organization can actually take, not an optimistic story about future options.
For each objective, record its evidence and owner. Acquisition.gov’s FAR provisions require documented prenegotiation objectives and a record of principal negotiated elements in covered federal acquisitions. That specific rule does not apply universally, but it provides a useful official example of separating objectives, supporting facts, positions, and the final agreement.
Use an issue register:
| Issue | Preferred outcome | Limit or authority | Evidence | Trade potential | |---|---|---|---|---| | Pilot scope | Two teams, synthetic work | Sponsor may approve one additional team | Capacity plan | Trade for longer schedule | | Start date | 1 October | No earlier than access approval | Review timeline | Low | | Payment timing | Half at start, half at completion | Finance approval below half upfront | Cash-flow model | Trade for term length | | Public reference | None during pilot | Founder approval required later | Claims boundary | Not pre-authorized |
The example is synthetic and does not state Two Prune’s terms or pricing.
Separate facts from counterpart hypotheses
Create three columns: confirmed fact, working hypothesis, and question to test. “Their procurement lead asked for quarterly billing” is a fact if recorded. “They care more about cash timing than total price” is a hypothesis. The negotiation plan should propose a question rather than assume the motive.
Ask AI to identify where language about the counterpart lacks a source. It may generate possible interests to explore, but label them as hypotheses. Never use sensitive personal profiling or unsupported behavioral claims.
A common failure is designing concessions around an imagined constraint. For example, offering a price reduction because the counterpart “must have a tight budget” may surrender value without learning anything. Repair the plan with evidence-seeking questions and conditional trades.
Build conditional concession packages
Rank issues by importance and cost to each side where evidence exists. Design packages that exchange value rather than making isolated concessions. Every concession needs a condition, authority, sequencing rule, and record.
A synthetic package might say: “If the start date moves to 15 October and the scope remains two teams, then payment may be split across kickoff and completion, subject to finance approval.” It links movement on one issue to another and protects unresolved authority.
Set a walk-away point for the combined agreement, not just individual issues. Describe who may change it and what new evidence would justify that change. Prepare pause language for requests outside the negotiator’s authority.
Plan the conversation and evidence capture
Sequence opening questions, issue exploration, package testing, internal caucus points, and confirmation. Identify the people who own technical, commercial, legal, security, and delivery issues. Plan how agreements will be restated and recorded.
FAR 15.406-3 lists elements for documenting covered negotiations, including purpose, participants, objectives, supporting data, significant facts, and differences between positions. Use the principle of reconstructable decisions without assuming the federal format governs another setting.
After the session, separate tentative understandings from approved terms. Record open items, owners, and expiry dates. Compare the final position with the approved strategy and explain material deviations.
Verify the negotiation plan
Before entering the discussion, confirm:
The artifact is the negotiation plan plus issue register, fact-hypothesis-question table, alternative analysis, concession packages, authority matrix, and post-session record.
- objectives and priorities have accountable owners;
- the no-agreement alternative is executable;
- facts cite evidence and hypotheses are labeled;
- questions test the most important assumptions;
- concession packages are conditional;
- limits and escalation authority are explicit;
- the combined walk-away condition is understood;
- specialist issues have specialist owners; and
- the record can reconstruct objectives, movement, and final terms.
Sources and claim map
The issues, positions, dates, and packages are synthetic. This educational workflow does not establish fair pricing, legal sufficiency, bargaining outcome, or authority for a real negotiation.
- Acquisition.gov, FAR 15.406-1 Prenegotiation objectives: supports documented negotiation objectives for covered federal acquisitions.
- Acquisition.gov, FAR 15.406-3 Documenting the negotiation: supports recording purpose, participants, objectives, evidence, significant facts, differences, and negotiated position in its scope.
Sources: [1] [2]
Sources
- 1.FAR 15.406-1 Prenegotiation objectives · U.S. Acquisition.gov
- 2.FAR 15.406-3 Documenting the negotiation · U.S. Acquisition.gov