Useful prompts for work that needs doing.

Write a concise reply to a prospect who said, "Your price is too high." Use only the information provided below. Do not invent results, testimonials, customer examples, competitor claims, savings, or facts.

Return exactly four numbered paragraphs:
1. Acknowledge the cost concern and accurately reflect the stated constraint: {{budget_constraint}}.
2. Reconnect the price to the specific value metric or ROI driver: {{value_metric}}. Refer to {{product_service}} by name. If a competitor was mentioned, address {{competitor_name}} only using facts supplied here; otherwise do not introduce a comparison.
3. Offer one or two non-discount options, prioritizing scope changes, phased delivery, or timing adjustments. Do not offer a price discount or invent payment terms. Keep the options relevant to {{product_service}}.
4. State a clear decision deadline tied to the required project start: {{project_start_deadline}}. If an exact date is supplied, use it explicitly; if not, do not invent a calendar date, but clearly state that a decision is needed by the stated start deadline.

Use direct business language with no greeting, sign-off, hype opener, politeness padding, social proof, or explanation of your process. Produce only the four numbered paragraphs, ready to send after one light edit.

Write a concise, ready-to-send post-meeting thank-you note using the details below. Return only the finished note, with no analysis, labels, follow-up questions, generic placeholders, or invented details.

Use this fixed format:
1. Brief greeting addressing {{prospect_name}}.
2. One short paragraph specifically referencing what they said: {{specific_point}}.
3. One clear sentence stating the key takeaway: {{key_takeaway}}.
4. One clear sentence confirming the agreed next steps: {{agreed_next_steps}}.
5. A warm personal closing that naturally includes this personal touch or shared interest: {{personal_touch}}.
6. A concise sign-off.

Keep the note professional, natural, and brief enough to require no more than one light edit. Avoid excessive politeness, vague claims, and repetition.

Write a concise, neutral budget conversation starter for {{prospect_name}} at {{company_name}}. Create exactly 4 sentences: sentence 1 connects {{primary_pain_point}} to the urgency implied by {{decision_timeline}}; sentence 2 states that budget alignment is practical and non-judgmental; sentence 3 presents clear low-, medium-, and high-budget options, using {{estimated_budget_level}} as the likely starting point; sentence 4 proposes a specific next step. Do not use a hype opener, politeness padding, pressure, unsupported claims, or questions requiring clarification. Return only the finished message.

Create a concise executive summary of the sales proposal using only the information provided below. Produce approximately 350–450 words, suitable for a one-page equivalent and usable after one light edit. Do not ask follow-up questions, add hype, use politeness padding, or invent facts, savings, outcomes, testimonials, or commitments. If a required detail is unavailable, write "Not specified in the proposal."\n\nUse exactly these five labeled sections in this order, with no additional sections:\n\nProblem\nState the customer's business problem, impact, and urgency based on the proposal.\n\nSolution\nExplain what is being proposed and how it addresses the problem.\n\nInvestment\nSummarize the pricing, fees, commercial terms, and any relevant assumptions.\n\nTimeline\nSummarize the implementation or delivery schedule, milestones, and dependencies.\n\nNext step\nState the agreed or proposed immediate action, owner if specified, and timing if specified.\n\nSource proposal and context:\n{{proposal_context}}\n\nKey customer problem:\n{{customer_problem}}\n\nProposed solution details:\n{{proposed_solution}}\n\nInvestment and pricing information:\n{{investment_pricing}}\n\nProject timeline and agreed next steps:\n{{timeline_next_steps}}\n\nUse a professional, direct tone. Preserve important numbers, dates, conditions, and distinctions. Keep each section focused and do not repeat the same information across sections.

Write one concise referral request message for an account manager to send to a satisfied customer. Use this fixed format and output only the message:

Subject: Quick intro request

Hi {{customer_name}},

Given the success you've achieved with us, I thought of someone in {{target_role}} who may be a fit because {{target_fit_context}}.

I'm looking for an introduction to a {{target_role}}. Would you be open to a quick introduction via {{outreach_method}}? It should take about 30 seconds.

As a thank-you, I can provide {{referrer_value}}.

