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.

Extract actionable next steps from the activity notes and return only the following four sections, in this exact order:

Due Today/Tomorrow
- [task] — [due date or "overdue"]

Due This Week
- [task] — [due date, if known]

Can Wait
- [task] — [due date or "no stated deadline"]

Delegate-able
- [task] — Delegate to: [team member]

Rules:
- Use {{todays_date}} to interpret relative dates and classify deadlines accurately.
- Use {{project_deadlines}} as the deadline authority when it conflicts with the notes.
- Use {{team_members}} to identify realistic delegation options; delegate only tasks clearly suited to a named person.
- Extract explicit tasks and implicit tasks only when the notes clearly indicate a required next action. Do not invent tasks, owners, dates, priorities, or dependencies.
- Put overdue tasks in Due Today/Tomorrow and label them "overdue".
- Include each task in only one section. Put delegate-able tasks in Delegate-able rather than another section.
- Keep bullets concise and actionable. Do not add introductions, conclusions, explanations, or conversational filler.
- If a section has no items, write "- None" under that heading.

Activity notes:
{{raw_activity_notes}}

Today's date:
{{todays_date}}

Known project deadlines:
{{project_deadlines}}

Team members available for delegation:
{{team_members}}

Create a focused morning plan from these current work inputs:

Open deals:
{{open_deals_status}}

Active customer issues:
{{active_customer_issues}}

Team priorities:
{{team_priorities}}

Available work time:
{{available_work_time}}

Rank work by urgency, customer impact, revenue impact, deadlines, and dependencies. Make reasonable assumptions without asking questions. Select exactly three priorities, assign practical time blocks that fit within the available work time, and choose the highest-value task for a one-hour contingency.

Return exactly this three-point structure and nothing else:
1. Top 3 priorities today: [Priority A]; [Priority B]; [Priority C]
2. Time block for each: [Priority A — time block]; [Priority B — time block]; [Priority C — time block]
3. One thing if only one hour: [Specific task]

Use concise, action-oriented wording. Do not add an introduction, conclusion, rationale, caveats, or follow-up questions.

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.

Convert the industry report findings below into actionable marketing and sales strategy points for {{buyer_persona}}, aligned to {{product_or_service}} and the goal of {{primary_business_goal}}.

Use the report evidence as the basis for recommendations. Make reasonable assumptions where details are missing, and do not ask follow-up questions. Avoid generic advice, hype, unsupported claims, and invented statistics. Keep each point specific enough to use after one light edit.

Return exactly these four numbered sections and no extra introduction or conclusion:

1. Impact on buyers: Explain how the reported trend changes the needs, concerns, priorities, or buying behavior of {{buyer_persona}}. Cite the relevant finding in plain language.

2. Positioning: State the specific stance {{product_or_service}} should take in response to the trend, including the value or problem it should emphasize.

3. Content angle: Suggest one concrete marketing topic or hook tied to the findings, buyer needs, and {{primary_business_goal}}.

4. Sales talking point: Write a concise script of 2–4 sentences that a sales representative can use with {{buyer_persona}}. Keep it factual and relevant to the report.

Industry report findings:
{{report_findings}}

Draft a concise, honest customer failure notification using only the facts provided. Do not invent details, blame the customer, use jargon, add hype, or include a greeting, sign-off, or politeness padding. Acknowledge the impact directly without excessive apology or defensiveness. State the root cause in plain language, describe the current resolution status and timeline exactly as provided, and include the specific goodwill offer. Return only this fixed structure:

Subject: Automation failure update for {{customer_name_or_id}}
What happened: The {{failed_process_name}} failed because {{root_cause_summary}}.
Current status: {{resolution_status_and_steps}}
Goodwill: {{goodwill_offer_details}}

Keep the notification concise and suitable for sending after one light edit. If the information does not confirm a fix or timeline, state that clearly rather than implying one.

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}}

Create a complete feature release announcement pack using only the information provided below. Do not ask questions, invent testimonials, add social proof, or claim unsupported capabilities. Avoid hype openers and politeness padding. Write clear, specific copy that is usable after one light edit.

Feature description and capabilities: {{feature_description}}
Target customer segment: {{target_customer_segment}}
Launch date and time zone: {{launch_date_timezone}}
Primary value proposition or benefit: {{primary_value_proposition}}

Return exactly these four labeled sections:

1. CUSTOMER EMAIL
Include a subject line, preview text, and an email body ready to send. State what is launching, who it is for, the primary benefit, key capabilities supported by the feature description, and the launch date and time zone. Include a clear call to action without inventing a link; use [CTA LINK] only if a link is needed.

2. SOCIAL MEDIA POST
Write one post of no more than 280 characters. Include the feature name or a concise description, the primary benefit, target customer relevance, and launch timing. Do not use unsupported claims, hashtags, emojis, or hype language.

