Someone Built a Full Procurement Agent in a Single Prompt and It Actually Makes Sense

Yesterday a Reddit user dropped something in r/PromptEngineering that stopped me mid-scroll. Not another “be my assistant” wrapper. Not another generic GPT instructions copy-paste. This one is a full-blown procurement agent called BidBuddy, and the twist is how deep the operational logic goes inside a single system prompt.

The creator, a Redditor going by Savage_Azzax, built this prompt to function as a procurement copilot. We’re talking supplier research, RFP structuring, proposal comparison, risk analysis, negotiation strategy, and decision documentation. All from one prompt. The key insight here is that this isn’t just a chatbot with procurement vocabulary. It’s a structured workflow engine disguised as a system prompt, and it handles the kind of branching logic most people reserve for actual code.

What Makes This Different

Most procurement prompts give you a persona and hope for the best. BidBuddy takes a completely different approach: it defines operating modes, decision trees, and incremental analysis updates. The agent classifies every purchase across three dimensions (complexity, urgency, market structure) and then adapts its behavior accordingly. A low-complexity, competitive-market purchase gets a lean workflow. A high-complexity, single-supplier deal triggers the full risk and negotiation stack.

Here’s the core classification logic from the original prompt:

Purchase complexity: Low / Medium / High
Urgency: Normal / High
Supplier market structure: Competitive market / Restricted market / Single supplier

Briefly explain the reasoning behind the classification.

Simple, right? But that three-axis classification drives everything downstream, from how aggressive the negotiation strategy gets to how detailed the risk analysis becomes.

The Architecture That Makes It Work

The prompt uses 16 numbered sections, each handling a specific part of the procurement lifecycle. Here’s what the original poster built into the structure:

• 📋 Demand diagnosis (Section 4): a mandatory intake questionnaire that forces the AI to understand the actual business need before doing anything else
• ⚖️ Five-dimensional risk analysis (Section 6): operational, supplier, financial, technical, and timeline risks, each classified and explained with a severity rating
• 🔍 Proposal analysis engine (Section 9): a seven-step process that goes from raw proposal data to negotiation scenarios
• 🔄 Dynamic update rules: scattered throughout the prompt, these tell the AI to recalculate analysis whenever new documents arrive

The negotiation section alone is worth studying. It doesn’t just say “negotiate better.” It defines three concrete scenarios from the original prompt:

Conservative scenario: Small improvement in terms or conditions
Target scenario: Most realistic negotiation objective
Ambitious scenario: Best plausible outcome if the negotiation goes very well

That’s genuine procurement thinking baked into prompt architecture.

How to Use This in Your Own Workflows

You don’t need to be in procurement to learn from this approach. Here’s how to adapt the pattern:

1. Define operating modes upfront. BidBuddy has three: Quick Task, Structuring, and End-to-End. Your agent prompt should tell the AI when to go deep vs. when to just execute
2. Build classification axes. Pick 2-3 dimensions that actually change how work gets done. BidBuddy uses complexity, urgency, and market structure. A sales agent might use deal size, buyer readiness, and competitive pressure
3. Add dynamic update rules. Tell the AI explicitly: “when new information arrives, recalculate X, Y, and Z.” This is what makes the prompt work incrementally instead of starting fresh each turn
4. Separate facts from assumptions. The prompt explicitly requires distinguishing between facts, assumptions, and recommendations. This one rule alone prevents most AI hallucination in business contexts
5. Include safety rails. BidBuddy has a whole section on what it must never do: never invent suppliers, never fabricate prices, never assume unconfirmed facts. Your domain agent needs the same boundaries, spelled out just as explicitly

Pro Tips

The real power here is the incremental design. Most people build prompts for single-turn interactions. This one expects a multi-session procurement process where the buyer keeps feeding new proposals and documents. If you’re building any kind of workflow agent, steal this pattern. Define what triggers a recalculation and what stays stable. That distinction alone will make your prompts dramatically more reliable across long conversations.

Watch the section numbering. 16 sections sounds like a lot, but each one has a clear trigger condition. The AI doesn’t dump all 16 sections at once. It activates the relevant section based on where the user is in the process. That’s the difference between a wall of instructions and an actual operating system for your AI.

Try It Yourself

Grab the full prompt from the original Reddit discussion in r/PromptEngineering and drop it into Claude or GPT-4. Start with a real purchase you’re working on (even something simple like picking a SaaS tool for your team) and watch how the structured diagnosis changes the quality of output you get back. The original poster is actively looking for feedback on prompt structure, risk analysis gaps, and negotiation logic, so if you spot improvements, jump into the thread and share them.

I built a procurement agent prompt for sourcing, supplier comparison, risk analysis, and negotiation — looking for feedback
by u/Savage_Azzax in PromptEngineering