Framework · The action layer

Deal Moves

A Deal Move is a structural change to the offer made for a reason.

The offer is the design object. Promise and Credibility set out what you propose and why it should be believed. The six lenses stress-test the structure. Decision Context describes the environment the offer has to survive. Deal Moves are what you do about what those tell you: deliberate transformations of the exchange, aimed at a diagnosed constraint.

Working definition

A Deal Move changes one or more variables in the proposed exchange in order to solve a specific acceptance or economics problem.

Not a trick, not a script, not a stock response to a stock objection. You are trying to get the other side to accept an offer while preserving what matters to you, and the instrument you have is the structure of the deal itself.

Order of operations

Diagnose first. Move second.

Do not negotiate the objection. Redesign the structure underneath it. The named objection is not necessarily the variable you should change.

Three things that are not the same

Deal Moves are frequently confused with tactics and with concessions. The distinction is practical, not moral.

Negotiation tactic

How you communicate: what you anchor on, what you concede and when, how you sequence asks, how you respond to pressure. Tactics change the conversation. They do not change the deal.

Concession

You give the other side more on a variable, usually at your own expense, without changing the shape of the exchange. Sometimes exactly right. Sometimes the fastest way to pay for a problem you have not diagnosed.

Deal Move

You change the configuration of the exchange to address the constraint that is actually blocking acceptance. A concession counts as a Deal Move when diagnosis says that variable genuinely has to move.

Nothing here says conceding is weak. Sometimes the constraint really is price and the cheapest route through is to lower it. The failure is reaching for that first, before you know which variable is actually blocking the deal.

Every move is a hypothesis

You rarely know the other side's real constraint. You have their words, their behaviour, and inference. So a move is not a solution — it is a causal claim you are testing: if we change this part of the offer, will the real constraint move enough to make the transaction possible?

A hypothesis, written out

"They are not resisting the $300K. They are resisting paying it before implementation risk is resolved. If payment sits behind a milestone, acceptance should improve without reducing total nominal price."

That claim is falsifiable. If they accept the milestone structure, the diagnosis was probably right. If they still push on the number, it was not — and you have learned something a discount would have hidden.

This is the loop the whole framework runs on: design, offer, learn, redesign. Their response is the most reliable information you will get, and it only arrives if the move you made was specific enough to be wrong.

The working sequence

Most of the value sits in steps three and six — the two most often skipped.

1 · Current offer

State what is on the table now: price, scope, sequence, commitment, risk allocation, who carries the work.

2 · Trigger

What actually happened? An objection, a stalled approval, silence, a competing bid, a legal redline, a budget freeze. Record the words used.

3 · Diagnose the constraint

Run the trigger through Decision Context and the six lenses. The named objection is a symptom. What underneath it makes yes hard or impossible?

4 · Select the variable

Which part of the exchange, if it changed, would relieve that constraint most cheaply for you?

5 · Form the move

Write down precisely what changes. Not 'be more flexible' — the new term, the new sequence, the new allocation.

6 · Trace propagation

Follow the change through every lens and through the other side's approval path. What else moves because of this?

7 · Re-test acceptance

Does the new configuration solve their real problem, and does it survive the people who must sign it?

8 · Re-test your side

Is the resulting deal still worth doing on value, risk, burden, capacity and precedent?

9 · Offer and read the response

Their reaction is data. It confirms your hypothesis, corrects it, or reveals a constraint you had not seen.

10 · Iterate, abandon, or stop

Refine the move, replace it with a different one, or conclude there is no deal here worth designing.

No variable moves alone

A discount changes value capture, and often positioning and credibility with it. A pilot changes timing, burden, risk, commitment, credibility and economics at once. Termination flexibility reduces their commitment and risk while reducing your forecast certainty and the quality of the revenue. Exclusivity can raise value for one side while raising commitment and opportunity cost for the other.

Rule

A move that solves one objection by quietly breaking three other parts of the deal is not a good move.

Trace every candidate move through the six lenses, through Credibility, and through the approval path on the other side before you put it on the table. Propagation is where deals are actually won and lost.

Families of moves

Organised by the problem they solve rather than by legal category. Not exhaustive and not mutually exclusive — a strong move usually touches several families at once.

Change the economics

Price, discount, payment timing, ramps, prepayment, royalties, revenue share, contingent consideration, credits, minimums, volume tiers.

Price is one variable among many, not the default move. Most price objections are objections to when money moves, to what the money is buying, or to the risk attached to it.

Change the scope

Narrower initial scope, modular scope, phased deliverables, field or territory limits, retained rights, carve-outs, standard versus custom configuration.

Reducing what is bought is not the same as reducing what it is worth. Scope moves change the size of the problem being solved rather than the price of solving it.

Change the sequence

