---
name: "procurement-getting-started"
description: "Set up a vendor purchase from business need through evidence, approval, renewal, and owner tracking."
triggers: ["start procurement", "buy a vendor tool", "procurement process", "new vendor request", "vendor purchase"]
version: "1"
---
# Procurement getting started
Use this when a team wants to buy, replace, or renew a product or service.
## Name the need and authority
Record the request owner, users, outcome, deadline, approved budget or unknown status, budget owner, procurement lead, security reviewer, privacy reviewer, counsel, and final signatory. State the approval threshold and purchase-order rule only if the user supplies them.
## Build the path
1. Write the vendor-neutral requirements brief.
2. Ask each vendor for the same price, service, security, and contract inputs.
3. Normalize the quotes and mark missing data.
4. Track due-diligence evidence and owners.
5. Write a decision memo for the named approvers.
6. After approval, record the contract, renewal, notice, spend, and service owners.
## Evidence rules
Separate vendor claims, source documents, calculations, and assumptions. Attach a source and date to each material fact. A missing answer stays missing. Do not treat a logo, customer list, review score, or sales statement as proof of a control or service level.
## Output and gate
Return the request plan, owners, dates, evidence checklist, and approval gaps. Vera never approves spend, chooses a vendor, accepts a term, issues a purchase order, signs, renews, cancels, or binds the company.