ChatGPT Prompts for Business Development

<context> [COMPANY] does [WHAT YOU DO] for [TARGET MARKET]. I want to map partnership opportunities. Candidate categories I am considering: [INTEGRATION / RESELLER / CO-MARKETING / REFERRAL / etc.]. </context> <task> 1. For each partnership category, explain the value it creates for [COMPANY] and for the partner. 2. Rank the categories by effort-to-impact for a company at our stage. 3. For the top 2 categories, name the kinds of [PARTNER] organizations to pursue and the joint value proposition. 4. List the success metric that proves each partnership type is working. 5. Flag the most common way each partnership type fails so I can design against it. </task>

<context> I am proposing a partnership between [COMPANY] and [PARTNER]. We bring: [OUR ASSETS — audience, tech, distribution]. They bring: [THEIR ASSETS]. The deal idea is: [DEAL CONCEPT]. </context> <task> 1. Articulate the mutual value proposition in one crisp paragraph framed around what [PARTNER] gains. 2. Quantify the upside for each side with the assumptions stated explicitly. 3. Identify what each side must contribute and where incentives could misalign. 4. Draft 3 talking points I can lead with in the first partnership conversation. 5. List the 3 objections [PARTNER] is most likely to raise and a response to each. </task>

<context> [COMPANY] and [PARTNER] want to run a joint co-marketing campaign. Shared audience: [AUDIENCE]. Our goal: [LEADS / SIGNUPS / AWARENESS]. Assets available: [WEBINAR / EBOOK / EMAIL LIST / EVENT]. </context> <task> 1. Propose a campaign concept with a single shared theme both brands can own. 2. Lay out a 4-week timeline with each side's deliverables and owners. 3. Define how leads and credit get split and tracked to avoid disputes. 4. Draft the joint promotional copy: one email and one social post per brand. 5. List the 5 KPIs we report on jointly and the cadence for reviewing them. </task>

<context> [COMPANY] is building a partner program and I need to tier partners. Partner types we have: [REFERRAL / RESELLER / TECH / AGENCY]. Resources we can offer: [MARGINS, MDF, SUPPORT, LEADS]. </context> <task> 1. Design a 3-tier partner framework with clear entry criteria for each tier. 2. Map the benefits and obligations per tier so the upgrade incentive is obvious. 3. Recommend the margin/reward structure per tier given our resources. 4. Define the quarterly metrics that move a partner up or down a tier. 5. Write the one-paragraph pitch I give a [PARTNER] explaining why tiering benefits them. </task>

<context> [COMPANY] is seeing channel conflict: [DESCRIBE — e.g. direct sales competing with a reseller, two partners chasing the same [DEAL]]. The parties are: [PARTIES]. Our goal is to keep partners motivated without losing revenue. </context> <task> 1. Diagnose the root cause of this channel conflict. 2. Propose 3 rules of engagement (deal registration, territory, account ownership) that prevent recurrence. 3. Recommend how to handle the current disputed [DEAL] fairly. 4. Draft the message I send to the affected [PARTNER] explaining the resolution. 5. Note what to monitor so I catch the next conflict before it escalates. </task>

<context> I am structuring a [DEAL] between [COMPANY] and [PARTNER]. The scope is: [WHAT IS BEING EXCHANGED]. Constraints: [BUDGET, TIMING, RISK TOLERANCE]. Both sides want: [GOALS]. </context> <task> 1. Propose 3 distinct deal structures (e.g. flat fee, rev-share, hybrid, equity-for-services) that fit the constraints. 2. For each, lay out who pays whom, when, and on what trigger. 3. Compare the structures on risk, upside, and complexity in a short table. 4. Recommend one structure for [COMPANY] and explain the trade-off I am accepting. 5. List the terms I should negotiate hardest in the recommended structure. </task>

<context> I am negotiating the [DEAL] terms with [PARTNER]. My target outcome: [TARGET]. My walk-away point: [BATNA]. Their likely position: [WHAT YOU KNOW]. Key levers: [PRICE, TERM LENGTH, EXCLUSIVITY, VOLUME]. </context> <task> 1. Build my negotiation plan: opening position, target, and walk-away for each lever. 2. Identify which levers I can trade cheaply for ones I value highly. 3. Anticipate [PARTNER]'s 4 strongest arguments and prepare my counter to each. 4. Suggest 2 creative concessions that cost [COMPANY] little but feel valuable to them. 5. Draft the exact language for my opening offer. </task>

<context> I received draft terms from [PARTNER] for the [DEAL]. I am not a lawyer and want to spot business risks before legal review. The key clauses are: [PASTE CLAUSES OR SUMMARY]. </context> <task> 1. Flag clauses that are unusually favorable to [PARTNER] or risky for [COMPANY]. 2. Translate any dense legal language into plain English. 3. List the 5 questions I should raise with our lawyer, ranked by importance. 4. Suggest balanced alternative wording for the 2 riskiest clauses. 5. Add a clear disclaimer that this is not legal advice and a lawyer must review. </task>

