Prompts for Business Development Managers

26 ready-to-use ChatGPT prompts for business development managers. Fill in the bracketed fields, paste into ChatGPT, and go.

Sales · 26 prompts

01

Create a Plan for Pursuing Untapped Markets

Build a practical plan for identifying and pursuing new business opportunities in untapped markets.

You’ll needbusiness contexttarget marketsgrowth goalconstraintsteam resources
Prompt
You are a business development strategist.

Build a plan for pursuing untapped markets using the context below.

Context:
- Business context: [business]
- Candidate target markets: [markets]
- Growth goal: [goal]
- Constraints: [constraints]
- Team resources available: [resources]

Instructions:
1. Require a low-cost validation step (a handful of real conversations, a small pilot) before committing significant resources, since untapped-market plans often skip validation and discover the gap the hard way.
2. Rank candidate markets by a combination of opportunity size and realistic reach given current resources, not opportunity size alone.
3. Flag markets that look attractive on paper but would require capabilities the team doesn't currently have (different sales motion, different buyer, regulatory differences).
4. Set a decision checkpoint with a go/no-go criterion after the validation step, so the plan doesn't default into full pursuit regardless of what validation shows.
5. Note the resourcing tradeoff against existing market efforts.

Output format:
- Market ranking (opportunity vs realistic reach)
- Validation step before commitment
- Capability-gap flags per market
- Go/no-go checkpoint
- Resourcing tradeoff note

Missing information policy:
Ask up to 2 concise questions only if the target markets or growth goal are unclear.

Quality bar:
- Includes a low-cost validation step before full commitment.
- Capability gaps flagged honestly.
- Includes an explicit go/no-go checkpoint.
02

Create a Strategic Partnership Growth Strategy

Build a strategy for creating and nurturing partnerships that support growth.

You’ll needbusiness contextpartnership goaltarget partner typesconstraints
Prompt
You are a business development strategist.

Build a partnership growth strategy using the context below.

Context:
- Business context: [business]
- Partnership goal: [goal]
- Target partner types: [partner types]
- Constraints: [constraints]

Instructions:
1. Check for incentive alignment explicitly — a partnership where the value flows mostly one direction tends to decay even if it looked good on paper at signing, so name what's genuinely in it for the partner.
2. Define what success looks like for both sides with a specific metric, not just "mutual growth," so the partnership has a way to be evaluated later.
3. Note the resourcing commitment required to actually nurture the partnership after signing, since partnerships that get no attention post-launch quietly go dormant.
4. Flag partner types likely to create channel conflict with existing sales motion.
5. Include an exit or renegotiation path if the partnership underperforms, rather than assuming it's permanent once signed.

Output format:
- Incentive alignment check per partner type
- Success metrics (both sides)
- Post-signing resourcing plan
- Channel-conflict flags
- Exit/renegotiation path

Missing information policy:
Ask up to 2 concise questions only if the partnership goal or partner types are unclear.

Quality bar:
- Incentive alignment addressed explicitly.
- Success defined with specific metrics.
- Includes a post-signing resourcing plan.
03

Create a Business Development Proposal Template

Build a proposal template for potential partners that highlights mutual value clearly.

You’ll needbusiness contextpartner typemutual benefit goaltone
Prompt
You are a business development strategist.

Build a partnership proposal template using the context below.

Context:
- Business context: [business]
- Partner type: [partner type]
- Mutual benefit goal: [goal]
- Tone constraints: [tone]

Instructions:
1. Structure the proposal to state the partner's specific benefit before your own ask, since proposals that lead with what you want read as one-sided and get deprioritized.
2. Include a concrete first step (a pilot, a small joint initiative) rather than asking the partner to commit to a full long-term agreement on the first proposal.
3. Name the resourcing or effort required from the partner honestly, so they can evaluate the real cost of participating, not just the upside.
4. Include a section addressing likely partner objections (bandwidth, competing priorities, brand risk) proactively.
5. Keep the template adaptable to different partner sizes and types, not written for only one specific partner profile.

Output format:
- Proposal template (partner benefit first)
- Concrete first-step ask
- Partner effort/resourcing transparency
- Anticipated-objection section

Missing information policy:
Ask up to 2 concise questions only if the partner type or mutual benefit goal is unclear.

Quality bar:
- Leads with partner benefit, not your ask.
- Proposes a concrete first step, not full commitment.
- Addresses likely objections proactively.
04

Create a Market Research Guide for Business Development

Write a practical guide to research markets in support of business development strategy.

You’ll needbusiness contextgrowth questiontarget marketresearch constraints
Prompt
You are a business development strategist.

Create a market research guide using the context below.

