Discovery Call Cheat Sheet for Technical Products
Ask the right questions when the product is complex.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Build a discovery cheat sheet for a technical product. Product and who buys it: [PRODUCT_AND_BUYERS]. Technical environment the product must fit: [TECH_ENVIRONMENT]. Typical blockers (security review, integration effort, procurement): [BLOCKERS]. Produce a one-page sheet in four columns: Topic | Questions to ask | Why it matters | Red flag answer. Topics: current systems and architecture; data and integrations; security and compliance requirements; who evaluates and who signs; success criteria and timeline; budget and approval path; previous attempts; internal champions and resistors. Write 25 questions in plain language, such as "What happens today when this system is unavailable for an hour?" and "Who would need to be comfortable with this before you could go ahead?" Add a short script to bring in a technical colleague without losing the conversation (60 words), a post-call checklist (technical risks to verify with engineering, claims I must not make), and a template for a technical summary shared with the buyer. Do not state specifications I did not provide; mark them [VERIFY with engineering].
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.