Sales prompts that prioritize context, brevity, and a clear ask. Built for BDRs and AEs who need outreach, discovery structure, and follow-ups—not motivational spam.
Write a cold email to {{role_title}} at {{company}}. My product: {{product_name}} Why them now: {{trigger}} Proof point: {{proof}} Ask: {{ask}} Constraints: under 120 words, no fluff, one clear CTA, no fake personalization.
Build a 25-minute discovery agenda for a call with {{role_title}} selling {{product_name}}. Known context: {{context}} Hypothesized pain: {{pain}} Include: opening, 6 discovery questions (open-ended), qualification checklist, next-step script.
Write a post-demo follow-up email after presenting {{product_name}} to {{role_title}}. What they liked: {{liked}} Open questions: {{open_questions}} Proposed next step: {{next_step}} Tone: concise, helpful, not pushy. Include a short recap and one clear ask.
Create an objection-handling sheet for {{product_name}}. Common objections: {{objections}} Competitors mentioned: {{competitors}} For each objection: reframe, clarifying question, proof angle, suggested reply (2–3 sentences).
Draft a mutual action plan after a discovery call for {{product_name}} with {{company}}. Stakeholders: {{stakeholders}} Desired go-live: {{date}} Open risks: {{risks}} Include owner, date, and dependency for each step.
Do not fabricate case studies, discounts, or meeting availability. Keep claims you can defend. These prompts are drafting aids, not permission to misrepresent your product.
Interviewing for a sales role? Use the AI Resume builder for ATS-friendly bullets. Need a pitch outline? Open AI Presentation. For research PDFs, Chat with PDF keeps files local in-browser when possible.
Cold outreach fails when it reads like a template blast. These prompts force a trigger, a proof point, and a single ask. Discovery agendas keep calls from wandering. Follow-ups recap what the buyer cared about instead of dumping a feature list. Objection sheets prepare reframes without insulting the buyer.
New logo prospecting: cold email, then discovery. After a demo: follow-up with liked items and open questions. Late stage: mutual action plan with owners and dates. Competitive deals: objection sheet with honest tradeoffs. Do not send the cold email template to an inbound evaluation that already had three meetings.
Do not invent logos, discounts, security certifications, or meeting slots. Log what you actually promised. If your company requires approved snippets, paste those into {{proof}} instead of letting the model improvise. These drafts are starting points for humans who own the relationship.
If you are the candidate, reuse discovery and follow-up structures to prepare stories, then polish bullets in the AI Resume builder. If you are selling, keep customer data out of public chat tools when policy requires it—draft structure here, fill sensitive details offline.
Reply rates depend on list quality, timing, and offer strength. A perfect prompt cannot fix a bad ICP. LinkedIn DMs need even shorter copy than email. Always personalize the first line with something true before you hit send.
Strong discovery prompts ask how success is measured, who else evaluates vendors, what happens if the problem stays unsolved, and which tools already failed. Encourage open questions over yes/no traps. After the call, translate notes into a mutual action plan instead of a vague “great chatting” email that leaves next steps ambiguous.
No prompt guarantees replies. Response rates depend on targeting, offer, and timing. These templates reduce blank-page time and keep structure tight.
Yes—shorten the cold email body to 2–3 lines and move proof to a soft ask for a call.
No. dk-js provides copy-paste prompts, not a sequencer or CRM send engine.
The template targets under 120 words. If your market expects shorter, ask the model for a 60-word cut that keeps the ask.
Generate structure, then replace claims with approved language before review. Do not submit invented case studies to legal as if they were real.
