Pretend you are the procurement buyer so price fiction, risk gaps, and RFP theater fail before a vendor package absorbs them.
Optimistic seller and internal sponsor packages optimize for "this clears purchasing." The procurement buyer seat does the opposite. It asks which total cost line is missing, which risk claim lacks an owner, which SLA invents capacity, and which competitive alternative was never priced. A fluent vendor brief is not evidence that purchasing will clear the deal without redlines or a delay.
Mandate and constraints
Name a real mandate: underwrite a vendor award without inventing savings, clear a risk scorecard that security and legal can defend, or defend a single-source ask without dual-counted urgency. Give constraints: the evidence standard for price and risk, the deal types you will not invent coverage for, and the residual risk you will refuse to hide. Without constraints the seat becomes cartoonish. With constraints it produces questions you might actually hear in a sourcing review, a vendor risk committee, or a renewal fight over who owns the exit plan.
Write the seat into the prompt as a named role with a mandate. Example: "Procurement buyer: list the top reasons to delay this award, the claim with the weakest cost evidence, the risk path that worries you most, and the ten diligence questions you would send after review. Stay inside a realistic mandate."
Outputs that count
- Top reasons to challenge, delay, or reject this vendor package.
- The claim that looks strongest and is least evidenced.
- The cost line, SLA, or exit path that would break first under scrutiny.
- What would make you accept residual vendor risk in writing.
- The ten hardest questions you would send after the meeting.
Run that brief in Pingpong against the real RFP pack, scorecard, security findings, and contract redlines. Follow with a home-team response pass so you leave with edits and source packs. When the decision is a public vendor announcement, run this seat after security and legal attacks so it can use earlier objections as ammunition.
When the plan leans on a single champion price, a single risk waiver, or a single "we need them live by Friday" story, force the seat to price concentration risk in writing. Ask what happens if the champion leaves, if the waiver expires, or if the go-live date slips while the contract already locks fees. Pair with war-game a vendor selection, pretend you are the enterprise buyer, before you sign the contract, stress-test a vendor exit, and the war-game decisions hub. See how to run a Pingpong.
If the package coincides with a budget freeze or a tooling consolidation, ask the procurement buyer seat to map every SKU, renewal, and shadow IT spend that still assumes the old vendor set. Concentration that only appears in a footnote still counts.