3. SALES TALKING POINTS
Provide concise bullet points covering the customer problem, what the feature does, the primary benefit, who should care, launch timing, and one objection-handling point based only on the provided information. Do not invent pricing, results, integrations, or customer evidence.

4. SUPPORT ONE-SHEET
Include: feature summary, eligible users or target segment, launch timing, supported capabilities, how to get started, and troubleshooting steps. Make troubleshooting practical and conservative. Use only known facts; where feature-specific details are unavailable, provide general checks such as confirming launch availability, access permissions, supported configuration, and contacting the appropriate support channel without inventing channel details. Clearly label any item that requires confirmation before publication.

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.

Create a concise weekly performance digest for leadership covering {{week_start_date}} through {{week_end_date}}. Use the provided figures exactly: total revenue of {{total_revenue}}, {{deals_won}} deals won, and {{deals_lost}} deals lost. Infer reasonable business context without asking questions or inventing unsupported details.

Write exactly three short paragraphs, with each paragraph beginning with its required label: Highlights: Focus on revenue and wins. Concerns: Address lost deals and clearly state relevant risks or implications. Week ahead priorities: Identify practical focus areas based on the results.

Return only the three labeled paragraphs, with no bullets, headings beyond the required labels, hype, unnecessary politeness, or commentary about the process.

Act as a pragmatic strategic adviser. Based only on the information provided, choose the strongest path and do not ask follow-up questions. If information is incomplete, state the most important assumption briefly and proceed.

Decision options:
{{decision_options}}

Current resource constraints:
{{resource_constraints}}

Deadline or urgency level:
{{urgency_level}}

Key stakeholder priorities:
{{stakeholder_priorities}}

Acceptable risk tolerance:
{{risk_tolerance}}

Return exactly this format:

RECOMMENDATION
[Name one option and state the decision in 1-2 sentences.]

OPTION ASSESSMENT
1. [Option name]
Pros: [Concise bullets or semicolon-separated points]
Cons: [Concise bullets or semicolon-separated points]
Timeline fit: [How well it fits the urgency and why]

2. [Option name]
Pros: [Concise bullets or semicolon-separated points]
Cons: [Concise bullets or semicolon-separated points]
Timeline fit: [How well it fits the urgency and why]

[Continue for each provided option.]

TIMELINE PRESSURE
[State whether the deadline materially changes the decision, including the main timing trade-off.]

DECISION RATIONALE
[Give 2-4 concise sentences linking the recommendation to constraints, stakeholder priorities, risk tolerance, and urgency.]

KEY ASSUMPTION
[State one assumption only if needed; otherwise write None.]

Draft one ready-to-send verification message using only the information provided. Recipient: {{recipient_name_role}}. Confirm this specific detail: {{detail_to_confirm}}. Reference this context: {{context_reference}}. Use the {{contact_method}} format. Urgency: {{urgency_level}}. Requested next step: {{expected_next_step}}. Do not invent details or add unnecessary politeness. Keep it clear, concise, professional, and under 100 words. If the method is email, include a concise subject line; otherwise, start with the message. Return only the message.

Draft a concise cancellation-prevention message from a Customer Success Manager to {{customer_name}}.

Customer context:
- Cancellation reason: {{cancellation_reason}}
- Current plan tier: {{plan_tier}}
- Recent usage activity: {{recent_usage_activity}}

Acknowledge the customer's frustration without defensiveness. Ask exactly one clarifying question about the underlying cause. Suggest one specific alternative solution that fits the context, such as a configuration change, onboarding support, training, temporary plan adjustment, or workflow recommendation. End with a low-pressure invitation to stay. Do not invent facts, use hype, include fabricated proof, or ask the sender for more information.

Return only the finished message, ready to send after one light edit. Include a subject line followed by the message body.

Convert the source content into a concise, actionable learning insight brief for {{audience_department}}. Use the project context, priority, deadline, and preferred channel to make the recommendations practical. Extract only information supported by the source; do not invent facts, names, roles, dates, or decisions. If a required detail is absent, write "Not stated in source".

Return exactly these four plain-text lines and nothing else:
Work change: State the specific behavior, process, decision, or knowledge that should change.
Stakeholders: List the relevant people, teams, or roles explicitly identified or clearly required by the source; otherwise write "Not stated in source".
Sharing method: State how and where this should be shared using the {{preferred_channel}} channel, including the intended audience and any useful timing based on {{deadline}}.
Action item: Give one direct next action, including an owner and due date only when supported by the source or provided context. Reflect {{priority}} and {{related_project}} without adding unsupported facts.

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.

