Write Faster, Sharper, and More Persuasively with ChatGPT

Write a 1,200-word blog post about [topic] for an audience of [target audience]. Use this outline: [paste outline]. Write in a [conversational/authoritative/witty] tone. Include a hook in the introduction that references [specific pain point], use subheadings for scannability, and end with a clear call to action pointing readers to [desired next step].

I have these raw notes from my research on [topic]: [paste notes]. Turn them into a well-structured blog post of approximately [word count] words for [target audience]. Organize the information logically, remove redundancies, add transitions between sections, and flag any claims that need a source citation with [CITATION NEEDED].

Write a listicle titled "[number] [adjective] Ways to [achieve outcome]" for [target audience]. For each item, include: a concise subheading, a 2-3 sentence explanation of why it works, and one concrete example or actionable step the reader can take immediately. Avoid generic advice - every point should pass the "so what?" test.

Write 3 different introductions for a blog post about [topic] targeting [audience]. Version 1: Open with a surprising statistic or counterintuitive claim. Version 2: Open with a relatable scenario that illustrates [pain point]. Version 3: Open with a bold, contrarian statement. Each intro should be 80-120 words and transition naturally into the thesis: [your main argument].

Here is a blog post written for [original audience]: [paste post]. Rewrite it for [new audience] by adjusting the vocabulary, examples, and framing. Replace jargon they wouldn't know with accessible language, swap case studies for ones relevant to their industry, and shift the value proposition to emphasize [what this new audience cares about]. Keep the core argument intact.

Write a conclusion for a blog post about [topic]. The post's main argument is [thesis]. Summarize the key takeaways in 2-3 sentences without simply repeating the subheadings. Then write a call to action that motivates readers to [desired action] by connecting it directly to the benefit they just read about. The tone should be [encouraging/urgent/reflective] and the conclusion should be under 150 words.

Write landing page copy for [product/service] using the Problem-Agitate-Solution framework. Target audience: [describe audience and their main frustration]. Problem: Describe [pain point] in language the audience actually uses. Agitate: Expand on the consequences of not solving this - lost time, money, or opportunity. Solution: Introduce [product/service] as the answer, listing 3 specific benefits with proof points. End with a CTA button text and one supporting line that reduces purchase anxiety.

Write 15 email subject lines for a [type of email: welcome, promotional, re-engagement, newsletter] about [topic/offer]. The target audience is [audience]. Write 5 using curiosity gaps, 5 using specific numbers or data, and 5 using urgency or exclusivity. Each subject line should be under 50 characters. After the list, rank your top 3 and explain why they would outperform the others based on open-rate psychology.

Write a product description for [product name] in [word count] words. Target buyer: [describe buyer persona]. Structure: Lead with the single biggest benefit (not a feature). Then list [number] features, each translated into a benefit using the format "Feature → so you can [outcome]." Close with a micro-CTA. Avoid superlatives like "best" or "revolutionary." Use sensory or specific language instead.

Write 4 variations of [platform: Google Ads/Facebook/LinkedIn] ad copy for [product/service] targeting [audience]. Each variation should use a different angle: (1) social proof, (2) pain point, (3) aspiration/outcome, (4) scarcity or urgency. Follow the platform's character limits: [specify limits]. Include the primary keyword "[keyword]" naturally in each version. For each ad, write the headline, body text, and CTA.

Here is my current copy: [paste copy]. Rewrite it to be more persuasive. Specifically: Replace passive voice with active voice. Replace vague claims ("We help businesses grow") with specific ones ("We helped 200+ SaaS companies increase trial conversions by 30%"). Cut filler words and redundant phrases. Strengthen the CTA. Keep the same length or shorter. Show me the before and after for each change you make.

Write a 3-email sales sequence for [product/service] targeting [buyer persona] who [describe where they are in the funnel: downloaded a lead magnet, signed up for a trial, attended a webinar]. Email 1: Deliver value related to [topic of lead magnet/webinar], subtly introduce the product. Email 2: Address the #1 objection ("[specific objection]") with a case study or proof point. Email 3: Create urgency with [offer/deadline] and include a direct CTA. Each email should be under 200 words. Write subject lines for each.

