A contract manufacturer. A multinational customer. A six-figure advance payment request. Zero prior experience in formal commercial negotiation. That was the situation on the table — and there was no senior commercial manager to call, no legal team to loop in, and no template in the shared drive that came close to covering it.
The customer had signed a multi-year supply agreement, and the factory needed to purchase specialised raw materials upfront before production could begin. The advance payment request was legitimate, commercially reasonable, and completely unfamiliar territory for the BD manager handling it. Writing a vague email and hoping for the best wasn't an option. Getting the structure wrong — the payment milestones, the conditions, the language around default — could expose the company to significant risk, or worse, kill the deal before it started.
What happened next was nine iterations of a structured proposal, built with AI, revised in real time, and sent as a document that the customer's procurement team accepted without a single revision request. This is how it was done.
Want this working in your own office? There is no standard method — the Insight PDFs first diagnose your business nature, then hand you my exact prompts to customize for YOUR office. Pay once, use forever.
Get the Insight PDFs — USD 9.99The Problem with Negotiation When You Have No Script
Most BD managers in contract manufacturing are skilled at the technical side of the relationship — understanding tolerances, translating customer drawings into quotations, managing delivery schedules. Commercial negotiation at the contract level is a different discipline. The language is different. The structure of a payment proposal is different. The way you frame risk-sharing — advance payment, milestone releases, performance bonds — requires precision that doesn't come naturally from a factory floor background.
The instinct in this situation is usually one of two things: either you write a short email asking for the money and hope the customer's goodwill carries it, or you call your boss and the conversation stalls for two weeks while everyone tries to figure out who owns the decision. Neither of those was acceptable here. The customer was waiting. The material order had a lead time. The window was real.
AI didn't solve the negotiation. It solved the preparation problem. It gave structure to a conversation that needed structure before it could happen.
How the Proposal Was Built
The first step was not writing. It was briefing. The BD manager sat down and described the situation to Claude in plain language — the contract value, the material cost, the advance payment amount being requested, the customer's profile (a multinational, risk-averse, procurement-driven), and the outcome needed. No jargon. No corporate template. Just the facts of the deal as they existed.
From that brief, the AI returned a first-draft proposal structure: an opening that framed the request as a commercial partnership position rather than a cash-flow problem, a breakdown of the advance payment into two milestone tranches, conditions tied to purchase order confirmation and material delivery verification, and a repayment mechanism linked to the first three production shipments.
That first draft was directionally right but too generic. The language was appropriate for a generic B2B transaction, not for a CNC contract manufacturing relationship with a customer the factory had been serving for two years. Iteration two added relationship context. Iteration three sharpened the milestone language. Iteration four changed the repayment mechanics after the BD manager realised the original structure would create cash flow pressure in the wrong month. By iteration six, the payment mechanics were solid. Iterations seven through nine were about tone — making the proposal sound like it came from a confident, organised supplier, not a factory scrambling for working capital.
What Nine Iterations Actually Looks Like
Each revision was a short, specific prompt. Not "make this better" — that produces nothing useful. Instead: "The milestone release in clause 2 is tied to delivery confirmation. Revise it so the release trigger is the customer's goods received note, not our shipping date." Or: "The opening paragraph sounds apologetic. Rewrite it to open with the mutual benefit framing — we're investing in capacity dedicated to this customer's program."
This is the discipline that makes AI useful in commercial contexts: you have to know what you're trying to change and why. The AI doesn't know the deal. You know the deal. AI knows how to write the language once you tell it what the language needs to say.
The email drafts followed the same pattern. Three versions: an introductory email to the customer's procurement lead framing the advance payment request at a high level, a follow-up with the formal proposal document attached, and a negotiation response email prepared in advance for the most likely pushback scenario — the customer asking for a reduced advance or a longer repayment window. Having the response email ready before the customer's reply came in meant the BD manager could respond within the hour, not the next day.
What the Final Proposal Contained
The submitted document was four pages. It covered the commercial context — why the advance was needed, framed as a dedicated capacity investment for the customer's program rather than a working capital request. It outlined two payment tranches tied to specific trigger events: purchase order issuance and raw material delivery to the factory's warehouse, with photographic and documentation evidence offered for the second trigger. It specified the repayment mechanism: a fixed deduction per shipment across the first twelve shipment months, with a table showing the projected paydown schedule. And it included a brief force majeure and default clause — not legal boilerplate, but a plain-language statement of what would happen if the program was cancelled before repayment was complete.
The customer's procurement team reviewed it and countered on one point: the deduction per shipment was slightly higher than they wanted, which would accelerate repayment faster than their preferred cashflow model. The BD manager accepted a modest reduction. The deal closed the following week.
What This Changes for BD Managers
The advance payment negotiation is one scenario. The principle applies to any commercial conversation where the structure and language matter as much as the underlying business logic: contract renewal terms, penalty clause negotiations, Incoterms changes, new program onboarding agreements, VMI arrangement frameworks. In each case, the pattern is the same — brief the AI with the facts of the deal, generate a structured draft, iterate with specific revision instructions until the document reflects the commercial reality accurately, then prepare the email chain alongside the document.
The BD manager who handled this negotiation had no prior experience writing commercial proposals at this level. Nine AI iterations and one afternoon later, they had a document that the customer accepted without revision. That's not a story about AI replacing commercial judgment. It's a story about AI giving people the tools to execute at a level their experience hasn't yet reached — and doing it in the time the deal requires.
Before You Start Any Commercial Proposal With AI
- Write out the deal facts in plain language before opening the AI tool
- Know your outcome — what does acceptance look like, what are the minimum terms you can accept
- Profile your counterpart — risk appetite, procurement culture, decision-making speed
- Prepare for the most likely pushback before you send
- Review every clause for unintended liability before submitting
- Don't send AI output without a human read for tone and accuracy



