Complex B2B Software Discovery Plan
Plan a multi-call discovery for a technical deal.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Plan discovery for a complex B2B software deal. Our product and typical deployment: [PRODUCT_AND_DEPLOYMENT]. The prospect (company, size, systems, regulations): [PROSPECT_CONTEXT]. Known stakeholders: [STAKEHOLDERS]. Deal size and timeline: [DEAL_SIZE_AND_TIMELINE]. Create a plan across four sessions, each with a goal, attendees, duration, agenda, key questions, and exit criteria: Session 1, business discovery (champion and sponsor): problem, impact, goals, success metrics, timeline. Session 2, process and users: current workflow end to end, volumes, pain points, edge cases, integration points. Session 3, technical and security: systems, data flows, authentication, hosting constraints, compliance requirements, procurement of security questionnaires. Session 4, commercial and decision: budget, approval path, legal and procurement steps, evaluation plan, risks. For each session include 8 to 10 questions, documents to request, and a short summary email to send within 24 hours. Add: a discovery document template that accumulates answers; a risk register for the deal; a "do not proceed" checklist (no budget owner, no clear problem, no access to users); a mutual evaluation plan outline; and guidance on keeping calls short by using pre-reads. Mark every claim about my product for verification by the solutions team as [VERIFY]. Keep the plan flexible for smaller deals.
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.