Edit the following text for clarity and conciseness. Cut wordiness, eliminate redundancy, replace jargon with plain language where possible, and break long sentences into shorter ones. Do not change my meaning, voice, or key terminology. For each significant edit, add a brief [Editor's note: reason] so I understand the change. Here is the text: [paste text].

Read the following text as a critical editor. Identify: (1) Any logical gaps where a claim is made without sufficient support. (2) Any leaps in reasoning where the connection between paragraphs or ideas is unclear. (3) Any places where a counterargument should be acknowledged. (4) Any sections that feel redundant or could be cut without losing meaning. For each issue, quote the specific passage and suggest a concrete fix. Here is the text: [paste text].

Here are 3 examples of writing in our brand voice: [paste 3 samples]. Analyze the tone, sentence structure, vocabulary level, and personality traits of this voice. Then rewrite the following text to match this brand voice exactly while keeping the original information and meaning intact: [paste text to rewrite]. After the rewrite, list 5 specific style rules you extracted from the samples.

Proofread the following text. Fix grammar, spelling, and punctuation errors. Check for consistency in: (1) serial comma usage, (2) capitalization of key terms, (3) number formatting (numerals vs. spelled out), (4) heading style. Use [preferred style guide: AP/Chicago/internal] as the reference. List every change you made in a numbered changelog below the corrected text. Here is the text: [paste text].

Rewrite the following text at a [grade level, e.g., 8th grade] reading level. Simplify sentence structure and replace technical jargon with everyday language, but do NOT remove nuance or oversimplify the ideas. Keep all specific data, numbers, and proper nouns. Maintain a [professional/friendly/neutral] tone. After the rewrite, show the Flesch-Kincaid readability score of both versions. Here is the text: [paste text].

The following text is [current word count] words. Cut it to approximately [target word count] words - a [percentage]% reduction. Prioritize cutting: (1) redundant phrases and filler words, (2) unnecessary qualifiers and hedging language, (3) paragraphs that repeat a point already made. Do NOT cut: specific data, quotes, unique examples, or key arguments. Preserve the overall structure and flow. Here is the text: [paste text].

Generate 10 blog post titles for an article about [topic] targeting the keyword "[primary keyword]." Each title should include the keyword naturally (not forced). Write 3 titles using numbers (listicles), 3 using "how to" format, 2 using a question format, and 2 using a bold or contrarian angle. Keep every title under 60 characters for SEO. After the list, recommend the top 2 for both search ranking and click-through rate and explain your reasoning.

Write 10 social media headlines for a post about [topic/content] on [platform: Twitter/LinkedIn/Instagram]. The target audience is [audience]. Each headline should be a standalone hook - no clicks required to get value, but curiosity to learn more. Use these power techniques across the 10: pattern interrupts, unexpected juxtapositions, specific numbers, "You" addressing the reader, micro-stories in one sentence. Each headline should be under [character limit] characters.

Write 10 newsletter subject lines for an edition about [this week's content/topic]. My newsletter audience is [describe subscribers]. My open rate average is [X%] and I want to beat it. Write 5 subject lines that create curiosity without being clickbait, 3 that lead with a specific insight or number from the content, and 2 that are personal or conversational. Keep all under 45 characters. Avoid spam trigger words. Rank your top 3.

I'm hosting a [webinar/workshop/event] about [topic] for [target audience]. The key takeaway attendees will get is [main benefit]. Generate 8 event titles: 4 that emphasize the transformation or outcome ("From X to Y"), 2 that use a "masterclass" or "blueprint" framework, and 2 that are short and punchy (under 6 words). Each title should make a busy professional think "I can't miss this." Avoid clichés like "unlock" or "unleash."

I want to A/B test the title of my [blog post/landing page/email] about [topic]. The current title is: "[current title]." Generate 5 alternative titles, each testing a different variable against the original: (1) different emotional trigger, (2) different number or specificity level, (3) different format (question vs. statement), (4) different audience callout, (5) shorter or punchier version. For each pair, explain what hypothesis the A/B test would validate.

I'm writing a [guide/ebook/report/course] about [topic] with [number] chapters. Here is a brief summary of each chapter: [paste chapter summaries]. Write 2 title options per chapter: one that is clear and descriptive (tells the reader exactly what they'll learn), and one that is intriguing and benefits-driven (makes the reader want to read the chapter). Titles should be consistent in style and parallel in grammatical structure across all chapters.

Turn the following case study data into a compelling story: Client: [name/industry]. Challenge: [describe problem]. Solution: [what was implemented]. Results: [metrics and outcomes]. Structure it as a narrative arc: Set the scene (who is the protagonist and what's at stake), build tension (what was failing and why), introduce the turning point (the decision to change), show the resolution (implementation and results), and end with the lesson learned. Write it in [word count] words. Make the reader feel the stakes, not just read the data.

Write our brand origin story using these facts: Founder(s): [names]. Year founded: [year]. The problem we saw: [describe the frustration or gap]. The "aha moment": [describe what triggered the idea]. Early struggles: [describe obstacles]. First breakthrough: [describe turning point]. Where we are now: [current state]. Write it in first person (as the founder) in [word count] words. Tone: [authentic/scrappy/visionary/humble]. Focus on the emotional journey, not the business plan. Make readers root for us.

My article about [topic] currently opens with this dry introduction: [paste intro]. Rewrite it three ways, each opening with a different storytelling device: (1) A micro-story about a real or composite character who experienced [related problem] - use vivid, specific details. (2) A "imagine this" scenario that puts the reader inside the situation. (3) A historical anecdote or unexpected origin story that connects to the topic. Each version should be 80-120 words and transition naturally into the article's thesis.

Write a transformation story about [person/company/situation] for use in [marketing copy/presentation/blog post]. Before state: [describe the frustrating situation in detail - emotions, daily reality, failed attempts]. The catalyst: [what finally pushed them to try something different]. The journey: [key steps taken, including one moment of doubt or setback]. After state: [describe the new reality with specific, measurable improvements]. Write it in [word count] words. Make the "before" vivid enough that readers who share that pain feel seen.

I need to present these statistics in a blog post without it reading like a research report: [paste 5-10 data points]. Write a narrative section of [word count] words that weaves these numbers into a story. Use techniques like: anchoring a stat to a human moment ("That's one in every classroom"), comparing to something tangible ("enough to fill [X]"), and placing the most surprising stat at a moment of narrative tension. The audience is [describe audience] and the overall story is about [topic/argument].

Write API documentation for the following endpoint: [paste code or endpoint details]. Include: (1) Endpoint URL and method. (2) A one-sentence description of what it does. (3) Request parameters in a table (name, type, required/optional, description). (4) A request example with realistic sample data. (5) Response format with field descriptions. (6) One success and one error response example. (7) Common error codes and what triggers them. Use concise, imperative language. Assume the reader is a developer who has never seen this API before.

Write a step-by-step tutorial on [task/process] for [audience: beginners/intermediate/advanced developers]. Prerequisites: [list what the reader needs before starting]. The tutorial should have [number] steps. For each step: (1) A clear action-oriented heading ("Install the dependency," not "Installation"). (2) One sentence explaining WHY this step matters. (3) The exact command, code snippet, or action to take. (4) Expected output or what success looks like. (5) A troubleshooting note for the most common mistake at this step. End with a "Next steps" section suggesting what to build or learn next.

Here are rough meeting notes about a feature/project: [paste notes]. Turn them into a structured technical specification with these sections: (1) Overview - one paragraph explaining what we're building and why. (2) Requirements - numbered list of functional requirements. (3) Non-functional requirements - performance, security, scalability constraints. (4) Technical approach - high-level architecture or implementation plan. (5) Open questions - flag any decisions that weren't resolved in the notes. (6) Out of scope - explicitly state what this spec does NOT cover. Use precise language. Flag any ambiguities in the notes with [CLARIFICATION NEEDED].

Write release notes for version [X.X.X] of [product name]. Here are the raw changes: [paste changelog/commit messages/ticket summaries]. Organize them into: New Features (explain the benefit, not just the feature), Improvements (what's better and why users should care), Bug Fixes (what was broken and is now fixed, in plain language), Breaking Changes (what users need to do differently, with migration steps). Write for [technical/non-technical] users. Lead with the most impactful change. Keep each item to 1-2 sentences maximum.

Write an internal process document for [process name, e.g., "deploying to production," "onboarding a new client," "handling a security incident"]. Audience: [role/team]. Structure: (1) Purpose - when and why this process is used. (2) Prerequisites - what you need before starting. (3) Step-by-step procedure - numbered, with clear ownership for each step (who does what). (4) Decision points - if/then branches where the process might diverge. (5) Escalation path - who to contact if something goes wrong. (6) Checklist - a summary checklist for quick reference. Keep language direct and imperative. Avoid "should" - use "must" or "do."

Write a README.md for [project name]. The project does [one-sentence description]. Tech stack: [languages/frameworks]. Here is additional context: [paste any notes, features, or architecture details]. Include these sections: (1) Project title and one-line description. (2) A "Why" section - what problem this solves and who it's for (3 sentences max). (3) Quick start - the fewest possible commands to get it running locally. (4) Usage - 2-3 code examples showing common use cases. (5) Configuration - environment variables or config options in a table. (6) Contributing - brief contribution guidelines. (7) License. Keep the total under [word count] words. Optimize for a developer who wants to evaluate this project in under 2 minutes.