Sales Opportunity Stakeholder Map
Map likely stakeholders, assess the sponsor, and prioritize practical next actions for a sales opportunity.
Customise & copy
Add the context you have. The prompt updates as you work.
Enter the opportunity name, account-opportunity label, or CRM ID.
Enter the organization being pursued.
List names, titles, departments, and relationship context only when known.
Describe the offering and the business problem it addresses.
Select the current sales stage.
State the target decision or implementation timing.
Live prompt
6 fieldsCreate a practical stakeholder map for the sales opportunity below. Use only the information provided and reasonable role-based inferences. Do not invent names, email addresses, phone numbers, reporting lines, or personal contact details. Mark unknown information as "Unknown" and distinguish known contacts from inferred stakeholders. Opportunity: {{opportunity_name}} Target company: {{target_company}} Known contacts: None provided Product or service: {{product_service}} Deal stage: Discovery Timeline: {{timeline}} Return exactly this format: OPPORTUNITY SUMMARY - Opportunity: [name or ID] - Company: [company] - Product/service: [offering] - Stage: [stage] - Timeline: [timeline] STAKEHOLDER MAP | Stakeholder or role | Likely position | Influence and interest | Evidence or assumption | Best realistic way to reach them | |---|---|---|---|---| [One row per known or likely stakeholder] SPONSOR ASSESSMENT - Most likely sponsor: [one named contact if supported; otherwise role] - Why: [brief evidence-based rationale] - Sponsor confidence: [High, Medium, or Low] - Sponsor validation question: [one question the Account Executive can ask] PRIORITY ACTIONS 1. [Next action for the highest-priority stakeholder] 2. [Next action for validating the sponsor] 3. [Next action for identifying any critical missing stakeholder] Use practical contact routes such as an introduction from a known contact, an executive-to-executive request, a discovery call, a procurement or security process, or a role-based outreach path. Do not recommend scraping private data or guessing direct contact details.
Proof before you use it
A real example
Tested on gpt-5.6-luna on 2026-09-10
{
"timeline": "Target decision by 30 September; pilot planned for October",
"deal_stage": "Discovery",
"known_contacts": "Maya Chen, VP Operations — attended the initial discovery call; Daniel Ortiz, IT Applications Manager — copied on one follow-up email",
"target_company": "Northstar Logistics",
"product_service": "Cloud CRM and workflow automation platform to improve regional sales forecasting and handoffs",
"opportunity_name": "Northstar CRM Modernization"
}A small ritual that works
How to use it
- 01Enter the opportunity name or ID and target company name.
- 02Add known contacts, including titles, departments, and relationship context if available.
- 03Describe the product or service, then select the deal stage.
- 04Enter the target decision or implementation timeline and run the prompt.
Why it works
The prompt combines a defined sales objective with explicit evidence boundaries. It separates known contacts from inferred stakeholders, requires unknown details to remain marked as "Unknown," and prohibits invented personal or reporting information. The fixed sections create a practical progression from opportunity context to stakeholder roles, sponsor reasoning, and next actions. Its role-based inference rule helps the reader identify likely participants such as sales, finance, IT, security, procurement, and executive decision-makers without treating those inferences as confirmed facts. The required evidence-or-assumption column makes the basis for each stakeholder entry visible.
Where it fails
The structure becomes less informative when the supplied opportunity data is sparse, especially when there are no known contacts, no clear business problem, or no usable timeline. In those situations, the map must rely more heavily on role-based inference and label more information as unknown. The prompt also cannot establish actual authority, reporting lines, internal politics, or approval requirements unless the input provides evidence for them.
Customisation tips
Add fields for decision criteria, budget status, incumbent provider, competitors, implementation scope, approval process, regulatory requirements, and relationship strength when those details matter. If the workflow distinguishes economic buyers, technical approvers, users, blockers, and champions, name those categories explicitly in the stakeholder table. You can also tailor the priority actions to the deal stage—for example, emphasizing discovery participants early and procurement, security, legal, or contracting steps later. If the map will be imported into a CRM, replace the prose table with a field structure that matches the destination system.
Watch-outs
- Treat inferred roles as hypotheses to validate, not confirmed stakeholders.
- Do not convert a known contact's job title into assumed budget authority or final decision rights.
- Keep contact routes practical and permission-based; the prompt specifically excludes guessing direct details or scraping private data.
- Check that the timeline supports the proposed sequence of discovery, validation, business-case work, and approval steps.
Works in
Was this useful?
Submit your variation
If your version helps, it may be published with your name and a link back to you.
Related prompts
Want to make AI useful across your team? Explore Atul's training.