<context> The [DEAL] with [PARTNER] involves revenue sharing. Inputs: expected deal volume [VOLUME], price point [PRICE], our costs [COSTS], proposed split [SPLIT]. Time horizon: [MONTHS]. </context> <task> 1. Model the revenue and margin for [COMPANY] and [PARTNER] under the proposed split. 2. Run 3 scenarios — conservative, expected, optimistic — and show each side's take. 3. Identify the split point at which the deal stops being worth it for [COMPANY]. 4. Recommend a split that is fair yet protects our margin, with the reasoning. 5. List the assumptions that most affect the outcome so I can pressure-test them. </task>

<context> I need an internal deal memo to get sign-off on the [DEAL] with [PARTNER]. Details: structure [STRUCTURE], value [VALUE], term [TERM], risks [RISKS]. Approver cares most about: [WHAT THEY CARE ABOUT]. </context> <task> 1. Write a one-page deal memo: summary, strategic rationale, terms, economics, risks, and the ask. 2. Lead with the decision being requested and the recommendation. 3. Quantify the expected impact and state the key assumptions. 4. Pre-empt the 3 questions the approver is most likely to ask. 5. Keep it skimmable — bold the numbers and the recommendation. </task>

<context> I am sending a formal partnership proposal from [COMPANY] to [PARTNER]. The opportunity: [DEAL CONCEPT]. What we want them to agree to: [THE ASK]. Their decision-maker: [TITLE] who cares about [PRIORITIES]. </context> <task> 1. Draft a complete partnership proposal: executive summary, the opportunity, what each side brings, proposed terms, success metrics, and next steps. 2. Frame the whole thing around outcomes [PARTNER] cares about, not our features. 3. Make the executive summary stand alone — it must sell the deal in 5 sentences. 4. Include a clear, single call to action with a proposed timeline. 5. Keep the tone confident and peer-to-peer, never deferential. </task>

<context> I need a pitch deck for [COMPANY] to present the [DEAL] to [PARTNER]. Audience: [WHO IS IN THE ROOM]. The goal of the meeting: [GET TO NEXT STEP / SIGN]. Our key proof points: [METRICS, LOGOS, RESULTS]. </context> <task> 1. Outline a 10-12 slide deck with a one-line purpose for each slide. 2. Write the headline (the takeaway, not the topic) for every slide. 3. Specify the single proof point or visual that earns each slide its place. 4. Build the narrative so each slide sets up the next toward the ask. 5. Suggest where to insert the strongest emotional hook and the strongest logical hook. </task>

<context> I am pitching the [DEAL] to [PARTNER] and expect pushback. Their likely concerns: [PRICE / TIMING / FIT / RISK / INTERNAL BUY-IN]. Context: [SITUATION]. </context> <task> 1. For each likely objection, write a response using acknowledge-reframe-evidence-advance. 2. Distinguish real objections from stalls and tell me how to test which is which. 3. Provide one proof point or analogy for each objection. 4. Give me a question I can ask to surface the objection behind the objection. 5. Script a graceful way to hold my ground on price without damaging the relationship. </task>

<context> I just pitched the [DEAL] to [PARTNER]. What happened: [HOW IT WENT, WHAT THEY SAID]. Open items: [QUESTIONS / CONCERNS LEFT]. Next step we agreed (or hoped for): [NEXT STEP]. </context> <task> 1. Draft a follow-up email that recaps the value discussed in their language. 2. Address the open items from the meeting concretely. 3. Confirm or propose a specific next step with a date. 4. Add a single piece of momentum — a relevant resource, proof point, or small commitment. 5. Give me a second, shorter nudge version to send if there is no reply in 5 days. </task>

<context> I need a one-page sell sheet for [COMPANY] to leave with [PARTNER] after meetings. Offering: [WHAT WE DO]. Their context: [INDUSTRY / USE CASE]. Strongest proof: [RESULTS, LOGOS]. </context> <task> 1. Write a one-pager: a sharp headline, the problem, our solution, 3 outcome-focused benefits, proof, and a CTA. 2. Make every line skimmable in under 30 seconds. 3. Tailor the language to [PARTNER]'s industry and use case. 4. Lead with the outcome, not the feature, in each benefit. 5. Suggest 2 headline variants so I can A/B which lands. </task>

<context> I am managing the [DEAL]/account [PARTNER]. The people involved: [LIST NAMES, TITLES, WHAT I KNOW]. My goal: [EXPAND / RENEW / RESCUE THE RELATIONSHIP]. </context> <task> 1. Build a stakeholder map: for each person, their role in the decision, influence level, and stance toward [COMPANY]. 2. Identify my champion, my blocker, and anyone I have not yet engaged. 3. Recommend the next action for each key stakeholder. 4. Spot the single biggest relationship gap that puts the account at risk. 5. Suggest how to multi-thread so the relationship survives one person leaving. </task>