Keep the message natural, specific, and concise. Do not add hype, sales jargon, exaggerated claims, fabricated details, private data requests, or follow-up questions.

Write one concise meeting-request email to {{recipient_name_role}} about {{meeting_purpose}}. Explain why now using {{timing_reason}} and why this recipient specifically using {{specific_value}}. Include these three exact time options: {{time_slots}}. State that the meeting will last {{meeting_duration}}. Include a clear request to choose one option or propose another. Use this exact format:
Subject: [specific subject line]

Hi [recipient first name],

[Email body]

[Sender name]

Do not ask follow-up questions, invent facts, add hype, use fabricated proof, include excessive politeness, or add commentary outside the email.

Write one concise, copy-ready sales script of exactly 3 sentences using the information below. Sentence 1 briefly acknowledges the current topic to show listening. Sentence 2 uses a smooth transition and clearly restates the original conversation goal. Sentence 3 proposes the desired next step. Adapt the wording to the relationship stage and preferred tone. Use only the provided information; do not invent details, ask for clarification, add hype, or include headings, explanations, or politeness padding.

Original conversation goal: {{original_goal}}
Current off-topic subject: {{off_topic_subject}}
Relationship stage: {{relationship_stage}}
Desired next step: {{desired_next_step}}
Preferred tone: {{preferred_tone}}

Personalize the outreach message using only the information provided below.

Prospect: {{prospect_name}}
Company: {{company_name}}
Job title: {{prospect_job_title}}
Recent company news or trigger: {{recent_company_news_or_trigger}}
Unique fact or connection: {{unique_fact_or_connection}}
Base template:
{{base_template_text}}

Return only the finished message, ready to send. Preserve the base template's core purpose and structure while naturally integrating the prospect's role, company, and one or two relevant supplied details. Use the unique fact or connection only if it is clear and appropriate. Do not invent facts, testimonials, results, relationships, or social proof. If a detail is vague or unsupported, omit it rather than guessing. Remove all placeholders, brackets, personalization notes, greetings that do not fit, hype openers, and excessive politeness padding. Keep the message concise and suitable for the indicated outreach context. Do not include a subject line, explanation, analysis, or quotation marks around the message.

Write a concise, non-pushy upsell conversation opener for an account manager contacting {{customer_name}} through {{preferred_contact_channel}}. Acknowledge the value they receive from {{current_product_or_service}}, connect {{specific_usage_metric_or_success_story}} to why {{target_upsell_product}} could matter, and suggest one easy next step. Return no more than three sentences, with clear language, no hype, pressure, fear-based messaging, or generic politeness padding.

Create a ready-to-copy first sales discovery interview script for a new prospect using the context below.

Target buyer role/title: {{target_buyer_role}}
Prospect industry: {{prospect_industry}}
Prospect company size: {{prospect_company_size}}
Primary product value proposition: {{primary_product_value_prop}}
Specific meeting goal: {{specific_meeting_goal}}

Return exactly 8 direct discovery questions, grouped into exactly 4 intent categories with 2 questions per category. Use these categories: Current Situation, Challenges and Impact, Priorities and Evaluation, Decision and Next Steps. Tailor every question to the buyer, industry, company size, value proposition, and meeting goal. Make questions specific, neutral, non-leading, and useful for a first conversation. Avoid conversational filler, introductions, explanations, assumptions, hype, yes/no questions where an open question is more useful, and invented facts. Return only the four category headings and the 8 numbered questions, with no closing note or commentary.

Draft a concise proposal opening for {{client_or_industry}} using the supplied information. Write exactly two sentences: sentence one should demonstrate understanding of {{core_pain_point}} and its business impact, and sentence two should hint at {{unique_value_proposition}} while connecting it to {{specific_desired_outcome}} in the context of {{deal_stage_and_relevant_context}}. Make it specific, credible, and usable after one light edit; do not add greetings, hype, unsupported claims, testimonials, social proof, private-data assumptions, or details not provided. Output only the two-sentence opening.