Context:
- Business context: [business]
- Growth question the research needs to answer: [question]
- Target market: [market]
- Research constraints (time, budget): [constraints]

Instructions:
1. Scope the research to the specific growth question, not a general market overview — a broad study takes longer and often doesn't actually answer the decision at hand.
2. Recommend a mix of desk research and direct signal (a handful of prospect or partner conversations) since desk research alone tends to miss the on-the-ground reality that changes a go/no-go decision.
3. Note where public data is likely to be stale or incomplete and flag the confidence level of conclusions drawn from it.
4. Time-box the research phase so it doesn't become an open-ended exercise that delays the actual decision.
5. End with a direct answer to the growth question and the confidence level behind it.

Output format:
- Research scope tied to the growth question
- Desk research + direct signal mix
- Confidence level per data source
- Time-boxed research plan
- Direct answer to the growth question

Missing information policy:
Ask up to 2 concise questions only if the growth question or target market is unclear.

Quality bar:
- Scoped to the specific question, not a broad overview.
- Includes direct signal, not desk research alone.
- Ends in a direct, confidence-labeled answer.
05

Create a Cross-Department Collaboration Plan for BD

Build a collaboration plan that aligns other departments with business development goals.

You’ll needbusiness contextbd objectivedepartments involvedconstraints
Prompt
You are a business development strategist.

Build a cross-department collaboration plan using the context below.

Context:
- Business context: [business]
- BD objective: [objective]
- Departments involved (product, marketing, legal, finance): [departments]
- Constraints: [constraints]

Instructions:
1. Frame the ask to each department in terms of their own goals, not just BD's goal, since a collaboration request that only serves BD's objective tends to get deprioritized against the department's own workload.
2. Name a specific point of contact and decision-maker per department rather than a vague "work with marketing" ask.
3. Set realistic timelines that account for each department's existing commitments, not an idealized BD timeline imposed on everyone else.
4. Flag where legal or compliance sign-off is genuinely required (partnership agreements, data sharing) so it's built into the plan rather than discovered as a blocker later.
5. Include a way to surface and resolve conflicting priorities across departments early rather than at the point of a stalled deliverable.

Output format:
- Department-specific framing of the ask
- Named contacts and decision-makers
- Realistic cross-department timeline
- Legal/compliance checkpoints
- Conflict-resolution approach

Missing information policy:
Ask up to 2 concise questions only if the BD objective or departments involved are unclear.

Quality bar:
- Ask framed around each department's own goals.
- Named contacts, not vague department-level asks.
- Legal/compliance checkpoints included where relevant.
06

Write Partner Outreach Email Templates

Create email templates for initiating contact with potential partners or clients.

You’ll needofferpartner typemutual valueCTAtoneproof
Prompt
You are a business development communicator.

Write partner outreach emails using the context below.

Context:
- Offer or collaboration idea: [offer]
- Partner type: [partner type]
- Mutual value: [mutual value]
- CTA: [cta]
- Tone constraints: [tone]
- Proof (existing partnerships, relevant results): [proof]

Instructions:
1. Frame the outreach around strategic fit and mutual value, not a product pitch — a partnership contact is evaluating whether this makes sense for their organization, which is a different decision than a buyer evaluating a product.
2. Reference something specific about the potential partner's business that makes this pairing make sense, not a generic "we think there's synergy" line.
3. Propose a low-commitment first conversation rather than asking for a partnership decision in the first email.
4. Include relevant proof (existing partnerships, credibility signals) that speaks to organizational trust, not individual customer testimonials.
5. Keep the tone appropriately more formal than a typical cold sales email, since this is usually going to a decision-maker evaluating organizational risk.

Output format:
- Outreach email template
- Partner-specific fit rationale
- Low-commitment CTA
- Proof points included

Missing information policy:
Ask up to 2 concise questions only if the partner type or mutual value is unclear.

Quality bar:
- Framed around strategic fit, not a product pitch.
- Partner-specific reasoning, not generic synergy language.
- Low-commitment CTA, not a partnership ask upfront.
07

Create a Framework to Evaluate Business Development ROI

Build a framework for evaluating the potential ROI of business development opportunities.

You’ll needopportunity typesgoaldecision criteriaconstraints
Prompt
You are a business development strategist.

Build an ROI evaluation framework using the context below.

Context:
- Opportunity types being evaluated: [opportunity types]
- Goal: [goal]
- Decision criteria: [criteria]
- Constraints: [constraints]

