Prompting, the skill that makes or breaks your AI results

Act as [role or perspective].

Context:
I run/work at [business type]. We serve [audience]. The situation is [brief background]. The goal is [desired result].

Task:
[Tell the AI exactly what to create, compare, rewrite, summarize, diagnose, or review.]

Inputs:
[Paste the details, notes, transcript, source material, examples, or draft here.]

Constraints:
- Use [tone/style].
- Keep it [length/depth].
- Include [required elements].
- Avoid [claims, topics, tone, formatting, or risks].
- Flag anything that needs human verification.

Output format:
Return [format: email, table, outline, checklist, brief, script, SOP, etc.].
Use this structure:
[Add the exact structure you want.]

Business:
[Business name] is a [business type] that helps [target audience] with [main problem or desired outcome].

Audience:
Our best customers are [describe ideal customers]. They usually care about [priorities], struggle with [problems], and hesitate because [common objections].

Offer:
Our main products/services are [list offers]. We position them as [positioning].

Voice:
Our tone is [tone]. We sound like [description]. We avoid [phrases, tone, claims, or style issues].

Rules:
- Use [spelling convention].
- Don't make unsupported claims.
- Don't promise outcomes we can't control.
- Ask for missing information when the task depends on it.
- Flag legal, financial, medical, privacy, or compliance concerns for human review.

Write a blog post about customer retention.

Act as a content strategist for a service-based small business.

Context:
I run a digital marketing agency with 8 employees. We serve local service businesses. Our clients often leave after the first 6-month contract because they don't clearly understand what improved and what needs more time.

Task:
Write a 900-word blog post for other agency owners about how to improve retention without discounting.

Constraints:
- Use a practical, peer-to-peer tone.
- Avoid generic advice like "communicate more" or "exceed expectations."
- Include three strategies: onboarding, expectation setting, and renewal conversations.
- Each strategy should include one action the reader can take this week.
- Don't make unsupported statistics or claims.

Output format:
Use a short introduction, three strategy sections with headings, and a brief closing.

Act as [role].

Decision:
We need to choose between [option A], [option B], and [option C].

Context:
[Describe the business situation, constraints, budget, team capacity, timeline, and goal.]

Criteria:
Evaluate each option against:
1. Expected impact
2. Time to results
3. Cost
4. Team effort
5. Risk
6. Fit with our current stage

Task:
Compare the options using the criteria above. State your assumptions, identify the biggest trade-off, and recommend one option.

Output format:
Return a table comparing the options, followed by:
- Recommendation
- Concise rationale
- Risks to watch
- What information would change the recommendation

Review the draft below against these criteria:

1. Accuracy: Flag any factual claims that need verification.
2. Clarity: Identify unclear, vague, or confusing sections.
3. Audience fit: Explain where the draft may miss the intended reader's needs.
4. Tone: Flag anything that sounds too formal, too salesy, too casual, or off-brand.
5. Risk: Flag unsupported promises, sensitive claims, or compliance concerns.
6. Action: Identify whether the next step is clear.

For each issue, explain:
- The issue
- Why it matters
- The specific fix

Draft:
[Paste draft here]

I used the prompt below and the output had problems.

Original prompt:
[Paste prompt]

What went wrong:
[Describe the issues: too generic, wrong tone, missing detail, unsupported claims, poor structure, etc.]

Task:
Rewrite the prompt so it avoids these problems next time. Keep the prompt reusable as a template. Add fields in brackets where I should insert task-specific information.

Output format:
Return:
1. Improved prompt
2. What changed
3. Why those changes should improve the output

Act as a helpful customer support specialist for [business type].

Context:
We help [audience] with [offer/service]. Our tone is [tone]. The customer has sent the inquiry below.

Customer inquiry:
[Paste message]

Task:
Draft a response that answers the customer's question, acknowledges their situation, and guides them to the next step.

Constraints:
- Don't invent facts, pricing, availability, or policies.
- If information is missing, ask for it clearly.
- Keep the response warm, direct, and concise.
- Don't over-apologize.
- Don't promise outcomes we can't control.

Output format:
Return:
1. Email response
2. Notes for human review
3. Missing information to confirm before sending

Act as a practical B2B sales assistant.

Context:
Business: [your business]
Prospect: [prospect type/company]
Call summary: [paste notes]
Main problem discussed: [problem]
Offer discussed: [offer]
Next step desired: [book call/send proposal/confirm scope/etc.]

Task:
Write a follow-up email that summarizes the conversation, reinforces the value of the next step, and makes it easy for the prospect to respond.

Constraints:
- Don't sound pushy.
- Don't use hype or fake urgency.
- Don't promise specific results unless included in the approved source material.
- Keep it under [word count].

Output format:
Return one email draft and three subject line options.

Act as a content strategist for [business type].

