Sales & Prospecting Prompts

Draft a cold prospecting email sent by [your name and title] from [company] to [prospect's title] at [type of target company].

What we sell: [product or service]. The specific problem we solve for this role: [problem]. Personalization element available: [element, e.g., recent company news, LinkedIn post, funding round].

Constraints: 90 words maximum, one single idea, no superlatives, avoid "I hope you're doing well," and use a low-friction call to action (a question or a brief time slot suggestion). Provide 3 subject lines under 40 characters, the email body, and a 50-word follow-up to be sent 4 days later that adds new value rather than just "bumping" the thread.

Prepare a discovery call outline for a [duration, e.g., 30-minute] meeting between a sales rep from [company] and [prospect's title] at [type of company]. We sell [product or service], average deal size [amount].

Structure the outline into 5 phases: opening and agenda setting (2 min), prospect context, problem exploration, the cost of inaction/status quo, and next steps. For each phase, write the exact open-ended questions to ask (one at a time) and what specific cues to listen for in the response.

Include a qualification framework [method, e.g., BANT or MEDDIC] to fill out during the call, and 3 ways to propose the next step without pressure. Rule: do not pitch the product until the problem has been fully explored.

I sell [product or service] to [target] at [price]. Here are the objections I hear most often: [objection 1], [objection 2], [objection 3].

For each objection, build a 4-step response: acknowledge without contradicting, dig deeper with a question to understand the root cause, respond with a concrete element (data, client example, guarantee: [available elements]), and verify if the answer addresses their concern.

Write the exact phrasing in natural spoken English. For each objection, identify the signal that indicates it is actually a polite rejection and how to end the conversation professionally without burning the bridge.

Write a 3-message LinkedIn sequence from [your title] at [company] to [target title] in the [industry] sector. Final goal: secure a 15-minute chat about [topic related to your offer].

Message 1 (Connection request, 250 characters max): a commonality or a sincere reaction to [element from their profile or activity]. Message 2 (3 days after acceptance): share a useful resource or observation regarding [industry problem], with no ask. Message 3 (one week later): a short request for a chat, providing a specific reason why it benefits them.

Tone: direct, peer-to-peer, no flattery. No sales links in the first 2 messages.

Draft a sales proposal from [company] for [client], following a meeting where we identified: client context [context], priority problem [problem], target objective [quantified goal], and deadline [deadline].

Our solution: [description of offer]. Price: [price and terms]. Decision maker: [title].

Structure: recap of the situation using the client's own words, objectives and success criteria, proposed solution mapped point-by-point to the problem, timeline and roadmap, investment (presented after value, never before), and a dated next step. Maximum two pages of text. Ban "we are the leader" and any paragraph discussing our history that isn't directly linked to their problem.

Act as an experienced Sales Director. Help me define the Ideal Customer Profile for [company], which sells [product or service] at an average price of [average deal size].

Here are our 5 best current clients: [list with industry, size, buying context]. Here are 3 clients who churned or were problematic: [list and reasons].

Produce: firm ICP criteria (industry, size, maturity, tech stack, buying trigger), exclusion signals that should disqualify an account even if they seem interested, the 3 personas to contact within these accounts with their primary pain point, and a checklist of max 8 questions to score an account in 5 minutes.

Constraint: base every criterion on the provided examples; do not generalize beyond them. Output format: structured ICP sheet ready for CRM upload.

You are a Sales Operations Manager. I am prospecting for [company], selling [offer] to [ICP summary]. My territory: [geographic zone or segment]. Goal: [number] meetings per month.

Build my target account list method: where to find accounts matching the ICP in the [US/UK] market (e.g., LinkedIn Sales Navigator, ZoomInfo, Crunchbase, industry-specific press for [sector], public filings), what data to collect per account (max 10 fields), and a 100-point scoring grid combining ICP fit and observable intent signals ([available signals, e.g., hiring, funding, leadership change]).

Output format: table of sources with the type of info they provide, list structure (columns), scoring grid, and a rule for segmenting into 3 priority tiers with the associated contact cadence for each.

Design a multi-channel prospecting sequence of [duration, e.g., 15 business days] to reach [target title] at [type of company]. We sell [offer], the problem we solve: [problem]. Available proof: [client reference or verifiable stat].

Structure the cadence day-by-day, alternating between email, call, and LinkedIn (max [number] touches). For each touch: channel, objective, and full drafted content (complete emails, 30-second call scripts, LinkedIn messages).

Rules: each touch must provide a new angle, never use "just following up"; emails must be under 90 words; the sequence ends with a clean break-up message that leaves the door open. Output format: table of day / channel / objective, followed by numbered content blocks.

Draft a cold call script for a sales rep at [company] calling [target title] at [type of company]. We sell [offer]. Common problem for this target: [problem]. Call objective: [objective, e.g., 20-minute meeting].

Structure: an honest opening that states the purpose in one sentence (no "is this a bad time?"), a specific reason for the call linked to their context, a hook question about the problem, and a proposal for the next step.

Add branching paths for the 5 most common reactions: "I don't have time," "send me an email," "we already have a provider," "I'm not the right person," and hostile silence. For each, provide the exact response in natural spoken English and the criteria for hanging up politely rather than pushing. Total main script length: max 30 seconds of speech.

You are a phone prospecting coach. I need to reach [decision maker's title] at [type of company] and I constantly hit the gatekeeper or assistant. Our offer: [offer]. Legitimate reason for my call: [reason].

Give me 5 honest approaches to get transferred: no impersonation ("it's personal," "they're expecting my call" when false), no aggressive techniques. For each approach: the exact phrasing, the context where it works, and how to respond if the assistant asks "what is this regarding?"

Include: how to turn the assistant into an ally (questions to ask them to qualify the account, best time to call back), and 2 alternatives when the phone fails (email to the decision maker mentioning the chat with the assistant, another entry point in the account). Format: numbered list with drafted dialogues.

Draft 3 prospecting voicemails, max 20 seconds each, left by [name and title] from [company] for [target title]. Context: we sell [offer] and solve [problem].

Voicemail 1: first contact, never spoken. Voicemail 2: after an unanswered email (reference it without being accusatory). Voicemail 3: final attempt before closing the sequence.

Rules for each: name and company articulated at the start AND end, one single idea, one concrete element justifying the call ([element: industry stat, client reference, prospect news]), callback number stated slowly, no "hope you're doing well" or jargon. Write the messages word-for-word with pauses in parentheses, and specify the target word count per message.

A prospect from [company] hasn't replied for [duration]. History: [summary of previous exchanges and last signal of interest]. Our offer: [offer]. Identified pain point: [pain point].

Build a follow-up plan over [duration, e.g., 6 weeks]: number of touches, increasing intervals, and channel for each touch.

For each follow-up, draft the full message with a mandatory new value add: a useful resource on their pain point, a comparable client case, a different angle on the problem, or a short question that is easy to answer in one word. Banned: "just checking in," "did you have time to look at this?", any guilt-tripping.

End with a break-up message: close professionally, give a reason to return, and ask if another contact is more relevant. Format: table of day / channel / angle, then drafted messages.

Draft the break-up email that ends a prospecting sequence that received no response. Sender: [name and title] from [company]. Recipient: [title] at [target company]. History: [number] messages sent over [duration], topic: [problem and offer].

Constraints: 70 words maximum, calm and non-accusatory tone, clearly state that you are stopping the outreach, restate the value you thought you could provide in one sentence, leave a simple exit (reply "not now" or point to the right person), zero passive-aggressive language (e.g., "I assume this isn't a priority" is banned).

Provide 3 variants: neutral professional, slightly humorous, and a very short 40-word version for LinkedIn. Add 2 subject lines under 35 characters for each variant.

Draft a reactivation email sent by [name and title] from [company] to a dormant former client. Context: they bought [product or service] [duration] ago, the relationship stopped because [reason: project end, contact change, dissatisfaction, budget]. Since then, at our company: [relevant updates for them].

Structure: acknowledge the time passed without being heavy-handed, recap the work done together in one sentence, give the real reason for reaching out (a new update or change that affects them, not "I was cleaning my contacts"), and propose a short chat with a specific agenda.

Constraints: 100 words maximum, no guilt-tripping or over-enthusiasm. Provide a variant for cases where the relationship ended poorly: take ownership of the past in one sentence. Add 3 subject lines.

A business signal just appeared for a target account: [signal, e.g., funding, hiring a key role, new office, executive appointment, earnings report]. We are [company], we sell [offer], and this signal is relevant because [link between signal and your offer].

Help me leverage this signal: first, verify the strength of the signal-offer link and tell me honestly if it feels forced. Then draft the outreach for 2 channels: a max 80-word email and a 300-character LinkedIn message, addressed to [target title].

Rules: mention the signal in one factual sentence without empty praise (e.g., "congrats on the great round" is banned), immediately link the signal to a concrete problem this change will create for them, and end with a low-friction question. Format: verdict on the link, then the 2 messages.

Help me ask for referrals from [satisfied client], a client of [company] for [duration], who achieved [concrete result with us]. I am looking for introductions to [type of contacts sought, e.g., counterparts in other subsidiaries, industry peers].

Draft: the verbal phrasing to slip the request into the end of a client meeting (2 sentences, no solemnity), the follow-up email that makes it easy for them to act with a pre-written message they can just forward, and the thank-you message once the introduction is made.

Rules: ask for a specific introduction rather than a vague "if you know anyone," make it easy for them to say no without guilt, and never tie a benefit to the referral without stating it explicitly. Add the 2 best moments in the client relationship to make this request and why.

We sell [offer] and our deals involve 3 personas: [persona 1, e.g., CEO], [persona 2, e.g., Ops Manager], [persona 3, e.g., CFO]. Our current generic message: [current message].

For each persona, produce: their dominant concern regarding our product category, what annoys them in sales pitches they receive, the hook that actually matters to them, a max 80-word prospecting email written in their language, and the 2 metrics to discuss with them (only those our product actually influences: [actually influenced metrics]).

Constraint: the 3 emails must be so distinct that it's not obvious they sell the same product to the same company. Format: one sheet per persona, then a one-line comparison table per dimension.

I have a first meeting with [title] from [target company] in [timeframe]. We sell [offer]. What I already know: [known info]. Sources available: company website, LinkedIn, press, [other sources].

Build my 30-minute prep plan: the 6 priority pieces of info to find (where to look and how many minutes to spend on each), how to turn each piece of info into a discovery question or a hypothesis to validate during the meeting, and the 2 problem hypotheses I should formulate based on [known info].

Produce a one-page meeting sheet: account context, hypotheses, 5 prioritized questions, meeting objective, and the ideal next step to propose. Rule: no questions that can be answered by their website (they kill credibility).

Draft the recap email to send to [contact] after our meeting today. Discussion points: context discussed [context], identified problems [problems], objections or reservations expressed [reservations], agreed next step [step and date].

Structure: one-line thank you, summary of key points using the prospect's own words (no jargon), restatement of the main pain point in a sentence they could forward to their boss, recap of the next step with date and ownership, and one open question if critical info is missing: [missing info].

Constraints: 120 words maximum, no new product pitching not discussed in the meeting, ready to send within the hour. Add a short 60-word version for informal meetings.

You are a Sales Ops Manager. Create the standard CRM note template for the sales team at [company], selling [offer] with an average sales cycle of [duration].

The template must allow any colleague to take over the deal without a handoff call. Sections: 2-line account context, contacts met with their role in the decision, expressed problem and impact (client quotes in ""), decision criteria and timeline, competitors mentioned, identified risks, and dated next step with owner.

Include: the length rule (readable in 90 seconds), 3 examples of bad notes vs. their useful rewrites (e.g., "good meeting, follow up" turned into a useful note), and the list of structured CRM fields to update alongside the note for reliable reporting. Format: ready-to-copy template, then examples.

You are a social selling expert. Rewrite my sales LinkedIn profile: my prospects check it immediately after my first message, so it must reassure them and make them want to reply.

My current profile: headline [current headline], about section [current about]. I sell [offer] from [company] to [target]. Verifiable results I can cite: [real client results, authorized data].

Produce: a headline focused on the problem I solve for my target (not "Passionate Business Developer"), a max 5-line about section written for the prospect googling me (what they gain by replying, with proof), current job description in 3 factual bullets, and 3 ideas for featured content that build credibility ([existing resources: case study, article, webinar]).

Banned: "passionate," "expert," superlatives without proof, internal jargon. Format: each block ready to paste with character counts.

Draft a LinkedIn post for [your name, title] from [company]. My target: [target title] in the [industry] sector. Subject: [field observation, common client mistake, lesson from a recent anonymized case].

Structure: a first line that states the problem exactly as the target experiences it (they decide whether to read more), development in short sentences with an anonymized concrete example, a clear stance (a post that doesn't take a side adds no value), and a final question inviting those concerned to react.

Constraints: 150 words maximum, no mention of the product or sales links (selling happens in private, not in the post), no made-up numbers: only [available verifiable data] or clearly stated estimates, no sob stories or "I failed. Then I realized." Provide 2 hook variants and the first comment to post to start the discussion.

I am attending [trade show or event] on [date] for [company] ([offer], target [target]). Format: [booth, simple visitor, speaker]. Goal: [number] qualified contacts.

Build my 3-phase plan. Before: how to identify the [number] priority accounts from the exhibitor/speaker list and the short message to book on-site meetings in advance. During: a natural conversation hook that qualifies in 2 questions without feeling like an interrogation, the rule for taking quick notes on each contact (3 fields: context, interest, agreed next step), and how to politely cut short a conversation with an off-target visitor. After: the follow-up email at D+2 that references the specific conversation ([noted element]) and proposes the agreed step, plus a variant for a brief encounter.

Output format: before checklist, during scripts, after emails, all drafted and customizable with brackets.

Draft the invitation sequence for [company]'s webinar: "[webinar title]", on [date and time], hosted by [speakers]. What participants will know how to do afterward: [2 or 3 concrete takeaways]. Target: [target title], including some already in our CRM ([existing relationship: contacted prospects, clients, strangers]).

Produce: the initial invitation email (max 100 words, focused on participant learning, not us; 3-bullet agenda; single registration button), a D-3 follow-up with a new angle (a question the webinar will answer), a short D-0 reminder, and 2 post-webinar emails: replay for no-shows, and next steps for attendees with a 1-on-1 chat proposal linked to a question asked during the session.

Rule: differentiate the tone between known prospects and strangers. Provide 3 subject lines per email, under 45 characters.

Build a nurturing sequence for prospects of [company] who said "not now" or "contact me in a few months." Our offer: [offer]. Their underlying problem: [problem]. Existing resources: [available content: case studies, articles, templates, webinars].

Design 5 emails over [duration, e.g., 8 weeks]: each email must provide standalone value (the prospect should gain something even if they never buy), one topic per email, max 80 words of text before the resource.

For each email: subject line, full text, attached or linked resource, and the reply signal that justifies pulling the prospect out of the sequence for direct contact. The final email asks the sales question again, simply and directly.

Rules: no fake personalization ("I was just thinking of you"), no purely promotional content disguised as advice. Format: sequence table followed by numbered emails.

Act as a Sales Director challenging their team during a pipeline review. Vet this deal using the [method: MEDDIC, BANT, or other] grid:

Deal: [description: account, proposed offer, amount, current stage, history, contacts met, planned next step].

For each criterion: what I know (with proof: who told me, when), what I assume without proof (mark clearly as assumption), and what I don't know. Be ruthless about the difference: "they seemed interested" is not proof.

Conclude with: the deal health score with justification, the 3 most critical missing pieces of info, the exact question to ask to get each (phrased naturally, not as an interrogation), and your frank recommendation: push, requalify, or remove the deal from the forecast. Format: table by criterion then summary.

Help me build the business case for [offer] for [prospect]. Their numbers, collected during discovery: [prospect data: volumes, current costs, time spent, observed rates]. Our price: [price]. What our solution changes concretely: [improvement mechanisms, with levels observed at comparable clients if available: [references]].

Build the calculation: current cost of the problem (using ONLY their numbers), expected gain with a low and median hypothesis (never just a best-case scenario), total cost of our solution in year one (license + implementation + internal time), and break-even point in months.

Rules for honesty: every assumption displayed and editable, no numbers pulled out of thin air, flag what is missing to make the calculation more reliable. Format: step-by-step calculation table, 3-sentence summary my champion can repeat internally, and 2 likely objections to this calculation with responses.

Prepare my [product] demo flow for [prospect], duration [duration]. Discovery done: their priority problems [ranked problems], who is attending [participants and roles], their current tool [current tool or process].

Build the demo backward from their problems: start with a recap of what we understood about their situation (out loud validation), then max 3 sequences, each showing how the product solves ONE of their problems, in their vocabulary, using example data that mirrors their business ([context for demo data]). Never do a generic feature tour.

For each sequence: the problem restated in one sentence, the step-by-step scenario shown, and the validation question asked to the audience. Plan for: Plan B if the tech fails, the 2 likely trap questions from [most skeptical participant], and the closing with the next step proposed before hanging up. Format: timed outline.

We received an RFP from [issuer] for [subject of consultation]. Our offer: [offer]. Deadline: [date]. Our position: [context: incumbent, challenger, unknown to client; any contacts in account].

Help me first with the go/no-go: 6 questions to answer honestly before investing days in a response (including: do we have access to anyone to ask questions? Does the spec seem written for a competitor?), with a decision grid.

If go: build the response skeleton: follow the exact structure required by the issuer, restate their needs in their words in the intro, answer every requirement with proof (reference, method, verifiable stat), clearly admit what we don't do rather than burying it, and a final review checklist (admin compliance, consistent pricing, no untenable promises). Format: go/no-go grid + detailed proposal outline.

Draft a client case study for [company] based on these elements: client [name and context, with permission to publish], starting situation [initial problem and its cost], solution implemented [what was done, duration], measured results [real client-validated data], available verbatims [client quotes].

Structure: headline with the main result, summary of 3 key stats, the context told from the client's perspective (their words, their daily life before), the decision trigger, implementation without fluff (including one real challenge met and solved: perfection sounds fake), quantified results with their measurement period, and the final quote.

Rules: only use provided data, no extrapolation; the client is the hero, not us; 400 words max. Also provide: a 100-word short version for proposals, and 2 LinkedIn posts derived from the case.

Create a battlecard for [company] vs. [competitor]. What we know from verifiable sources: [factual elements: public positioning, known pricing, features, client types]. Our real strengths: [strengths with proof]. Our honest weaknesses against them: [weaknesses].

Structure the sheet: when this competitor appears in our deals (prospect profiles where they are strong), where THEY legitimately win (denying this kills sales credibility), where WE win with proof, questions to ask the prospect to reveal competitor limits without badmouthing (let the prospect discover it, exact phrasing), and responses to the 3 most frequent comparisons: [heard comparisons].

Rules: no direct badmouthing or unverifiable claims, clearly distinguish facts from our interpretation. Format: one-page sheet, updatable, with the date of info.

You are a sales negotiation coach. My offer: [offer] at [price]. My target: [target]. The "it's too expensive" I hear most often happens [moment: at price reveal, after proposal, at the very end].

Teach me to handle this objection: first, 3 questions to diagnose what it really means (no budget at all, more expensive than a specific alternative, value not yet perceived, or a negotiation ritual), with exact phrasing.

Then, the response for each diagnosis: requalify or exit professionally if no budget exists, compare real scope if an alternative is present (questions to expose differences without badmouthing), return to quantified impact if value isn't perceived ([available value elements]), and hold the price in negotiation by trading every concession for a counter-concession.

Banned: lowering price without a trade, justifying by listing costs. Format: decision tree + drafted dialogues.

My prospect replies "we already work with [type of competitor] and we're happy with them." Context: I sell [offer] for [company], and this objection arrives [moment: cold call, meeting, after demo].

Give me the method: why this response is often a protective reflex rather than a status report (without assuming the prospect is lying), then the exact phrasing to handle it in 3 steps: validate their choice without flattery (attacking their provider is attacking their decision), ask ONE opening question without being aggressive (on what has changed since their choice, what they would improve, or the last time they benchmarked), and propose a useful fallback: stay as a point of comparison for the next renewal, with a concrete gesture ([resource: benchmark, diagnostic, audit]).

Provide 3 complete dialogues based on when the objection occurs, and the signal that indicates I should just move to the next account.

My prospect is asking for a discount: [exact request, e.g., 20% off, match a competitor's quote, a gesture to sign this month]. Deal: [offer, amount, stage, stakes for us]. My real wiggle room: [allowable margin and internal conditions].

Build my response: first, understand the request (question to see if it's a ritual, a real budget constraint, or a comparison: exact phrasing), then the rule of counter-concessions: every concession is traded (longer commitment, volume, upfront payment, public reference, signature by [date], reduced scope), with a table of my possible counter-concessions ranked by cost to us and value to them.

Draft 3 standard responses: holding the price elegantly when I can't move, the concession-trade phrased positively, and refusing to match an incomparable competitor quote. Banned: immediate discount that devalues the starting price, "I'll check with my boss" as a reflex. Format: drafted dialogues + counter-concession table.

Prepare my final negotiation with [prospect] for [offer]. Status: [history: proposal sent, feedback received, points of agreement and friction]. Their negotiator: [contacts and roles, including any professional buyer]. My internal limits: [floor price, non-negotiable terms, required approvals].

Build the plan: my objectives per variable (price, duration, scope, payment, clauses) with target, floor, and opening position for each; list of possible concessions ranked by real cost to us and perceived value to them (always trade, never give); their likely requests with my prepared response for each; the 3 deadlock scenarios ([anticipated hard points]) and the planned exit for each, including a defined walk-away position.

Include: the meeting opening checklist (revalidate the scope of agreement BEFORE negotiating the rest), and phrases to pause rather than yield under pressure. Format: one-page negotiation sheet.

Build a Mutual Action Plan (MAP) to share with [prospect] for the [offer, amount] deal. Client objective: be operational by [target date]. Status: [current stage, remaining hurdles: legal, security, budget, signature]. Known contacts: [contacts and roles].

Produce the reverse timeline from the target date: each step with its owner (client side AND our side), realistic duration, and deadline, including steps prospects always forget ([frequent steps: contract review, vendor setup, DPA, internal PO]).

Draft the email proposing this plan to the champion: present it as a tool to hit THEIR date, not as a pressure tactic.

Explain how to use it as a detector: a date that slips without a new date, a step without a client owner, or a refusal to share the validation process are signals to address. Format: plan table + email + signal list.

My sales proposal sent to [prospect] on [date] remains unanswered. Content: [offer, amount]. Last exchange: [context: warm meeting, explicit request for proposal, mentioned deadline]. What was supposed to happen: [agreed step].

Draft 3 follow-ups spaced by [interval]. Follow-up 1: remind them of the agreed step and propose a short slot for questions (no "did you have time to read?", which is patronizing). Follow-up 2: add a new element that enriches the proposal (clarification, client example on a discussed point, response to an anticipated objection: [available element]). Follow-up 3: ask the frank question about the decision status, giving permission to say no ("if the project is postponed or you're going elsewhere, just let me know so I can organize my time").

Constraints: 80 words max per follow-up, peer-to-peer tone, no artificial pressure (fake deadlines, fake scarcity). Add the best channel for each follow-up and why.

My entire deal with [account] rests on one contact: [current contact's title]. Deal: [offer, amount, stage]. The decision will likely involve: [assumed roles: leadership, finance, users, procurement, IT].

Help me expand without offending my contact: first, the mapping to complete (for each assumed role: their likely part in the decision, their concerns, the question to ask my contact to confirm their existence and influence), then 3 expansion maneuvers with exact phrasing: ask my contact to organize the expansion themselves (the ideal way, phrased to empower them rather than bypass them), propose content that naturally justifies other participants (workshop, deep-dive demo, security review), and direct contact with another decision maker as a last resort, with a message that doesn't undermine my champion.

Include: signals that my contact is intentionally blocking access, and what to conclude from it. Format: mapping + scripts.

My contact at [prospect], [title], is sold on [offer] but must convince [decision maker: leadership, board, finance]. What matters to this decision maker: [known or assumed priorities]. Elements validated together: [quantified problem, solution, price, timeline].

Prepare the kit my champion can forward as-is: a summary email written ON THEIR BEHALF (first person, in THEIR interest: their team's problem, the cost of doing nothing, the solution studied, the investment, their recommendation, and the requested decision; 150 words, zero sales jargon: this must not sound like it came from a vendor), a one-page talking points sheet with the 3 questions the decision maker will likely ask ([anticipated questions]) and factual answers, and a proposal for a time slot where I am available if they prefer I present.

Rule: everything must be defensible by the champion alone, without me in the room. Format: email + Q&A page.

Analyze this lost deal: [account, offer, amount, cycle length, winning competitor if known, reason given by prospect]. History: [timeline: stages reached, contacts met, friction points, delays between stages].

Conduct the post-mortem by looking past the stated reason (polite "too expensive" often hides something else): reconstruct the chronology, flagging moments where the deal likely shifted, compare each stage to best practices (real qualification, access to decision maker, active champion, early competition identification), distinguish between sales execution (actionable), product/pricing (feedback), and factors outside our control (accept).

Produce: the 3 most likely causes ranked by plausibility with supporting evidence, the actionable lesson for future deals of this profile, and the message to send to the lost prospect: elegant thank you, open door, and a request for frank feedback in one question. Do not conclude anything the provided history doesn't support.

Debrief this won deal: [account, offer, amount, cycle length, defeated competitors]. Timeline: [history: lead source, stages, key moments, contacts, objections handled].

Look for what is REPEATABLE: what actually triggered the deal (source, signal, timing) and can we systematize this detection? What moments shifted the decision in our favor according to the facts? What account profile and context does this victory outline (compare to our ICP: [current ICP]: does it confirm or correct the targeting?)? What did we improvise that should become a standard (content created, objection response, demo format)?

Produce: a one-page victory sheet (context, trigger, decisive factors, client verbatim if available), 2 concrete actions to repeat (to integrate into the playbook), and questions to ask the client now that they've signed to understand their decision from the inside (phrased, max 5). Flag what the provided timeline doesn't allow for a conclusion.

Prepare an upsell proposal for [client], a client of [company] for [tenure] on the [current offer, amount]. Usage signals: [real signals: hit limits, requested features, business growth, telling support tickets]. Higher offer: [target offer, amount, what it unlocks].

First, verify the opportunity: test each signal against the question "what does the client gain from this?". If the upsell primarily serves our revenue, say so and stop there.

If legitimate: draft the proposal message starting from THEIR observed usage ("you reached X last month"), show concretely what would change for them with the higher offer on THEIR use cases, state the price differential clearly, and propose discussing it during the next check-in rather than as a hard sell. Include: the best time to send this message ([relationship context]), and the response if the client declines (accept gracefully, note the signal for later).

Identify and formulate a cross-sell opportunity for [client], who already uses [current product] from [company]. Our catalog: [other offers]. What I know of their context: [elements: organization, current projects, problems mentioned in check-ins, other known vendors].

First, the sorting: for each offer in the catalog, evaluate the real link to an expressed or observable need for THIS client (strong, hypothetical, non-existent), and only keep the strong link; if there are none, say so: a forced cross-sell damages account trust.

For the selected offer: draft the approach angle starting from the observed adjacent problem ("you mentioned [problem] to me..."), the proposal for a short chat with the right person if it's not my usual contact, and the setup that reduces their trial risk ([levers: pilot, reduced scope, short commitment]). Format: catalog sorting table, then drafted message and 2-step next plan.

Prepare the renewal for [client]'s contract expiring on [expiry date]. Current contract: [offer, amount, duration, special terms]. Account health: [real usage, any incidents, perceived satisfaction, contacts and their turnover, known competitor outreach].

Build the prep plan to launch [timeframe before expiry, e.g., 4 months before]: the factual value report to present (what the client achieved during the period, quantified with THEIR data: [available data]; never a report that lists our deliveries without their results), the risk diagnostic (fragility signals in the account health listed above, to be addressed BEFORE the sales discussion), the renewal strategy (simple renewal, anticipated renegotiation, expansion to propose) with the position on a potential price increase ([pricing context]) and its justifications.

Draft: the email that opens the discussion without sounding like an administrative deadline, and the outline for the review meeting. Format: dated plan + drafted content.

Draft the price increase announcement for [company]: [scale of increase, affected offers, effective date]. Real reason: [reason: costs, product investment, correcting historically low pricing]. Affected clients: [segments, including legacy clients with special terms]. Planned notice: [timeframe], contractual obligations: [notice clauses to respect].

Draft the announcement email: full info in the subject line and first paragraph (amount or percentage, date, who is affected: no burying the increase in the 3rd paragraph), honest justification in 2 sentences without whining or over-justifying, what isn't changing and what the client has gained since ([delivered improvements, factual]), and the open door: a named contact to discuss it.

Include: the variant for legacy clients with a larger gap, the response script for 3 expected reactions (threat to leave, request for freeze, request for detailed explanation) with wiggle room [allowable margin], and the sending schedule relative to the effective date.

Structure the weekly pipeline review for the sales team at [company] ([number] reps, average sales cycle [duration], pipe stages: [stages]).

Design the ritual for max 45 minutes: required prep BEFORE the meeting (each rep updates their deals and flags where they need help: the meeting is for deciding, not updating the CRM live), the order of deal review (by exception: those that moved, those stalling beyond [stagnation threshold per stage], those where a decision is needed; never the exhaustive list), and for each discussed deal, the 3 ritual questions: what changed since last time? What is the dated next step on the CLIENT side? What could cause us to lose this deal?

Include: hygiene rules (a deal without a dated next step leaves the forecast, a deal pushed week-to-week [number] times is requalified or closed), and the 5-line recap template. Format: outline + displayable rules.

Help me build the sales forecast for [period] for [company]. Current pipeline: [list of deals: amount, stage, dated next step or not, recent history]. Historical conversion by stage if known: [observed rates or unknown].

Classify each deal into a commitment category using OBJECTIVE criteria: Committed (verbal agreement obtained, signature process identified, date set), Probable (decision maker met, budget confirmed, dated next step), Possible (real interest but one major criterion missing: which one), Out of Forecast (no dated next step, prolonged silence, deal-breaker identified). For each deal: its category, the criterion placing it there, and what would move it up a category.

Produce: the forecast by category (no made-up weighting: if I haven't provided historical rates, don't invent them, state what should be measured), the 3 deals whose classification is most debatable with the question to settle for each, and the defensible summary sentence for my leadership. Format: table + summary.

Organize a CRM cleanup for the sales team at [company]. Tool: [CRM used]. Symptoms: [observed problems: zombie deals, duplicates, empty fields, misused stages, false forecast]. Volume: [number of open deals, accounts, contacts].

Build the one-week operation: day-by-day, what to process and with what decision rule: deals with no activity for [threshold] (last-chance follow-up or close-lost with reason), account/contact duplicates (merge rule: which record survives), mandatory fields never filled (fill them or delete them: a dead field is clutter), pipe stages (redefinition with objective entry criteria per stage).

Include sustainable rules to prevent recurrence: the 5 truly mandatory fields and why only them, the 20-minute monthly hygiene review, and what the manager monitors. Format: day-by-day plan + rules + announcement message to the team explaining the "why" without blame.

Draft my monthly sales activity report for [month] for my leadership. My numbers: [real data: sales closed, pipeline created, deals lost, prospecting activity, month's goal and attainment]. Highlights: [events: big win, notable loss, market signal, recurring bottleneck].

Structure: 3-sentence summary (result vs. goal, main event of the month, requested decision if any), numbers in a short table with comparison to previous month and goal (only provided numbers: only calculate % if both terms exist), honest analysis (why it's above or below: distinguish market conditions, execution, and inherited pipeline), key deals for next month with their tipping point, and explicit requests (arbitration, resource, help on an account).

Rules: a gap is explained without three paragraphs of justification, a success is factualized without triumphalism, the report is readable in 3 minutes. Format: one page, titled sections.

Sharpen my 30-second pitch. I am [title] at [company]: we help [target] to [achieved result] through [mechanism in one sentence]. Proof: [verifiable element: recognizable client, authorized stat, tenure]. My current pitch: [current pitch if existing].

Build the pitch on the problem-result-proof structure (the product comes last, if at all): 60 words max, no buzzwords ("innovative solution," "leader," "revolutionize"), phrasing that a layperson understands and can repeat to someone else: that is the true test.

Tailor it for 3 contexts: meeting a potential prospect at a professional event (end with a question about THEM), opening a cold call (15-second version), and responding to "so, what do you do?" at a dinner (version stripped of business jargon).

Include: the 2 reactions that show the pitch works, the 2 that show it fails (polite smile, "oh, like [big player]?"), and how to iterate based on these signals.