Instructions:
1. Include opportunity cost explicitly — pursuing one opportunity uses team bandwidth that could go to another, and a framework that only scores absolute upside misses this.
2. Weight time-to-value, not just total potential value, since a large but slow-to-materialize opportunity can be worse for the business than a smaller, faster one depending on current priorities.
3. Separate confident estimates (based on real data or signed terms) from speculative ones (based on optimistic assumptions), and require the framework to label which is which.
4. Include a risk-adjustment factor for opportunities dependent on external parties (a partner's follow-through, a market shift) rather than treating all projected ROI as equally certain.
5. Keep the framework simple enough to apply consistently across different opportunity types, not a bespoke model for each one.

Output format:
- ROI framework with opportunity-cost weighting
- Time-to-value factor
- Confidence labeling (data-backed vs speculative)
- Risk-adjustment for external dependency
- Application guidance across opportunity types

Missing information policy:
Ask up to 2 concise questions only if the opportunity types or decision criteria are unclear.

Quality bar:
- Includes opportunity cost, not just absolute upside.
- Confidence labeled per estimate.
- Risk-adjusts for external dependency.
08

Design a Business Development Networking Workshop with Pipeline and Relationship Outcomes

Design a business development networking workshop with practical relationship-building exercises, follow-up discipline, and pipeline-oriented outcomes instead of generic confidence advice.

You’ll needaudiencetraining goaltime availablesales contextrelationship outcomesconstraints
Prompt
You are a business development trainer.

Design a networking workshop using the context below.

Context:
- Audience: [audience]
- Training goal: [goal]
- Time available: [time]
- Sales context: [sales context]
- Desired relationship outcomes: [outcomes]
- Constraints: [constraints]

Instructions:
1. Anchor the workshop in follow-up discipline, not just conversation skills — most networking value is lost after the event through weak or missing follow-up, not during the conversation itself.
2. Include a practical exercise for qualifying who's worth pursuing at an event, since not every conversation is a real opportunity and time at events is limited.
3. Build in a concrete follow-up template or process the participant leaves with, tied to what they'll actually do in the 48 hours after an event.
4. Define what a successful networking outcome looks like in pipeline terms (a scheduled follow-up call, an added contact with context) rather than a vague "made connections" metric.
5. Keep the workshop time-realistic and practice-heavy rather than lecture-heavy.

Output format:
- Workshop outline (practice-heavy)
- Qualification exercise
- Follow-up template/process
- Pipeline-defined success outcomes

Missing information policy:
Ask up to 2 concise questions only if the training goal or audience is unclear.

Quality bar:
- Anchored in follow-up discipline, not just conversation skills.
- Includes a concrete follow-up template.
- Success defined in pipeline terms, not vague connection-making.
09

Create a Social Media Strategy for Business Development

Build a strategy for using social platforms to support business development and brand growth.

You’ll needbusiness contextplatformsgoalaudienceconstraints
Prompt
You are a business development strategist.

Build a social media strategy for business development using the context below.

Context:
- Business context: [business]
- Platforms: [platforms]
- Goal: [goal]
- Audience: [audience]
- Constraints: [constraints]

Instructions:
1. Tie the strategy to pipeline-relevant outcomes (relationship starts, inbound partner interest) rather than vanity engagement metrics like follower count or likes, which don't reliably translate to BD outcomes.
2. Recommend content that demonstrates expertise or credibility relevant to potential partners, not generic company updates.
3. Note the realistic time commitment required to sustain a BD-focused social presence, since this often gets deprioritized without a defined weekly time budget.
4. Distinguish platforms by their actual usefulness for BD relationship-building (some platforms work far better for this than others) rather than treating all platforms as equally valuable.
5. Include a way to track whether social activity is actually contributing to real BD conversations, not just impressions.

Output format:
- Platform prioritization for BD relevance
- Content themes tied to credibility
- Realistic time budget
- Pipeline-relevant tracking method

Missing information policy:
Ask up to 2 concise questions only if the platforms or goal are unclear.

Quality bar:
- Tied to pipeline outcomes, not vanity metrics.
- Platforms prioritized by actual BD usefulness.
- Includes a realistic time budget.
10

Create a Method to Track Business Development Initiatives

Design a method for tracking and analyzing the outcomes of business development initiatives.

You’ll needinitiative typesgoalmetricsworkflowstakeholders
Prompt
You are a business development strategist.

Design a tracking method using the context below.

Context:
- Initiative types: [initiative types]
- Goal: [goal]
- Metrics: [metrics]
- Workflow: [workflow]
- Stakeholders: [stakeholders]

Instructions:
1. Include a stall detector — a way to flag initiatives that haven't had meaningful progress in a defined window, since BD initiatives often quietly go dormant without anyone officially closing them.
2. Separate leading indicators (early relationship signals) from lagging outcomes (closed partnership, revenue), since BD initiatives take time and need interim signals to judge health before final outcomes are known.
3. Assign a single owner per initiative, since shared ownership is a common reason initiatives lose momentum without anyone noticing.
4. Include a periodic review to explicitly decide whether to continue, pause, or kill each initiative, rather than letting initiatives persist indefinitely by default.
5. Keep the tracking method lightweight enough to actually maintain.

Output format:
- Stall-detection criteria
- Leading vs lagging indicators
- Single-owner assignment
- Continue/pause/kill review cadence

Missing information policy:
Ask up to 2 concise questions only if the initiative types or goal are unclear.

Quality bar:
- Includes stall detection.
- Leading and lagging indicators distinguished.
- Includes an explicit continue/pause/kill review.
11

Negotiate More Effectively in Business Development

Write a practical negotiation guide for deals and partnership conversations.

You’ll needbusiness contextdeal typegoalcommon challenges
Prompt
You are a business development strategist.

Write a negotiation guide using the context below.

Context:
- Business context: [business]
- Deal type: [deal type]
- Goal: [goal]
- Common negotiation challenges: [challenges]

Instructions:
1. Identify your actual walk-away point before the negotiation, not during it, since negotiating without a predetermined floor leads to concessions made under pressure that look bad in hindsight.
2. Distinguish terms that are genuinely non-negotiable from ones that feel important but have real flexibility, so effort isn't spent defending positions that don't matter.
3. Address anchoring — note who should make the first substantive offer and why, based on the specific deal dynamics, rather than a generic "always anchor first" rule that doesn't fit every situation.
4. Prepare for the specific objections or pushback likely in this deal type, not generic negotiation tactics divorced from context.
5. Note where a partnership or BD negotiation differs from a straightforward sales negotiation — the relationship usually needs to survive past the signature, which changes how hard to push on certain terms.

Output format:
- Walk-away point (defined in advance)
- Non-negotiable vs flexible terms
- Anchoring guidance for this deal type
- Anticipated objections and responses
- Relationship-preservation considerations

Missing information policy:
Ask up to 2 concise questions only if the deal type or goal is unclear.

Quality bar:
- Walk-away point defined before the negotiation, not during.
- Non-negotiable and flexible terms distinguished.
- Addresses relationship preservation, not just deal terms.
12

Create a Quarterly Business Development Report Template

Build a quarterly report template covering goals, achievements, and areas for improvement.

You’ll needteam contextreporting goalstakeholdersmetrics
Prompt
You are a business development strategist.

Build a quarterly BD report template using the context below.

Context:
- Team context: [team]
- Reporting goal: [goal]
- Stakeholders: [stakeholders]
- Metrics: [metrics]

Instructions:
1. Separate activity metrics (meetings held, proposals sent) from outcome metrics (partnerships signed, pipeline value added), since a report full of activity numbers can look busy while hiding weak actual results.
2. Include initiative status (continued, paused, killed this quarter) so leadership sees the full picture, not just the wins.
3. Tie each section to a decision or ask, since a report with no action implication tends to just get filed away.
4. Note confidence level on any forward-looking projections included in the report.
5. Keep the template concise enough that stakeholders read the whole thing each quarter.

Output format:
- Activity vs outcome metrics (separated)
- Initiative status summary (including paused/killed)
- Section-level decisions or asks
- Forward-looking projection confidence notes

Missing information policy:
Ask up to 2 concise questions only if the reporting goal or stakeholders are unclear.

Quality bar:
- Activity and outcome metrics kept separate.
- Includes paused/killed initiatives, not just wins.
- Each section ties to a decision or ask.
13

Create a Diversification and New Venture Roadmap

Build a roadmap for scaling through diversification and new venture exploration.

You’ll needbusiness contextgrowth goalmarket opportunitiesconstraints
Prompt
You are a business development strategist.

Build a diversification roadmap using the context below.

Context:
- Business context: [business]
- Growth goal: [goal]
- Candidate market opportunities: [opportunities]
- Constraints: [constraints]

Instructions:
1. Stage the roadmap so early phases are low-commitment validation (a pilot, a small test) and later phases require evidence from the prior stage before scaling investment, rather than committing significant resources to an unproven venture upfront.
2. Flag where a new venture would compete for the same resources or attention as the core business, and name that tradeoff explicitly.
3. Note capability gaps a new venture would require and whether they're realistically buildable versus needing new hires or partners.
4. Define a clear kill criterion for each phase so the roadmap doesn't quietly continue funding a venture that isn't working.
5. Keep timelines realistic given the constraints named, not an idealized fast-scaling narrative.

Output format:
- Staged roadmap (validation before scale)
- Core-business resource tradeoff
- Capability-gap assessment
- Kill criteria per phase
- Realistic timeline

Missing information policy:
Ask up to 2 concise questions only if the growth goal or market opportunities are unclear.

Quality bar:
- Staged with validation before major commitment.
- Resource tradeoff against core business named explicitly.
- Includes kill criteria per phase.
15

Create a Long-Term Client and Partner Relationship Strategy

Build a strategy for maintaining long-term relationships with key clients and partners.

You’ll needrelationship typesgoalcurrent issuestouchpoint strategyconstraints
Prompt
You are a business development strategist.

Build a long-term relationship strategy using the context below.

Context:
- Relationship types (clients, partners): [relationship types]
- Goal: [goal]
- Current issues: [issues]
- Touchpoint strategy: [touchpoints]
- Constraints: [constraints]

Instructions:
1. Define what quiet disengagement looks like for this relationship type (fewer replies, declined meetings, reduced usage) so it can be caught early rather than discovered when the relationship is already effectively over.
2. Set a touchpoint cadence proportional to relationship value, since applying the same effort to every relationship spreads attention too thin on the ones that matter most.
3. Assign a clear owner per key relationship, since relationships without a named owner tend to get informally deprioritized.
4. Note where the relationship depends on a single point of contact on the other side, since that's a fragility risk if that person leaves.
5. Include a way to periodically reassess which relationships still warrant "key" status, since priorities shift.

Output format:
- Disengagement warning signs
- Value-proportional touchpoint cadence
- Named ownership per relationship
- Single-point-of-contact fragility flag
- Periodic reassessment method

Missing information policy:
Ask up to 2 concise questions only if the relationship types or goal are unclear.

Quality bar:
- Defines disengagement warning signs concretely.
- Cadence proportional to relationship value.
- Flags single-point-of-contact fragility.
16

Create an Executive Sponsor Brief for a Strategic Account

Build an executive sponsor brief with account context, stakeholder dynamics, risks, and conversation priorities.

You’ll needaccount contextcustomer goalskey stakeholdersrenewal or expansion contextrisksdesired exec outcome
Prompt
You are an account strategist preparing an executive sponsor brief.

Build the brief using the context below.

Context:
- Account context: [account]
- Customer goals: [customer goals]
- Key stakeholders: [stakeholders]
- Renewal or expansion context: [renewal context]
- Known risks: [risks]
- Desired executive outcome: [outcome]

Instructions:
1. Keep the brief short enough for an executive to absorb in a few minutes before a call, not a full account history — prioritize what changes how they should show up in the conversation.
2. Name stakeholder dynamics explicitly (who's the champion, who's skeptical, who has budget authority) since an executive sponsor walking in blind to internal politics can say the wrong thing to the wrong person.
3. State risks honestly, including ones that reflect poorly on the account team, since a sanitized brief sets the executive up to be surprised in the room.
4. Give the executive 2-3 specific talking points or questions tied to the desired outcome, not generic relationship-building advice.
5. Flag anything time-sensitive the executive needs to know before the meeting (a recent escalation, a competitor mention).

Output format:
- Account snapshot
- Stakeholder dynamics
- Honest risk summary
- Specific talking points tied to the outcome
- Time-sensitive flags

Missing information policy:
Ask up to 2 concise questions only if the account context or desired outcome is unclear.

Quality bar:
- Short enough for quick executive prep.
- Risks stated honestly, not sanitized.
- Talking points are specific, not generic.
17

Summarize Renewal Risk for a Leadership Audience

Analyze account health signals and summarize renewal risk, likely causes, and recommended executive action.

You’ll needaccount data or notesrenewal timelineusage or adoption signalsstakeholder sentimentcommercial contextkey question
Prompt
You are a revenue strategist analyzing renewal risk.

Summarize renewal risk using the context below.

Context:
- Account data or notes: [account data]
- Renewal timeline: [timeline]
- Usage or adoption signals: [usage signals]
- Stakeholder sentiment: [sentiment]
- Commercial context: [commercial context]

Instructions:
1. Separate hard signals (usage decline, support ticket volume, a champion departure) from softer impressions (a rep's gut feeling) and weight the hard signals more heavily in the risk assessment.
2. Give a direct risk level (low/medium/high) with the reasoning behind it, not just a narrative that leaves leadership to infer the severity themselves.
3. Name the most likely underlying cause of risk, not just the symptom (e.g. "low usage" is a symptom; "champion left and no replacement engaged" is closer to a cause).
4. Recommend a specific executive action tied to the timeline (an exec-to-exec call, an early renewal conversation) rather than a vague "stay close to the account" note.
5. Note the confidence level of the assessment given the available data.

Output format:
- Risk level with reasoning
- Hard signals vs soft impressions
- Likely underlying cause
- Recommended executive action with timing
- Confidence level

Missing information policy:
Ask up to 2 concise questions only if the account data or renewal timeline is unclear.

Quality bar:
- Hard signals weighted over soft impressions.
- Direct risk level stated, not left implicit.
- Recommended action is specific and timed.
18

Summarize Pipeline Risk for Leadership

Analyze pipeline risk for leadership using stage distribution, concentration, slippage, and fragility signals.

You’ll needpipeline summarystage distributionrisk signalsknown big dealstime horizonmain question
Prompt
You are a revenue operations strategist.

Summarize pipeline risk using the context below.

Context:
- Pipeline summary: [pipeline]
- Stage distribution: [stages]
- Risk signals (slippage, stalled deals, single-threaded accounts): [risk signals]
- Known large or concentrated deals: [big deals]
- Time horizon: [horizon]
- Main question leadership wants answered: [question]

Instructions:
1. Note that CRM stage is self-reported by reps and often optimistic — flag where stage distribution alone would overstate pipeline health.
2. Call out concentration risk explicitly: if a small number of large deals make up most of the forecast, the summary should say so rather than presenting an aggregate number that hides it.
3. Distinguish slippage that reflects a real deal problem (stalled stakeholder engagement) from slippage that's just a scheduling shift.
4. Flag single-threaded deals (one contact, no multi-stakeholder engagement) as a fragility signal regardless of stage.
5. Answer the leadership question directly and lead with it, not bury it under a full pipeline dump.

Output format:
- Direct answer to the leadership question
- Stage-distribution caveat
- Concentration risk
- Fragility signals (single-threading, stalled engagement)
- Recommended actions

Missing information policy:
Ask up to 2 concise questions only if the pipeline summary or main question is unclear.

Quality bar:
- Stage self-report bias flagged.
- Concentration risk stated explicitly.
- Leads with the direct answer.
19

Create a Deal Review Brief for a High-Stakes Opportunity

Build a deal review brief covering stakeholders, blockers, risks, and next moves for a high-stakes opportunity.

You’ll needdeal contextbuyer stakeholdersmain blockerscommercial stakescompetitive contextdecision goal
Prompt
You are a sales strategist preparing a deal review brief.

Build the brief using the context below.

Context:
- Deal context: [deal]
- Buyer stakeholders: [stakeholders]
- Main blockers: [blockers]
- Commercial stakes: [stakes]
- Competitive context: [competitive context]
- Decision goal for the review: [decision goal]

Instructions:
1. State blockers honestly and specifically, since deal reviews often default to an optimistic status update that hides the real risk until it's too late to address.
2. Map stakeholder support level explicitly (champion, neutral, blocker, unknown) rather than assuming broad support because the primary contact is enthusiastic.
3. Distinguish blockers that are within the rep's control to address from ones that depend on the buyer's internal process or timeline.
4. Tie the brief to the specific decision the review needs to make (more resources, exec involvement, walk away) rather than a general deal update.
5. Note what specifically needs to happen before the next milestone, with an owner.

Output format:
- Deal snapshot
- Stakeholder support map
- Honest blocker assessment (controllable vs not)
- Decision the review needs to make
- Next steps with owners

Missing information policy:
Ask up to 2 concise questions only if the deal context or decision goal is unclear.

Quality bar:
- Blockers stated honestly, not softened.
- Stakeholder support mapped explicitly.
- Tied to a specific decision, not a general update.
20

Analyze Repeated Objection Patterns Across Sales Conversations

Analyze repeated objection patterns across sales conversations and identify messaging, qualification, or positioning fixes.

You’ll needobjection examplesoffer contextbuyer segmentsstage contextknown lossesmain question
Prompt
You are a sales strategist analyzing objection patterns.

Analyze the objection data below.

Context:
- Objection examples: [objections]
- Offer context: [offer]
- Buyer segments involved: [segments]
- Deal stage where objections occurred: [stage]
- Known deals lost to these objections: [losses]
- Main question: [question]

Instructions:
1. Distinguish objections that recur across many deals from a few memorable but non-representative examples reps happen to recall — anecdote-driven fixes often miss the real pattern.
2. Segment objections by buyer type and deal stage, since the same-sounding objection can mean different things early versus late in a deal.
3. For each recurring objection, identify whether the fix is a messaging problem, a qualification problem (talking to the wrong buyer), or a genuine product gap, since each needs a different owner.
4. Note where an objection correlates with lost deals versus one that comes up often but rarely costs the deal.
5. End with specific, owned recommendations, not a general "improve messaging" note.

Output format:
- Recurring vs anecdotal objection patterns
- Segment and stage breakdown
- Root cause per pattern (messaging / qualification / product)
- Correlation with lost deals
- Owned recommendations

Missing information policy:
Ask up to 2 concise questions only if the objection examples or main question are unclear.

Quality bar:
- Recurring patterns distinguished from anecdotes.
- Root cause typed per pattern.
- Recommendations are owned and specific.
21

Build a Stakeholder Map for a Late-Stage Account

Build a stakeholder map for a late-stage account with influence, concerns, blockers, and next actions.

You’ll needaccount contextstakeholdersdeal stageknown concernschampion statusnext milestone
Prompt
You are a sales strategist mapping account stakeholders.

Build a stakeholder map using the context below.

Context:
- Account context: [account]
- Known stakeholders: [stakeholders]
- Deal stage: [stage]
- Known concerns per stakeholder: [concerns]
- Champion status: [champion status]
- Next milestone: [milestone]

Instructions:
1. Flag single-threading explicitly if most engagement is with one contact, since late-stage deals that rely on one relationship are fragile even if that relationship feels strong.
2. Map each stakeholder's actual influence and decision authority, not just their title, since titles don't reliably predict who drives the real decision.
3. Note where a stakeholder's support is inferred versus confirmed directly, since assumed support that turns out to be wrong is a common late-stage deal failure.
4. Identify unknown or unmapped stakeholders (a legal or procurement reviewer who hasn't been engaged yet) as a specific risk to close before the next milestone.
5. Tie the map to concrete next actions per stakeholder, not just a static org chart.

Output format:
- Stakeholder map (influence, decision authority, support level)
- Single-threading risk flag
- Confirmed vs inferred support
- Unmapped-stakeholder risk
- Next actions per stakeholder

Missing information policy:
Ask up to 2 concise questions only if the account context or known stakeholders are unclear.

Quality bar:
- Single-threading risk flagged explicitly.
- Confirmed and inferred support distinguished.
- Includes concrete next actions per stakeholder.
22

Prepare a Note Before an Executive Customer Meeting

Create a prep note before an executive customer meeting with context, risks, stakeholder dynamics, and goals.

You’ll needaccount contextmeeting purposestakeholders attendingcurrent riskscommercial contextdesired outcome
Prompt
You are an account strategist preparing an executive meeting note.

Create the prep note using the context below.

Context:
- Account context: [account]
- Meeting purpose: [purpose]
- Stakeholders attending: [attendees]
- Current risks: [risks]
- Commercial context: [commercial context]
- Desired outcome: [outcome]

Instructions:
1. Keep the note short enough to read in the few minutes before a meeting — a long brief doesn't get read by a busy executive walking between meetings.
2. Lead with what the executive needs to say or ask, not background history they don't need to reconstruct the whole account story.
3. Name each attendee's role and what they likely care about in this specific meeting, not a generic stakeholder bio.
4. State current risk honestly so the executive isn't caught off guard by something the account team already knew about.
5. End with the single most important outcome to walk away with.

Output format:
- Meeting purpose and desired outcome (top of note)
- Attendee-specific notes
- Honest risk summary
- Key talking points
- Single most important outcome

Missing information policy:
Ask up to 2 concise questions only if the meeting purpose or attendees are unclear.

Quality bar:
- Short enough for last-minute reading.
- Leads with what to say/ask, not history.
- Risk stated honestly.
23

Summarize Expansion Signals in an Existing Account

Analyze an existing account for expansion signals, blockers, timing, and next strategic moves.

You’ll needaccount signalsusage contextstakeholder contextcommercial historyknown blockersmain question
Prompt
You are an account strategist analyzing expansion opportunity.

Summarize expansion signals using the context below.

Context:
- Account signals (usage growth, new use cases, stakeholder requests): [signals]
- Usage context: [usage context]
- Stakeholder context: [stakeholder context]
- Commercial history: [commercial history]
- Known blockers: [blockers]

Instructions:
1. Distinguish signals that indicate genuine expansion readiness (a stated new use case, budget-holder interest) from routine account activity that just looks like engagement but isn't an expansion signal on its own.
2. Note the account's commercial history (recent renewal, past pricing pushback) since that affects how an expansion conversation should be timed and framed.
3. Flag any blocker likely to derail an expansion conversation (unresolved support issue, low current satisfaction) that should be addressed before pitching more.
4. Recommend a specific timing for raising expansion, tied to account context rather than a generic quarterly cadence.
5. End with a direct answer to the main question and a recommended next move.

Output format:
- Genuine expansion signals vs routine activity
- Commercial history considerations
- Blockers to resolve first
- Recommended timing
- Direct answer and next move

Missing information policy:
Ask up to 2 concise questions only if the account signals or main question are unclear.

Quality bar:
- Genuine signals distinguished from routine activity.
- Commercial history factored into timing.
- Ends with a direct, actionable recommendation.
24

Create a Save Plan for a Renewal Showing Risk Signs

Create a save plan for a renewal showing risk signs, including stakeholders, recovery actions, and timing logic.

You’ll needrenewal contextrisk signalsstakeholderscommercial stakescurrent relationship statusconstraints
Prompt
You are a revenue strategist building a renewal save plan.

Create the save plan using the context below.

Context:
- Renewal context: [renewal]
- Risk signals: [risk signals]
- Stakeholders: [stakeholders]
- Commercial stakes: [stakes]
- Current relationship status: [relationship status]
- Constraints: [constraints]

Instructions:
1. Diagnose the actual cause of risk (value not realized, a departed champion, a budget cut, dissatisfaction with support) before proposing a recovery action, since a discount offered without addressing the real cause usually doesn't fix the underlying problem.
2. Prioritize actions that rebuild the business case (demonstrating value achieved, addressing an unresolved issue) over pure price concessions.
3. Identify who on the customer side needs to be re-engaged and why, especially if a former champion is gone.
4. Set a realistic timeline given how much runway remains before the renewal date.
5. Note the walk-away scenario — what happens and what's the fallback if the save attempt doesn't work, so the team isn't caught without a plan.

Output format:
- Root-cause diagnosis
- Recovery actions (value-based before price-based)
- Stakeholder re-engagement plan
- Realistic timeline
- Fallback if the save doesn't work

Missing information policy:
Ask up to 2 concise questions only if the renewal context or risk signals are unclear.

Quality bar:
- Root cause diagnosed before proposing actions.
- Value-based actions prioritized over pure discounting.
- Includes a fallback scenario.
25

Review Loss Patterns Across Recent Deals

Analyze recent deal losses for recurring patterns in qualification, objections, timing, pricing, and competition.

You’ll needlost deal notessegment contextcompetitor presencepricing contextobjection themesmain question
Prompt
You are a sales strategist reviewing lost-deal patterns.

Review the loss data below.

Context:
- Lost deal notes: [deal notes]
- Segment context: [segment]
- Competitor presence in these losses: [competitors]
- Pricing context: [pricing]
- Objection themes noted: [objections]
- Main question: [question]

Instructions:
1. Distinguish the stated loss reason (often logged quickly by a rep as "price" or "no budget") from the more likely underlying cause visible in the deal notes — CRM loss reasons are frequently a convenient label, not the real story.
2. Segment losses by deal size, buyer type, and competitor presence to find real patterns instead of treating all losses as one undifferentiated bucket.
3. Flag losses that were likely qualification failures (wrong buyer, no real budget) separately from losses that were genuinely competitive, since the fix differs.
4. Note where a specific competitor recurs in losses and whether a common theme (price, feature, timing) is associated with it.
5. End with specific, owned recommendations tied to the actual patterns found, not generic "improve qualification" advice.

Output format:
- Stated vs likely-real loss reasons
- Segment and competitor breakdown
- Qualification-failure vs competitive-loss split
- Competitor-specific patterns
- Owned recommendations

Missing information policy:
Ask up to 2 concise questions only if the deal notes or main question are unclear.

Quality bar:
- Stated and real loss reasons distinguished.
- Segmented, not treated as one bucket.
- Recommendations tied to actual patterns found.
26

Turn Discovery Call Notes into a Next-Steps Brief

Build a next-steps brief from discovery call notes with pains, buying signals, risks, stakeholders, and recommended follow-up.

You’ll needdiscovery call notesaccount contextmain painsstakeholdersrisks or blockersdesired next step
Prompt
You are a sales strategist turning discovery notes into an action brief.

Build the next-steps brief using the context below.

Context:
- Discovery call notes: [notes]
- Account context: [account]
- Main pains surfaced: [pains]
- Stakeholders identified: [stakeholders]
- Risks or blockers surfaced: [risks]
- Desired next step: [next step]

Instructions:
1. Separate what the prospect explicitly stated from your interpretation of it, so the brief doesn't overstate confidence in inferred signals.
2. Prioritize pains by how directly they connect to a business outcome the prospect cares about, not just by how many pains were mentioned.
3. Flag any stakeholder gaps (someone clearly relevant who wasn't on the call) as a risk to close before the next step.
4. Make the recommended next step specific and time-bound, not a generic "schedule a follow-up."
5. Note anything uncertain rather than presenting a guess as fact.

Output format:
- Facts vs interpretation
- Prioritized pains (tied to business outcomes)
- Stakeholder gaps
- Specific, time-bound next step
- Uncertainty flags