Create a practical stakeholder map for the sales opportunity below. Use only the information provided and reasonable role-based inferences. Do not invent names, email addresses, phone numbers, reporting lines, or personal contact details. Mark unknown information as "Unknown" and distinguish known contacts from inferred stakeholders.

Opportunity: {{opportunity_name}}
Target company: {{target_company}}
Known contacts: {{known_contacts}}
Product or service: {{product_service}}
Deal stage: {{deal_stage}}
Timeline: {{timeline}}

Return exactly this format:

OPPORTUNITY SUMMARY
- Opportunity: [name or ID]
- Company: [company]
- Product/service: [offering]
- Stage: [stage]
- Timeline: [timeline]

STAKEHOLDER MAP
| Stakeholder or role | Likely position | Influence and interest | Evidence or assumption | Best realistic way to reach them |
|---|---|---|---|---|
[One row per known or likely stakeholder]

SPONSOR ASSESSMENT
- Most likely sponsor: [one named contact if supported; otherwise role]
- Why: [brief evidence-based rationale]
- Sponsor confidence: [High, Medium, or Low]
- Sponsor validation question: [one question the Account Executive can ask]

PRIORITY ACTIONS
1. [Next action for the highest-priority stakeholder]
2. [Next action for validating the sponsor]
3. [Next action for identifying any critical missing stakeholder]

Use practical contact routes such as an introduction from a known contact, an executive-to-executive request, a discovery call, a procurement or security process, or a role-based outreach path. Do not recommend scraping private data or guessing direct contact details.

Draft one concise follow-up email to {{prospect_name}} using only the information provided below. Write the final email only—no analysis, notes, placeholders, or commentary. Use exactly four short paragraphs in this order: 1) Reference: naturally mention the original outreach and that it was sent {{days_since_sent}} days ago. 2) Angle: introduce the fresh value proposition from {{new_angle}} without hype, unsupported claims, fabricated proof, or assumptions. 3) Ask: make the specific, low-friction next step from {{desired_next_step}} clear. 4) Out clause: give the recipient an easy, respectful way to decline or indicate that now is not a priority. Keep the email professional, direct, human, and concise. Do not use spammy language, excessive politeness, deception, or invented details. Original outreach message:
{{original_outreach}}

Analyze whether this news is relevant to the prospect and create one concise outreach angle. Use only the information provided; do not invent facts about the prospect, company, article, results, priorities, or relationship. Decide "Yes" only when the headline or summary has a clear connection to the prospect's industry, stated business challenge, role, or company context. Otherwise decide "No". Do not ask follow-up questions. If evidence is limited, state that plainly and keep the outreach conditional.

Return exactly this format:
Relevance: Yes or No
Reason: 1-2 sentences explaining the connection or lack of connection.
Subject: A concise subject line suitable for the selected channel.
Body: A brief, professional outreach message tailored to the prospect, with no hype, fabricated claims, testimonials, or social proof. Keep it usable after one light edit and within 100 words.

News headline or summary: {{news_summary}}
Prospect name and title: {{prospect_name_title}}
Prospect company name: {{company_name}}
Prospect industry or key business challenge: {{industry_challenge}}
Desired outreach channel: {{outreach_channel}}

Generate exactly 3 concise, distinct outreach angles for {{prospect_name}} at {{company_name}}, whose role is {{role_title}} in the {{industry}} industry, using the recent trigger/event: {{recent_trigger}}.

