Prompt Workshop
Why it is written this way
Tap a block to see its paragraph
You are a senior general affairs and procurement manager with over 10 years of experience reviewing purchase proposals in mid-to-large corporations. You know exactly which business justifications get approved immediately and which ones get rejected.
I am submitting a formal purchase request for {{purchased items}}. The estimated total cost is {{monetary amount}}, and this proposal must be approved first by my team lead and ultimately by the Finance Director. The alternatives already evaluated are: {{alternative comparison}}.
Draft a complete purchase proposal based on the notes below. In the "Business Justification" section, do not simply write vague phrases like "needed for operational tasks." Instead, clearly specify the concrete problems currently occurring without these items and the measurable improvements expected after purchasing them.
Structure the document with the following sections in order: Subject, Purchase Details, Business Justification, Alternative Comparison, Expected ROI & Benefits, Approval Request. Present the Purchase Details as a markdown table with columns for Item, Quantity, Unit Price, and Total. Keep the Business Justification between 3 to 5 clear sentences.
Do not invent any unmentioned costs, dates, or vendor names; label any missing specific figures as [Needs Verification]. Avoid unsubstantiated buzzwords like "revolutionary" or "essential." State the amortized monthly cost in parentheses alongside the total amount, explicitly specifying the amortization period (e.g., across 36 months).
Notes on Necessity: """ {{required necessity reason}} """
Before providing the final draft, ask up to three critical questions regarding any essential information missing from the notes that an approver would likely challenge. If all necessary information is present, proceed directly with drafting the proposal.
- Role Who answers ×1
- Material What the AI needs to know ×2
- Work What to do, and how ×2
- Output What comes back, in what shape ×2
Purchase proposals are usually rejected not because of the price tag, but because of a weak justification. A single sentence like "Needed to perform daily business operations" forces decision-makers to question what will actually happen if we do not buy it now, or if there is a cheaper workaround. Preventing this generic reasoning is the primary goal of this prompt.
Read the full explanation · 3 paragraphs
This is why the Context section explicitly includes the total cost, approval chain, and alternatives. Approvers evaluate a $300 purchase very differently from a $3,000 one, and finance directors scrutinize the underlying cost logic much more strictly. Addressing the alternative comparison upfront proactively resolves the inevitable objection: "Did you consider cheaper alternatives or leasing?"
In the Task section, separating "current problems without the item" from "improvements after purchase" provides the core framework for a rock-solid business case. The Format section mandates a structured order and standardizes item details into a table because numbers are much easier to audit in a tabular view.
Lastly, the Constraints require [Needs Verification] placeholders to prevent AI hallucination on prices and dates. Asking the AI to raise up to three clarifying questions first ensures that critical gaps are surfaced back to you rather than filled with assumptions.
Unfamiliar terms? See Aha AI: prompt, output-format
Compared with a bad example
Write a purchase proposal for 4 monitors. Around $3,200.
A prompt this vague results in generic fluff like "To enhance operational efficiency and drive team productivity." Approvers get zero concrete decision-making criteria from such statements and will inevitably bounce the request back asking for justification. Furthermore, without quotation details, the AI will invent unit prices and totals, creating discrepancies that require re-submitting amended requests later.
Variations
When a Submitted Proposal Was Rejected
Asking for an immediate rewrite without diagnosing the root cause often leads to repeating the same mistakes in future proposals. Getting a critique first builds better long-term proposal habits.
Show prompt
Below is the justification section of a purchase proposal for {{purchased items}} that was rejected by management. Before rewriting it, please diagnose the flaws: ① Sentences the approver would view as lacking concrete evidence, ② Points that provoke unanswered questions about cheaper alternatives, and ③ Adjectives that should be replaced with hard metrics or data. After the breakdown, provide a revised justification addressing the most critical issues.
""" {{required necessity reason}} """
For Recurring Consumables and Supplies
Proposals for recurring supplies get stuck on quantity validation rather than basic necessity. This variant shifts the justification focus onto inventory metrics and burn rates.
Show prompt
Draft a purchase request for recurring orders of {{purchased items}}. The estimated total amount is {{monetary amount}}, and this will be submitted as a recurring quarterly expense rather than a one-time purchase. Base the justification strictly on consumption data (monthly burn rate, current inventory levels, projected stock-out date), and explain in one sentence why the requested order batch quantity is optimal.
""" {{required necessity reason}} """
Model notes
LLMs can occasionally make arithmetic errors when summing totals in markdown tables. After receiving your draft, always double-check the calculations with a quick prompt: "Recalculate the table totals to verify the math is accurate."
Last updated 2026-09-02 · Found a mistake? Let us know