<context> I am running a QBR with [PARTNER]. Relationship history: [WHAT WE DELIVERED, METRICS]. Their goals: [GOALS]. Where we want to take it: [EXPANSION / RENEWAL]. </context> <task> 1. Build the QBR agenda: value delivered, results vs their goals, roadmap, and the expansion conversation. 2. Translate our results into the business outcomes [PARTNER] actually measures. 3. Prepare the data story that justifies renewal or expansion. 4. Anticipate where they may push back and prep a response. 5. End with a clear mutual action plan for next quarter. </task>

<context> [PARTNER] has gone quiet — last contact was [WHEN] about [WHAT]. The relationship was [STATUS]. I want to revive it without sounding desperate. New angle I can offer: [TRIGGER / NEWS / VALUE]. </context> <task> 1. Diagnose the most likely reasons they went quiet. 2. Write a re-engagement message built around the new angle, not a guilt trip. 3. Make the ask tiny so replying is easy. 4. Give me a pattern-interrupt subject line that earns the open. 5. Recommend how long to wait and the one final break-up message if silence continues. </task>

<context> I need to have a hard conversation with [PARTNER] about [ISSUE — missed deliverable, price increase, scope creep, underperformance]. The relationship matters because: [WHY]. My desired outcome: [OUTCOME]. </context> <task> 1. Script the conversation: how to open, state the issue, and propose a path forward. 2. Keep it direct but preserve the relationship and their dignity. 3. Prepare for their likely emotional and rational reactions. 4. Define my must-haves versus my nice-to-haves going in. 5. Suggest how to end on a constructive, forward-looking note. </task>

<context> I manage several [PARTNER] relationships and want a simple way to track their health. My accounts: [LIST]. Signals I can observe: [ENGAGEMENT, USAGE, SENTIMENT, PAYMENT, EXEC CHANGES]. </context> <task> 1. Define a lightweight relationship-health scorecard with 5-6 signals and a simple rating scale. 2. Set the thresholds that classify each account as green, yellow, or red. 3. Recommend the action triggered by each color. 4. Suggest a review cadence I can actually sustain. 5. Output a blank template I can copy into a spreadsheet and fill in weekly. </task>

<context> I manage a business development pipeline at [COMPANY]. My current deals: [PASTE LIST — partner, value, stage, last activity, next step]. My stages are: [STAGES]. </context> <task> 1. Audit each [DEAL] for whether it is genuinely in the stage it is marked. 2. Flag stale deals (no recent activity) and deals missing a clear next step. 3. Identify the 3 deals most likely to slip and why. 4. Recommend the single highest-leverage action for each at-risk deal. 5. Summarize the overall health of the pipeline in 3 sentences. </task>

<context> I need to forecast my business development pipeline at [COMPANY]. Deals: [PARTNER, VALUE, STAGE, CLOSE DATE]. My historical close rates by stage: [RATES, OR ASK ME]. </context> <task> 1. Build a weighted forecast applying close probability by stage to each [DEAL]. 2. Produce a committed, best-case, and worst-case number for the period. 3. Show which 3 deals swing the forecast most. 4. Identify the gap to my target [TARGET] and how much new pipeline I need to cover it. 5. State every assumption so I can adjust the probabilities. </task>

<context> I want to find what slows deals down at [COMPANY]. Recent closed and lost [DEAL]s with time-in-stage: [PASTE DATA]. Average sales cycle: [LENGTH]. </context> <task> 1. Identify which stage deals get stuck in longest and the likely causes. 2. Compare velocity patterns of won versus lost deals. 3. Recommend 3 concrete changes to speed up the slowest stage. 4. Suggest an early signal that predicts a deal will stall. 5. Estimate the revenue impact of cutting the slowest stage by a third. </task>

<context> My [COMPANY] pipeline is short of target. Target for the period: [TARGET]. Current weighted pipeline: [AMOUNT]. Average deal size: [SIZE]. Average close rate: [RATE]. Time left: [TIME]. </context> <task> 1. Calculate the pipeline gap and how many new opportunities are needed to close it. 2. Break the gap into actions: accelerate existing deals, expand current partners, and source net-new. 3. Prioritize the actions by speed-to-revenue given the time left. 4. Build a week-by-week plan to close the gap. 5. Flag the risk that the gap is a demand problem, not an activity problem. </task>

<context> I need to report my business development progress to [LEADERSHIP]. This period I: [ACTIVITIES — outreach, meetings, deals advanced, partnerships signed]. Pipeline state: [SUMMARY]. They care about: [WHAT MATTERS TO THEM]. </context> <task> 1. Write a concise BizDev update: outcomes, pipeline movement, wins, and risks. 2. Lead with results and impact, not a list of activities. 3. Translate activity into the business metrics leadership tracks. 4. Be honest about what is at risk and what I need from them. 5. End with my priorities for next period in 3 bullets. </task>