Understanding the Core of Proposals
Imagine a scenario where a company is presented with two proposals for the same service. One is cheaper, while the other offers a more detailed description of the work, outlines client dependencies, and explains how changes will be managed. The question arises: which is truly less expensive? The answer lies in understanding who bears the cost of any discrepancies between what was promised and what will actually be required. This gap often sets the stage for future conflicts, even if both parties leave the negotiation table satisfied.
The Importance of Clarity Over Price
A simple rule I advocate is that a proposal should first make the commitment clear before making it appealing. While price is an important factor, focusing solely on it can lead to misunderstandings. One party may believe they have purchased continuous availability, while the other thinks they have sold a limited intervention. This misalignment often becomes apparent during execution, leading to disputes.
Defining Expectations Clearly
Consider a hypothetical situation where a maintenance provider promises rapid response to a network's requests. The buyer interprets 'rapid' as immediate resolution, while the provider considers it the initial response. When a unit fails, the contract turns into a debate over definitions. Before negotiating further discounts, it would be more beneficial to clarify what happens from the moment a problem is reported to the potential intervention.
Selling with Transparency
Sellers may fear that detailing limitations could weaken their proposal's appeal. While it might dampen initial enthusiasm, it doesn't necessarily harm the deal. Instead, it removes expectations that the operation cannot fulfill. 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.
Buyer's Role in Clarifying Responsibilities
Buyers also have a role in ensuring clarity. If they cannot specify who validates results, who provides information, and who decides on changes, they are transferring uncertainty to the supplier. This uncertainty can manifest in price, deadlines, or conflicts. To demand precision from the other side, buyers must offer enough clarity about their own processes. Negotiation is not about shifting responsibilities onto the other party.
Focusing on Desired Outcomes
The initial conversation should focus on the desired outcome. What changes are needed in the operation? 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.
Discussing Execution Conditions
The second conversation should address 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 date as if nothing has changed.
Planning for Deviations
The third conversation should focus on handling 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 revisited. This mechanism is more useful than a vague statement of flexibility. A relationship's flexibility is also measured by its ability to change without forcing one party to pretend the change had no cost.
Balancing Detail and Simplicity
A legitimate objection is that detailing everything can delay a simple purchase. I agree. A small, repeated order doesn't require 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 more effective than an extensive document that merely repeats qualifications and promises.
Practical Calibration of Details
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 personnel, or commit to third parties, the proposal should explain these transitions. If the supplier needs to reserve capacity or purchase specific materials, this dependency also matters. The conversation about risk should begin where change stops being a simple exchange of messages.
Ensuring Continuity in Negotiation
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 everything later, while some suppliers accept any scenario to close a deal. In such cases, an apparent deal might just delay recognizing an incompatibility that would be cheaper to address while choices are still available.
Bridging Negotiation and Execution
As negotiations progress, the content must transition from the commercial team to the execution team. It's not enough to just pass on the final price. It's crucial to convey what was included, what changed, which doubts remain, and why the client emphasizes certain points. The service deliverer should not discover through complaints that a commercial conversation created an expectation they were unaware of.
Communicating Commitments Internally
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 schedule and another withholds necessary information, the issue isn't blaming the supplier for lack of initiative. The agreement only becomes operational when relevant responsibilities reach those capable of fulfilling them. Signing a contract ends a phase; it doesn't automatically distribute understanding.
Learning from Initial Deliveries
After the first delivery, compare the work done with the initial promise. Repeated doubts should improve the next proposal. This exercise allows learning without attributing all difficulties to the client or the sales team. There are execution failures, legitimate changes, and poorly designed offers. Mixing these prevents the company from correcting what it can control and leads to repeating discounts to compensate for issues not caused by pricing.
Crafting a Robust Proposal
The best proposal isn't one that eliminates all risks—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 space before it begins, someone will have to pay the difference. I prefer that conversation happens while we're still at the table.