Skip to main content
Steady at the Top
← All articles

How to stop a closed deal becoming a delivery dispute

A closed deal needs a delivery team that understands what the buyer believes it bought. Before celebrating the signature, compare the negotiated terms, sales conversations, and implementation plan. Resolve consequential gaps with the customer and the people authorized to change the agreement.

A psychological contract is an individual’s understanding of reciprocal obligations in an exchange. Denise Rousseau and Judi McLean Parks discuss those beliefs in their 1993 review, The Contracts of Individuals and Organizations. Their organizational research helps explain why two people can experience different commitments. Applying that lens to a buyer’s expectations is an advisory extension, not a finding that this handoff procedure prevents disputes.

An expectation and an enforceable obligation require different assessments. Counsel should evaluate contractual questions. Delivery leaders must also understand expectations that could undermine adoption, even when their legal status remains unresolved. You need a documented answer to both questions before assigning work.

The promise travels through several conversations

An enterprise buyer may hear a capability described during discovery, see a simplified demonstration, and negotiate a statement of work with different people. Implementation receives a project summary after signature. Each document can be accurate within its narrow purpose while the overall picture remains incomplete.

Suppose a hypothetical customer expects the supplier to migrate historical data. The statement of work assigns data preparation to the customer. A sales demonstration showed a clean dataset but did not establish who would clean the real files. The implementation manager can follow the document and still surprise the buyer.

The useful question is which communication produced the expectation and what an authorized person can now offer. Calling the customer unreasonable will not produce usable files. Asking delivery to absorb unlimited preparation may create another promise the company cannot fulfill.

The broader negotiation and pricing guide connects these commitments to commercial choices. A handoff should carry those choices forward, including the trade-offs that made the final package feasible.

When the celebration becomes another work evening

Consider a composite founder who returns home after closing a long enterprise deal. Dinner begins with relief. Then implementation asks whether sales promised a capability missing from the project brief. The founder leaves the table to search messages and reconstruct a conversation from weeks earlier.

The interruption has a concrete cause: nobody reconciled the buyer’s intended result with the resources assigned to deliver it. More reassurance at home cannot answer that question. A practical repair starts with the messages, demonstration notes, proposed scope, and final agreement.

Avoid forwarding the entire archive without interpretation. The delivery manager needs the disputed commitment, its source, its current status, and the person who can resolve it. Unfiltered volume can conceal the very issue that caused the interruption.

Use a joint deal-commitment review

The joint deal-commitment review is a proposed operating method for sales, delivery, and the customer. It combines a commitment record with a short confirmation conversation. It has not been validated as a complete intervention.

Schedule it before final commitment whenever possible. If the agreement is already signed, use the review to identify discrepancies and authorized remedies. Do not describe an unsigned worksheet as a revision to signed terms.

1. Reconstruct the commitments that affect delivery

Start with the signed documents and their version history. Add sales statements that could affect functionality, timing, migration, training, security, support, or customer effort. Record who made each statement and where it appears.

Distinguish an agreed deliverable from a forecast, demonstration assumption, and unanswered request. “We usually finish quickly” needs clarification if the buyer planned a launch around it. Do not silently convert that sentence into a guaranteed delivery date.

Ask the account owner to identify the buyer’s most consequential expectation in plain language. Compare that answer with the project manager’s understanding. A mismatch at this stage is a reason to investigate, not evidence of dishonesty.

2. Translate each expectation into observable work

For every consequential commitment, identify the required input, supplier activity, customer activity, acceptance condition, and dependency. Explain the boundary using the actual workflow rather than an internal product label.

In the migration example, identify who extracts records, corrects errors, maps fields, approves the sample, and handles rejected rows. Specify what happens when the supplied data does not meet the agreed condition.

Delivery should estimate effort before the company offers an accommodation. A salesperson’s desire to protect the relationship does not establish capacity. Likewise, an implementation team’s customary process does not automatically answer what this particular customer was promised.

3. Resolve gaps through authorized decisions

List discrepancies without assigning a verdict prematurely. One row may concern ambiguous wording; another may reveal a missing resource or an unsupported sales assurance. Each requires a different response.