Pilot, phased rollout, milestone gates, staged rights, delayed exclusivity, ramped minimums, an option before an acquisition, proof before full commitment.

Sequence moves buy information. They work when the blocker is uncertainty that time and evidence can resolve, and fail when the blocker is economics.

Change the commitment

Shorter initial term with a pre-priced extension, termination rights or fees, minimums, exclusivity earned by performance, reversion, capacity reservation, renewal options.

Commitment is a currency. Someone is always paying for the flexibility that gets added, usually in price or certainty.

Change the risk

Warranties, guarantees, service credits, liability caps, insurance, acceptance criteria, rollback rights, escrow, holdbacks, contingent payments, responsibility aligned with control.

The cheapest risk moves put each exposure with the party that controls it. The expensive ones move exposure to whoever has the weakest negotiating position that week.

Change the burden

Managed implementation, migration support, standard integrations, a prepared diligence pack, named resources, training, fewer internal dependencies, narrower customisation.

Burden moves are often the least expensive way to unlock a yes, because the work usually costs you far less than it costs them.

Change the proof

Demonstrations, tests, references, benchmarks, diligence access, transparent mechanism, measurable outputs, milestones tied to evidence.

Some of these change Credibility and context more than they change terms. They still count as design moves when they are embedded in the offer or the process rather than added to the pitch.

Change the mechanism

Sale to licence; exclusive to field-limited; purchase to option; fixed fee to royalty; vendor relationship to partnership or joint venture; build-or-buy to a hybrid.

Usually the highest-order move available, because it changes the form of the transaction rather than its settings. Reach for it when the settings cannot be made to work.

Change the comparison

Bundle work that is genuinely better done together, differentiate rights or service or structure, reframe against the real cost of the status quo, remove handoffs and dependencies the alternative leaves behind.

This must be fact-based. Changing what the offer actually contains changes the comparison. Changing only how it is described does not.

Give and get

When a move costs you something real, ask whether it can return something valuable. Not as a reflex, and not as tit-for-tat bookkeeping — the point is to search for asymmetry. Some things are cheap for one side to give and expensive for the other to obtain elsewhere. Those pairings are where structure creates value instead of moving it around.

Lower price

for Longer term or an earlier start

Payment flexibility

for Volume certainty or a minimum

Exclusivity

for Performance minimums and milestones

Broader rights

for Higher economics or a royalty on the upside

Managed implementation

for Standardised scope and a reference

Termination right

for A higher rate or a break fee

If nothing useful comes back, the move can still be right. Demanding reciprocity for its own sake is a habit, not a discipline.

Moves versus packages

Instead of arguing over one offer, construct two or three coherent configurations that solve the same objective differently and are comparably attractive to you. Which one they pick tells you what they actually value — something no amount of questioning reliably reveals. It also stops the conversation collapsing into a single-variable haggle over price.

Option A · Flexibility priced in

Higher annual price, twelve-month term, termination for convenience with notice. They buy the right to leave; you are paid for the revenue quality you give up.

Option B · Commitment priced in

Lower annual price, thirty-six-month term, annual uplift fixed at signature. They pay less per year and give up the option to reprice later.

Option C · Scope traded for delivery

Mid price, standard configuration only, implementation fully managed by you. They give up customisation and get speed and a lower internal workload.

Every option must be one you would genuinely sign and one that hangs together as a structure. Decoys are a sales gimmick, and a sophisticated counterparty will read them as one.

Worked example · Enterprise software

Current offer: $300K per year, three-year term, annual prepayment, enterprise-wide rollout. The response: "Too expensive. We need twenty percent off."

That sentence is compatible with at least four different constraints, each pointing at a different move.

Budget timing

The total is fine; this fiscal year is not. Move: ramp to $200K / $325K / $375K across the term, or defer the first payment to the next budget period. Nominal value preserved.

Implementation uncertainty

They doubt it will work in their environment. Move: paid ninety-day pilot with written success criteria and a pre-priced expansion to the full rollout. Price per seat unchanged.

Competitor benchmark

Procurement holds a cheaper quote. Move: differentiate what is actually being bought — managed migration, named team, service credits — or, if the offering really is commoditised, move price and stop pretending otherwise.

Commitment discomfort

Three years is the problem, not the number. Move: twelve-month initial term at $340K with a pre-priced twenty-four-month extension. Lower commitment, higher economics.

Pick one and trace it

Suppose the evidence points at implementation uncertainty: the sponsor has been burned by a failed rollout, and the security review keeps returning to deployment risk rather than to cost. The move is the paid pilot with a pre-priced expansion. Here is what it does to the rest of the deal.

Value creation

Unchanged in substance; a pilot narrows the initial surface but not the eventual result.

Value capture

