The prompt
Score 10 of 10, Excellent
Use it when A new business customer wants to buy on account and you need a credit limit and terms based on what you actually know about them.
- {{decision_maker}}
- {{application}}
- {{credit_information}}
- {{credit_policy}}
- {{margin}}
Full prompt and why it works
Prompt
Recommend a credit limit and payment terms for the new customer below, for {{decision_maker}} to approve, so we can offer terms that fit their expected orders without taking on more risk than our policy allows. Customer application and what they told us (expected order size and frequency, years trading, references): """ {{application}} """ Credit information we have (credit report, trade references, bank reference, financial statements, any history with us): """ {{credit_information}} """ Our credit policy (standard terms, limit bands, who approves what, security we can ask for): {{credit_policy}} Our gross margin on this kind of order, if known: {{margin}} Use these headings: 1. Recommendation: the credit limit, the terms and any conditions, in two sentences. 2. How the limit was sized: from the expected order pattern, with the arithmetic shown. For example: "Expected orders of 6,000 a month, paid on day 45 at worst = 1.5 months outstanding x 6,000 = 9,000 peak balance." This example shows the form only. If our margin is given, add one line showing the sales it would take to make back a loss of the full limit (the limit divided by the margin). 3. Evidence for and against: each point tied to a line in the information above. 4. Conditions and review: for example a lower starting limit reviewed after a set number of on-time payments, a deposit or a guarantee, only where our policy allows it. 5. Gaps: information we would normally want and do not have. Base every point on the information above and quote figures exactly as given. Do not infer a customer's financial strength from their size, industry or location, and do not treat missing information as good or bad; list it under Gaps and say how it changes the recommendation. Stay within our policy's limit bands and name the approver the recommended limit requires. Keep the whole recommendation under 400 words. A good recommendation lets the approver see how the figure was reached and what would change it. If the information is too thin to support more than our policy's starting limit, say so and recommend what to collect first.
Variables
- {{decision_maker}}
- Who approves credit, for example "the finance director".
- {{application}}
- The customer's credit application or what they told you: expected orders, how often, how long they have traded.
- {{credit_information}}
- Credit report summary, trade and bank references, financial statements, or "none yet".
- {{credit_policy}}
- Your standard terms, limit bands and approval levels, for example "30 days standard; up to 10,000 approved by the credit controller".
- {{margin}}
- Your gross margin on these orders, for example 25%. Write "not known" if you do not have it.
Why it works
- What good looks like. The limit is sized from the customer's own expected orders with the arithmetic shown, so the figure can be defended or adjusted.
- What to avoid. No inferring creditworthiness from a customer's size, industry or location, which keeps the decision to the evidence.
- If unsure. Missing information is listed with its effect on the recommendation, and thin files get the starting limit plus what to collect.