Bring the appropriate commercial, delivery, and legal decision makers into material scope questions. They might clarify existing terms, propose a documented change, adjust timing by agreement, or explain why a requested outcome is unavailable.

Before signing, a credible alternative can help the company resist a delivery promise it cannot honor. Prepare that alternative explicitly. After signing, an attractive alternative does not release the company from its existing obligations. Obtain legal advice before changing performance.

4. Confirm the shared account with the customer

Describe the practical plan and ask the buyer to explain what its team will do. A general “Are we aligned?” often produces a polite answer without exposing a dependency.

Use a focused question: “Who on your side will prepare the source data, and what date can that team support?” If the buyer expected supplier preparation, the misunderstanding becomes visible before a missed milestone.

For complicated discrepancies, move the discussion out of email. Follow the conversation with an accurate written record through the appropriate agreement process. A meeting itself does not resolve an unapproved change.

5. Transfer ownership with the unresolved items attached

Give delivery a named commercial contact and a decision route for exceptions. Mark each open issue with its consequence, next action, owner, and required decision date.

The account owner should remain involved until material expectation gaps have a disposition. A handoff is incomplete when implementation has inherited a question but lacks access to the person who can answer it.

At the first delivery review, compare actual customer inputs and supplier activity with the confirmed plan. Escalate a failed assumption while options remain available. Do not wait for the customer to turn the discrepancy into a complaint.

A conversation that exposes the migration gap

A useful opening could be:

“Before kickoff, I want to check the work behind the migration promise. Our implementation plan has your team preparing the source files. You may have understood that we would do that preparation. Can we compare the relevant conversations and agree on the authorized next step?”

This opening identifies the discrepancy without declaring which account is legally decisive. The salesperson should then produce the relevant record. The delivery lead should explain the work and capacity involved. The buyer should have room to describe its understanding without being pressed to endorse the supplier’s version.

Suppose the review confirms that the customer cannot prepare the data on the proposed schedule. The company might offer a scoped preparation service, investigate another delivery sequence, or review responsibility with counsel. Each option needs its own feasibility and approval check.

Do not close the meeting with “We will make it work” unless the company has approved a concrete commitment. That phrase can recreate the original gap immediately.

Separate fairness arguments from the delivery record

Thompson and Loewenstein’s 1992 bargaining research examines self-serving interpretations of fairness. It gives a reason to inspect each side’s account carefully. It does not determine the fair scope or price of this deal.

Sales may remember the flexibility needed to win. Delivery may remember the warnings about capacity. The customer may remember the demonstration and the business outcome. Those memories can supply useful evidence, but none should replace the actual messages and agreement.

Ask each participant to identify the strongest record supporting the other account. This is an operating choice for the review, not a tested component of the cited study. If disagreement persists, document the competing interpretations and assign their resolution to the proper authority.

Judge the handoff by what delivery can use

A complete file can still be unusable. Sample one important deliverable and ask the implementation owner to explain its acceptance condition, dependencies, escalation contact, and commercial boundary. Then compare that explanation with the buyer’s.

Watch for work that falls between teams. Customer training may exist in the contract but lack a scheduled trainer. A security review may have an owner but no access to the buyer’s system. These are delivery gaps even when nobody disputes the commercial wording.

Repairing cross-functional trust becomes necessary when repeated transfers have taught departments to expect hidden promises. Begin with visible commitment records and reliable exception handling. Asking teams to trust one another cannot substitute for answering a specific unresolved obligation.

Keep the record alive through the first milestone

At the next milestone, review the commitments most likely to have changed. Record whether the customer supplied the expected inputs, whether delivery met its part, and whether an approved change altered the plan.

If the same kind of misunderstanding recurs, revise the sales proposal, demonstration language, or approval process that produces it. Adding another handoff meeting will have limited value if the originating promise remains vague.

The result you want is a delivery owner who can act and a customer who recognizes the plan. A signature starts that responsibility. The commitment review gives the company a practical way to carry it into implementation.

The customer-facing schedule should identify the version of the commitment record it uses. When someone updates that schedule, check whether the change also requires commercial approval or a revised customer responsibility.

Sources

Steady at the Top