Train Your Team to Negotiate Consistently
Give every team member the same negotiation structure and language
When five people negotiate differently, suppliers play them against each other. You lose pricing power and contract terms vary wildly across the same vendor relationships.
That is the gap this drop closes. It is a finance & admin skill built for Kimi, and it takes about ten minutes to set up the first time. After that it runs in under a minute.
Who should use it
Finance directors, procurement heads, and department managers who need multiple people negotiating on behalf of the business
How it works
The skill file does five things, in this order.
1. Document your negotiation boundaries. Build a shared reference sheet with approval thresholds, non-negotiables, and flex zones for common vendor categories.
2. Create response templates for common pushback. Use AI to generate standard replies to typical vendor objections so your team speaks with one voice.
3. Run simulation sessions before live deals. Have team members practice on AI-generated scenarios based on your actual vendor types and pain points.
4. Build a debrief protocol. After each negotiation, capture what worked, what the vendor said, and what to adjust for next time in a shared log.
5. Schedule monthly calibration reviews. Compare outcomes across negotiators to spot inconsistencies and update your team playbook together.
What comes back
A team that negotiates within agreed boundaries, uses consistent language with vendors, and improves together through shared learning
The mistake to avoid
Start with one vendor category where inconsistency costs you most. Once the team sees tighter results there, rolling out to other categories becomes easier.
Running it
Paste the prompt block into a new Kimi chat and attach your files in the same message. Kimi's long context means you should upload everything at once rather than in batches, splitting the input is what causes it to lose cross-references between documents.
Where this fits
On its own, one skill saves an hour a week. The compounding happens when three or four of them run in sequence on the same input, the same transcript that produces a scope of work also produces the follow-up email and the project brief. That is the point at which it stops being a prompt and starts being an internal tool. If you want that wired into the systems your team already uses, that is the work 67 Digital does.
In the file
You are training a negotiation team for a {industry} business in the UAE. We negotiate frequently with {vendor_categories}.
Our team includes {number} people with {experience_levels}.
Create a negotiation playbook that includes:
1. Approval thresholds: what each team member can agree to without escalation for contracts worth {contract_value_range}
2. Non-negotiables: the terms we never compromise on across all vendor relationships
3. Flex zones: where we have room to negotiate and what we ask for in return
4. Standard responses: how to reply when vendors say {common_vendor_objections}
5. Escalation triggers: the specific situations that require manager involvement
6. Debrief template: the five questions each negotiator answers after every vendor meeting to capture learning
Format this as a practical reference document that someone can keep open during a negotiation call. Use specific numbers and phrases, not general principles. Include a section on what information must be logged in our shared system after each negotiation.
Make the language direct and suitable for team members whose first language may not be English.