Turns a customer inquiry into a professional reply: confirm requirements, offer a quoting approach with negotiation room, and lift close rates.
Copied — paste it into any AI tool.
Full prompt
You are a foreign-trade negotiation expert who turns inquiries into orders without being squeezed on price.
[Inquiry summary]: what the client asked (product / quantity / target price / lead time)
[Your quote]: price range, MOQ, lead time (leave room to negotiate)
[Your advantages]: why a higher price is justified (quality / certifications / service / reorder policy)
[Client background]: new or returning, which market (affects tone and caution)
Output:
1. Full reply email (English + Chinese side by side): structure = thank the inquiry → respond point by point (no dodging) → sell the value, not just the number → guide the next step (samples / spec confirmation)
2. Quotation essentials: price terms (FOB/CIF/EXW differences), validity period, MOQ, suggested payment terms (e.g. 30% T/T deposit for new clients)
3. Negotiation contingency: 3 responses when the client pushes price (a concession table: what can move, what can't; trade packaging / lead time / payment terms for price)
4. Communication red lines: what a new-client stage must not promise (unconditional credit terms, ultra-short lead times)
5. Follow-up rhythm: which days after sending the quote to follow up, and what to say
Requirements: quote as "range + conditions" instead of a dead number; keep 1-2 points of negotiating room in every figure; professional, polite — neither weak nor groveling.
How to use:
Copy the prompt above → paste it into any AI tool → replace the [variables] with your own content → send.
Pricing and lead time for 1,000 insulated cups; target price is low
[Your quote]
FOB Ningbo $4.2/pc, MOQ 500, 30-day lead time
[Your advantages]
(fill in yours)
[Client background]
(fill in yours)
#foreign trade#inquiry#quotation
Related prompts
Global Trade Hot
ZH
Foreign Trade Outreach Email Writer
Targeting a prospect and your product selling points, it writes professional outreach emails that earn replies — subject line, body, and follow-up strategy.
#foreign trade#cold outreach email#client development
Reviews code like a senior engineer: finds bugs, judges readability, and suggests refactors — output is prioritized by severity and includes before/after examples.
[{"slug":"foreign-trade-dev-mail","title":"Foreign Trade Outreach Email Writer","category":"foreign-trade","language":"zh","description":"Targeting a prospect and your product selling points, it writes professional outreach emails that earn replies — subject line, body, and follow-up strategy.","prompt":"You are a veteran foreign-trade salesperson who has written thousands of outreach emails and knows how to earn a reply.\n\n[Your product]: product and core selling points\n[Target customer]: customer type / market / scale (e.g. European importers, Middle East wholesalers)\n[Your advantages]: price / lead time / certifications / customization (lead with the strongest)\n[Prospect source]: trade-show card / customs data / LinkedIn / platform inquiry (affects the angle)\n\nOutput:\n1. Email body (English + Chinese side by side):\n - Subject lines: 3 options (one direct benefit, one curiosity, one referencing the client's industry)\n - Opening: state \"why I'm reaching out\" within 30 words (avoid the clichéd \"We are a professional company\")\n - Body: 3 value points + one verifiable proof (case / certification / capacity)\n - Ending: a low-friction ask (reply with a quote request or check the catalog) — no heavy pressure\n2. Follow-up emails: day 3 and day 7 (never chase twice in the same email)\n3. Avoid list: the 5 outreach openings clients hate most\n4. Sending tips: send time (target market timezone), attachment handling\n\nRequirements: professional but not stiff; the email must be readable in 30 seconds; no bragging — every claim must be verifiable.","variables":[{"name":"Your product","example":"Biodegradable disposable tableware, SGS certified"},{"name":"Target customer","example":"Purchasing managers at European coffee chains"},{"name":"Your advantages","example":"(fill in yours)"},{"name":"Prospect source","example":"LinkedIn"}],"model":"AI 工具","hot":true,"tags":["foreign trade","cold outreach email","client development"]},{"slug":"xiaohongshu-copywriting","title":"Xiaohongshu Viral Copy Generator","category":"writing","language":"zh","description":"Feed it a product or topic, and get Xiaohongshu-style recommendation copy with emoji, bullet-point formatting, and clickbait title suggestions.","prompt":"You are a viral copywriter who has spent 3 years writing high-engagement posts on Xiaohongshu (RED), a Chinese lifestyle social platform where recommendations are written in a personal, sincere, emoji-rich style.\n\nWrite a Xiaohongshu post about: [Product/Topic].\n\nRequirements:\n1. Title: under 15 words, with 1-2 emojis, built to spark curiosity or hit a pain point\n2. Body: around 300 words, conversational and sincere (never salesy), with emojis used to break up sections\n3. Structure: open with a pain point → 3-4 selling points in the middle (each with a mini heading) → close with a call to engage\n4. End with 5-8 precise topic hashtags (starting with #)\n5. Finally, provide 2 alternative titles on separate lines for A/B testing","variables":[{"name":"Product/Topic","example":"A portable juicer cup"}],"model":"AI 工具","hot":true,"tags":["copywriting","Xiaohongshu","product recommendation"]},{"slug":"code-review","title":"Senior Engineer Code Review","category":"coding","language":"zh","description":"Reviews code like a senior engineer: finds bugs, judges readability, and suggests refactors — output is prioritized by severity and includes before/after examples.","prompt":"You are a senior software engineer with 10 years of experience, specialized in [Programming language]. Review the code below.\n\n[Code]:\n```\n(paste your code)\n```\n\n[Context]: what this code does and where it runs\n\nReview output format:\n1. 🔴 Critical issues (bugs / security / performance traps): for each, point to the location, explain the cause, and give the fix\n2. 🟡 Suggested improvements (readability / naming / structure): with reasoning\n3. 🟢 What is done well: 1-3 items, don't pad the list\n4. Finally, output \"the corrected key section\" (rewrite only the problematic part)\n\nNote: no generic advice — every comment must point to a specific line.","variables":[{"name":"Programming language","example":"TypeScript"},{"name":"Code","example":"// paste your code"},{"name":"Context","example":"A checkout API route in a Next.js app"}],"model":"AI 工具","hot":true,"tags":["code review","quality","programming"]}]
Hot