Library/Meeting Prep & Discovery/Discovery Call Execution/Technical discovery agenda (IT / Security / Engineering buyer)
TestedMeeting Prep & DiscoveryDeep Work (30+ min)

Technical discovery agenda (IT / Security / Engineering buyer)

Technical discovery agenda with environment mapping phases, objection prep, POC readiness check, and SE coaching for the hardest moment in technical sales.

About this prompt

Build a technical discovery agenda for a CTO, VP Engineering, or Security buyer. Three environment mapping phases, objection prep, POC readiness check, and an SE coaching note.Technical buyers evaluate for architectural honesty and specific knowledge before considering business value. This prompt builds a discovery agenda in three technical phases: environment mapping (build the mental architecture diagram before asking about pain), technical pain and risk (quantify in engineering hours and incidents, then bridge to business impact), and evaluation criteria (surface integration requirements and POC readiness). The SE coaching note specifically addresses the trust-building move when a rep doesn't know an answer — saying 'I don't know, I'll get you the right answer' is more credible than guessing.

The prompt

You are an expert B2B sales engineer building a technical discovery agenda for an AE and/or SE running a deep-dive call with a technical buyer — CTO, VP Engineering, IT Director, Security Architect.
The rest of this prompt is Pro.Copying the full text is Pro. Browsing stays free, and 100 prompts are free in full.
Copy prompt
☆ Save to library
Send to a teammate
Email it
Link copied — paste it in Slack
Copying the full text is Pro.

Variables to replace

  • [AE_NAME] — AE's name
  • [SE_NAME] — SE name or 'AE running solo'
  • [YOUR_COMPANY] — Company name
  • [PRODUCT_OR_SERVICE] — Technical product description
  • [TECH_DIFFERENTIATOR] — Core technical differentiator (e.g., 'agentless deployment')
  • [INTEGRATIONS] — Key integration capabilities
  • [CALL_LENGTH] — 45 / 60 min
  • [BUYER_NAME] — Technical buyer name
  • [BUYER_TITLE] — VP Engineering / IT Director / Security Architect
  • [PROSPECT_COMPANY] — Their company
  • [PROSPECT_INDUSTRY] — Industry
  • [TECH_STACK] — Known or inferred tech environment
  • [TECHNICAL_TRIGGER] — Recent incident, scaling, compliance, or migration signal

How to run it

  1. Copy the prompt and paste it into Claude, ChatGPT, Gemini, or Copilot — it's tuned to run in any of them.
  2. Replace the variables — swap each bracketed token for your deal's specifics. The variables list above explains every field.
  3. Make it yours — run it, keep what's strong, and tighten your inputs on the next pass. The prompt improves with your context.

What good output looks like

Technical research checklist + likely objection + credibility detail + environment mapping + technical pain questions + evaluation criteria + POC readiness question + SE coaching note

Make it yours

TECH_STACK and TECHNICAL_TRIGGER are the upgrade fields. Job postings reveal tech stack; public incidents or compliance certifications reveal the trigger. Spend 10 minutes here before running the prompt.
StageDiscovery
SeatAE, SE
DifficultyAdvanced
Time to valueDeep Work (30+ min)
Works withAI-Agnostic
CategoryMeeting Prep & Discovery
Promptifi ProFull text of all 2,900+ prompts, every workflow, unlimited saves.Start Pro — $4.99/moor $99 once, lifetime
You're ProFull library open. Copy, save, and chain anything.

Stop rewriting. Start closing.

Copy prompt
Start Pro — $4.99/mo