Map and navigate a prospect's procurement process without losing momentum
Maps the procurement stages standing between verbal yes and signature for your specific buyer, arms you with discovery questions that surface the whole process upfront, and lists the documents to prepare before anyone asks. Deals stall in procurement because of surprises; this removes them.
You are an enterprise deal-desk veteran who has shepherded hundreds of contracts through procurement at companies from 200 to 20,000 employees. You know procurement isn't the enemy — it's a process with predictable stages, gatekeepers, and paperwork, and deals die there because sellers discover the stages one painful surprise at a time. Build me a procurement navigation plan for a specific deal: 1. STAGE MAP: the likely stages between verbal yes and signature for a company of this size and industry (security review, legal review, vendor onboarding, finance approval, InfoSec questionnaire, insurance requirements), with a realistic time estimate for each. 2. DISCOVERY QUESTIONS: 6-8 questions to ask my champion NOW that surface the whole process upfront — phrased so they don't sound like I'm rushing them. 3. PRE-EMPTIVE PACKAGE: the documents I should prepare before being asked (security overview, W-9 or local equivalent, insurance certificates, standard MSA, SOC 2 or posture summary) ranked by how often procurement requests them. 4. RISK FLAGS: the three most common places deals of this shape stall in procurement, and one move to prevent each. 5. CHAMPION SCRIPT: a short message my champion can forward to procurement introducing us and framing the purchase as already-decided pending process. Rules: no advice to 'go around procurement' — that kills deals. No generic 'be patient'. Every recommendation must shorten the timeline or reduce surprise. Before you write anything, interview me. Ask me these questions ONE AT A TIME, waiting for my answer each time: 1. What are you selling, at what contract value, and what does the buyer's company look like (size, industry, region)? 2. Where is the deal today, and who is your champion? 3. What has anyone said so far about their buying process, security requirements, or legal review? 4. What compliance assets do you already have (SOC 2, ISO, insurance, standard contracts)? Once you have my answers, produce the plan. If any answer is vague, ask one follow-up before proceeding.
How to use it
- 1
Copy the prompt into Claude, ChatGPT, or any LLM.
- 2
Answer the interview — company size and industry matter most, since they drive which stages exist.
- 3
Ask your champion the discovery questions on your next call and paste their answers back into the chat.
- 4
Have the model revise the stage map and timeline with the real answers, then build your close plan around it.
Best practices
Ask the discovery questions at verbal yes, not after — the day the buyer says 'let's do it' is your maximum-goodwill moment to map the process.
Prepare the pre-emptive package before it's requested; responding to a security questionnaire in hours instead of weeks is a visible competitive edge.
Get the name of the actual procurement contact early and treat them like a stakeholder, not an obstacle.
Pair this with a mutual action plan so every procurement stage has an owner and a date.
Example: what this looks like in practice
An AE at a data-integration startup gets a verbal yes on a $45K deal from a 3,000-person healthcare company, her first buyer that size. The interview captures the deal, and the plan predicts security review, BAA negotiation, and vendor onboarding as the likely stages, estimating 6-9 weeks. She asks her champion the discovery questions and learns there's also a new-vendor committee that meets monthly — a stage she'd have discovered three weeks too late. She gets on the next committee agenda, sends the security package pre-emptively, and signs in seven weeks instead of the quarter-plus her team's last enterprise deal took.
Best fit
This prompt is one gear in a bigger machine. We orchestrate 20+ tools into outbound systems our clients own — and guarantee the results.
Apply for a Pilot Spot → →Frequently asked questions
Typically 4-12 weeks after the verbal yes, depending on contract value, security requirements, and whether legal redlines the agreement. The variance mostly comes from surprises — an unexpected InfoSec questionnaire or a vendor committee that meets monthly. This prompt's stage map and discovery questions exist to find those stages before they find you.
More negotiation, proposals & closing prompts
Build a mutual action plan working back from a signature date
Builds a milestone-by-milestone mutual action plan backward from your signature date — owners, dates, dependencies, and a risk note per buyer-owned step — plus a forwardable version framed around the buyer's go-live, not your close. It also tells you honestly when the target date is fantasy.
Build a negotiation prep brief with leverage, concessions, and a walk-away point
Produces a one-page prep brief that maps the buyer's leverage against yours, sets a concrete walk-away point with the sentence to deliver it, and pre-plans responses to their three most likely demands. It replaces the 'wing it and hope' approach with a written plan you can glance at mid-call.
Build an expansion pitch for an existing customer
Builds an expansion pitch that starts from the customer's own results and stated goals rather than your quota — including an honest check on whether you've earned the right to pitch at all, a bridge narrative, spoken and forwardable versions, and the commercial framing for the incremental spend.