Start here
Better deals are designed, not just negotiated.
Deal Geometry is a practical system for designing transactions. It is for the person trying to make a deal happen: selling a solution, acquiring technology, securing a license, obtaining distribution, structuring a partnership, buying an asset, or otherwise getting something valuable from another party.
Most negotiation advice focuses on the visible, at-the-table layer: anchors, objections, concessions, persuasion, leverage, deadlines. Those techniques can matter. But much of the real intellectual work happens underneath: understanding what each side actually needs, diagnosing why the current offer is hard to accept, finding movable variables, and redesigning the exchange so both sides have a reason to say yes.
Negotiation tactics ask: “How do I negotiate this offer?”
Deal design asks: “What should I offer?”
The negotiating table is only one part of dealmaking. Much of the highest-value work is designing what gets put on the table. A well-designed offer can change the conversation entirely — from haggling over a discount to solving the real constraint underneath the objection.
That does not mean negotiation disappears. It means negotiation becomes more productive, because the thing being negotiated is closer to what the parties actually need.
Surface negotiation
Treats the variables of the deal as fixed and fights over the split. The main levers are pressure, persuasion, and concession.
Deal design
Treats the variables as movable and searches for a configuration that creates, preserves, and distributes value more effectively.
Two operating principles
“Don't negotiate the objection. Diagnose the structure underneath it.”
An objection is information about a mismatch between the offer and the other side's reality. The first move is not to concede on the variable named in the objection. It is to understand which structural problem the objection is pointing to.
“Don't just negotiate the deal in front of you. Design a better deal to put in front of them.”
The current offer is a hypothesis. Resistance is feedback. The goal is to generate a new hypothesis that fits the other side's constraints without giving away what matters to you.
The offer is the principal design object
An offer is the proposed exchange you put in front of the other side. A deal is the offer the parties ultimately accept.
In B2B and other complex transactions, an offer is far broader than product plus price. It is the complete configuration of the proposed exchange. A well-designed offer makes clear what each side will give, get, bear, risk, commit, and wait for.
The governing practical question is: “What offer should I make?”
After the other side responds, the question becomes: “What did their response teach me about how the deal should be redesigned?”
A practical point of view
Deal Geometry is used by the person trying to make a transaction happen. We study the other side's value, burden, risk, alternatives, stakeholders, constraints, and incentives because understanding those things helps us design an offer they can rationally accept while still preserving what matters to us.
This is not generic win-win negotiation. Sometimes interests conflict. Sometimes the right answer is to pay more, take more risk, accept less, or walk away. The purpose is to search for better structure before assuming the problem is zero-sum.
Promise and credibility still matter. When something is not working, do not immediately improve the persuasion; improve what you are asking the other party to say yes to.
The design cycle
Negotiation is partly an information-gathering and iterative design process. Resistance to an offer should generate information. The cycle is simple, but the discipline is not.
Step 1
Understand
What each side needs, fears, and can actually do.
Step 2
Design
What configuration of variables might make the exchange work.
Step 3
Offer
The specific proposal you put in front of the other side.
Step 4
Learn
What their response reveals about the real structure of the problem.
Step 5
Redesign
A better offer, informed by what you learned.
Step 6
Deal
The configuration both sides ultimately accept.
The loop is not always sequential. You may understand more while offering, learn more while redesigning, and return to understanding after a surprise. But the direction matters: design before concession, and learn before redesign.
“They asked for 20% off.”
A request for a price reduction is not always a price problem. Surface negotiation treats it as one. Deal design treats it as a signal.
| Diagnosis | Possible redesign |
|---|---|
| First-year budget ceiling | Ramped pricing or lower first-year fee for a longer term |
| Approval threshold | Phased scope, staged signature, or committee-ready business case |
| Implementation capacity | Seller-delivered implementation, slower rollout, or lighter initial scope |
| Uncertainty about adoption | Paid pilot with conversion criteria, success metrics, or proof milestone |
| Commitment concern | Shorter initial term with pre-priced expansion |
| Cash timing | Quarterly or milestone-based payment aligned to value realization |
None of these responses is universally superior. The right move depends on which diagnosis is true, and on what your side can afford to give. The point is that a single objection can point to several different structural problems — and each problem has a different redesign.
Surface negotiation vs. deal design
Surface negotiation
How do I resist the discount? Should I split the difference? What anchor do I set?
Deal design
Why do they need 20% off? Budget ceiling? Approval threshold? Implementation capacity? Uncertainty about adoption? Cash timing? Commitment concern? What structure solves the real problem without destroying my economics?
How this connects to the rest of the framework
The existing framework pages are tools underneath the deal-design purpose. They are not an ontology lecture; they are practical lenses and methods for doing the work described on this page.
Stress-Test the Offer
Value Creation, Value Capture, Burden, Risk, Commitment, and Timing as six lenses for testing a proposed offer before you put it on the table.
Read moreDecision Context
The alternatives, constraints, stakeholders, and approval gates that determine why the other side rejects or accepts a given structure.
Read moreDeal Moves
The movable variables in a deal — and the second-order effects that any change propagates through the structure.
Read morePareto Efficiency
The underlying economics: search for configurations that create more joint value before assuming the problem is zero-sum.
Read moreDeal Geometry Map
A working method for mapping a live deal across both sides and testing how candidate moves change the structure.
Read moreDeal Geometry Diagnostic
Apply the design lens to your stalled, lost, and heavily negotiated deals.
The Deal Geometry Diagnostic reviews a sample of recent transactions and identifies the structural issues slowing your sales cycle.