Context:
Audience: [target reader]
Topic: [topic]
Business goal: [awareness/leads/trust/sales support]
Reader problem: [problem]
Angle we want to take: [angle]
Source material to use: [paste notes or approved facts]

Task:
Create a detailed blog outline that would help the reader solve the problem without feeling like a sales pitch.

Constraints:
- Avoid thin or generic advice.
- Include only claims that can be supported by the source material or clearly mark them as needing verification.
- Use headings in sentence case.
- Keep the outline practical and specific.

Output format:
Return:
1. Suggested title
2. Search intent summary
3. Outline with section purpose notes
4. Examples or proof needed
5. Potential internal links or related resources to consider

Act as a social media strategist for [business type].

Context:
Audience: [target audience]
Platform: [LinkedIn/Instagram/Facebook/TikTok/X/etc.]
Brand voice: [voice]
Source content: [paste article, notes, video transcript, or campaign idea]

Task:
Turn the source content into [number] platform-native posts.

Constraints:
- Don't copy the source word-for-word.
- Don't use clickbait.
- Match the platform's natural style.
- Keep the message useful even if the reader never clicks.
- Include one clear next step where appropriate.

Output format:
Return each post with:
1. Post copy
2. Visual idea
3. CTA
4. What part of the source it came from

Act as an operations coordinator.

Context:
Meeting purpose: [purpose]
Team/department: [team]
Meeting notes or transcript:
[Paste notes]

Task:
Turn the notes into a clear action plan.

Constraints:
- Don't invent decisions that aren't in the notes.
- If ownership or deadlines are missing, mark them as "needs confirmation."
- Keep the tone plain and operational.

Output format:
Return:
1. Brief meeting summary
2. Decisions made
3. Action items table with owner, deadline, and status
4. Open questions
5. Follow-up message draft

Act as a skeptical but fair buyer reviewing a proposal from [business type].

Context:
Buyer type: [buyer]
Offer: [offer]
Goal of proposal: [goal]
Proposal draft:
[Paste draft]

Task:
Review the proposal and identify anything that could stop the buyer from saying yes.

Constraints:
- Be direct.
- Focus on clarity, trust, relevance, risk, and next steps.
- Don't rewrite the full proposal unless asked.

Output format:
Return:
1. Biggest strengths
2. Biggest objections a buyer may have
3. Sections that need more proof
4. Confusing or vague language
5. Recommended fixes in priority order

Act as a customer education specialist.

Context:
Business: [business]
Offer/product/service: [offer]
Audience: [audience]
Customer questions:
[Paste real questions, sales notes, support tickets, or comments]

Task:
Create FAQ questions and answers that reduce buyer confusion and support better decisions.

Constraints:
- Use only information provided or clearly mark missing facts.
- Keep answers concise but complete.
- Don't make claims about price, guarantees, timelines, or outcomes unless provided.
- Write in the brand voice: [voice].

Output format:
Return [number] FAQs. For each FAQ, include:
1. Question
2. Answer
3. What source input supports the answer
4. Any information that needs verification

Act as an operations manager creating clear internal documentation for a small business.

Context:
Process name: [process]
Who performs it: [role/team]
When it happens: [trigger/frequency]
Current notes:
[Paste notes, checklist, transcript, or rough process]

Task:
Turn the notes into a practical standard operating procedure.

Constraints:
- Keep the steps clear and sequential.
- Mark missing details as "needs confirmation."
- Don't add tools or approvals unless they appear in the notes.
- Write for someone doing the task for the first time.

Output format:
Return:
1. Purpose
2. When to use this SOP
3. Required tools or inputs
4. Step-by-step process
5. Quality checks
6. Common mistakes
7. Escalation rules

Act as a calm customer success manager.

Context:
Business: [business]
Customer issue: [issue]
Relevant policy or facts: [policy/facts]
Desired outcome: [refund/replacement/call/fix/escalation/etc.]
Customer message:
[Paste message]

Task:
Draft a response that acknowledges the issue, explains the next step, and protects the customer relationship.

Constraints:
- Don't admit fault unless approved facts support it.
- Don't blame the customer.
- Don't overpromise.
- Keep the tone human, accountable, and clear.
- Flag anything that needs manager approval.

Output format:
Return:
1. Customer response
2. Internal notes
3. Escalation or approval needed

Act as a senior editor for [business/publication].

Context:
Audience: [audience]
Goal: [goal]
Brand voice: [voice]
Draft:
[Paste draft]

Task:
Review the draft for quality and usefulness.

Constraints:
- Focus on clarity, redundancy, weak arguments, unsupported claims, tone, structure, and reader value.
- Don't praise the draft generally.
- Be specific and actionable.

Output format:
Return:
1. Publish-readiness score from 1 to 10
2. Priority issues
3. Redundant sections
4. Claims needing verification
5. Suggested edits
6. Final recommendation