Skip to main content
Back to Blog
ChatGPTprompt templatesGPT-4oAI prompts2026

50 Best ChatGPT Prompts in 2026: Copy-Paste Templates That Actually Work

50 copy-paste ChatGPT prompts for writing, coding, business, marketing, research, productivity, and creative tasks. Optimized for GPT-4o in 2026.

SurePrompts Team
March 27, 2026
27 min read

Most ChatGPT prompts floating around the internet are vague garbage. "Write me a blog post about marketing." Cool — enjoy your 500 words of beige filler. These 50 templates are different. They're structured to exploit what GPT-4o actually does well: following detailed instructions, switching between tools, and generating output you can use without rewriting half of it.

Why Most ChatGPT Prompts Fail

The gap between a mediocre prompt and a great one isn't cleverness — it's specificity. ChatGPT doesn't read your mind. It reads your words, and it optimizes for exactly what you ask for. Ask vaguely, get vaguely.

Three things make GPT-4o prompts work in 2026:

Context up front. Tell ChatGPT who you are, who the output is for, and what constraints exist before you make the request. Frontloading context changes everything.

Explicit format instructions. Don't hope for the right structure — specify it. Tables, bullet points, word counts, section headers. GPT-4o follows formatting instructions reliably when you're clear.

Tool awareness. GPT-4o can browse the web, run Python code, generate images with DALL-E, and use memory across conversations. The best prompts leverage these capabilities directly.

Build structured ChatGPT prompts in seconds with the AI prompt generator, or use the ChatGPT prompt generator for model-specific templates.

50
Copy-paste prompts organized by category — writing, coding, business, marketing, research, productivity, and creative

Writing Prompts (1–8)

1. Blog Post From Outline

code
You are a senior content writer. Write a 1,500-word blog post on [TOPIC].

Audience: [TARGET READER — e.g., startup founders]
Tone: conversational, direct, slightly opinionated
Structure:
- Hook opening (2-3 sentences, no "In today's world" filler)
- 4-5 sections with ## headers
- Short paragraphs (3-4 sentences max)
- End with a concrete, actionable takeaway

Include 3 specific real-world examples. No generic advice. Every claim 
should have evidence or a concrete illustration behind it.

2. Email That Gets Replies

code
Write a cold outreach email to [RECIPIENT ROLE] at [COMPANY TYPE].

Goal: [WHAT YOU WANT — meeting, intro, feedback]
My context: [WHO YOU ARE, WHAT YOU OFFER]
Their likely pain point: [WHAT THEY PROBABLY STRUGGLE WITH]

Rules:
- Under 120 words
- No "I hope this finds you well"
- Open with something specific about their company or role
- One clear ask, not three
- Subject line under 6 words

3. Rewrite for Different Audiences

code
Rewrite this text for three different audiences. Keep the core 
information identical — change vocabulary, tone, and complexity level.

Original text:
[PASTE TEXT]

Audience 1: [e.g., C-suite executives — concise, business impact focused]
Audience 2: [e.g., technical developers — detailed, precise]
Audience 3: [e.g., general consumers — simple, benefit-focused]

For each version, note the 3 biggest changes you made and why.

4. LinkedIn Post Series

code
Write 5 LinkedIn posts about [TOPIC] that I can publish over the next week.

