Gemini Prompts

Write a professional follow-up email after a client meeting.

Meeting details:
- Date: [DATE]
- Attendees: [YOUR NAME, CLIENT NAMES]
- Main topics discussed: [TOPICS]

Key decisions made:
[LIST KEY DECISIONS]

Action items:
[LIST ACTION ITEMS WITH OWNERS AND DUE DATES]

Next steps:
[DESCRIBE NEXT MILESTONE OR MEETING]

Tone: Professional but warm. Keep it scannable with clear sections. Thank them for their time.

Write a project proposal for a potential client.

Client: [COMPANY NAME]
Project type: [TYPE OF PROJECT]
Client's problem/need: [DESCRIBE THE PROBLEM THEY WANT SOLVED]
Proposed solution: [YOUR APPROACH]

Include these sections:
1. Executive Summary (2-3 sentences)
2. Understanding of the Problem
3. Proposed Solution
4. Deliverables
5. Timeline
6. Investment (leave pricing as [TO BE DISCUSSED])
7. Next Steps

Tone: Confident and professional. Focus on outcomes and value, not features. Keep it concise—aim for 1-2 pages when formatted.

Write a brief check-in email to a client.

Context:
- Project: [PROJECT NAME]
- Current phase: [WHERE WE ARE IN THE PROJECT]
- Last major milestone: [WHAT WE RECENTLY COMPLETED]
- Next milestone: [WHAT'S COMING UP]

Purpose of check-in: [e.g., making sure they're happy with progress / seeing if they have questions / confirming we're on track]

Keep it brief (3-4 short paragraphs max). Friendly and professional. End with an easy question or offer to chat.

Write an email addressing a scope change request from a client.

Original scope: [WHAT WAS ORIGINALLY AGREED]
Requested change: [WHAT THE CLIENT IS ASKING FOR]
Impact of change: [TIMELINE / BUDGET / RESOURCE IMPLICATIONS]

My recommendation: [ACCEPT / MODIFY / DISCUSS OPTIONS]

Tone: Collaborative, not defensive. Acknowledge their needs while being clear about impacts. Offer solutions, not just problems.

Keep it professional but direct. The goal is to protect the project while maintaining a good relationship.

Write a polite payment reminder email.

Invoice details:
- Invoice number: [NUMBER]
- Amount: [AMOUNT]
- Original due date: [DATE]
- Days overdue: [NUMBER]

This is reminder number: [1st / 2nd / 3rd]

For 1st reminder: Very gentle, assume it slipped through the cracks
For 2nd reminder: Slightly more direct, offer to help if there's an issue
For 3rd reminder: Firm but professional, mention next steps if needed

Keep it short and friendly. The goal is to get paid while preserving the relationship.

Write a project completion email to wrap up an engagement.

Project: [PROJECT NAME]
Client: [CLIENT NAME]
Duration: [START DATE] to [END DATE]

What was delivered:
[LIST MAIN DELIVERABLES]

Key outcomes/results:
[LIST MEASURABLE OUTCOMES IF AVAILABLE]

Any follow-up items or recommendations:
[ONGOING MAINTENANCE, FUTURE IMPROVEMENTS, ETC.]

Include:
- Thank you for the collaboration
- Offer to answer questions about handoff
- Mention availability for future work (subtle, not salesy)
- Request for testimonial or referral (optional—mark if I should include this)

Tone: Warm, professional, and forward-looking.

Create a 5-post social media series for the week.

Platform: [LINKEDIN / TWITTER / INSTAGRAM / FACEBOOK]
Theme/topic: [WHAT THE SERIES IS ABOUT]
Goal: [AWARENESS / ENGAGEMENT / TRAFFIC / LEADS]
Brand voice: [PROFESSIONAL / CASUAL / PLAYFUL / AUTHORITATIVE]

For each post include:
1. Hook (first line that grabs attention)
2. Main content
3. Call-to-action
4. Suggested hashtags (if appropriate for platform)

Make each post able to stand alone, but have them build on each other when viewed as a series. Vary the format (question, tip, story, statistic, etc.).

Write an email newsletter for my audience.

Newsletter name: [NAME IF YOU HAVE ONE]
Audience: [WHO RECEIVES THIS]
Frequency: [WEEKLY / MONTHLY / ETC.]

This issue's main topic: [PRIMARY CONTENT]
Secondary items to include: [OTHER THINGS TO MENTION]

Tone: [PROFESSIONAL / CONVERSATIONAL / EDUCATIONAL / ENTERTAINING]

Structure:
1. Subject line (and preview text)
2. Opening hook (1-2 sentences)
3. Main content
4. Secondary items (brief)
5. CTA or closing thought

Keep it scannable. Aim for 300-500 words max. Make readers feel like they gained something by opening it.

Create ad copy variations for testing.

Platform: [GOOGLE ADS / META / LINKEDIN / OTHER]
Product/service: [WHAT YOU'RE PROMOTING]
Target audience: [WHO YOU'RE TARGETING]
Primary benefit: [MAIN VALUE PROPOSITION]
Offer (if any): [DISCOUNT, FREE TRIAL, ETC.]

Character limits:
- Headline: [LIMIT]
- Description: [LIMIT]

Create 5 variations using different angles:
1. Problem-focused (address pain point)
2. Benefit-focused (highlight outcome)
3. Social proof (credibility/numbers)
4. Urgency (time-sensitive)
5. Question hook (engage curiosity)

Keep copy clear and direct. No jargon. Focus on what matters to the reader, not the advertiser.

Write copy for a landing page.

Purpose: [LEAD GEN / SALES / SIGNUP / DOWNLOAD]
Product/service: [WHAT YOU'RE OFFERING]
Target audience: [WHO THIS IS FOR]
Main problem you solve: [PAIN POINT]
Key benefits (3 max): [BENEFITS]
Social proof available: [TESTIMONIALS, STATS, LOGOS]

Write sections for:
1. Hero headline + subheadline
2. Problem section (agitate the pain)
3. Solution section (your offer)
4. Benefits (with brief explanations)
5. Social proof section
6. FAQ (3-4 common objections)
7. Final CTA section

Tone: [PROFESSIONAL / CONVERSATIONAL / URGENT / REASSURING]

Focus on outcomes, not features. Write for scanners—use headers and short paragraphs.

Write a product description.

Product: [PRODUCT NAME]
Category: [TYPE OF PRODUCT]
Price point: [BUDGET / MID-RANGE / PREMIUM]
Target customer: [WHO BUYS THIS]

Key features:
[LIST 3-5 FEATURES]

What makes it different:
[UNIQUE SELLING POINTS]

Desired tone: [LUXURIOUS / PRACTICAL / FUN / TECHNICAL]
Word count: [TARGET LENGTH]

Write a description that:
- Opens with the benefit, not the product
- Paints a picture of the product in use
- Addresses the "why should I care" question
- Ends with a reason to buy now

Avoid clichés like "high-quality" or "best-in-class." Be specific.

Create a detailed outline for a blog post.

Topic: [WHAT THE POST IS ABOUT]
Target keyword (if SEO-focused): [PRIMARY KEYWORD]
Target audience: [WHO WILL READ THIS]
Post goal: [EDUCATE / CONVERT / RANK / BUILD TRUST]
Desired length: [WORD COUNT]

Include:
1. Working title (3 options)
2. Meta description
3. Introduction hook
4. Main sections (H2s) with subsections (H3s)
5. Key points to make in each section
6. Where to include examples or data
7. CTA recommendation
8. Internal/external linking opportunities

Make the outline detailed enough that writing becomes easy. Include notes on what each section should accomplish.

Write a press release.

Company: [COMPANY NAME]
News: [WHAT ARE YOU ANNOUNCING]
Why it matters: [SIGNIFICANCE OF THE NEWS]
Target media: [INDUSTRY PUBLICATIONS, LOCAL NEWS, ETC.]

Key details:
- Who: [PEOPLE INVOLVED]
- What: [THE NEWS]
- When: [DATE/TIMING]
- Where: [LOCATION IF RELEVANT]
- Why: [WHY THIS MATTERS]

Include:
- Attention-grabbing headline
- Dateline and lead paragraph (who, what, when, where, why)
- Supporting details and context
- Quote from company spokesperson
- Quote from partner/customer (if applicable)
- Boilerplate about the company
- Media contact information placeholder

Follow AP style. Keep it under 500 words. Make it newsworthy, not promotional.

Create a Standard Operating Procedure (SOP) document.

Process name: [NAME OF THE PROCESS]
Purpose: [WHY THIS PROCESS EXISTS]
Who performs it: [ROLE/TEAM RESPONSIBLE]
Frequency: [HOW OFTEN IT'S DONE]

Current steps (rough):
[LIST THE STEPS AS YOU UNDERSTAND THEM]

Tools/systems used:
[SOFTWARE, EQUIPMENT, OR RESOURCES NEEDED]

Create an SOP that includes:
1. Purpose and scope
2. Roles and responsibilities
3. Prerequisites (what needs to be in place before starting)
4. Step-by-step procedure (numbered, clear actions)
5. Quality checkpoints
6. Troubleshooting common issues
7. Related documents or resources

Write for someone who has never done this before. Each step should be one clear action. Use screenshots or diagram placeholders where helpful.

Create a checklist for a recurring process.

Process: [WHAT PROCESS IS THIS FOR]
Used by: [WHO USES THIS CHECKLIST]
Frequency: [DAILY / WEEKLY / PER PROJECT / ETC.]

Key steps to include:
[LIST THE MAIN THINGS THAT NEED TO HAPPEN]

Critical items (must not be missed):
[HIGHLIGHT THE MOST IMPORTANT STEPS]

Format the checklist with:
- Clear, action-oriented items (start with verbs)
- Logical grouping by phase or category
- Space for checkmarks/completion
- Notes field for any items that need it
- Date/name fields if it needs to be signed off

Keep items specific and verifiable. "Review document" is vague; "Check document for spelling errors and broken links" is checkable.

Create a meeting agenda.

Meeting purpose: [MAIN OBJECTIVE OF THIS MEETING]
Meeting type: [STANDUP / PLANNING / REVIEW / BRAINSTORM / DECISION]
Duration: [LENGTH IN MINUTES]
Attendees: [WHO'S ATTENDING AND THEIR ROLES]

Topics to cover:
[LIST THE TOPICS/ITEMS TO DISCUSS]

Decisions needed:
[ANY DECISIONS THAT MUST BE MADE IN THIS MEETING]

Pre-work required:
[ANYTHING ATTENDEES SHOULD PREPARE BEFOREHAND]

Create an agenda with:
1. Meeting objective (1 sentence)
2. Timed agenda items with owners
3. Discussion topics vs. information-sharing clearly marked
4. Time for questions
5. Action items capture section
6. Next steps

Total times should add up to meeting length. Include buffer for discussion.

Create a status report template.

Report type: [PROJECT STATUS / TEAM UPDATE / EXECUTIVE SUMMARY]
Audience: [WHO READS THIS]
Frequency: [WEEKLY / MONTHLY / ETC.]
Project/team: [WHAT THIS COVERS]

Information to include:
[LIST WHAT NEEDS TO BE REPORTED ON]

Create a template with:
1. Report header (period, author, date)
2. Executive summary (3 bullets max)
3. Overall status indicator (On Track / At Risk / Off Track)
4. Progress highlights
5. Challenges or blockers
6. Key metrics (if applicable)
7. Upcoming milestones
8. Decisions or input needed
9. Resource needs

Design it to be scannable. Busy readers should get the key points in 30 seconds. Include formatting guidance.

Create an onboarding guide for new team members.

Role: [JOB TITLE/ROLE]
Team: [TEAM OR DEPARTMENT]
Company: [COMPANY NAME]

Key things new hires need:
[LIST ESSENTIALS—ACCESS, TOOLS, KNOWLEDGE]

First week priorities:
[WHAT SHOULD THEY ACCOMPLISH IN WEEK 1]

Key people to meet:
[IMPORTANT CONTACTS AND THEIR ROLES]

Create a guide that covers:
1. Welcome and role overview
2. First day checklist (access, setup, introductions)
3. First week roadmap with daily goals
4. Key tools and how to access them
5. Important contacts and what they help with
6. Essential reading/documentation
7. 30-60-90 day expectations
8. FAQ for common new hire questions
9. Who to ask for what

Write in a welcoming tone. Reduce anxiety by being clear about expectations.

Document a workflow.

Workflow name: [NAME]
Purpose: [WHAT THIS WORKFLOW ACCOMPLISHES]
Trigger: [WHAT STARTS THIS WORKFLOW]
End state: [WHAT INDICATES IT'S COMPLETE]

People/roles involved:
[LIST ROLES AND THEIR PART IN THE WORKFLOW]

Systems/tools used:
[LIST TOOLS INVOLVED]

Current flow (rough):
[DESCRIBE THE STEPS AS THEY HAPPEN NOW]

Create documentation that includes:
1. Workflow overview and purpose
2. Trigger conditions (when does this start?)
3. Step-by-step process with role assignments
4. Decision points and criteria
5. Handoff procedures between roles
6. Expected timeframes for each stage
7. Exception handling (what if X goes wrong?)
8. Completion criteria
9. Diagram placeholder/description

Write for clarity. Someone unfamiliar should understand how work flows through the process.

Write a job description.

Job title: [TITLE]
Department: [TEAM/DEPARTMENT]
Reports to: [MANAGER'S ROLE]
Location: [REMOTE / HYBRID / OFFICE LOCATION]
Employment type: [FULL-TIME / PART-TIME / CONTRACT]

About the role:
[DESCRIBE WHAT THIS PERSON WILL DO AND WHY IT MATTERS]

Key responsibilities:
[LIST 5-7 MAIN RESPONSIBILITIES]

Must-have qualifications:
[REQUIREMENTS THAT ARE ACTUALLY REQUIRED]

Nice-to-have qualifications:
[THINGS THAT WOULD BE BONUS BUT AREN'T DEAL-BREAKERS]

What we offer:
[BENEFITS, CULTURE, GROWTH OPPORTUNITIES]

Create a job description that:
- Opens with what makes this role exciting
- Is honest about the work and expectations
- Distinguishes between must-haves and nice-to-haves
- Gives a sense of the team and company culture
- Avoids gendered language and unnecessary requirements

Keep it under 700 words. Write to attract, not to filter out.

Create interview questions for a role.

Position: [JOB TITLE]
Level: [ENTRY / MID / SENIOR / LEADERSHIP]
Key skills needed: [LIST 3-5 CRITICAL SKILLS]
Team culture: [DESCRIBE YOUR TEAM'S WORK STYLE]

Interview stage: [PHONE SCREEN / TECHNICAL / CULTURE FIT / FINAL]
Interview length: [MINUTES]

Create questions that assess:
1. Relevant experience and skills
2. Problem-solving approach
3. Culture fit and work style
4. Growth mindset and learning
5. Specific scenarios they'll face in this role

For each question, include:
- The question itself
- What you're looking for in the answer
- Follow-up probes if needed

Mix behavioral ("Tell me about a time...") with situational ("How would you handle...") questions. Avoid questions with obvious "right" answers.

Create a candidate evaluation form.

Position: [JOB TITLE]
Key competencies to evaluate:
[LIST 4-6 SKILLS OR QUALITIES]

Interview stage: [WHICH ROUND THIS IS FOR]

Create an evaluation form with:
1. Candidate information section
2. Rating scale (1-5) with clear definitions
3. Competency sections with:
   - Specific criteria to evaluate
   - Space for evidence/examples
   - Rating for each competency
4. Overall recommendation section
5. Strengths observed
6. Concerns or gaps
7. Questions for next round (if applicable)
8. Hire / No Hire / Unsure with explanation

Design for consistency across interviewers. Include prompts for specific examples, not just impressions.

Write a job offer letter.

Candidate name: [NAME]
Position: [JOB TITLE]
Department: [TEAM]
Start date: [DATE]
Salary: [AMOUNT AND FREQUENCY]
Employment type: [FULL-TIME / PART-TIME / CONTRACT]

Additional compensation:
[BONUS, EQUITY, ETC.]

Benefits:
[KEY BENEFITS TO HIGHLIGHT]

Reporting to: [MANAGER NAME AND TITLE]

Special terms (if any):
[SIGNING BONUS, RELOCATION, ETC.]

Write an offer letter that:
- Opens with genuine excitement about them joining
- Clearly states the key terms (title, compensation, start date)
- Summarizes benefits
- Explains next steps
- Includes deadline to respond
- Notes that this is pending [background check, etc.] if applicable

Tone: Professional but warm. Make them feel wanted, not processed.

Write a rejection email to a candidate.

Candidate name: [NAME]
Position they applied for: [JOB TITLE]
Stage they reached: [APPLICATION / PHONE SCREEN / INTERVIEW / FINAL ROUND]

Reason for rejection (internal, don't share specifics):
[WHY THEY WEREN'T SELECTED]

Should I:
- Encourage them to apply for other roles? [YES/NO]
- Offer to keep them in mind for future opportunities? [YES/NO]
- Provide any feedback? [YES/NO - if yes, what's appropriate to share]

Write an email that:
- Thanks them sincerely for their time and interest
- Delivers the news clearly and early (don't bury it)
- Doesn't over-explain or give false hope
- Leaves the door open appropriately
- Maintains the company's reputation

Keep it brief but human. They spent time on this process—respect that.

Create reference check questions.

Candidate: [NAME]
Position they're being considered for: [JOB TITLE]
Key qualities we need to verify: [LIST 3-4 IMPORTANT TRAITS]

Reference type: [FORMER MANAGER / COLLEAGUE / DIRECT REPORT]

Create questions that:
1. Verify basic information (role, dates, responsibilities)
2. Assess specific competencies needed for our role
3. Understand their work style and collaboration approach
4. Identify growth areas or development needs
5. Get a sense of fit for our specific environment

Include:
- Opening questions to build rapport
- Behavioral questions about specific situations
- Questions about areas of concern from interviews
- Closing question: "Would you hire them again?"

Design questions to get beyond generic praise. Ask for specific examples.

Summarize these meeting notes.

Meeting: [MEETING NAME/TYPE]
Date: [DATE]
Attendees: [WHO WAS THERE]

Raw notes:
[PASTE YOUR MEETING NOTES HERE]

Create a summary that includes:
1. Meeting purpose (1 sentence)
2. Key discussion points (bullet points)
3. Decisions made (with who decided)
4. Action items (with owner and due date for each)
5. Open questions or parking lot items
6. Next meeting date/topic (if discussed)

Format for easy scanning. Someone who missed the meeting should be able to get up to speed in 2 minutes.

Write a weekly status update.

Week of: [DATE RANGE]
Project/Team: [NAME]
For: [WHO WILL READ THIS]

What happened this week:
[LIST ACCOMPLISHMENTS AND PROGRESS]

What's planned for next week:
[LIST PLANNED ACTIVITIES]

Blockers or risks:
[ANY ISSUES THAT NEED ATTENTION]

Key metrics (if applicable):
[NUMBERS THAT MATTER]

Help needed:
[ANYTHING YOU NEED FROM READERS]

Create an update that:
- Opens with the most important news
- Uses bullet points for scannability
- Clearly flags anything that needs attention
- Keeps good news proportional (don't pad it)
- Includes specific numbers where relevant

Keep it under 300 words unless there's major news.

Write a summary of data analysis findings.

Analysis topic: [WHAT YOU ANALYZED]
Data source: [WHERE THE DATA CAME FROM]
Time period: [DATE RANGE]
Audience: [WHO WILL READ THIS]

Key findings:
[LIST THE MAIN THINGS YOU DISCOVERED]

Data highlights:
[SPECIFIC NUMBERS OR TRENDS]

Create a summary that includes:
1. Executive summary (3-4 sentences)
2. Background/context
3. Methodology (brief)
4. Key findings with supporting data
5. Implications (so what?)
6. Recommended actions
7. Limitations or caveats
8. Next steps

Write for the audience's level of data literacy. Lead with insights, not methodology. Make it actionable.

Write a quarterly review.

Quarter: [Q1/Q2/Q3/Q4] [YEAR]
Team/Project/Business: [NAME]
Audience: [WHO WILL READ THIS]

Goals for this quarter (what we set out to do):
[LIST THE QUARTER'S GOALS]

Results (what actually happened):
[LIST OUTCOMES AGAINST EACH GOAL]

Key metrics:
[RELEVANT NUMBERS AND COMPARISONS]

Major wins:
[SIGNIFICANT ACCOMPLISHMENTS]

Challenges faced:
[WHAT DIDN'T GO AS PLANNED]

Lessons learned:
[INSIGHTS TO CARRY FORWARD]

Next quarter focus:
[PREVIEW OF UPCOMING PRIORITIES]

Create a review that:
- Honestly assesses performance against goals
- Celebrates wins without over-inflating
- Acknowledges challenges constructively
- Extracts actionable lessons
- Sets up next quarter clearly

Keep it comprehensive but readable (aim for 1-2 pages).

Write an incident report.

Incident type: [WHAT HAPPENED—OUTAGE, SECURITY, ERROR, ETC.]
Date and time: [WHEN IT OCCURRED]
Duration: [HOW LONG IT LASTED]
Severity: [LOW / MEDIUM / HIGH / CRITICAL]
Affected: [WHO OR WHAT WAS IMPACTED]

Timeline of events:
[LIST WHAT HAPPENED IN ORDER]

Root cause:
[WHAT CAUSED THIS TO HAPPEN]

Resolution:
[HOW IT WAS FIXED]

Impact:
[WHAT WAS THE EFFECT]

Create a report that includes:
1. Executive summary (3-4 sentences)
2. Timeline of events (with timestamps)
3. Root cause analysis
4. Impact assessment
5. Resolution steps taken
6. Preventive measures for the future
7. Action items with owners
8. Lessons learned

Write factually, not defensively. The goal is learning, not blame.

Write a performance summary.

Employee name: [NAME]
Role: [JOB TITLE]
Review period: [DATE RANGE]
Reviewer: [YOUR NAME/ROLE]

Goals from this period:
[LIST THEIR GOALS]

Performance against goals:
[HOW DID THEY DO ON EACH]

Key accomplishments:
[NOTABLE ACHIEVEMENTS]

Areas for development:
[CONSTRUCTIVE FEEDBACK]

Feedback from others (if available):
[PEER OR STAKEHOLDER INPUT]

Create a summary that:
- Provides specific examples for all feedback
- Balances recognition with constructive growth areas
- Focuses on behaviors and outcomes, not personality
- Gives actionable development suggestions
- Aligns with their career goals

Write as if they'll read this—because they will. Be honest, specific, and constructive.

Create an FAQ section.

Product/service: [WHAT THIS FAQ IS FOR]
Audience: [WHO WILL READ THIS]
Tone: [FORMAL / FRIENDLY / TECHNICAL]

Common questions we get:
[LIST THE QUESTIONS CUSTOMERS ASK]

Topics to cover:
[AREAS THAT SHOULD HAVE FAQ ENTRIES]

For each FAQ entry, create:
1. Clear question (as a customer would ask it)
2. Concise answer (get to the point quickly)
3. Additional details if needed
4. Link to more info (placeholder if applicable)

Organize by category. Write answers that actually help—don't be vague or redirect unnecessarily. Anticipate follow-up questions.

Create customer service response templates.

Company/product: [NAME]
Support channel: [EMAIL / CHAT / SOCIAL / PHONE SCRIPTS]
Tone: [FORMAL / FRIENDLY / EMPATHETIC]

Scenarios to create templates for:
[LIST THE COMMON SITUATIONS]

For each template, create:
1. Scenario name
2. When to use it
3. Template text with [PLACEHOLDERS] for personalization
4. Variations if the situation differs slightly
5. Escalation guidance (when this template isn't enough)

Templates should:
- Acknowledge the customer's situation
- Provide clear information or next steps
- Sound human, not robotic
- Include personalization points
- End with an offer to help further

Make them easy to customize—no template should go out unchanged.

Write a response to a customer complaint.

Customer name: [NAME]
Issue: [WHAT THEY'RE COMPLAINING ABOUT]
How they contacted us: [EMAIL / SOCIAL / REVIEW / ETC.]
Severity: [MINOR INCONVENIENCE / SIGNIFICANT ISSUE / MAJOR PROBLEM]
Our fault? [YES / NO / PARTIALLY]

What happened:
[DESCRIPTION OF THE SITUATION]

What we can do to resolve it:
[AVAILABLE REMEDIES]

Write a response that:
1. Acknowledges their frustration (don't be defensive)
2. Takes responsibility where appropriate
3. Explains what happened (briefly, without excuses)
4. Offers a clear resolution
5. Commits to preventing recurrence (if applicable)
6. Thanks them for bringing it to our attention

Tone: Empathetic and professional. Match their energy level. If they're very upset, be warmer. If they're businesslike, be efficient.

Write a feedback request message.

Context: [WHAT JUST HAPPENED—PURCHASE, SUPPORT INTERACTION, ETC.]
Customer name: [NAME]
Feedback type: [REVIEW / SURVEY / NPS / GENERAL]
Where feedback goes: [GOOGLE, SURVEY LINK, REPLY TO EMAIL, ETC.]

What we want to learn:
[WHAT QUESTIONS DO WE WANT ANSWERED]

Incentive (if any):
[DISCOUNT, ENTRY TO WIN, ETC.]

Write a request that:
- Thanks them for their business/interaction
- Explains why their feedback matters
- Makes it easy to provide feedback (one click if possible)
- Sets expectations on time required
- Mentions any incentive naturally

Keep it short. Make the ask clear and the action easy. Don't guilt-trip—invite them genuinely.

Write a service update notice to customers.

Type of update: [MAINTENANCE / OUTAGE / FEATURE CHANGE / POLICY UPDATE]
Timing: [WHEN THIS HAPPENS/HAPPENED]
Impact: [WHAT CUSTOMERS WILL EXPERIENCE]
Duration: [HOW LONG]
Action required: [WHAT CUSTOMERS NEED TO DO, IF ANYTHING]

Write a notice that:
1. States what's happening clearly (don't bury the lead)
2. Explains when and how long
3. Describes the impact honestly
4. Tells them what to do (if anything)
5. Explains why (briefly)
6. Apologizes for inconvenience if appropriate
7. Provides a way to get help or updates

Tone: Clear, direct, and reassuring. Don't over-apologize, but acknowledge impact.

Write an apology email to a customer.

What went wrong: [DESCRIBE THE MISTAKE]
Impact on customer: [HOW IT AFFECTED THEM]
Our responsibility: [OWN IT / PARTIAL / EXTERNAL FACTOR]
Resolution: [WHAT WE'RE DOING TO FIX IT]
Goodwill gesture: [DISCOUNT, CREDIT, FREE ITEM, ETC.]

Customer name: [NAME]
Relationship: [NEW CUSTOMER / LONG-TIME / VIP]

Write an email that:
1. Apologizes directly (don't hide behind passive language)
2. Acknowledges the specific impact on them
3. Explains briefly what happened (no excuses)
4. Details the resolution clearly
5. Offers appropriate goodwill gesture
6. Commits to doing better
7. Invites them to reach out with any concerns

Be genuine. A good apology can strengthen the relationship.

Write a cold outreach email.

Target: [JOB TITLE / TYPE OF PERSON]
Company type: [INDUSTRY, SIZE, ETC.]
What I'm selling: [PRODUCT OR SERVICE]
Main value proposition: [WHY THEY SHOULD CARE]

Research on this specific prospect:
[ANYTHING YOU KNOW ABOUT THEM—LINKEDIN, NEWS, ETC.]

Relevance trigger:
[WHY NOW—RECENT NEWS, COMMON PAIN POINT, ETC.]

Write an email that:
1. Has a specific, non-salesy subject line
2. Opens with something relevant to them (not about you)
3. Establishes credibility quickly
4. Offers one clear value proposition
5. Ends with a low-friction ask (not "Can we schedule a call?")

Keep it under 100 words. No fluff, no jargon. Sound like a human, not a template.

Create a follow-up email sequence.

Context: [WHAT HAPPENED BEFORE—COLD EMAIL, MEETING, PROPOSAL]
Prospect: [WHO THEY ARE]
What we're trying to achieve: [GOAL OF THE SEQUENCE]
Number of follow-ups: [HOW MANY EMAILS]
Timing between emails: [DAYS BETWEEN EACH]

Create a sequence where each email:
1. Adds new value (don't just "check in")
2. Has a different angle or hook
3. Gets progressively more direct
4. Remains professional and not pushy
5. Has a clear, easy next step

Include:
- Subject line for each
- Body copy
- Timing recommendation
- When to stop following up

Final email should be a "break-up" email that creates urgency without desperation.

Create responses to common sales objections.

What I sell: [PRODUCT OR SERVICE]
Target customer: [WHO BUYS THIS]
Price point: [APPROXIMATE COST]

Common objections:
[LIST THE OBJECTIONS YOU HEAR MOST]

For each objection, create:
1. Acknowledge the concern (don't dismiss it)
2. Reframe or address the underlying issue
3. Provide evidence or social proof
4. Transition back to value
5. Suggested follow-up question

Tone: Consultative, not combative. The goal is to understand and help, not to "win" the objection.

Create a pitch deck outline.

Audience: [WHO WILL SEE THIS DECK]
Purpose: [FIRST MEETING / DETAILED PROPOSAL / BOARD PRESENTATION]
Time available: [HOW LONG IS THE PRESENTATION]
Product/service: [WHAT YOU'RE PITCHING]

Problem you solve: [THE PAIN POINT]
Your solution: [HOW YOU SOLVE IT]
Key differentiators: [WHY YOU VS. ALTERNATIVES]
Social proof: [CUSTOMERS, RESULTS, CREDENTIALS]

Create a slide-by-slide outline:
1. Slide title
2. Key message (one sentence)
3. Supporting points or visuals needed
4. Transition to next slide

Follow a logical story arc: Problem → Solution → Why Us → Proof → Next Steps

Keep it focused. Better to go deep on fewer points than shallow on many.

Create a sales proposal.

Client: [COMPANY NAME]
Contact: [DECISION MAKER]
Opportunity: [WHAT THEY WANT TO BUY]
Deal size: [APPROXIMATE VALUE]

Their situation:
[WHAT PROMPTED THIS PROPOSAL—PROBLEMS, GOALS]

What we're proposing:
[YOUR SOLUTION]

Pricing:
[YOUR PRICING STRUCTURE]

Competition:
[WHO ELSE THEY'RE CONSIDERING, IF KNOWN]

Create a proposal that includes:
1. Executive summary (their problem, our solution, key benefit)
2. Understanding of their needs (prove you listened)
3. Proposed solution with clear deliverables
4. Timeline and milestones
5. Investment and payment terms
6. Why us (differentiators, relevant experience)
7. Case study or testimonial
8. Next steps with clear deadline
9. Terms and conditions

Write to the decision maker, but remember others may read it. Make it easy to say yes.

Create a win/loss analysis.

Outcome: [WON / LOST]
Client: [COMPANY NAME]
Deal size: [VALUE]
Sales cycle length: [TIME FROM FIRST CONTACT TO CLOSE]
Competitor: [WHO ELSE THEY CONSIDERED]

Key facts:
- Who was involved in the decision: [STAKEHOLDERS]
- Main criteria they evaluated: [WHAT MATTERED TO THEM]
- Our strengths in their eyes: [WHAT THEY LIKED]
- Our weaknesses in their eyes: [CONCERNS THEY HAD]
- Why they chose us / the competitor: [DECIDING FACTOR]

Create an analysis that:
1. Summarizes the situation
2. Identifies what went well
3. Identifies what could have been better
4. Extracts actionable lessons
5. Recommends specific improvements
6. Notes patterns if this connects to other wins/losses

Be honest. The goal is learning, not justification.

Write a blog post.

Topic: [WHAT THE POST IS ABOUT]
Target reader: [WHO THIS IS FOR]
Goal: [EDUCATE / DRIVE TRAFFIC / GENERATE LEADS / BUILD AUTHORITY]
Target length: [WORD COUNT]
Keyword focus (if SEO): [PRIMARY KEYWORD]

Key points to cover:
[LIST THE MAIN POINTS]

Angle or unique perspective:
[WHAT MAKES YOUR TAKE DIFFERENT]

Write a post that includes:
1. Engaging headline (and 2 alternatives)
2. Hook in the first paragraph
3. Clear structure with subheadings
4. Actionable takeaways
5. Examples or evidence
6. Conclusion with CTA

Tone: [PROFESSIONAL / CONVERSATIONAL / EDUCATIONAL / PROVOCATIVE]

Write for scanners—use short paragraphs, bullets, and subheads. Get to value fast.

Create a case study outline.

Client: [COMPANY NAME—OR ANONYMIZED DESCRIPTION]
Industry: [THEIR INDUSTRY]
Project/engagement: [WHAT YOU DID FOR THEM]
Results achieved: [MEASURABLE OUTCOMES]

Permission level: [FULL ATTRIBUTION / ANONYMOUS / SPECIFIC RESTRICTIONS]

Create an outline for a case study that includes:
1. Headline that leads with the result
2. Quick facts sidebar (industry, size, challenge, solution, result)
3. The challenge (their situation before)
4. The solution (what you did)
5. The process (how you approached it)
6. The results (specific, measurable)
7. Client quote (placeholder)
8. Key takeaways
9. CTA

Structure this as a story: Problem → Journey → Transformation. Include specific numbers wherever possible.

Write a video script.

Video type: [EXPLAINER / TUTORIAL / TESTIMONIAL / AD / SOCIAL]
Platform: [YOUTUBE / LINKEDIN / INSTAGRAM / WEBSITE]
Length: [TARGET DURATION]
Audience: [WHO WILL WATCH THIS]
Goal: [WHAT SHOULD VIEWERS DO AFTER WATCHING]

Key message:
[THE ONE THING VIEWERS SHOULD REMEMBER]

Points to cover:
[LIST MAIN CONTENT POINTS]

Write a script that includes:
1. Hook (first 3 seconds to grab attention)
2. Introduction (who this is for and what they'll learn)
3. Main content sections
4. Visual/b-roll suggestions in [brackets]
5. Call-to-action
6. End screen content

Write conversationally—this will be spoken. Include pacing notes. Time it so it fits the target duration.

Create a podcast episode outline.

Podcast name: [NAME]
Episode topic: [WHAT THIS EPISODE IS ABOUT]
Format: [SOLO / INTERVIEW / CO-HOSTED / PANEL]
Target length: [MINUTES]

Guest (if interview): [NAME, CREDENTIALS]
Guest expertise: [WHAT THEY'RE KNOWN FOR]

Audience: [WHO LISTENS]
What they should take away: [KEY LEARNING]

Create an outline with:
1. Episode title (and alternatives)
2. Episode description (for show notes)
3. Cold open / hook
4. Introduction
5. Main segments with talking points
6. Questions for guest (if applicable)
7. Transitions between sections
8. Wrap-up and CTA
9. Keywords for show notes

Include timestamps estimates. Make it detailed enough to keep things on track but flexible enough for natural conversation.

Create a whitepaper structure.

Topic: [SUBJECT OF THE WHITEPAPER]
Target audience: [WHO WILL READ THIS]
Goal: [LEAD GEN / EDUCATION / AUTHORITY BUILDING]
Length: [TARGET WORD COUNT OR PAGES]

Problem or question it addresses:
[WHAT ISSUE ARE YOU TACKLING]

Your perspective/thesis:
[YOUR MAIN ARGUMENT OR POSITION]

Key supporting evidence:
[DATA, RESEARCH, EXAMPLES YOU'LL INCLUDE]

Create a structure that includes:
1. Title (and alternatives)
2. Executive summary
3. Introduction and problem statement
4. Section outline with key points for each
5. Data/research section
6. Analysis and implications
7. Recommendations or solutions
8. Conclusion
9. About the company
10. Call-to-action

This should position you as a thought leader. Balance education with subtle promotion.

Create a webinar content plan.

Webinar title: [TOPIC]
Format: [PRESENTATION / DEMO / PANEL / WORKSHOP]
Duration: [LENGTH]
Audience: [WHO WILL ATTEND]
Goal: [LEADS / EDUCATION / PRODUCT DEMO / COMMUNITY]

Speaker(s): [WHO'S PRESENTING]
Co-marketing partner (if any): [PARTNER COMPANY]

Create a plan that includes:
1. Title and subtitle
2. Registration page copy (headline, benefits, speaker bio)
3. Agenda with time allocations
4. Content outline for each section
5. Engagement points (polls, Q&A, interactive elements)
6. Slides outline (key slides needed)
7. Q&A preparation (anticipated questions)
8. CTA and offer
9. Follow-up email sequence outline

Plan for a 60-minute webinar: 45 min content, 15 min Q&A. Keep slides visual, not text-heavy.

Write a tutorial guide.

Topic: [WHAT YOU'RE TEACHING]
Audience skill level: [BEGINNER / INTERMEDIATE / ADVANCED]
Goal: [WHAT WILL THEY BE ABLE TO DO AFTER]
Format: [WRITTEN / VIDEO SCRIPT / BOTH]

Prerequisites:
[WHAT THEY NEED TO KNOW OR HAVE BEFORE STARTING]

Steps to cover:
[LIST THE MAIN STEPS]

Create a tutorial that includes:
1. Clear title that states the outcome
2. Introduction (what they'll learn, why it matters)
3. Prerequisites checklist
4. Step-by-step instructions
5. Screenshots or visual placeholders
6. Common mistakes and how to avoid them
7. Troubleshooting section
8. Next steps or related tutorials

Write for someone doing this for the first time. Don't skip "obvious" steps. Test the tutorial yourself.

Create a high-resolution, studio-lit product photograph of [PRODUCT DESCRIPTION].

Scene setup:
- Surface: [polished marble / rustic wood / clean white / concrete]
- Lighting: Three-point softbox setup with soft, diffused highlights and minimal shadows
- Camera angle: Slightly elevated 45-degree shot to showcase product dimensions

Style requirements:
- Ultra-realistic with sharp focus on product details
- Subtle contact shadow for grounding
- Clean, professional composition with generous padding
- [Include steam/movement/lifestyle element if relevant]

Constraints:
- No watermarks, logos, or text
- No background distractions
- Preserve exact product geometry and any label text

Create an original, non-infringing logo for a company called [COMPANY NAME], a [BUSINESS TYPE/INDUSTRY].

Brand personality: [warm and approachable / bold and innovative / elegant and refined / playful and energetic]

Design requirements:
- Clean, vector-like shapes with strong silhouette
- Balanced negative space for visual clarity
- Works at both small (favicon) and large (billboard) sizes
- [Incorporate subtle reference to: specific element]

Style: Flat design, minimal strokes, no gradients unless essential
Background: Plain [white/transparent]
Output: Single centered logo with generous padding

Constraints:
- No watermarks
- No copyrighted or trademarked elements
- Original design only

Create a [Instagram post / LinkedIn banner / Twitter header] graphic for [PURPOSE/TOPIC].

Composition:
- Aspect ratio: [1:1 for Instagram / 16:9 for LinkedIn / 3:1 for Twitter header]
- [Significant negative space on left/right/top for text overlay] OR [bold, full-bleed visual]

Visual style: [Modern gradient / Bold geometric / Minimalist flat / Lifestyle photography style]
Color palette: [Specific brand colors or mood: professional blues / energetic oranges / calm earth tones]

Subject/scene: [DESCRIBE THE MAIN VISUAL ELEMENT]

Constraints:
- No text in image (text will be added separately)
- No watermarks or logos
- Suitable for professional social media

Create a website hero image for a [BUSINESS TYPE] company's landing page.

Scene: [DESCRIBE THE SCENE - office environment / abstract concept / lifestyle moment]
Mood: [Bright and optimistic / Professional and trustworthy / Bold and innovative]

Composition requirements:
- Aspect ratio: 16:9 (widescreen)
- Significant negative space on [left side / right side] for headline text overlay
- Subject positioned in [right third / left third] of frame

Lighting: [Natural daylight / Soft studio / Golden hour warmth]
Style: [Editorial photography / Modern 3D render / Artistic illustration]

Constraints:
- No text, logos, or watermarks
- Avoid generic stock photo aesthetics
- Colors should complement a [dark/light] website design

Create a realistic [billboard / bus stop ad / storefront sign] mockup featuring [PRODUCT/BRAND].

Environment: [Highway scene at sunset / Urban street corner / Shopping mall interior]
Time of day: [Golden hour / Night with city lights / Bright midday]

Billboard content:
- Headline text (EXACT, verbatim, no extra characters): "[YOUR HEADLINE]"
- Typography: [Bold sans-serif / Elegant serif], high contrast, [centered / left-aligned]
- Visual: [Product image / Lifestyle scene / Abstract graphic]

Style: Photorealistic mockup that looks like an actual photograph
Lighting: Match billboard illumination to environment lighting

Constraints:
- Text must appear exactly once and be perfectly legible
- No watermarks
- No additional logos or text beyond specified

Create a photorealistic professional headshot/portrait.

Subject: [DESCRIBE PERSON - age range, general appearance, expression]

Photography specifications:
- Framing: Head and shoulders portrait, centered
- Lens: 85mm portrait lens with soft background blur (bokeh)
- Lighting: Soft studio lighting, three-point setup with key light at 45 degrees
- Background: [Neutral gray / Soft gradient / Blurred office environment]

Style requirements:
- Professional but approachable expression
- Natural skin texture (visible pores, subtle imperfections—not over-retouched)
- [Business attire: suit/blazer / Smart casual: button-down shirt]
- Warm, natural color balance

Aspect ratio: 1:1 (square) for profile photos

Constraints:
- No heavy retouching or glamorization
- Natural, authentic appearance
- No watermarks

Create a detailed infographic explaining [TOPIC/PROCESS].

Purpose: [Explain a process / Compare options / Show statistics / Timeline]
Audience: [General public / Executives / Technical team / Students]

Content to visualize:
1. [First point/step]
2. [Second point/step]
3. [Third point/step]
[Add more as needed]

Design specifications:
- Layout: [Vertical flow / Horizontal timeline / Grid comparison / Circular process]
- Style: [Modern flat design / Illustrated icons / Data-visualization focused]
- Color scheme: [Specific brand colors or: professional blues / vibrant multicolor / monochromatic]

Text requirements:
- Section headers: Bold, clear hierarchy
- Labels: Concise, readable at small sizes
- Flow: Clear visual path from start to finish

Constraints:
- All text must be accurate and legible
- No watermarks
- Clean, uncluttered composition

Transform [SUBJECT/SCENE DESCRIPTION] into the artistic style of [STYLE REFERENCE].

Subject to render: [Detailed description of what should be shown]

Style specifications:
- Art style: [Van Gogh's swirling brushstrokes / Japanese woodblock print / Art Deco geometric / Watercolor illustration / Pixel art / 1980s corporate photography]
- Color palette: [Match original style's colors / Adapted modern palette / Specific colors]
- Texture: [Heavy impasto brushstrokes / Smooth gradients / Halftone dots]

Preserve from original:
- [Composition and layout]
- [Key subject positioning]
- [Overall mood/atmosphere]

Transform:
- Rendering technique and brushwork
- Color treatment
- Lighting interpretation

Constraints:
- Maintain recognizable subject
- No watermarks
- Original artwork inspired by style (not copying specific works)

Create a realistic mobile app UI mockup for [APP TYPE/PURPOSE].

App screens to show:
- [Primary screen: e.g., home feed / dashboard / product listing]
- Key features visible: [List 3-4 main UI elements]

Design specifications:
- Platform: [iOS style / Android Material / Custom modern]
- Color scheme: [Primary color + accents]
- Typography: Clean, readable system fonts
- Layout: [Tab navigation / Hamburger menu / Bottom nav bar]

Content on screen:
- Header: [App name or section title]
- Main content: [What the user sees]
- Navigation: [Bottom tabs / Top bar / Floating action button]

Presentation:
- Device frame: [iPhone 15 / Pixel / Generic smartphone]
- Background: [Solid color / Gradient / Lifestyle context]
- Angle: [Straight-on / Slight 3D perspective]

Constraints:
- Realistic, shippable UI—not concept art
- Practical spacing and touch targets
- No placeholder lorem ipsum—use realistic content

Create a [seamless / tileable] background texture or pattern.

Type: [Abstract gradient / Geometric pattern / Natural texture / Subtle noise]

Visual description:
- Primary element: [Soft organic shapes / Sharp geometric forms / Gradient mesh / Paper texture]
- Color palette: [Specific hex codes or: muted pastels / bold primaries / monochromatic / brand colors]
- Density: [Sparse with lots of negative space / Medium density / Dense pattern]

Purpose: [Website background / Presentation slide / Social media / Print material]

Technical requirements:
- Suitable for [text overlay / standalone decorative / subtle branding]
- [High contrast for dark text / Low contrast for overlay use]
- [Seamlessly tileable if needed]

Constraints:
- No recognizable objects or figures
- No text, logos, or watermarks
- Subtle enough to not compete with foreground content