Bottom line: a Reddit user built a 16-section system prompt that turns any LLM into a procurement copilot handling everything from supplier research to negotiation strategy. It’s free, it’s public, and it’s one of the most structured agent prompts we’ve seen.
Buying stuff for a company sounds simple until you’re three weeks deep in supplier comparisons, risk assessments, and contract negotiations. That’s the problem u/Savage_Azzax decided to solve on r/PromptEngineering with a prompt called BidBuddy, a system prompt so detailed it reads more like a procurement handbook than an AI instruction.
What Makes This Prompt Different
Most agent prompts give the AI a role and some guardrails. BidBuddy gives it an entire operating system. The prompt is organized into 16 numbered sections, each handling a specific part of the procurement lifecycle. It starts with a core role definition, moves through operating principles, and then maps out workflows for demand diagnosis, risk analysis, proposal comparison, negotiation strategy, and supplier selection documentation.
The structure isn’t random. Each section builds on the previous one, creating a logical flow that mirrors how real procurement actually works. You don’t negotiate before you understand what you’re buying. You don’t compare proposals before you’ve defined evaluation criteria. The prompt enforces this sequence.
🔧 The Architecture (Broken Down)
Here’s how the 16 sections work together:
- Sections 1-3 set identity and first contact. The AI introduces itself with numbered options so users can jump straight to their task.
- Sections 4-5 handle demand diagnosis. Before doing anything, BidBuddy asks targeted questions about the purchase need, deadline, budget constraints, and stakeholders. Then it classifies the purchase by complexity, urgency, and market structure.
- Section 6 runs a five-dimension risk analysis: operational, supplier, financial, technical, and timeline risk. Each gets a Low/Medium/High classification with mitigation actions.
- Sections 7-8 define three operating modes: quick task (just write me an email), structured support (help me build an RFP), and end-to-end (walk me through the whole process).
- Section 9 is where it gets interesting. When users upload proposals, the AI builds comparison tables, identifies hidden risks, spots scope gaps, and constructs negotiation arguments with three scenarios (conservative, target, ambitious).
- Sections 10-16 cover supplier research, RFP structuring, selection justification, document handling, safety rules, response structure, and next-step guidance.
Why This Prompt Works
Three design choices make BidBuddy effective where simpler prompts fall apart:
Incremental context building. The prompt is designed for multi-turn conversations where users add information over time. Upload a proposal on turn 5, and the AI updates its risk analysis, comparison table, and negotiation strategy. Most procurement prompts treat each message as isolated. This one maintains state.
Forced separation of facts, assumptions, and recommendations. Section 2 explicitly tells the AI to distinguish between these three categories. This is critical in procurement where a wrong assumption about delivery timelines can blow up an entire contract.
Anti-hallucination guardrails. Section 14 forbids the AI from inventing suppliers, prices, market benchmarks, or technical requirements. If information is incomplete, the AI must say so and work with what it has. In a domain where made-up numbers can cost real money, this matters.
📋 Use Cases
- Junior buyers who need structure and checklists to avoid missing steps
- Experienced procurement pros who want to speed up RFQ/RFP drafting
- Teams comparing 3-5 supplier proposals and need a structured side-by-side analysis
- Anyone preparing for a supplier negotiation who wants data-driven arguments
- Procurement managers who need auditable supplier selection documentation
Prompt of the Day
The full BidBuddy prompt is too long to paste here (it runs 16 sections), but here’s the core role definition that anchors the whole thing:
“You are BidBuddy, an assistant specialized in procurement, strategic sourcing, supplier comparison, and contracting support. Your purpose is to help buyers conduct procurement activities with more clarity, speed, structure, and decision quality. You act as a procurement copilot, helping users turn purchasing needs into clear actions, documents, comparisons, negotiation strategies, and decision records. Your priority is always practical execution.”
What makes this role definition work: it specifies the domain (procurement), the user (buyers of any experience level), the outputs (documents, comparisons, strategies), and the priority (practical execution over theory). Copy this pattern for any domain-specific agent you’re building.
🧩 Two Variations to Try
Want to adapt this approach for your own domain? Steal the architecture:
Version 1: IT Vendor Selection. Replace procurement terminology with IT-specific language. Swap “RFQ” for “technical requirements document,” add sections for integration assessment and security review, and modify the risk dimensions to include data privacy and vendor lock-in.
Version 2: Freelancer Hiring. Scale it down. Keep the demand diagnosis and comparison table sections, drop the contracting risk analysis, and add sections for portfolio review criteria and trial project design. The three operating modes (quick task, structured, end-to-end) translate directly.
The full prompt is available in the original Reddit thread on r/PromptEngineering. If you work in procurement or manage any kind of vendor selection process, it’s worth reading the complete version and adapting it to your workflow.
I built a procurement agent prompt for sourcing, supplier comparison, risk analysis, and negotiation — looking for feedback
by u/Savage_Azzax in PromptEngineering