Deal design lens
Timing
A deal is not only a set of terms. It is a sequence of events.
As a design lens: is the offer hard to accept because the right things happen in the wrong order, or at the wrong time — and can sequencing solve the constraint without materially changing the ultimate economics or the objective?
The same economics at different times are not the same deal.
Two offers can carry identical totals and be, in practice, entirely different propositions. Cash that leaves in January is not cash that leaves in October. Work that lands during a change freeze is not the same work in a quiet quarter. A commitment made before proof is not the commitment made after it.
Sequence itself can create value.
This is not an argument that faster is better. Speed is sometimes the wrong objective: an accelerated start can outrun readiness, and an early decision can destroy the information that would have made it a good one. The question is fit between the sequence and both sides' circumstances, not compression.
Everything in a deal happens at a moment.
Most offers are written as a list of terms and never laid out as a timeline. Doing so is often enough on its own to expose the constraint. Ask, for each of these, when it occurs — and for whom.
Timing is not time-to-value.
Time-to-value is a real and useful relationship, and it is only one of them. Timing also governs financing, burden, commitment, information, risk, optionality, approvals, renewal and exit. A deal can deliver value quickly and still fail on timing, because the money, the work, or the irreversible decision sit in the wrong place.
A delay and a pilot may consume the same amount of calendar time. Only one necessarily produces information.
What timing does to the other lenses.
Timing and value creation
Earlier usable value is often worth more than later complete value, because it arrives while the problem still matters and while the sponsor still owns it. Smaller value sooner can beat the full solution a year out — and occasionally the reverse is true, when a partial result would discredit the whole thing.
Timing and value capture
Timing quietly allocates financing. Prepayment finances you. Net terms finance them. Milestones share the financing with progress. Deferred or ramped payments can solve a first-year budget ceiling while leaving nominal economics largely intact — but not for free: you take on credit and default exposure, your own cash flow moves, and money later is worth less than money now. Recognise which side is lending, and price it. Value Capture is where that cost shows up.
Timing and burden
Total burden can be entirely tolerable and still impossible in a specific organisational window. The same integration is routine in March and unthinkable during the year-end close. Moving work is frequently cheaper than reducing it.
Timing, risk, credibility and information
A pilot, a test, a diligence period, or a milestone can create proof before exposure. That is productive waiting: the calendar is being spent to buy something. Dead delay spends the same weeks and produces nothing, and it damages credibility rather than building it. Distinguish the two ruthlessly — see Risk.
Timing and commitment
The ultimate commitment can stay exactly as it is and simply attach later: exclusivity after launch, minimums that ramp, a purchase option exercisable after diligence, rights that widen stage by stage. Amount and moment are separate variables, and the moment is usually the cheaper one to move.
Most timing failures are synchronisation failures.
The problem is rarely that something is early or late in the abstract. It is that two clocks — yours and theirs — are running against each other, and nobody has looked at both at once.
Value after the budget is spent
The benefit lands in a year the money has already left.
Payment before funding exists
The invoice arrives ahead of the line it is supposed to hit.
Implementation during peak season
The work is affordable in total and impossible in that particular quarter.
Your capacity ahead of their readiness
You staff a team that waits, then are unavailable when they finally move.
Exclusivity before commercialisation
Rights are locked up during the period nobody is using them.
Renewal notice before usage data
They must decide to continue before the evidence of value has accumulated.
Decision before diligence
The irreversible choice is scheduled ahead of the work that would inform it.
Support withdrawn before handoff
Responsibility transfers before the receiving side can carry it.
Deal design synchronises clocks.
Organisations run on calendars, not on your pipeline.
Much of what looks like hesitation is a calendar you cannot see. These clocks belong to Decision Context, and they set what is possible before any term is negotiated.
Sometimes the answer is to move the deal to the calendar. Sometimes it is to design around it — split the value across two budget years, start with what needs no approval, or land the heavy work either side of the freeze. Which one applies is a question about their situation, not about your quarter.
Timing-oriented design moves.
Each of these changes when something happens rather than what is ultimately exchanged. That is precisely why they can resolve an objection the price could not.
Ramped pricing or payments
Matches cash outflow to the adoption curve rather than the signature date.
Deferred payment
Solves a funding window without reducing what is ultimately paid.
Milestone billing
Ties cash to observable progress, so financing is shared as the work proves out.
Phased rollout
Keeps burden inside the capacity a specific quarter actually has.
Pilot before full deployment
Buys information before exposure, rather than simply postponing the decision.
Delayed or earned exclusivity
Rights attach once commercialisation is underway instead of before it.
Ramped minimums
Obligation grows with the ability to absorb it.
Staged rights
Scope widens as each stage completes, so neither side over-grants early.
Pre-priced expansion
Removes the future renegotiation that makes a small start feel dangerous.
Implementation aligned to capacity
Schedules the heavy work when their people are actually available.
Renewal after performance data
Moves the decision point past the evidence that should drive it.
Termination window after a proof period
Prices an exit at the one moment uncertainty is genuinely resolved.
Transition period
Prevents a cliff at handoff, exit, or supplier change.
Option period
Holds a future right open without demanding a present obligation.
Escrow release on milestones
Consideration moves as the underlying condition is satisfied.
Contingent consideration
Part of the price waits for the outcome it depends on.
Staged acquisition or licence
Converts one large irreversible step into a sequence of informed ones.
Seasonal launch
Starts the deal at the moment the market, not the pipeline, is ready.
Example · Enterprise software
The right deal in the wrong quarter.
The buyer accepts the value and accepts the price. The offer nevertheless requires an annual prepayment now and an enterprise-wide rollout starting immediately. Their budget arrives next quarter and their implementation team is committed until then. Nothing about the economics is in dispute; the sequence is simply unexecutable.
Designed instead: sign now, begin with a smaller paid initial phase, align implementation with the capacity that actually exists, ramp payments so cash follows the rollout, and place the wider deployment and expansion behind a milestone. Full commitment attaches once the evidence exists.
Value Capture
Nominal totals are largely preserved; you finance part of the first year and should price that, not ignore it.
Burden
The same work, moved into a window where their people can absorb it.
Risk
Their exposure in phase one is small; yours becomes whether the expansion trigger is reached.
Commitment
The ultimate term is unchanged. It attaches after proof rather than before it.
Credibility
Willingness to start small and be measured is more persuasive than an assurance that the rollout will go fine.
Example · Technology licence
Agreed on everything except when.
Both sides agree on the rights and on the economics. Two facts block execution: the owner cannot transfer the know-how immediately, because the people who hold it are mid-project; and you will not pay full consideration before the technology has been validated in your own environment.
Staged: signing, then a documentation milestone, then limited initial rights that let you begin, then validation, then technology transfer, then milestone payments as each step completes, then broader rights and exclusivity on completion. If a milestone fails, rights revert or an option lapses rather than a dispute beginning.
The basic exchange is the same one both sides already accepted. The difference is that this version can actually be executed.
Architectural note
Timing is a stress-test lens, not a claim about the fundamental constituents of a deal.
It earns its place because sequence changes the practical meaning of everything else: the same value, economics, burden, risk, commitment and credibility are experienced differently depending on when they arrive. Timing is often the cheapest variable to move and the last one anyone examines.
Timing audit
Run this against a live offer.
- 01What are the major events in this offer, in order?
- 02When does the other side receive first meaningful value? When do they receive full value?
- 03When do they pay, incur burden, assume risk, and surrender optionality?
- 04When do you receive value, and when do you incur your own cost and exposure?
- 05Which irreversible decisions occur before the information needed to make them?
- 06Which burden lands in an organisational window where it is impossible?
- 07Are we financing the other side, or asking them to finance us, without recognising it?
- 08Which events are out of sync across the two sides?
- 09Could changing the sequence solve the objection without changing total nominal economics or ultimate commitment?
- 10Is any delay producing information or value, or is it merely dead time?
Next
That completes the current six stress-test lenses.
An offer can pass all six and still fail. Structural coherence is not acceptance: the other side decides against their alternatives, their stakeholders, their constraints, their approval path, their individual incentives, and their moment in time. That is Decision Context. You can revisit the full set under Stress-Test the Offer, or work a live transaction end to end with the Deal Geometry Map.