Total nominal contract value preserved; recognition and cash move later. Expansion economics fixed now, not renegotiated later.

Burden

Rises for you — pilot scoping, success criteria, a second approval cycle. Falls for them.

Risk

Their performance risk falls sharply. Your risk shifts to the pilot failing on criteria you agreed to.

Commitment

Their initial commitment falls; the pre-priced expansion preserves your path to the full deal.

Timing

Full capture is pushed out one quarter. Information arrives earlier, which is what makes the larger commitment possible.

Credibility

Improves: you are willing to be measured. Only if the criteria are specific.

Decision context

A $75K pilot may clear a delegated authority the $300K commitment could not, changing who has to approve it.

The move remains a hypothesis. If they accept the pilot readily, deployment risk was the constraint. If they accept it but immediately reopen the expansion price, the constraint was economics all along and you have spent a quarter finding out.

Worked example · Technology rights

You want to acquire a technology outright. The owner refuses to sell at any price you would pay. More cash has not moved them, which is the signal that cash is not the constraint.

Diagnosis

What they are protecting is future upside and control over how the technology develops in the fields they care about. An outright sale asks them to surrender both, permanently, in exchange for a number set today under uncertainty.

The move · Change the mechanism

Purchase becomes a field-limited exclusive licence: an upfront payment, a royalty on commercialised revenue, exclusivity confined to your fields of use, commercialisation milestones you must hit, and reversion of the rights if you do not.

What they get

Retained ownership, continued upside through the royalty, freedom in other fields, and protection against the technology being shelved.

What they give

Exclusivity where it matters to you, and a commitment to work with a single partner in those fields.

Your value capture

Lower upfront cost, economics that scale with success rather than with a valuation argument, and no need to win a price debate about an unknowable future.

Your commitment

Milestones you must actually hit. This is a real obligation, and the reversion clause makes it enforceable.

Risk

Reallocated toward the party that controls each outcome: they carry technology continuity, you carry commercialisation.

Timing

The transaction closes sooner because the hardest question — what is the future worth — is deferred into the royalty rather than settled upfront.

Credibility

Accepting milestones and reversion is costly for you, which is precisely why it is believable.

This can outperform simply raising the cash offer, because more cash pays for something they have decided not to sell. Changing the mechanism changes what is being sold.

The move card

One structure per card. Writing it out is the discipline — it forces the hypothesis into the open and makes the second-order effects impossible to skip.

Current offer

The configuration on the table today.

Observed trigger

What was said or done, in their words.

Hypothesised constraint

The underlying reason the current structure cannot be accepted.

Evidence and unknowns

What supports the hypothesis, and what you are still guessing.

Proposed structural change

Exactly what changes, stated as a term.

Variables changed

Which parts of the exchange move, and in which direction.

Why it should help them

The causal claim about their constraint.

Cost and value to you

Economics, risk, burden, capacity, precedent.

Second-order effects

What else moves across the lenses and across their approval path.

What you receive or preserve

The return, if the move is costly.

Confirming and disconfirming responses

What their reaction would tell you either way.

Boundary

The point at which you stop redesigning.

When not to move

Not every deal should be redesigned until it closes. A framework that can only generate more moves eventually becomes a concession engine with better vocabulary.

The value available to them is genuinely below your minimum economics, and no configuration changes that.
Their constraint is immovable — a policy, a regulator, an incumbent contract, a decision already made elsewhere.
No feasible zone exists: everything acceptable to them is unacceptable to you.
The risk they need you to absorb is unbounded or cannot be priced.
The move sets a precedent, or consumes capacity, you cannot afford to repeat.
What they are actually trying to achieve is not something you can provide.
The transaction is simply not worth the cost of winning it.

Principle

Knowing which deals to stop designing is part of the design skill.

Deal Move audit

Twelve questions to run before a move goes on the table.

What exactly happened that tells you the current offer is not working?

What underlying constraint best explains it?

What evidence supports that diagnosis, and what are you guessing?

Which variable could relieve that constraint most cheaply?

Are you changing the named objection or the causal variable?

What else changes when you make this move?

Does it improve acceptance enough to matter?

What does it cost you in value, risk, burden, commitment, timing, capacity or precedent?

Can you get something valuable in return for something costly you give?

Is there another coherent configuration that solves the same problem better?

What response would tell you the hypothesis was wrong?

Is there actually a deal here, or should you stop redesigning and walk away?

Moves are transformations applied after diagnosis, not another lens. They need somewhere to be worked out.

The Deal Geometry Map is that workspace: the offer, the decision context, the friction the lenses expose, the candidate moves and their propagation, laid out together so a live deal can be redesigned rather than argued over. If you want the underlying objective a good move is reaching for, that sits in Pareto Efficiency.

Continue to the Deal Geometry Map