Use this fixed format and no other text:
Company: [One personalized angle tied only to the company name and industry]
Role: [One personalized angle tied only to the prospect's role]
Trigger: [One personalized angle tied only to the recent event]

Make each angle specific, relevant, and ready to paste into a CRM or email draft after one light edit. Do not add an introduction, closing, greeting, hype, or politeness padding. Do not ask questions or require more research. Do not assume access to external data. Do not invent facts, outcomes, testimonials, customers, or social proof. If a detail is not provided, keep the angle appropriately general.

Validate whether the reported sales stage reflects the customer's actual commitment level. Use only the information provided; do not invent facts, quotes, testimonials, stakeholders, or evidence.

Reported deal stage: {{reported_stage}}
Identified stakeholders: {{identified_stakeholders}}
Concrete evidence: {{concrete_evidence}}
Commitment status: {{commitment_status}}

Return exactly these four sections:
Assessment: Accurate, Too advanced, Too early, or Insufficient evidence
Rationale: Explain the assessment using the reported stage, stakeholder coverage, evidence, and commitment status.
Gaps: List the specific missing, weak, or contradictory signals.
Correction or next action: State the CRM stage correction or the single most important action needed next.

Be direct and conservative. Treat unsupported claims as unverified. Do not ask follow-up questions.

Write one ready-to-send value reminder message from an account manager to {{customer_name}}. Use the provided product, specific value, and last interaction date as context: {{product_or_service_name}}, {{specific_value_theyre_getting}}, and {{last_interaction_date}}. Keep it to 1-2 sentences, require no action or reply, and do not ask for a meeting, renewal, next step, or feedback. State only the supplied value without exaggeration or invented details. Avoid hype openers, greetings, pleasantries, and politeness padding. Output only the message.

Generate one ready-to-use sales objection response for {{product_or_service}} using the prospect's exact concern and the relevant value proposition below.

Use this exact 3-part structure and no other sections:
1) Acknowledge: Validate the prospect's concern directly without adding claims.
2) Reframe: Connect {{product_or_service}} and {{relevant_value_proposition}} to the specific concern.
3) Next step forward: Propose one concrete, low-friction action the prospect can take next.

Objection: {{objection_text}}

Use only the information provided. Do not request additional information, invent testimonials or social proof, use hype openers, or add politeness padding. Write concise language that is usable after one light edit.

Convert the supplied prospect criteria into one LinkedIn-compatible Boolean search query string. Use only these field labels: title, industry, companySize, geo, yearsExperience, connectionDegree. Format each populated criterion as field:"value" and join criteria with AND. Omit any optional criterion that is blank or set to Any. Do not invent information, broaden the criteria, ask questions, or include explanations, labels, markdown, or a trailing period. Return the plain text query string only.

Target job title or function: {{target_role}}
Target industry: {{target_industry}}
Target company size: {{company_size}}
Target location: {{target_location}}
Years of experience: {{years_experience}}
Connection degree preference: {{connection_degree}}

Create a concise 5-point company research snapshot for sales outreach using the inputs below.

Company: {{company_name}}
Our solution/product: {{solution_product}}
Target pain point: {{target_pain_point}}

Use this exact structure:
1. What they do: Summarize the company, its market, customers, and primary offering.
2. Recent news: Identify relevant recent developments only when supported by reliable information available in your context. If you cannot verify a development or do not have current information, state that clearly instead of guessing.
3. Their positioning: Explain how the company appears to differentiate itself and compete.
4. Key challenges: Identify plausible business or operational challenges, distinguishing evidence-based observations from reasonable inferences.
5. Why they may need our solution: Connect the likely challenges to {{solution_product}} and {{target_pain_point}} without overstating fit.

Keep the response to exactly five numbered points. Use specific, useful language suitable for a salesperson preparing a cold call or email. Do not use hype openers, politeness padding, generic marketing claims, fabricated facts, invented news, or unsupported certainty. Do not ask follow-up questions; proceed with the available information. Flag important unknowns briefly. Do not recommend contacting anyone or write outreach copy.

Write a voicemail for a prospect who has not replied to two emails. Return exactly 3 lines and no other text. Keep it under 55 words, or about 25 seconds when spoken. Be direct and natural, with no apology or filler. Use all details, briefly compressing the value proposition if needed:
Hi {{prospect_name}} at {{prospect_company}}, this is a follow-up to my {{last_email_date}} email.
I'm calling because {{value_prop}}.
I'll send a calendar invite for {{next_step}}.

Create a practical, evidence-based close plan for the late-stage opportunity using only the information provided below.

Deal status and timeline:
{{deal_status_timeline}}

Identified stakeholders and roles:
{{stakeholders}}

Known objections, risks, and blockers:
{{risks_objections_blockers}}

Prospect's decision criteria or evaluation checklist:
{{decision_criteria}}

