Generate sharp questions before a vendor call
Prepare tactical probing questions to expose hidden software costs and risks. Use it before product demos or contract negotiations.
Prompt
Act as an enterprise procurement strategist. Help me prepare for an upcoming vendor sales demo so I can uncover hidden constraints, technical trade-offs, and pricing traps.
First, ask me these 3 numbered questions in one message and wait for my response:
1. What product, service, or software category is the vendor selling?
2. What primary business problem or metric are you hoping this tool solves?
3. What are your biggest technical, compliance, or budget constraints?
After I reply, generate sharp evaluation questions grouped by category.
Output format:
### Technical Architecture & Integration
### Real Implementation & Support Overhead
### Contract, Renewal & Hidden Costs
### Red-Flag Signs to Watch For During the CallExample output
Send the prompt in ChatGPT, Claude, or Gemini. The model will reply with three intake questions; reply with your software category and current team setup to get targeted vetting questions.
Make it repeatable
Keep using this prompt without pasting it in every time.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Prepare tough board Q&A responses from metrics
Anticipate adversarial board questions on revenue, churn, and burn rate, and craft grounded responses using your metrics.
Turn discovery call notes into testable product hypotheses
Transform messy customer feedback into structured, prioritized product hypotheses with clear validation tests and metrics.
Capture parking lot topics and open questions
Extract sidelined ideas, deferred discussions, and unresolved questions from meeting transcripts before they get lost.
Extract customer pain points from call notes
Turn unstructured user interview notes into prioritized product pain points, real customer quotes, and actionable recommendations.
Extract hidden project risks from meeting transcripts
Identify informal warnings, scope slips, and cross-team dependencies buried inside meeting notes. Use this after project syncs to maintain a clean project risk register.
Flag implied decisions needing formal sign-off
Identify unconfirmed assumptions, silent agreements, and unratified choices hiding in discussions. Use this before ending projects or sprints to prevent scope creep.