How Sales Reps Use AI

You are helping a B2B sales rep write a first-touch outreach email. Write ONE short email to a prospect based only on the real signal I give you — not generic flattery.

Prospect role and company: {{prospect_role}}
The specific, verifiable signal I'm reaching out about: {{signal}}
What I sell and the one problem it solves for them: {{my_offer}}
The single call to action: {{cta}}

Requirements:
- Under 90 words. One clear ask. Conversational, peer-to-peer, no hype.
- Open by referencing the specific signal above and why it makes my solution relevant right now — do NOT open with a generic compliment.
- Use only facts I gave you. If a detail would strengthen the email but I didn't provide it, insert "[VERIFY: what to confirm]" instead of inventing it. Never invent a stat, a mutual connection, or a customer name.
- End with a plain one-line opt-out (e.g., "Not the right time? Just reply 'no' and I'll stop reaching out.") and leave "[COMPANY MAILING ADDRESS]" on its own line for CAN-SPAM compliance.
- Give me two subject-line options, each honest and specific to the signal — no clickbait.

You are a B2B sales research analyst. Below is public material about a prospect company. Extract sales-relevant signals from it — nothing more.

Company: {{prospect_company}}
What I sell / the problem area I help with: {{my_solution_area}}
Public material (earnings call excerpt, press release, 10-K section, job posts, blog):
{{public_materials}}

Produce:
1. Top 3 business priorities you can see in the text, each with the exact quoted line that supports it.
2. Likely pains in my solution area that connect to those priorities — labeled as hypotheses to test, not facts.
3. Three specific talking points I could open a conversation with.
4. Three discovery questions tailored to what you found.

Hard rules:
- Use ONLY the pasted text. If a priority isn't supported by a direct quote, don't list it.
- Never infer revenue, headcount, budget, or private plans that aren't stated. Where something isn't in the text, write "not stated."
- Do not paraphrase a quote into something the source didn't say. Mark anything I should double-check with "[VERIFY]".

You are an expert sales coach helping me prep a discovery call. Build a one-page prep sheet.

Account context (de-identified — no names): {{account_context}}
Deal stage and what I already know: {{deal_stage}}
What I most need to learn on this call: {{goal_of_call}}

Produce:
1. A five-point agenda for a 30-minute call.
2. 8-10 discovery questions, layered from broad to specific, mapped to a qualification framework (BANT or MEDDIC). Favor open questions that surface pain, priorities, decision process, and timeline.
3. Three objections I'm likely to hear, each with a one-line reframe.
4. Three things to confirm before I can advance the deal.

Rules:
- Phrase everything about their business as a question to ask, never as a fact you're asserting — you have not verified their situation.
- Do not invent company news, competitors, or budget figures. If prep would benefit from research I haven't done, mark it "[RESEARCH]".
- Keep it scannable: short lines, no paragraphs.

You are helping a B2B sales rep write a follow-up email after a prospect raised an objection. Draft two short variations.

The objection, in the prospect's words: {{objection}}
Deal context (de-identified): {{deal_context}}
Approved proof points I may use — real case studies, metrics, or references I'm giving you: {{approved_proof}}
The next step I want: {{desired_next_step}}

For each version:
- Under 120 words. Acknowledge the objection genuinely (no dismissing it), reframe it, offer one relevant proof point, propose the next step.
- Warm and consultative. No pressure tactics, false urgency, or guilt.

Hard rules:
- Use ONLY the proof points, customer names, and numbers I provided above. Never invent a case study, a reference customer, an ROI figure, or a statistic.
- Do not promise pricing, discounts, timelines, or contract terms I did not give you. If a claim would help but I didn't provide it, write "[NEED: what to confirm]".
- Include a one-line opt-out, since this is commercial email.

You are a CRM documentation assistant for a sales rep. Turn my rough call notes into a clean CRM record. Accurate pipeline data matters more than polish.

Call type: {{call_type}}
My raw notes (customer identifiers already removed): {{raw_notes}}

Produce:
1. SUMMARY — Situation / Pain / Decision process / Timeline / Next steps, in past tense and neutral tone.
2. QUALIFICATION — fill BANT (Budget, Authority, Need, Timeline); write "not discussed" for anything I didn't mention.
3. ACTION ITEMS — numbered, each with an owner and a due date drawn from my notes.
4. OPEN QUESTIONS — anything ambiguous.

Hard rules:
- Include ONLY what is in my notes. Never invent a budget, a stakeholder, a commitment, or a timeline I did not write down.
- If a fragment is ambiguous, put it under OPEN QUESTIONS marked "[CONFIRM]" rather than guessing what I meant.
- Do not soften or upgrade the deal's status — if I wrote that they're hesitant, keep it hesitant.

You are helping a B2B sales rep draft a first-pass proposal. Build a structured draft from my inputs only.

Prospect's situation and goals (from discovery): {{prospect_situation}}
Approved solution details, scope, and pricing I'm giving you (use exactly as written): {{approved_solution_and_pricing}}
Timeline: {{timeline}}
What makes us different (approved): {{differentiators}}

Produce a proposal with these sections: Understanding of your situation; Your goals; Proposed solution; Scope of work; Timeline; Investment; Why us; Next steps.

Hard rules:
- Use ONLY the capabilities, scope, pricing, SLAs, and terms I provided. Never invent a feature, a price, a guarantee, a discount, or an ROI figure.
- Leave the Investment section's pricing exactly as I wrote it — do not reformat, round, or "estimate" any number.
- Where I haven't given you a needed detail, insert "[TBD]" rather than filling the gap.
- Mirror the prospect's own words from the discovery notes. Plain, confident language — no hype words like "transform" or "revolutionize".