My voice: [DESCRIBE — e.g., "pragmatic founder, no hustle culture, 
shares real numbers and honest failures"]
Goal: position me as knowledgeable about [AREA]

Each post:
- Hook first line (stop the scroll — under 15 words)
- 150-200 words
- One specific insight, story, or contrarian take per post
- End with a question or clear POV, not a generic CTA
- No hashtag spam (3 max, only if relevant)

Topics to cover:
1. [SUBTOPIC]
2. [SUBTOPIC]
3. [SUBTOPIC]
4. [SUBTOPIC]
5. [SUBTOPIC]

5. Sales Page Copy

code
Write sales page copy for [PRODUCT/SERVICE].

Product: [DESCRIPTION]
Price: [PRICE POINT]
Target buyer: [WHO AND WHY THEY'D BUY]
Main competitor: [WHAT THEY'RE CURRENTLY USING INSTEAD]
Key differentiator: [YOUR UNFAIR ADVANTAGE]

Structure:
1. Headline (benefit-driven, under 12 words)
2. Subheadline (expand on the headline, address the skeptic)
3. Problem section (3 pain points they'll recognize)
4. Solution section (how your product fixes each pain point)
5. Social proof section (format for testimonials I'll fill in)
6. FAQ (5 objections phrased as questions, with answers)
7. CTA (action-oriented, specific)

Tone: confident but not hype-y. Write like you're explaining to a 
smart friend why this product is worth their money.

6. Newsletter Intro

code
Write the opening section (150-200 words) for my weekly newsletter 
about [TOPIC].

This week's angle: [WHAT HAPPENED OR WHAT YOU WANT TO SAY]
Newsletter voice: [DESCRIBE — e.g., "sharp, slightly irreverent, 
treats readers as insiders"]
Subscriber count: [NUMBER — this affects tone]

The opening should:
- Start with a specific observation, not a greeting
- Set up the issue's theme in a way that creates curiosity
- Feel like a smart person's take, not a news summary
- Transition naturally to the first section

7. Case Study Narrative

code
Transform these raw details into a compelling case study.

Client: [NAME/INDUSTRY]
Problem: [WHAT THEY WERE DEALING WITH]
Solution: [WHAT YOU DID]
Results: [NUMBERS AND OUTCOMES]
Timeline: [HOW LONG]

Format:
- Title: "[Result] — How [Client Type] [Achieved Outcome]"
- The Challenge (150 words — make the reader feel the pain)
- The Approach (200 words — what you did and why)
- The Results (150 words — numbers front and center)
- Key Takeaway (2-3 sentences)

Write in third person. Use specific numbers. No fluff.

8. Content Repurposing

code
I have this long-form content. Repurpose it into multiple formats.

Original content:
[PASTE ARTICLE, TRANSCRIPT, OR DOCUMENT]

Create:
1. Twitter/X thread (8-12 tweets, each standalone)
2. LinkedIn post (200 words, professional angle)
3. Email newsletter blurb (100 words with a link CTA)
4. Instagram carousel script (10 slides — headline + 1-2 sentences each)
5. YouTube short script (60 seconds, hook → value → CTA)

Each format should emphasize different aspects of the original. 
Don't just shorten it — adapt the message for each platform's audience.

Coding Prompts (9–16)

9. Debug This Code

code
Debug this code. Don't just fix it — explain the root cause.

Language: [LANGUAGE]
What it should do: [EXPECTED BEHAVIOR]
What it actually does: [ACTUAL BEHAVIOR / ERROR MESSAGE]

Code:
[PASTE CODE]

Steps:
1. Identify the exact line(s) causing the issue
2. Explain WHY it fails (not just what's wrong)
3. Provide the fixed code
4. Add a comment at the fix explaining what changed
5. Suggest one defensive improvement to prevent similar bugs

10. Code Review

code
Review this code like a senior engineer. Be specific and actionable.

Language: [LANGUAGE]
Context: [WHAT THIS CODE DOES, WHERE IT FITS]

Code:
[PASTE CODE]

Evaluate:
- Bugs or logic errors (priority 1)
- Security vulnerabilities (priority 2)
- Performance issues (priority 3)
- Readability and maintainability (priority 4)

For each issue:
- Quote the specific line(s)
- Explain the problem
- Show the fix

End with: "If I could only change one thing, it would be..." and explain why.

11. Build a Feature From Scratch

code
Build [FEATURE] for my [APPLICATION TYPE].

Tech stack: [LANGUAGES, FRAMEWORKS, DATABASE]
Existing code context: [RELEVANT ARCHITECTURE DETAILS]
Requirements:
- [REQUIREMENT 1]
- [REQUIREMENT 2]
- [REQUIREMENT 3]

Provide:
1. File structure (which files to create/modify)
2. Complete, working code for each file
3. Any database migrations or schema changes needed
4. How to test it (manual steps + suggested unit tests)
5. Edge cases I should handle

Write production-ready code, not demos. Include error handling, 
input validation, and loading states.

12. Explain This Codebase

code
I'm joining a project and need to understand this code quickly.

[PASTE CODE — UP TO 4000 WORDS OR A KEY FILE]

Give me:
1. One-paragraph summary of what this code does
2. Architecture diagram (describe the flow in text)
3. Key functions/classes and what each is responsible for
4. The data flow — what goes in, what transformations happen, what comes out
5. Potential gotchas a new developer should know
6. The 3 files/functions I should read first to understand this codebase

Write for a developer who knows the language but not this project.

13. API Endpoint Design

code
Design a REST API for [FEATURE/RESOURCE].

Context: [APPLICATION DESCRIPTION]
Users: [WHO CALLS THIS API]
Authentication: [AUTH METHOD]

For each endpoint, provide:
- Method + path
- Request body/params (with types and validation rules)
- Response format (success and error)
- Status codes used
- Rate limiting recommendation
- Example curl command

Also include:
- Pagination strategy
- Versioning approach
- Any webhooks needed

14. Write Tests for This Code

code
Write comprehensive tests for this code.

Code:
[PASTE CODE]

Test framework: [jest / pytest / go test / etc.]

Include:
- Happy path tests for each public function
- Edge cases (empty input, null values, boundary conditions)
- Error cases (what should throw/return errors)
- At least one integration-style test if applicable

Each test should have a descriptive name that reads as a specification:
"should return empty array when no items match filter"
not: "test filter function"

15. Refactor for Readability

code
Refactor this code for readability without changing its behavior.

Code:
[PASTE CODE]

Rules:
- Preserve all functionality and edge case handling
- Improve variable/function names to be self-documenting
- Break long functions into smaller ones with clear responsibilities
- Remove dead code and redundant comments
- Add comments only where the "why" isn't obvious from the code

Show the refactored code, then list every change you made and why.

16. Database Schema Design

code
Design a database schema for [APPLICATION/FEATURE].

Requirements:
- [DATA REQUIREMENT 1]
- [DATA REQUIREMENT 2]
- [DATA REQUIREMENT 3]
- Expected scale: [NUMBER OF ROWS/USERS]

Database: [PostgreSQL / MySQL / MongoDB / etc.]

Provide:
1. Table/collection definitions with columns, types, and constraints
2. Indexes (and why each one is needed)
3. Relationships and foreign keys
4. Migration SQL or schema definition
5. 3-5 example queries for common operations
6. One thing you'd do differently at 10x scale

Business Prompts (17–24)

17. Competitive Analysis

code
Analyze [MY PRODUCT/COMPANY] against these competitors:

Competitor 1: [NAME + URL]
Competitor 2: [NAME + URL]
Competitor 3: [NAME + URL]

My product: [BRIEF DESCRIPTION]
My target market: [WHO I'M SELLING TO]

Use web browsing to research current pricing, features, and positioning.

Deliver:
1. Feature comparison matrix (table format)
2. Pricing comparison
3. Each competitor's strongest differentiator
4. Gaps in the market none of them are filling
5. My best positioning strategy given this landscape
6. Three specific moves I should make in the next 90 days

18. Financial Model

code
Use Code Interpreter to build a financial model for [BUSINESS TYPE].

Inputs:
- Monthly revenue: [AMOUNT OR GROWTH RATE]
- Customer acquisition cost: [CAC]
- Monthly churn: [PERCENTAGE]
- Operating costs: [BREAKDOWN]
- Starting cash: [AMOUNT]

Build a 24-month projection spreadsheet showing:
- Monthly recurring revenue
- Customer count
- Burn rate
- Runway
- Break-even point
- Unit economics (LTV, LTV:CAC ratio)

Create charts for: revenue growth, cash position, and customer growth.
Generate the model as a downloadable CSV.

19. Business Plan One-Pager

code
Write a one-page business plan for [BUSINESS IDEA].

Include:
1. Problem (3 sentences — specific, felt pain)
2. Solution (3 sentences — what you build, how it works)
3. Target market (size + specific customer profile)
4. Business model (how you make money, pricing)
5. Traction (what you've done so far, or validation plan)
6. Competition (who else, why you win)
7. Team (relevant experience)
8. Ask (what you need, what it gets you)

Total: under 500 words. Every sentence should earn its place. 
Write for an investor with 2 minutes and zero patience for fluff.

20. Meeting Agenda and Follow-Up

code
Create a meeting agenda and post-meeting follow-up template.

Meeting type: [e.g., weekly team sync, client kickoff, board meeting]
Duration: [MINUTES]
Attendees: [ROLES, NOT NAMES]
Goal: [WHAT DECISIONS NEED TO BE MADE]

Agenda:
- Time allocation for each section
- Specific questions to answer (not just "discuss X")
- Pre-read requirements

Follow-up template:
- Decisions made
- Action items (owner + deadline)
- Open questions carried forward
- Next meeting date

21. Pricing Strategy

code
Help me set pricing for [PRODUCT/SERVICE].

What it does: [DESCRIPTION]
Target customer: [WHO]
Current price (if any): [AMOUNT]
Competitors charge: [RANGE]
My costs per unit/customer: [AMOUNT]
Value delivered: [QUANTIFY IF POSSIBLE — time saved, revenue gained]

Analyze:
1. Cost-plus pricing calculation
2. Value-based pricing calculation
3. Competitive positioning options (premium, mid-market, undercut)
4. Recommended tier structure (if applicable)
5. What I should test first
6. When to raise prices and by how much

22. Pitch Deck Script

code
Write a pitch deck script for [BUSINESS]. Each slide should be 
30-60 seconds of spoken content.

Slide 1: Hook (the problem in one vivid sentence)
Slide 2: Problem (quantify the pain)
Slide 3: Solution (demo-ready description)
Slide 4: Market size (TAM → SAM → SOM)
Slide 5: Business model
Slide 6: Traction (metrics or milestones)
Slide 7: Competition (why you win)
Slide 8: Team (why these people)
Slide 9: Ask (amount + use of funds)
Slide 10: Close (memorable one-liner)

For each slide, provide:
- The visual (what should be on screen)
- The spoken script (what I say)
- The one thing the audience should remember from this slide

23. SOP for a Business Process

code
Write a Standard Operating Procedure for [PROCESS].

Process: [WHAT IT IS]
Who performs it: [ROLE]
Frequency: [HOW OFTEN]
Tools used: [SOFTWARE, SYSTEMS]
Current pain point: [WHAT GOES WRONG NOW]

Include:
1. Purpose (one sentence)
2. Scope (what's included and excluded)
3. Prerequisites (what needs to be true before starting)
4. Step-by-step procedure (numbered, each step is one action)
5. Decision points (if X, do Y; if Z, do W)
6. Quality checks (how to verify each critical step)
7. Troubleshooting (top 3 things that go wrong and how to fix them)
8. Escalation path (when to involve someone else)

24. Quarterly OKR Framework

code
Help me set OKRs for [TEAM/COMPANY] for [QUARTER].

Context:
- Company stage: [e.g., Series A, 30 employees]
- Last quarter's results: [KEY WINS AND MISSES]
- Strategic priority this quarter: [ONE SENTENCE]

Create 3 Objectives, each with 3 Key Results.

Rules:
- Objectives are qualitative and inspiring
- Key Results are measurable and have deadlines
- Include a stretch target (70% confidence of hitting)
- Each KR has a specific metric, current baseline, and target
- Add one "health metric" per objective to prevent gaming the KRs

Marketing Prompts (25–32)

25. SEO Content Brief

code
Create a detailed content brief for the keyword "[TARGET KEYWORD]".

Use web browsing to analyze the current top 10 results.

Include:
1. Search intent analysis (informational, transactional, navigational)
2. Recommended title (with keyword, under 60 chars)
3. Meta description (under 155 chars, includes CTA)
4. Article structure (H2s and H3s based on what top results cover)
5. Topics to include that competitors miss
6. Word count target (based on top results)
7. Internal linking opportunities
8. Featured snippet opportunity and how to capture it
9. 5 related keywords to include naturally

26. Ad Copy Variations

code
Write ad copy for [PRODUCT/SERVICE] across multiple platforms.

Product: [DESCRIPTION]
Target audience: [WHO]
Key benefit: [THE #1 THING]
Budget context: [e.g., testing phase, scaling winner]

Write 3 variations for each:
1. Google Search Ad (3 headlines × 30 chars + 2 descriptions × 90 chars)
2. Facebook/Instagram ad (primary text + headline + description)
3. LinkedIn ad (introductory text + headline)

Each variation should test a different angle:
- Variation A: Pain point focused
- Variation B: Benefit focused
- Variation C: Social proof / urgency focused

27. Product Launch Checklist

code
Create a comprehensive product launch plan for [PRODUCT].

Launch date: [DATE]
Product: [DESCRIPTION]
Target audience: [WHO]
Budget: [RANGE]
Team size: [NUMBER]

Provide a week-by-week timeline covering:
- Pre-launch (4 weeks out): teaser content, email list building, beta access
- Launch week: announcements, outreach, press, social
- Post-launch (2 weeks): follow-up, optimization, feedback collection

For each task include:
- Owner role (marketing, product, engineering, design)
- Priority (must-do vs nice-to-have)
- Dependencies

28. Customer Persona

code
Build a detailed customer persona for [PRODUCT/SERVICE].

What we sell: [DESCRIPTION]
Price point: [RANGE]
Current customers: [WHAT YOU KNOW ABOUT THEM]

Create a persona that includes:
- Demographics (age, income, location, job title)
- Psychographics (values, fears, aspirations)
- Daily routine (where do they spend time online and offline)
- Buying triggers (what makes them start looking for a solution)
- Objections (top 3 reasons they DON'T buy)
- Decision process (who else is involved, how long it takes)
- Channels to reach them (ranked by effectiveness)
- A quote that captures their core frustration

Make it specific enough to actually use, not a generic "marketing Mary."

29. A/B Test Plan

code
Design an A/B test for [WHAT YOU WANT TO TEST].

Current state: [WHAT EXISTS NOW]
Hypothesis: [WHAT YOU THINK WILL IMPROVE AND WHY]
Primary metric: [WHAT YOU'RE MEASURING]
Traffic: [MONTHLY VISITORS/USERS]

Provide:
1. Control vs variant description
2. Sample size calculation (use Code Interpreter)
3. Expected test duration
4. Statistical significance threshold
5. Guardrail metrics (what shouldn't get worse)
6. Implementation notes
7. Decision framework (when do we call it)

30. Email Marketing Funnel

code
Design a [NUMBER]-email nurture sequence for [GOAL].

Context:
- Product: [WHAT YOU SELL]
- Entry point: [HOW THEY JOINED — lead magnet, sign-up, webinar]
- Goal: [CONVERSION TARGET]
- Audience knowledge level: [BEGINNER / INTERMEDIATE / EXPERT]

For each email:
- Send timing (days after trigger)
- Subject line + preview text
- Email goal (educate, build trust, soft sell, hard sell)
- Body outline (150 words max per email)
- CTA (one per email)
- Segment logic (who gets this vs who skips)

31. Brand Voice Guide

code
Create a brand voice guide for [COMPANY/PRODUCT].

About us: [DESCRIPTION]
Target audience: [WHO]
Current brand perception: [HOW PEOPLE SEE US NOW]
Desired brand perception: [HOW WE WANT TO BE SEEN]
Brands we admire (for tone): [2-3 EXAMPLES]

Include:
1. Voice attributes (3 adjectives with definitions)
2. "We are / We are not" table
3. Vocabulary list (words we use, words we avoid)
4. Tone variations by context (social media, support, sales, error messages)
5. Example rewrites: take 3 generic sentences and show our voice
6. Grammar and style rules (Oxford comma? Emoji? Sentence case?)

32. Social Media Content Calendar

code
Create a 30-day social media content calendar for [BRAND/PRODUCT].

Platforms: [WHICH ONES]
Posting frequency: [PER PLATFORM PER WEEK]
Goals: [AWARENESS / ENGAGEMENT / TRAFFIC / SALES]
Key dates this month: [EVENTS, LAUNCHES, HOLIDAYS]

For each post provide:
- Date and platform
- Content type (text, image, video, carousel, poll)
- Hook/headline
- Full caption (platform-appropriate length)
- CTA
- Hashtag set (if applicable)

Content mix: 40% value/educational, 30% engagement, 20% promotional, 
10% behind-the-scenes/personality.

Research & Analysis Prompts (33–38)

33. Literature Review

code
Conduct a structured analysis of [TOPIC] based on what you know.

Focus areas:
- [ASPECT 1]
- [ASPECT 2]
- [ASPECT 3]

For each area:
1. Current consensus (what most experts agree on)
2. Active debates (where experts disagree)
3. Recent developments (last 1-2 years)
4. Gaps (what hasn't been studied or solved)
5. Practical implications

Format as a structured report with section headers. 
Flag any claims where your knowledge might be outdated.

34. Data Analysis Prompt

code
Use Code Interpreter to analyze this dataset.

[UPLOAD FILE OR PASTE DATA]

Questions:
1. What are the key trends in this data?
2. Are there any outliers or anomalies?
3. What correlations exist between [VARIABLE A] and [VARIABLE B]?
4. Create visualizations for: [SPECIFY CHART TYPES]
5. What would you recommend based on these findings?

Provide statistical summaries, charts, and a plain-English interpretation 
a non-technical stakeholder would understand.

35. Industry Trend Report

code
Use web browsing to research [INDUSTRY] trends in 2026.

Create a trend report covering:
1. Top 5 trends shaping [INDUSTRY] right now
2. For each trend:
   - What's happening (with specific examples)
   - Why it matters
   - Who's winning and losing
   - What it means for [MY ROLE/COMPANY TYPE]
3. One trend most people are ignoring
4. Three predictions for the next 12 months
5. Sources for each major claim

Write for a [ROLE] who needs to brief their team on what's changing.

36. Decision Framework

code
Help me make this decision using a structured framework.

Decision: [WHAT I'M DECIDING]
Options:
A. [OPTION A]
B. [OPTION B]
C. [OPTION C — if applicable]

Context: [RELEVANT BACKGROUND]
Constraints: [TIME, BUDGET, RESOURCES, NON-NEGOTIABLES]
What matters most: [RANKED CRITERIA]

Steps:
1. Summarize each option in 2-3 sentences
2. Create a weighted scoring matrix
3. Identify risks for each option (probability × impact)
4. What's the reversibility of each choice?
5. Recommendation with a clear "If X, then Y" contingency

37. Process Documentation From Scratch

code
Help me document a process I know how to do but haven't written down.

I'll describe [PROCESS] in rough, out-of-order notes. Your job is to 
turn it into clean, followable documentation.

My rough notes:
[BRAIN DUMP EVERYTHING YOU KNOW ABOUT THE PROCESS]

Turn this into:
1. Process overview (one paragraph)
2. When to use this process (triggers)
3. Prerequisites
4. Step-by-step procedure (numbered, one action per step)
5. Screenshots/diagram descriptions (tell me what to capture)
6. Common mistakes and how to avoid them
7. FAQ (3-5 questions someone new would ask)

Ask me clarifying questions about anything ambiguous before writing 
the final version.

38. Survey Design

code
Design a survey to learn [WHAT YOU WANT TO KNOW] from [AUDIENCE].

Context: [WHY YOU'RE RUNNING THIS SURVEY]
Expected respondents: [NUMBER]
Max completion time: [MINUTES]

Provide:
1. Introduction text (sets expectations, motivation to complete)
2. 10-15 questions organized by theme
3. For each question: type (multiple choice, scale, open-ended), 
   why it's included, and how you'll use the answer
4. Skip logic recommendations
5. Closing text and next steps
6. Analysis plan (how to interpret results)

Bias check: flag any questions that might lead respondents toward 
a particular answer.

Productivity Prompts (39–44)

39. Learn Any Skill in 30 Days

code
Create a 30-day learning plan for [SKILL].

My current level: [BEGINNER / SOME EXPERIENCE / INTERMEDIATE]
Time available: [HOURS PER DAY]
Learning style: [READING / VIDEO / HANDS-ON / MIX]
Goal: [WHAT I WANT TO BE ABLE TO DO BY DAY 30]

For each week:
- Focus area and learning objectives
- Resources (specific — titles, URLs, channels)
- Daily practice task (15-30 minutes, builds on previous days)
- End-of-week milestone (concrete thing I can demonstrate)

Also include:
- Day 1 diagnostic (assess where I actually am)
- Day 15 checkpoint (am I on track? adjustment criteria)
- Day 30 final project (proves I learned the skill)

40. Weekly Review Template

code
I'm going to paste my notes, todos, and calendar from this week. 
Help me run a structured weekly review.

[PASTE YOUR MESSY NOTES, TASK LISTS, CALENDAR HIGHLIGHTS]

Process:
1. Wins: what got done that mattered
2. Misses: what didn't happen and why (be honest, not kind)
3. Lessons: one thing I'd do differently
4. Next week's top 3 priorities (based on what actually moves the needle)
5. One thing to stop doing (energy drain with low ROI)
6. Calendar audit: meetings I should decline next week

Format as a clean, skimmable document I can reference all week.

41. Automate My Workflow

code
I have a repetitive workflow that I want to automate or streamline.

Current process:
[DESCRIBE STEP BY STEP WHAT YOU DO MANUALLY]

Tools I already use: [LIST SOFTWARE]
Technical skill level: [NON-TECHNICAL / SOME CODING / DEVELOPER]
Budget for new tools: [RANGE OR $0]

Provide:
1. Quick wins (things I can automate today with current tools)
2. Medium effort (new tools or simple scripts)
3. Full automation (if I want to invest time to build it right)
4. For each suggestion: estimated time saved per week
5. Code/setup instructions for the top recommendation

42. Meeting Notes to Action Items

code
Convert these messy meeting notes into structured action items.

Meeting notes:
[PASTE RAW NOTES, TRANSCRIPT, OR BRAIN DUMP]

Extract:
1. Decisions made (list with one-sentence context each)
2. Action items (format: [Owner] will [action] by [deadline])
3. Open questions (unresolved items that need follow-up)
4. Key discussion points (3-5 sentence summary)
5. Next steps and follow-up meeting agenda suggestions

If owners or deadlines aren't clear from the notes, flag them as 
"[ASSIGN OWNER]" and "[SET DEADLINE]" rather than guessing.

43. Complex Spreadsheet Formula

code
I need a spreadsheet formula for [WHAT IT SHOULD DO].

Spreadsheet app: [Google Sheets / Excel]
Data layout:
- Column A: [WHAT'S IN IT]
- Column B: [WHAT'S IN IT]
- Column C: [WHAT'S IN IT]
[ADD MORE AS NEEDED]

Expected behavior:
- Input example: [SAMPLE DATA]
- Expected output: [WHAT THE FORMULA SHOULD RETURN]
- Edge cases: [WHAT HAPPENS WITH BLANKS, ERRORS, ETC.]

Provide:
1. The formula
2. Plain-English explanation of what each part does
3. How to drag/copy it for multiple rows
4. A simpler alternative if one exists

44. Negotiation Prep

code
Help me prepare for a negotiation.

Situation: [WHAT I'M NEGOTIATING — salary, contract, deal, price]
My position: [WHAT I WANT]
Their likely position: [WHAT THEY'LL PROBABLY OFFER]
My BATNA: [BEST ALTERNATIVE IF THIS FALLS THROUGH]
Relationship context: [NEW / ONGOING / HIGH STAKES]

Prepare:
1. My opening position and anchor
2. Three concessions I can make (ranked by cost to me)
3. Three things to ask for beyond the main item
4. Their likely objections and my responses
5. Walk-away point (non-negotiable minimum)
6. Opening statement (exactly what to say in the first 60 seconds)
7. Power phrases for common pressure tactics

Creative Prompts (45–50)

45. DALL-E Image for a Specific Use Case

code
Generate an image for [USE CASE — blog header, social post, 
presentation slide, product mockup].

Subject: [WHAT SHOULD BE IN THE IMAGE]
Style: [PHOTOREALISTIC / ILLUSTRATION / FLAT DESIGN / WATERCOLOR / etc.]
Mood: [BRIGHT AND ENERGETIC / MOODY AND DRAMATIC / CLEAN AND MINIMAL / etc.]
Color palette: [SPECIFY OR "complement my brand colors: #XXX, #YYY"]
Aspect ratio: [16:9 / 1:1 / 9:16]
Text in image: [NONE / SPECIFIC TEXT TO INCLUDE]

DO NOT include: [ANYTHING YOU WANT EXCLUDED]

After generating, suggest 2 variations that would test different 
visual approaches for the same use case.

46. Story or Narrative Structure

code
Help me develop a narrative structure for [PURPOSE — presentation, 
pitch, article, brand story].

Core message: [WHAT THE AUDIENCE SHOULD THINK/FEEL/DO AFTER]
Audience: [WHO]
Format: [SPOKEN / WRITTEN / VIDEO]
Length: [DURATION OR WORD COUNT]

Build the narrative using:
1. Hook (the opening moment that demands attention)
2. Context (just enough background — no throat clearing)
3. Tension (the problem, conflict, or gap)
4. Turn (the insight, discovery, or solution)
5. Resolution (the outcome with proof)
6. Call to action (what happens next)

Write the full narrative, then separately provide the "skeleton" 
(one sentence per beat) for easy revision.

47. Creative Brief

code
Write a creative brief for [PROJECT — ad campaign, video, 
rebrand, content series].

Background: [CONTEXT]
Objective: [WHAT SUCCESS LOOKS LIKE]
Target audience: [PRIMARY AND SECONDARY]
Key message: [ONE SENTENCE]
Tone: [DESCRIBE]
Deliverables: [WHAT NEEDS TO BE PRODUCED]
Budget: [RANGE]
Timeline: [KEY DATES]

Include:
- Mandatory elements (logo, tagline, legal)
- Inspiration references (describe the vibe, don't link copyrighted work)
- What this should NOT be (common pitfalls)
- Success metrics (how we'll know it worked)

48. Worldbuilding for Fiction

code
Help me build a consistent world for [GENRE] fiction.

Core concept: [ONE-SENTENCE PREMISE]
Setting: [TIME PERIOD / LOCATION / UNIVERSE TYPE]
Tone: [DARK / HOPEFUL / SATIRICAL / GROUNDED / etc.]

Develop:
1. Geography and key locations (3-5 places with personality)
2. Social structure (power dynamics, class, culture)
3. Rules of the world (what's different from reality — and the limits)
4. History (3 key events that shaped the present)
5. Factions or groups (2-4, with competing goals)
6. Sensory details (what does this world smell, sound, look like)
7. Internal logic check (flag any contradictions)

Ask me 5 questions to fill gaps before finalizing.

49. Brainstorm With Constraints

code
I need creative ideas for [CHALLENGE] with these constraints.

Challenge: [WHAT I'M TRYING TO SOLVE/CREATE]
Constraints:
- Budget: [AMOUNT OR "zero"]
- Time: [DEADLINE]
- Resources: [WHAT I HAVE AVAILABLE]
- Non-negotiables: [WHAT CAN'T CHANGE]

Generate:
1. 5 "safe" ideas (proven approaches, low risk)
2. 5 "stretch" ideas (creative but feasible)
3. 3 "wild" ideas (if constraints were loosened)

For each idea: one-sentence description + the key risk + first step 
to test it. Then recommend your top 2 and explain why.

50. Prompt Engineering Prompt

code
I want to get better results from ChatGPT for [TASK TYPE].

What I've been doing:
[PASTE YOUR CURRENT PROMPT]

What I'm getting:
[DESCRIBE THE OUTPUT AND WHAT'S WRONG WITH IT]

What I actually want:
[DESCRIBE THE IDEAL OUTPUT]

Help me:
1. Diagnose what's wrong with my current prompt
2. Rewrite it with specific improvements
3. Explain each change and why it matters
4. Give me 2 alternative approaches to the same task
5. Create a checklist I can use to improve my prompts going forward

ChatGPT-Specific Power Tips

1

Use Custom Instructions. Set your role, preferences, and output format once. ChatGPT applies them to every conversation so you don't repeat yourself.

2

Reference memory. Say "Remember that I prefer concise answers" or "Reference what we discussed about my marketing strategy." ChatGPT's memory persists across conversations.

3

Chain tools. Ask ChatGPT to browse the web, then analyze results with Code Interpreter, then generate a DALL-E image — all in one prompt. Tool chaining is where GPT-4o shines.

4

Upload files. Drag in PDFs, spreadsheets, images, or code files. ChatGPT can read, analyze, and transform them. Stop copy-pasting.

5

Use Code Interpreter for data. Any time you have a CSV, financial data, or need calculations, ask ChatGPT to use Code Interpreter. It runs real Python — not guesses.

6

Be specific about length. "Short" means different things to everyone. Say "3 sentences" or "under 200 words" or "fill one page."

Before

Write me a marketing email.

After

Write a 120-word cold outreach email to SaaS CTOs. Goal: book a 15-minute demo call. Open with a specific pain point about developer productivity. One clear CTA. No "I hope this finds you well." Subject line under 6 words.

Start Building Better Prompts

These 50 templates work because they give ChatGPT what it needs: context, constraints, and clear output specifications. The difference between a useless response and a genuinely helpful one is almost always in the prompt.

The AI prompt generator builds structured prompts like these automatically — describe what you need, get a ready-to-paste prompt optimized for GPT-4o. Or browse the Template Builder for hundreds of pre-built templates across every category. If you find yourself reusing the same prompt patterns, consider building a Custom GPT that packages your best prompts, system instructions, and reference files into a reusable assistant.

For a deeper dive into getting the most out of ChatGPT, read our guide on how to use ChatGPT like a pro.

Ready to Level Up Your Prompts?

Stop struggling with AI outputs. Use SurePrompts to create professional, optimized prompts in under 60 seconds.

Try AI Prompt Generator