AI Prompt Library

Generates a tailored discovery call agenda for an Indian B2B prospect.

You are an experienced B2B sales coach. Generate a 30-minute discovery call agenda for selling {{product}} to a {{industry}} company of {{size}} employees in India.

Return:
1. 3 opening questions to build rapport
2. 5 pain-discovery questions specific to {{industry}}
3. 3 budget/authority qualification questions phrased politely for Indian context
4. 2 next-step closing questions

Keep questions open-ended and consultative. Avoid pushy sales language.

Draft a follow-up email after a sales call.

Write a follow-up email after a sales call. The prospect is {{name}} at {{company}} ({{industry}}). Key pain point discussed: {{pain}}. Next step agreed: {{next_step}}.

Tone: warm, concise, specific. Reference one detail from the conversation. End with a single clear ask. Max 120 words.

Generate a search-intent-aligned blog outline.

You are an SEO strategist. Create a comprehensive blog outline for the keyword "{{keyword}}" targeted at {{audience}}.

Include:
- 1 H1 title (under 60 chars, includes keyword)
- 5-7 H2 sections with H3 sub-points
- Suggested meta description (under 155 chars)
- 3 internal link anchor ideas
- 5 related keywords to weave in
- A 1-paragraph intro hook

Match search intent: {{intent}} (informational/commercial/transactional).

Hook-driven LinkedIn post in your voice.

Write a LinkedIn post for {{role}} in {{industry}} about {{topic}}.

Format:
- Strong hook line (under 12 words)
- 2-3 short paragraphs with line breaks
- One concrete example or number
- Ends with one question to drive comments

Voice: confident, no jargon, no emojis. Between 100-180 words.

Reply to an angry customer.

You are a senior customer support specialist. Write a reply to this customer message:

"""
{{customer_message}}
"""

Guidelines:
- Acknowledge their feeling in the first sentence
- Apologise without being defensive
- Explain what happened in plain English
- State exactly what you will do next and by when
- Offer one goodwill gesture if appropriate

Tone: warm, professional, accountable. Max 150 words.

Turn an FAQ into a structured KB article.

Turn this FAQ into a structured help-centre article: "{{question}}".

Return:
- Title (question form)
- 1-sentence summary
- Step-by-step instructions (numbered)
- "When this doesn't work" troubleshooting list
- Related articles (3 suggestions)

Write in plain English. Avoid jargon. Add screenshot placeholders [screenshot: describe-here].

Generate a JD that attracts diverse candidates.

Write an inclusive job description for {{role}} at {{company}} ({{industry}}, India).

Include:
- 2-line "About the role"
- "What you will do" (5 bullets)
- "Must-have" skills (max 5 - be strict)
- "Nice-to-have" skills (3)
- "What we offer" (4 bullets including learning budget, hybrid policy, leave)
- "How to apply" with a 1-question screening prompt

Avoid gendered language, "rockstar", "ninja". Mention salary range openly.

Structured feedback notes from raw observations.

Convert these raw observations about {{employee}} into structured performance feedback:

"""
{{notes}}
"""

Return 4 sections: Strengths, Areas to Improve, Specific Examples (with dates), Goals for Next Quarter. Use SBI (Situation-Behaviour-Impact) for examples. Be specific, kind, and actionable.

Generate an SOP from a rough process description.

Create a Standard Operating Procedure for: "{{process}}" at {{company}}.

Include: Purpose, Scope, Owner role, Tools required, Step-by-step (numbered), Quality checks, What to do when it fails, Review frequency. Keep each step under 2 sentences. Suggest where AI/automation could help.

Build a weighted scorecard for vendor selection.

Create a vendor RFP scoring matrix for selecting a {{category}} vendor (e.g. CRM, ERP, support tool).

Return a table with: criterion, weight (sum to 100), what 1/3/5 score means.

Include criteria for: fit to use case, ease of implementation, India presence/support, data residency, pricing transparency, integration depth, security certifications, customer references.

Plain-English summary of monthly numbers.

Given these month-end numbers for {{company}}: revenue {{rev}}, gross margin {{gm}}, burn {{burn}}, runway {{runway}} months, plus this context: "{{context}}".

Write a 250-word narrative for the leadership team covering: what happened, why, what we are watching, and one action ask. Use plain English. No jargon.

Reminder email for overdue invoice (India).

Draft a polite payment reminder email for invoice {{invoice_no}} of {{amount}} due on {{due_date}}, now {{days_overdue}} days overdue. Recipient: {{name}} at {{company}}.

Tone: respectful, firm, helpful. Offer 2 payment options. Mention that this is the {{reminder_count}} reminder. End with a clear action and a fallback contact.

Compress messy idea into a structured one-pager.

Turn this raw idea into a product one-pager: "{{idea}}".

Sections: Problem, Target user, Proposed solution, Key user flows (3-5 bullets), Success metrics (3), Out-of-scope, Open questions. Max 1 page. Sharp and specific.

Generate non-leading discovery questions.

Create a 45-minute user research interview guide for understanding how {{persona}} currently handles {{job_to_be_done}}.

Structure: 3 warm-up, 6 main (open-ended, past-tense, non-leading), 3 closing. Add interviewer notes after each question (what to probe). Avoid solution-shaped questions.

Monthly investor update in 5 sections.

Draft a monthly investor update for {{company}}. Inputs: highlights "{{highlights}}", lowlights "{{lowlights}}", metrics {{metrics}}, asks "{{asks}}".

Format: TL;DR (3 lines), Highlights, Lowlights, Key metrics (table), Asks, Thanks. Honest, specific, scannable. Max 400 words.

Compress your company into a 60-second pitch.

Write a 60-second elevator pitch for {{company}}: we help {{audience}} solve {{problem}} using {{approach}}. Our edge is {{wedge}}. So far: {{traction}}.

Structure: hook (1 sentence), problem (2 sentences), solution (2 sentences), why us (1 sentence), traction (1 sentence), ask (1 sentence). 130-150 words.

Reviewer prompt for a code diff.

You are a senior engineer doing a code review. Review the following diff for {{language}}:

"""
{{diff}}
"""

Return:
- Correctness issues (bugs, edge cases)
- Security concerns
- Performance concerns
- Readability/naming suggestions
- Test coverage gaps

Be specific. Reference line numbers. Suggest concrete fixes, not just complaints.

Systematically debug a tricky issue.

I am debugging this issue: "{{symptom}}". Tech stack: {{stack}}. What I have tried: "{{attempts}}". Relevant logs/snippets:

"""
{{logs}}
"""

Walk me through a structured debugging plan: hypotheses (ranked by likelihood), how to validate each, and what to look for. Be specific about commands or code to run.