Business English for Negotiation: Make, Trade and Close Proposals Clearly
Use clear Business English to make proposals, exchange conditional concessions, clarify terms and close negotiations without confusing discussion with agreement.
A negotiation conversation can sound friendly and still be unclear. A team may discuss a discount, delivery date or service level without knowing which points are proposals, which are conditions and which are final commitments. Clear language protects the relationship because it prevents assumptions from becoming later disputes.
This article is about communication, not legal advice or a substitute for contract review. In a commercial negotiation, follow your organisation’s authority levels and involve the right legal, procurement or commercial colleagues where needed. The language below helps you make the conversation precise.
Prepare the language around the decision
Before the meeting, know what you are authorised to discuss and what requires approval. Write down:
- your objective and preferred outcome;
- the issues you can change;
- the points you cannot commit to;
- the information you still need;
- who will confirm a final agreement.
This preparation makes your English simpler. Instead of promising too early, you can say: “I can discuss the proposed delivery window today, but I need internal approval before confirming a final date.” That is clearer and safer than vague optimism.
Make a proposal that can be evaluated
A useful proposal names the subject, the term and the condition.
We could offer a six-month extension if the support scope remains unchanged.
Our preferred option is monthly delivery, provided that the forecast is confirmed two weeks in advance.
Would you consider moving the implementation date to October in exchange for an additional training session?
Notice the difference between “We could” and “We will.” The first introduces an option; the second may sound like a commitment. If you are exploring possibilities, say so. If the proposal is conditional, make the condition visible rather than leaving it implied.
Trade, do not simply give
In negotiation, a concession is often clearer when it is conditional. This is sometimes called an “if–then” structure:
If you can confirm the annual volume, we could review the unit price.
If the implementation moves to the next quarter, then we can keep the current resource allocation.
We may be able to shorten the notice period if the handover plan is agreed in advance.
The wording does not guarantee acceptance. It shows the relationship between two terms. Avoid giving a concession with no explanation of what changes in return: “Fine, we can reduce the price” may create a precedent and leaves the basis unclear. A conditional sentence allows both sides to test an option responsibly.
Clarify before you respond
When a proposal is unclear, ask for the missing detail before making a counterproposal.
| Need | Clarifying question |
|---|---|
| Definition | “When you say ‘full support’, which activities are included?” |
| Timing | “Does that date mean delivery, acceptance or contract signature?” |
| Authority | “Can the team confirm this today, or does it require further approval?” |
| Priority | “Which of price, timing and scope is most important for you?” |
| Condition | “Would the discount depend on a minimum order volume?” |
Questions are not a sign of weakness. They reduce the chance that two people agree to different interpretations of the same sentence.
Signal a concern without turning it into a threat
You may need to reject a term. Do so by explaining the constraint and inviting a workable alternative.
I understand the need to reduce cost. At that price, we could not maintain the agreed response time. Could we look at a smaller scope or a longer term instead?
We cannot accept the proposed deadline in its current form because the dependency has not been approved. We can, however, discuss a phased delivery plan.
This is firmer and more professional than “Take it or leave it.” It states what cannot be accepted while preserving room for a solution. If there is no authority or no viable alternative, say that accurately rather than using aggressive language to force a decision.
Close the conversation by recording the terms
Discussion is not agreement. Before you leave a meeting or send a final email, summarise what each side believes has been agreed and what remains subject to approval.
To confirm my understanding: we will provide the revised scope by Tuesday; you will review it by Friday; pricing remains subject to final volume confirmation. Is that accurate?
After the meeting, send a short written recap. Include the agreed terms, owners, deadlines, dependencies and open points. Avoid writing “As agreed” if the item was only discussed. Use “We discussed…” or “Subject to approval…” where that is more accurate.
Common wording mistakes
Unclear proposal: “Maybe we can do something about the price.” Clearer: “If the contract term is extended to two years, we could review the proposed price.”
Unclear acceptance: “That should be fine.” Clearer: “I can confirm that the revised delivery date of 18 October is acceptable, subject to the signed change request.”
Pressure without a basis: “You need to decide now.” Clearer: “To reserve the implementation team, we need confirmation by Friday. If that is not possible, we can discuss the next available window.”
Treating a possibility as a commitment: “We will probably include training.” Clearer: “Training is an option we can price separately; I will confirm availability after checking with the delivery team.”
Practise with a small scenario
Choose a familiar negotiation—service scope, a delivery date or a meeting agenda. Write one proposal, one conditional concession, one clarification question and one closing summary. Then check that each sentence says whether it is an option, a condition or a confirmed action.
Examova’s Negotiation & Persuasion module helps learners practise proposals, compromise, objections and closing deals in context. You can also see how the full Business English preparation path is organised.