Deal design lens
Value Creation
The Promise says what future state you are proposing. Value Creation asks how much that state is actually worth to the other side — and what the exchange is worth to you.
This is one lens for stress-testing an offer, not a stage in a process and not a category every deal must be sorted into. Use it when you need to know whether there is enough at stake to move anyone.
Promise proposes. Value evaluates.
Promise describes the change your offer commits to produce. Value Creation asks a different question: how significant would that change be to the party being asked to act, and what does the whole exchange produce for you?
Keeping these apart matters because they fail differently, and the repair is different in each case.
A promise can be clear, credible, and still not valuable enough to cause action.
The reverse also happens: a genuinely valuable outcome goes nowhere because the promise attached to it is vague, unscoped, or aimed at a condition the other side does not care much about. One is a value problem. The other is a promise problem. Improving the language will not fix the first.
The questions this lens asks
- 01
What becomes better for the other side if they accept?
- 02
How important is that improvement to them now?
- 03
What becomes better for you if the deal happens?
- 04
Is enough value created to justify the price, burden, risk, commitment, and delay the exchange requires?
- 05
Is there latent value a change in structure could create, rather than simply moving economics around?
There is no single amount of value in a deal
Value is party-relative. The same right, asset, service, guarantee, or commitment can be decisive for one party and marginal for another. A field you will never enter can be the most important thing on the table for the owner of the technology.
That asymmetry is not an inconvenience to be averaged away. It is usually where the good deal moves come from: something cheap for you to give that is expensive for them to obtain elsewhere, and the reverse.
Importance sets the ceiling
Start with what the other side is actually trying to achieve, not with what you are proposing. If their underlying problem were fully solved, or their objective fully achieved, how much would that be worth to them?
That question sets an upper bound. A minor issue puts a low ceiling on value no matter how well designed the offer is. And the objective is not always a problem: they may be after upside, access, strategic optionality, control, liquidity, retained rights, or removal of a risk they are carrying.
Can this structure actually produce the value?
A second ceiling sits under the first. Whatever the stakes, is the mechanism or structure you are proposing capable of producing the state they want?
In a technology sale this often shows up as category adequacy: some categories of solution are structurally able to address only part of a problem, and the best product in an inadequate category still creates limited value. In a licensing or acquisition transaction the same test applies to structure rather than product — whether the rights, field definition, exclusivity, retained control, or economic participation you are offering actually produce what the other side is after.
"Best in category" and "capable of producing the required outcome" are different claims. Only the second one determines how much value is available.
Outcome shape
Two offers can propose the same nominal result and be worth very different amounts. These are ways of inspecting how valuable the promised state would be if it actually arrived. Scoping the promise itself is a separate job, handled under Promise.
Magnitude
How large the improvement is relative to their current condition and to what obtaining it costs them.
Completeness
How much of the job the proposed state actually finishes, and what remains unresolved afterwards.
Fit
How well it matches their actual situation, data, workflow, market, or rights position rather than a generic case.
Quality
Whether it is good enough to be relied on for the decisions and processes that would depend on it.
Durability
Whether it persists, or decays as conditions, staff, systems, or markets change.
Reliability
Whether it arrives consistently rather than occasionally, across teams, periods, and edge cases.
Speed
How quickly the improvement begins to appear. Sequencing of cash, obligations, and risk belongs under Timing.
Value takes several forms
These overlap, and one transaction usually creates value in more than one of them. Translating value into money can help a committee decide, but value does not have to be monetized to be real or to drive a decision.
Economic
Revenue, margin, cost reduction, productivity, avoided losses, liquidity, cash timing.
Operational
Capacity, reliability, speed, simplicity, reduced workload, supply certainty, better process.
Strategic
Market access, distribution, positioning, new capability, learning, entry into a field they cannot reach alone.
Risk reduction
Lower probability or severity of adverse outcomes, less uncertainty, reduced compliance or operational exposure.
Optionality, control, and access
Retained rights, retained fields, reversion, participation in upside, decision rights, the ability to change course later.
Organizational and personal
Visibility, coordination, standardization, credit, career-relevant wins for the individuals who must sponsor the deal.
Creating value is not dividing it
Value Creation asks how much is available from doing the deal at all. Value Capture asks how that value and the economics around it get distributed and retained.
A discount changes capture, not creation: the same value, differently split. A structural move can do more than that. Giving a technology owner a royalty and a retained field may create upside and control they value highly while costing you far less than a larger cash number. Phasing implementation may reduce wasted effort and bring usable value forward for both sides.
Before fighting over how to divide the value, ask whether the structure can create more of it.
Asymmetric value is the design opportunity
Deal design gets interesting the moment the two sides value the same variable differently. Each difference is raw material for a move — though not every asymmetry produces a change both sides prefer, and some are simply not worth trading.
You care little about payment timing; they care a great deal about first-year cash.
They care about field rights you have no intention of using.
You value exclusivity highly; they value a guaranteed minimum volume more.
They value attribution or a public reference that costs you almost nothing.
You value speed of close; they value certainty of performance.
Value created is not value realized
An offer can carry substantial value that never arrives. Implementation, adoption, dependencies, elapsed time, exposure to downside, or simple disbelief can all stop it.
The distinction is worth keeping because it tells you which part of the offer to redesign. If the value is real but blocked, the repair is in Burden, Risk, Commitment, Timing, or Credibility. If there was never much value to begin with, none of those will help.
The other side is rarely a single mind
Organizations contain people and functions with different incentives, different workloads, different exposure, and different alternatives. Value is distributed unevenly among them, and so is cost.
A transaction can create real enterprise-level value and still fail because the person able to block it gains little and absorbs a disproportionate share of the work or the risk. That is a structural property of the offer, not a persuasion problem — and it is usually diagnosed under Decision Context.
The value created for you
Half of this lens points at yourself. Why do you want this transaction? Revenue is one answer, and often not the most important one.
This is not bookkeeping. If you cannot state what the deal is worth to you and in what form, you cannot know what you are able to trade away cheaply and what has to be preserved at all costs — which means every concession becomes a guess.
Example — a savings claim
"$2M a year in savings" is a starting point, not a conclusion
You are proposing an analytics platform and the case rests on $2M of annual savings. Before that number means anything to the person who has to approve it:
- Importance. How large and how strategic is the underlying spend problem for them this year? That is the ceiling.
- Completeness. The platform touches perhaps 60% of the relevant spend base, which bounds the claim immediately.
- Structure adequacy. It produces insight; it does not execute the changes that generate the savings. On its own the mechanism may be incapable of delivering the full outcome.
- Fit and reliability. Savings depend on several business units with different data and different incentives.
- Realization. Deployment takes time, so year one is well below the steady-state figure — which is also when they pay the most.
None of this yields a score. It tells you how much value is genuinely available, and which parts of the offer have to change to reach it. If the honest answer is a first-year improvement well under the first-year price, that is a value problem, and discounting will not solve it — but changing when they pay, or how much they deploy first, might.
Example — licensing technology you do not own
Creating value for an owner who does not want to sell
You want rights to a proprietary process. The owner has declined a straightforward purchase. Raising the cash number is a capture move: it redistributes, and it may not touch the reason they said no.
Ask what would actually become better for them. They may want continued participation in a field they still believe in, protection against enabling a competitor, evidence the technology works in a demanding application, or income without spending their own capital.
- A field-of-use limit creates value by preserving the markets they care about — at no cost to you if you never intended to enter them.
- A royalty or upside participation gives them exposure to a success they think is likely, which can be worth more to them than the cash it replaces.
- Milestones and reversion reduce the risk that the rights sit unused, which is often the real objection.
- Retained control over specific decisions can be worth a great deal to a founder and cost you very little in practice.
Each of these creates value that a higher price does not. None is universally correct; which one matters depends entirely on what the owner is protecting.
A value audit for a live offer
Run this against an offer you are about to put on the table, or one that has stalled.
What future state does the offer promise them?
How important is that state to them now?
What forms of value does it create for them, and what forms for you?
What limits the magnitude, completeness, fit, or durability of that value?
Who inside their organization gains, and who bears the cost or downside?
What value is currently missing because of how the offer is structured?
Which variable could create value cheaply for one side?
Are we trying to solve a value-creation problem with a value-capture concession?
A note on the framework
Value Creation earns its place as a stress-test lens, not as a claim that every transaction decomposes into a fixed set of dimensions. Promise now owns the definition of the proposed future state. Value Creation owns the question of how much that state, and the exchange around it, matter to each party.
That separation removes duplication that had crept in, and it makes the diagnosis sharper: a weak promise and an unimportant outcome look similar from the outside and call for entirely different repairs.
Next
Once you know how much value the deal can create, the next question is who keeps it.
Take the audit above to a live offer, then continue to Value Capture — or work a whole transaction end to end with the Deal Geometry Map.