Understanding the True Cost
Consider a scenario where a business faces two proposals for identical services. The first is cheaper, while the second offers a detailed description of the work, outlines client dependencies, and explains how changes will be managed. Which is less expensive? The answer isn't straightforward. The real cost lies in understanding who bears the gap between promised and actual work. This gap often leads to future conflicts, despite initial satisfaction from both parties.
Clarity Before Compelling
A simple rule should guide proposal writing: make the commitment clear before making it irresistible. While price is a natural discussion point, focusing solely on it can lead to misunderstandings. One party might believe they've secured continuous availability, while the other thinks they've sold a limited intervention. Such discrepancies often surface during execution, leading to disputes.
The Seller's Perspective
Sellers might fear that detailing limitations weakens their proposal. While it might dampen initial enthusiasm, it doesn't necessarily harm the deal. Instead, it prevents unrealistic expectations that could damage the relationship later. Building trust on an impossible promise is costlier than the clarity that prevents its formation. Selling well includes safeguarding the relationship from the moment the presentation ends.
The Buyer's Responsibility
Buyers also have a role in ensuring clarity. If they can't specify who validates results, provides information, or decides on changes, they transfer uncertainty to the seller. This uncertainty can affect price, timeline, or lead to conflict. To demand precision from the other party, buyers must offer clarity about their own processes. Negotiation isn't about shifting responsibilities onto the other side.
Discussing the Desired Outcome
The first discussion should focus on the desired outcome. What changes are needed in operations? An implementation might deliver a functional tool without ensuring its use by the entire team. Training might impart skills without addressing the lack of time to apply them. It's crucial to distinguish what the supplier delivers from what depends on the client's future decisions. Otherwise, one party might be charged for a result requiring both parties' intervention.
Execution Conditions
The second discussion revolves around execution conditions. What access, personnel, materials, or decisions are necessary? Dependencies shouldn't become preemptive excuses but should be visible. If a validation is delayed, who reorganizes the schedule and communicates the impact? The goal is to prevent known issues from circulating without ownership, while everyone continues to repeat the original timeline.
Handling Deviations
The third discussion addresses how to handle deviations. No proposal can anticipate every situation, but it can establish how changes will be analyzed, who can accept them, and when the commitment should be reviewed. This mechanism is more useful than vague statements of flexibility. A relationship's flexibility is also measured by the ability to change without forcing one party to pretend the change was cost-free.
Balancing Detail and Simplicity
A legitimate concern is that excessive detail can delay simple purchases. I agree. A small, repeated order doesn't need the same level of detail as a company integration. The depth of detail should match the proposal's scope. The error lies not in using a brief proposal but in using brevity to leave unanswered questions that could compromise the work. A clear page can be better than a lengthy document that merely repeats qualifications and promises.
Practical Risk Calibration
A practical way to gauge the necessary detail is to consider what would be difficult to reverse after starting. If the client needs to halt operations, train staff, or commit to third parties, the proposal should explain these transitions. If the supplier needs to reserve capacity or purchase specific materials, this dependency is also relevant. The risk discussion should begin where change stops being a simple exchange of messages.
Ensuring Seamless Transition
I don't suggest turning the meeting into a reading of terms. It can start with a concrete scenario: if necessary information isn't available, how do we proceed? The response reveals both parties' maturity. Some clients prefer to resolve issues later, while some suppliers accept any scenario to close a deal. In such cases, a seemingly good deal might just delay recognizing an incompatibility that would be cheaper to address while choices remain open.
Bridging Negotiation and Execution
As the deal progresses, the negotiation's content must transition from the commercial team to the execution team. It's not enough to pass on the final price. It's crucial to convey what was included, what changed, which doubts remain, and why the client prioritizes certain aspects. The service deliverer shouldn't discover, through complaints, that a commercial conversation created an expectation they were unaware of.
Operationalizing Agreements
The same applies to the buyer's side. Those who negotiated must explain the commitment to those involved in the work. If one manager accepts a timeline and another withholds necessary information, the issue isn't blaming the supplier for lack of initiative. An agreement only becomes operational when relevant responsibilities reach those capable of fulfilling them. A signature closes a phase; it doesn't automatically distribute understanding.
Learning from Delivery
After the first delivery, compare the work done with the initial promise. Repeated doubts should improve the next proposal. This exercise allows learning without blaming the client or commercial team entirely. There are execution failures, legitimate changes, and poorly designed offers. Mixing these prevents the company from correcting what it controls and leads to repeated discounts to compensate for problems not caused by the price.
The Essence of a Good Proposal
The best proposal isn't one that eliminates all risks, as that would be an insincere promise. It's one that allows parties to recognize the commitment they're making, discuss its conditions, and know how to act when reality demands a revision. A good deal leaves room for execution. If commercial enthusiasm consumes this room before it begins, someone will have to pay the difference. I prefer that conversation happens while we're still at the table.