The Full-Stack AI Marketing Prompt Stack: Top 21 Prompts That Replace Half Your Marketing Team
Whether you run a small business or a lean agency, these 21 AI prompts cover every stage of your marketing workflow — from proofing a social post to turning a podcast transcript into a blog outline. Copy, customise, and publish faster.
Lean marketing teams can now produce content at a scale that used to require a full agency — provided they use prompts that actually work. This article gives you 21 original, ready-to-use AI prompts covering every stage of the marketing workflow, from proofreading a single post to building an entire client proposal.
Compatible with ChatGPT, Claude, Gemini, and every other major AI model.
Contents
Why Most AI Prompts Produce Mediocre Output
The problem is rarely the AI model. It is the instruction. A vague prompt leaves the model to fill in the gaps using its default patterns — and those defaults are trained on millions of generic blog posts, corporate press releases, and LinkedIn filler content. The output reflects that.
Three things consistently close the gap between generic AI content and something worth publishing:
- Tell it what to avoid, not just what to do. A list of banned phrases, forbidden structures, and off-limits words narrows the model's output space far more effectively than describing what you want in positive terms alone.
- Give it a reference before asking it to write. Pasting an existing piece of your content — even a single paragraph — lets the model extract your actual voice rather than inventing a generic one.
- Specify format with precision. "Write a LinkedIn post" is almost useless as an instruction. "Write a LinkedIn post with no title, no bold text, a line break between every sentence, a hook as the opening line, and a maximum of two emojis" produces something you can actually use.
Every prompt below is built around these principles. Each one includes the full prompt text, customisation suggestions, and the expected output format.
Errors-Only Proofread
Use case: Check a social post for real errors without triggering an unwanted rewriteReview the social media post below for spelling errors and factual typos only. Do not suggest style improvements, restructure sentences, or comment on tone. Only flag items that are objectively incorrect — misspelled words, wrong numbers, or broken grammar. If there are no errors, say "No errors found" and nothing else. Do not copy the original text back. Post to review: [Paste your post here]
Tone-Matched Rewrite Using a Reference
Use case: Rewrite a draft to match an existing content style without losing the original meaningRewrite the text below to match the tone, rhythm, and vocabulary of the reference document attached. Keep every insight and piece of information from the original. Do not add new ideas, remove key points, or water down any claims. Style rules: — Write like an experienced operator, not a content marketer. — No clichés, no motivational language, no vague generalities. — Banned words and phrases: "ensure", "leverage", "in the realm of", "in the world of", "Remember,", "it's important to". Text to rewrite: [Paste your draft here]
Article Introduction Caption for LinkedIn
Use case: Write a standalone LinkedIn post that introduces a published article and drives clicksRead the article below and write a LinkedIn caption I can use to share it. The caption should stand alone — someone reading it without seeing the article should still find it interesting and want to click through. Rules: — First sentence: make it specific, surprising, or counterintuitive. Not a summary. — Use a single line break between every sentence so it is easy to scan. — Draw only from the article content. Do not invent context or add opinions I haven't expressed. — No generic sign-offs. No "check out my latest article" style lines. Article: [Paste article here]
New Hire Announcement Post
Use case: Write a company caption to repost a new employee's LinkedIn announcementA new team member has posted about joining [COMPANY NAME] on LinkedIn. I want to repost their announcement with a short company caption. Write a caption that: — Welcomes them by name and role — Mentions one specific thing they will own or contribute (see details below) — Sounds human and direct — not corporate, not over-enthusiastic — Avoids: "family", "thrilled", "excited to announce", "invaluable", "revolutionise" Match the tone and length of this previous caption I wrote: "[Paste your own example here]" New hire details: [Name, role, one sentence about what they'll do] Their announcement post: [Paste it here]
Video Clip Caption from Transcript
Use case: Write a social caption for a short video or podcast clip using its transcriptI have a short video clip I want to post on [PLATFORM]. Below is the transcript. Write a caption that makes someone stop scrolling and watch the clip. The first line needs to do the heavy lifting — it should be specific, not vague. Rules: — Pull the most interesting or unexpected line from the clip and build the caption around it. — No generic openers like "In this clip..." or "I sat down with...". — No jargon, no clichés, no motivational phrasing. — Keep it concise. This is a clip caption, not a blog intro. Clip transcript: [Paste transcript here]
Tight Rewrite for Long-Form Social Posts
Use case: Cut a bloated draft down to something sharp without losing the substanceRewrite the text below so it is sharper, more direct, and easier to read on a phone screen. Keep every insight intact. Cut anything that exists only to fill space. Formatting rules: — One sentence per line, with a blank line between each — No headers, no bold text, no bullet points (this platform strips formatting) — Maximum two emojis, only if they add structure (not decoration) — Opening line must create enough curiosity that someone reads the second line Writing rules: — Write in first person, direct and plain — Banned phrases: "ensure", "leverage", "the reality is", "game-changer", "it's important to", "in today's world" — No rhetorical questions used as transitions — Fix any spelling, grammar, or punctuation issues Text to edit: [Paste your draft here]
Conversation Transcript to Blog Post Outline
Use case: Extract the best ideas from a recorded conversation and structure them into a blog outlineThe transcript below is from a recorded conversation. Read it carefully, then do two things: Step 1 — List the five most interesting, specific, and non-obvious ideas from the conversation that could become standalone blog posts. For each idea, write one sentence explaining why it would be valuable to [TARGET AUDIENCE]. Step 2 — Take idea number [X] and build a full blog post outline: — A working headline (specific, not generic) — An intro paragraph that opens with a concrete hook — 3 to 5 body sections, each with a subheading and 2 to 3 supporting points — A practical takeaways section — A closing paragraph that brings it back to the central argument Use only ideas and information from the transcript. Transcript: [Paste transcript here]
Conversation Transcript to Social Post
Use case: Pull a social-worthy idea from a transcript and write a ready-to-post versionThe transcript below is from a recorded conversation. Do the following: Step 1 — List the five strongest ideas from the conversation that would work well as standalone social media posts. Focus on specific claims, counterintuitive points, or practical insights. Step 2 — Take idea number [X] and write a complete social media post around it. Use the full transcript to build context and depth around this specific point — do not just restate the obvious. Format requirements: — One sentence per line with blank lines between each — First line must be a specific, interesting statement — not an opener or setup — No titles, headers, or formatting (platform does not support it) — Written in first person, conversational and direct — Banned: "ensure", "leverage", "game-changer", "the reality is", "it's worth noting" Transcript: [Paste transcript here]
Full Blog Post from Notes and Data
Use case: Write a complete company blog post from scattered notes, quotes, and talking pointsYou are writing a blog post for [COMPANY NAME]'s website. The topic is: [TOPIC]. Use only the notes and information I provide below. Do not pull in external data, references, or examples I have not given you. The post should: — Open with a specific observation or situation the reader will recognise immediately — Build a clear argument across 4 to 6 sections — Use concrete examples from the notes rather than abstract generalisations — End with a practical conclusion the reader can act on Writing style: direct and informative. No filler. No grand claims without backing. Write for someone who will skip anything that wastes their time. Notes and information to use: [Paste everything here — bullet points, quotes, data, context]
Published Blog Post to Social Promotion
Use case: Write a social post that promotes a blog article without just summarising itThe blog post below is published on my company's website. Write a social media post that promotes it. The goal is to make someone curious enough to click through — not to summarise the whole article. Pull the most interesting or surprising single point from the post and build the caption around that. Rules: — First sentence must be specific and surprising — not a generic teaser — One sentence per line, blank line between each — Use the language and framing from the blog post — do not invent a different angle — This is a regulated area — do not overstate claims or add language I have not used — Banned: "ensure", "game-changer", "the reality is", "in the world of", any jargon I have not used in the original post Blog post: [Paste here]
Find Supporting Evidence for an Article Draft
Use case: Identify where to add citations and data sources to strengthen a piece of writingRead the article draft below. Take the role of a research editor. Identify the claims, statistics, or assertions that would benefit most from an external source. For each one: 1. Quote the specific sentence or claim that needs backing 2. Suggest what type of source would be most credible (academic study, government data, industry report, etc.) 3. Propose a specific search query I can use to find it 4. If you can cite a real, verifiable source with confidence, include it — but do not invent or guess sources Focus on the 3 to 5 highest-priority claims. Not everything needs a citation. Article draft: [Paste here]
Technical Document to Accessible Blog Post
Use case: Turn a research paper, whitepaper, or technical report into a readable blog postYou are rewriting a technical document as a blog post for [TARGET AUDIENCE]. Your job is not to simplify — it is to translate. The core findings must remain accurate and complete. What changes is how they are communicated. Process: 1. Identify the three most significant findings or arguments in the document 2. Identify the practical implication of each for [TARGET AUDIENCE] 3. Write a blog post that leads with the implications, then explains the findings as context Format: — Open with a single observation that connects to a problem [TARGET AUDIENCE] actually has — Use plain language; explain technical terms when you introduce them — Structure into clear sections with descriptive subheadings — End with one concrete takeaway the reader can apply Source document: [Paste or attach here] Writing style to follow: [Paste a sample of existing content here]
Podcast Episode to Promotional Post
Use case: Write a social post that drives listeners to a new podcast episodeThe transcript below is from episode [NUMBER] of [PODCAST NAME]. Write a social post promoting this episode. Do not summarise the episode. Instead, find the single most interesting exchange, claim, or insight in the transcript and use that as the hook. The post should make someone feel like they are missing something if they do not listen. Formatting: — One sentence per line, blank line between each — No titles, bold text, or section headers — Maximum two emojis if needed for structure only — First line must work as a standalone statement — not a setup Source only from the transcript. Do not add context or opinions that are not in the recording. Transcript: [Paste here]
Customer Interview to Case Study Post
Use case: Turn a recorded customer conversation into a testimonial blog postThe transcript below is from a recorded conversation with a customer of [PRODUCT/COMPANY NAME]. Write a testimonial blog post using this conversation. Structure it around the most compelling story in the transcript — the problem they had before, the specific moment or reason they chose [PRODUCT NAME], and what changed after. Rules: — Lead with the customer's situation, not a product description — Be specific about the problem and the outcome — avoid vague claims — Write in third person unless quoting the customer directly — Do not overstate results or add metrics that are not in the transcript — Match the tone and structure of the previous testimonial post attached Previous testimonial post (for structure and tone reference): [Paste here] Customer interview transcript: [Paste here]
Writing Style Instructions for a New Project
Use case: Set a consistent writing brief at the start of any AI project or client engagementFor all writing in this project, follow these rules: Style: Short sentences. Active voice. Concrete over abstract. When in doubt, cut. Voice: Write as someone with direct experience, not as a commentator. Opinions should be stated plainly, not hedged into uselessness. What to avoid: — Questions used as section transitions — Sentence structures like "X is not just about Y" or "X is more than simply Y" — Filler phrases: "it's important to", "ensure", "leverage", "the reality is", "at the end of the day", "Remember," — Anything that sounds like it was written to impress rather than communicate Format: Short paragraphs. No unnecessary preamble before answering. Get to the point in the first sentence. [Add client brief, audience details, and any additional constraints below this line]
Client Proposal from a Template
Use case: Adapt an existing proposal document for a new client without manual reformattingI need to write a project proposal for a new client. The previous proposal attached is the template — follow its structure exactly. Instructions: 1. Replace all references to the previous client with [NEW CLIENT NAME] — check every section, not just the header 2. Use the new client information below to fill in all personalised sections 3. Only include information I have provided — do not invent services, outcomes, or context 4. If any section of the template requires information I have not given you, flag it rather than filling it with a placeholder New client name: [NAME] Industry: [INDUSTRY] Project scope: [DESCRIPTION] Key goal: [WHAT THEY WANT TO ACHIEVE] Budget/timeline (if known): [DETAILS] Template proposal: [Attach or paste here]
Contract Proofread and Error Check
Use case: Review a contract for errors, wrong names, and unfilled placeholders before sendingReview the contract below carefully. This document will be sent to a client — it must be completely clean. Check for: 1. Spelling errors and grammatical mistakes 2. Punctuation problems that affect readability or meaning 3. Any company name other than [CLIENT NAME] — flag every instance 4. Unfilled placeholders such as [DATE], [AMOUNT], [NAME], or similar 5. Any sentence that is ambiguous enough to cause a dispute later For each issue found, give me: the location (paragraph/section), the problem, and the correction. Contract: [Paste here]
Voice Note to Action List
Use case: Convert a rambling voice note or brain dump into a clean, prioritised task listConvert the note below into a clean action list. Rules: — Each item should start with a verb (Write, Send, Review, Book, etc.) — Each item should be specific enough that someone else could complete it without asking a question — Group related tasks together — If something is time-sensitive or blocking something else, put it first — Do not add commentary, explanations, or preamble — only the list Format each item as: + [Action item] My note: [Paste voice transcription or notes here]
Project Scope to Priority Checklist
Use case: Structure a voice or written description of a project into a markdown task listRead the project description below and produce a structured priority checklist. Format: [Project Name] [ ] Task 1 [ ] Task 2 [ ] Task 3 Rules: — List tasks in the order they need to happen, not the order they were mentioned — If a task cannot start until another is finished, note the dependency in brackets: (Needs: Task X) — Keep task descriptions specific and action-oriented — Do not add anything outside the list — no preamble, no summary Project description: [Paste voice transcription or notes here]
Key Takeaways from Any Document
Use case: Extract the most important points from meeting notes, reports, or long transcriptsRead the document below and extract the most important points. Rules: — Include every significant point — do not compress meaning to save space — Write each takeaway as a complete sentence, not a fragment — Order by importance, not by where things appeared in the document — If a number, date, or specific claim is important, include it exactly — do not paraphrase figures — Do not include the document back in your response; only the takeaway list Write at least 5 takeaways, more if the content warrants it. Format each as: - [Takeaway] Document: """ [Paste your notes, transcript, or report here] """
Competitor Content Audit
Use case: Analyse a competitor's content strategy and identify gaps your own content can fillBelow are examples of content from a competitor in my space. Analyse what they are doing and identify what they are not doing. I want to understand: 1. What topics and angles they cover consistently 2. What tone and format they use most often 3. What questions their audience is likely asking that this content does not answer 4. What content angles are completely absent from their strategy 5. Where their content is strongest and where it is weakest Based on this, give me five specific content ideas that would occupy the gaps in their strategy and that my audience would find more valuable than what the competitor is publishing. My company: [NAME] My audience: [DESCRIPTION] My key differentiator: [ONE SENTENCE] Competitor content samples: [Paste 3 to 5 examples — social posts, articles, or a description of their content]
3 Rules That Improve Any Prompt
These apply regardless of which prompt you are using or which AI model you are running it on.
1. Lead with a reference, not a description. Telling the AI "write in a professional but approachable tone" produces generic output. Pasting a paragraph of your own writing and saying "match this" produces something far closer to your actual voice. A real example beats an abstract description every time.
2. Build a banned phrases list specific to your work. Every writer — and every AI — has default patterns. The model's defaults are "leverage", "ensure", "game-changer". Yours might be something else entirely. Run your existing content through a word frequency counter, find your repeated phrases, and ban them explicitly in your prompts.
3. Specify format as precisely as the content. A prompt that describes exactly what the output should look like — line breaks, word count, emoji limit, whether there's a headline or not — saves more editing time than any other single instruction. Format is not a minor detail. It is half the work.
All 21 Prompts at a Glance
| # | Category | Prompt | Output |
|---|---|---|---|
| 1 | Social | Errors-Only Proofread | Error list |
| 2 | Social | Tone-Matched Rewrite | Rewritten post |
| 3 | Social | Article Introduction Caption | LinkedIn caption |
| 4 | Social | New Hire Announcement | Announcement caption |
| 5 | Social | Video Clip Caption | Social caption |
| 6 | Copywriting | Tight Rewrite for Social | Edited draft |
| 7 | Copywriting | Transcript to Blog Outline | Blog outline |
| 8 | Copywriting | Transcript to Social Post | Social post |
| 9 | Copywriting | Notes to Full Blog Post | Blog draft |
| 10 | Repurposing | Blog Post to Social Promo | Social caption |
| 11 | Repurposing | Find Supporting Evidence | Citation suggestions |
| 12 | Repurposing | Technical Doc to Blog Post | Blog draft |
| 13 | Repurposing | Podcast to Promo Post | Promo post |
| 14 | Repurposing | Customer Interview to Case Study | Case study post |
| 15 | Agency & Ops | Writing Style Instructions | Reusable brief |
| 16 | Agency & Ops | Client Proposal from Template | Adapted proposal |
| 17 | Agency & Ops | Contract Proofread | Issue list + fixes |
| 18 | Agency & Ops | Voice Note to Action List | Task list |
| 19 | Agency & Ops | Project Scope to Checklist | Markdown checklist |
| 20 | Research | Key Takeaways Extractor | Takeaway list |
| 21 | Research | Competitor Content Audit | Gap analysis + ideas |
Verdict
The gap between AI content that gets used and AI content that gets deleted is almost entirely in the prompt. These 21 templates are built around the constraints, format rules, and reference-based techniques that consistently produce output worth publishing. Copy any prompt, replace the placeholders, and run it in whichever model you prefer. The quality of the output is down to you from that point.
Frequently Asked Questions
What is an AI marketing prompt stack?
A set of reusable prompt templates that guide AI models to produce specific marketing outputs — from social captions to full proposals — with consistent quality and on-brand writing.
Do these prompts work with ChatGPT and Claude?
Yes. All 21 prompts are model-agnostic. They work with ChatGPT, Claude, Gemini, and any other major AI model that accepts text instructions.
How do I adapt these prompts for my own brand voice?
Paste a sample of your existing content alongside any prompt. The model will match your tone, vocabulary, and sentence rhythm directly from the example — this is more reliable than describing your style in abstract terms.
Are these prompts suitable for UK businesses?
Yes. Add "use UK English spelling and conventions throughout" at the start of any prompt. All prompts work regardless of region or industry.
Why do these prompts include banned word lists?
AI models default to overused phrases like "ensure", "leverage", and "game-changer" because those patterns appear constantly in their training data. Explicitly banning them forces the model away from generic output and toward more natural writing.