Summarize the meeting notes below into exactly four sections. Use only information explicitly stated in the notes or inputs. Do not invent dates, commitments, decisions, attendees, or meeting details. If a date or status is missing, write "Not specified". Separate internal commitments from commitments made by the external company or its representatives. Preserve specific owners and dates when stated. Output only the following format:

Section 1: Decisions Made
- [Decision]
- If none are explicitly stated: Not specified

Section 2: Our Commitments with Dates
- [Internal team member]: [Commitment] — Due: [date or Not specified]
- If none are explicitly stated: Not specified

Section 3: Their Commitments with Dates
- [External owner or company]: [Commitment] — Due: [date or Not specified]
- If none are explicitly stated: Not specified

Section 4: Next Meeting Scheduled
- Status: [Scheduled, Not scheduled, or Not specified]
- Date/time: [Exact date and time or Not specified]
- Purpose: [Purpose or Not specified]

Company: {{company_name}}
Meeting date: {{meeting_date}}
Attendees: {{attendee_list}}
Internal team members: {{internal_team_members}}
Raw meeting notes:
{{raw_meeting_notes}}

Transform the product information below into exactly four concise marketing artifacts. Use specific, benefit-focused language for the target audience, avoid technical jargon, filler, hype openers, unsupported claims, testimonials, and social proof. Do not add commentary or extra sections. Maintain this exact format:

SALES PITCH ANGLE:
Write 2–3 persuasive sentences for a sales conversation.

MARKETING HEADLINE:
Write one clear headline of no more than 12 words.

CUSTOMER EMAIL:
Write a concise email with a subject line and body of 100 words or fewer.

EXECUTIVE SUMMARY:
Write one concise paragraph of 75 words or fewer for business decision-makers.

Feature description:
{{feature_description}}

Target audience segment:
{{target_audience_segment}}

Core value proposition:
{{core_value_proposition}}

Competitive differentiator:
{{competitive_differentiator}}

Desired tone or style:
{{desired_tone}}

Compose one calm, transparent crisis email for leadership communication using only the information provided below. Do not invent facts, causes, impacts, commitments, contact details, or recovery milestones. Avoid defensive language, blame, hype, and unnecessary jargon. Take clear ownership without assigning blame.

Use this exact plain-text structure:
Subject: [concise subject line]

Hello [appropriate audience],

Situation and impact:
[Direct explanation of what happened and who is affected.]

Our response:
[State ownership and summarize the proposed solution.]

Next steps and recovery timeline:
[List the immediate actions and the expected recovery timeline.]

Contact:
[Name and contact details of the primary contact person.]

Regards,
[Leadership team or organization]

Inputs:
Situation description: {{situation_description}}
Affected stakeholders: {{affected_stakeholders}}
Proposed solution: {{proposed_solution}}
Recovery timeline: {{recovery_timeline}}
Primary contact person: {{primary_contact_person}}

Return only the completed email, with no analysis, notes, placeholders, or markdown formatting.

Rewrite the original headline into exactly five distinct, high-converting headline variations for the specified publication channel.

Original headline: {{original_headline}}
Target audience: {{target_audience}}
Core benefit or value proposition: {{core_benefit}}
Product or feature name: {{product_name}}
Publication channel: {{publication_channel}}

Make every variation specific, urgent, benefit-focused, and curiosity-inducing without using vague claims, fabricated proof, unsupported guarantees, or clickbait. Preserve the core meaning and use only facts provided above. Adapt wording and length to the publication channel. Return exactly five plain-text headlines, one per line, with no numbering, bullets, quotation marks, explanations, or other text.

Create a competitor-loss counter-strategy using only the information provided. Do not invent competitor claims, customer facts, metrics, testimonials, or social proof. Clearly distinguish known information from reasonable inference, and do not ask follow-up questions.

Use exactly this four-section format:

1. Positioning summary
Write exactly one sentence explaining why the competitor won and how we should position against that outcome.

2. Counter-strategy
Give 2–3 specific points covering how to reframe the customer’s stated reason, use our differentiator, and address the competitor’s winning feature without bashing them.

3. Diplomatic mention script
Write a concise, customer-ready script that mentions {{competitor_name}} respectfully, acknowledges the appeal of {{competitor_feature}}, and explains where our approach may be a better fit. Do not make unsupported claims.

4. Future win plan
Give 3 actionable steps appropriate to the {{target_account_stage}} stage, including what to validate, who to engage or influence, and what proof or comparison to prepare. Keep the plan practical and usable after one light edit.

Inputs:
- Competitor name: {{competitor_name}}
- Product or feature they won with: {{competitor_feature}}
- Customer’s stated reason for the loss: {{loss_reason}}
- Our key differentiator: {{our_differentiator}}
- Target account stage: {{target_account_stage}}