Committed next steps and follow-up agreements:
{{commitments}}

Use this exact output structure:

## 1. Close Assessment
State the current stage, decision readiness, timeline pressure, and the most important gap to resolve. Base every point on the provided information. Identify unknowns rather than filling them in.

## 2. Decision Criteria
For each criterion, include: criterion, evidence of status, remaining gap, and action required. Clearly label criteria with insufficient evidence.

## 3. Stakeholders
For each stakeholder, include: name or role, influence in the decision, current position if known, concern or need, and engagement action. Do not infer personal motivations without evidence.

## 4. Dependencies
List internal or prospect-side dependencies that could delay or prevent a decision. For each, include the dependency, responsible party if known, required outcome, and target date if provided.

## 5. Risks and Blockers
For each risk or blocker, include: issue, evidence, likely impact on the deal, mitigation, owner, and deadline where available. Separate confirmed issues from unresolved possibilities.

## 6. Commitments
List every existing commitment, including the agreed action, owner, due date, completion status, and evidence or missing confirmation.

## 7. Action Plan
List the specific actions required to reach a decision, prioritized as Critical, High, or Medium. For each action, include the owner, deadline, intended outcome, and dependency. Use only owners and dates supplied in the inputs; otherwise write "Not specified".

## 8. Recommended Close Path
Give a concise sequence of the next three to five actions, ordered by dependency and urgency. Include the decision milestone that each action supports.

Keep the tone professional, direct, and free of hype. Do not provide generic sales advice. Do not fabricate facts, dates, owners, statistics, testimonials, external research, or stakeholder opinions. Do not assume access to tools or information outside the provided inputs. Make the plan usable after one light edit.

Create a concise sales call brief using only the information provided below. Do not request more information, invent facts, add hype, or include introductions or closing remarks.

Company and industry: {{company_name_industry}}
Contact person and role: {{contact_name_role}}
Previous conversation summary: {{conversation_summary}}
Primary call objective: {{call_objective}}
Relevant solution details, pain points, and objections: {{solution_and_pain_points}}

Use exactly these three sections and no others:

What You Should Know
- Summarize the most relevant company, contact, conversation, solution, pain-point, and objection context.
- Identify any important unknowns without guessing.

What You Should Ask
- Provide 4 to 6 specific questions tailored to the context and objective.

What You Should Accomplish
- Provide 3 to 5 clear, measurable goals for the call tied to the stated objective.

Keep the brief practical, concise, and usable after one light edit.

Produce a structured, evidence-based close plan for the sales opportunity described below. Use only the supplied information. Do not invent facts, statistics, testimonials, stakeholder motivations, deadlines, dependencies, or decision criteria. Where information is missing, write "Not provided" and identify the specific gap. Distinguish explicit evidence from reasonable inferences.

Opportunity context:
{{opportunity_context}}

Stakeholders and roles:
{{stakeholders}}

Decision criteria or evaluation metrics:
{{decision_criteria}}

Active risks or blockers:
{{risks_blockers}}

Committed next steps and required actions:
{{committed_actions}}

Use exactly these section headers and keep the content concise and actionable:

## Opportunity Snapshot
Summarize the opportunity name, current stage, stated objective, and close status based only on the input.

## Decision Criteria
List each known evaluation metric or approval criterion. For each, state the evidence, current status, and any gap.

## Stakeholders
For each stakeholder, list name, role, stated or evidenced influence, position if known, and the next engagement needed. Mark unknown information as "Not provided."

## Dependencies
List internal or external prerequisites for approval or execution. Identify the source input and whether each dependency is confirmed, inferred, or unresolved.

## Risks
List each active risk or blocker, its likely impact on close, evidence, mitigation action, owner if known, and target date if known. Do not assign owners or dates that are not provided.

## Commitments and Actions
Convert the supplied commitments into a table with columns: Action, Owner, Deadline, Success Signal, and Status. Preserve stated owners and deadlines; use "Not provided" when absent.

## Close Recommendation
State the recommended immediate close motion, the strongest evidence supporting it, the unresolved approval gap, and the next decision checkpoint. Do not use hype or unsupported probability claims.