ChatGPT has a default marketing voice and it will use it unless you stop it.
The default voice is enthusiastic, benefit-forward, and structurally predictable. It produces headlines like "Revolutionize Your Workflow" and "Say Goodbye to [Problem], Say Hello to [Product]." It uses words like "seamless," "powerful," "game-changing," and "effortless" with statistical regularity. It sounds like startup copy because it was trained on startup copy, and startup copy that got indexed online was disproportionately the marketing-speak variety.
The founders who get usable output from ChatGPT for marketing copy are the ones who know how to turn off the default voice and replace it with the constraints that produce something more specific and human.
Here's the prompt system for doing that across the six types of copy your launch requires.
The Foundation: The Anti-Generic Constraint Block
Before any specific prompt, add this constraint block. It trains the model on what output you don't want before you ask for what you do want.
Constraints for all copy you write:
- Do not use: revolutionary, game-changing, seamless, powerful, effortless, cutting-edge, robust, innovative, streamline, or any similar adjective.
- Do not use "Say goodbye to X, say hello to Y" structure.
- Do not use em-dashes in marketing copy.
- Write in plain English that sounds like a human founder wrote it, not a marketing department.
- Prioritize specificity over enthusiasm.
- If you find yourself writing a sentence that could describe any startup in this category, delete it and write something more specific.
Add this block to the top of every new chat session where you're generating marketing copy. It materially changes the default output.
1. Landing Page Hero Copy
What to feed it:
- Your specific customer type (not "small businesses" -- the individual person profile)
- The exact problem in customer language (from your interviews)
- The current workaround that customer uses
- The primary outcome your product delivers
The prompt:
I'm building [product name] for [specific customer type].
My customers describe their problem in these exact words (from interviews, paste verbatim quotes):
[paste 4-6 quotes]
Their current workaround: [describe what they do today]
The primary outcome my product delivers: [one specific outcome, not a list]
Write 6 landing page headlines. Requirements:
- Use the customer's own language where possible
- Each headline should describe one specific outcome, not a feature list
- None of them should start with "Introducing" or "Meet [Product Name]"
- At least two should lead with the problem, not the solution
- All six should pass this test: they would only make sense for this specific product, not any competitor in the category
What to do with the output: Expect 2-3 of the 6 to be usable as first drafts. The ones that sound like the customer's own words are better than the ones that sound polished. Edit the best survivor for length and rhythm; most AI headlines are two to three words too long.
2. Email Subject Lines
Subject lines are where AI assistance is most consistently useful because the format is short, testable, and volume matters (you want 10 options to test, not 2).
The prompt:
I'm sending a [welcome email / nurture email / launch email] to [customer type].
The email's purpose: [one sentence on what this email does -- informs, asks a question, announces]
The core problem this customer has: [one sentence]
The current workaround they use: [one sentence]
Write 10 subject line options. Requirements:
- No clickbait or artificial urgency ("You won't believe" / "Last chance" type language)
- At least 3 should be plain-text question format (the reader should feel like a real person sent it)
- At least 2 should reference the specific problem in the customer's language
- Length: all under 48 characters so they don't truncate on mobile
- None should start with: "Exciting," "Important," "We're thrilled," or any opener that signals a marketing email
What to do with the output: The question-format subject lines almost always outperform the announcement-style ones for welcome and nurture emails. The recipients don't know you yet; a question signals human contact rather than automation.
Test your top 3 by sending the same email with different subjects to subsets of your early list. The reply rate (not open rate) is the better signal.
3. Community Posts (Reddit, IndieHackers, Slack)
Community posts are where the anti-generic constraint matters most. Community moderators and experienced readers recognize startup marketing instantly and treat it accordingly.
The prompt:
I want to post in [community name, e.g., r/freelance] to share something genuinely useful about [problem area] and, at the end, mention I'm building something to solve it.
The community: [brief description of who's in it and what they care about]
The problem I'm addressing: [specific problem in plain language]
One piece of genuinely useful information about this problem that people would want to know even if my product didn't exist: [provide this yourself from your research]
Write a community post with this structure:
1. An opening that describes the problem with one specific, real-feeling detail (not a statistic from a press release)
2. The useful information section (expand on what I provided above while keeping it accurate)
3. A brief, honest close that mentions I'm building something to solve this problem and invites people who have this issue to either comment or DM
Constraints:
- This should read like a post from a real person who has been in this community for a while
- Do not start with "Are you tired of X?"
- Do not include a CTA like "Check out my new tool!" -- keep any product mention brief and non-promotional
- The useful section should take up at least 70% of the post
What to do with the output: Edit the opening heavily. AI-generated community post openings are identifiably AI. They set up the problem too neatly. Add a specific, rough detail from your own customer research -- a verbatim thing someone told you -- and the post becomes immediately more credible.
4. Product Description for Directories and Listings
Product directories (Product Hunt, Indie Hackers, app directories, Chrome extension store) each have specific format requirements. AI is fast at generating format-appropriate descriptions from a single briefing.
The prompt:
I'm listing [product name] on [platform name].
Product: [one sentence on what it does]
Customer: [specific customer type]
Primary use case: [what the customer does with it]
Key mechanism: [how it works, briefly]
Price: [price point]
Write listing descriptions in these formats:
1. Tagline (under 10 words, no punctuation, not a sentence)
2. Short description (2 sentences, for platforms with character limits)
3. Product Hunt description (3 short paragraphs: problem, solution, who it's for)
4. Full description (5-6 sentences, for longer listing formats)
Requirements for all: no superlatives, no "the only," no "the best," no comparisons to competitors that sound defensive.
What to do with the output: The tagline almost always needs two or three iteration rounds. Start from the AI's output and push it toward the customer's language by asking: "Replace the word [X] with the exact word a customer used to describe this outcome." Run that prompt for the two or three most generic words in the tagline.
5. Pricing Page
Pricing pages are undersupported by most copy advice. Most founders write feature lists and price points -- the copy that actually converts skeptical buyers at this stage is missing.
The prompt:
My product is [name], priced at [price] per [period]. Target customer: [customer type].
The primary concern a buyer has at the pricing page: [from your customer conversations, what do people worry about before paying?]
The most common reason prospects don't buy: [what you've heard or assume]
The thing that most differentiates this from the free/cheaper alternative: [one specific thing]
Write:
1. A pricing page headline (not "Simple, Transparent Pricing" -- something specific to this product and customer)
2. Three bullet points under the price that describe outcomes, not features (each under 15 words)
3. A one-sentence "who this is for" statement
4. A one-sentence "who this is NOT for" statement (this builds credibility with the right buyer by showing honesty)
5. One FAQ answer addressing the primary buyer concern you identified
What to do with the output: The "who this is NOT for" statement is the most useful output from this prompt and the one founders most often remove before publishing. Leave it in. Real specificity about who the product is not right for increases conversion with the right buyers because it signals confidence.
6. Social Copy for Launch
Launch posts require a different tone than community posts -- they're more personal and more nakedly asking for attention.
The prompt:
I'm launching [product name] today. This is for [customer type] who [specific problem in their language].
The founding story (why I built this): [2-3 sentences -- honest, not heroic]
The person I built it for (describe one specific person from your early conversations):
The specific thing it does that the alternatives don't:
Price:
Write 3 launch posts:
1. Twitter/X format (under 280 characters, can be a thread opener)
2. LinkedIn format (can be longer, more personal, story-led)
3. Short format for Indie Hackers or Hacker News (factual, no hype, who it's for, how it works, what you've validated so far)
For all three: the founding story detail should be the hook, not the product feature list. Start from what made you build it, not what it does.
What to do with the output: The LinkedIn version is usually the best starting point and the one that requires the least editing because the longer format gives AI more room to be specific. Use it as the source document and compress it for the shorter formats.
The Editing Pass That Makes All of It Better
After generating any copy from these prompts, run one final editing pass with this prompt:
Review this copy for any language that could describe any other company in this category. Underline or flag every phrase that a competitor could plausibly also use. For each flagged phrase, suggest a more specific version that only our product could claim.
This produces the list of still-generic language to refine. Not all of them will have better alternatives -- some generic language is necessary. But the ones that have more specific versions should be replaced.
The goal at the end: every sentence should be one that only your product, for your specific customer, could say. That's the gap between copy that sounds like everyone else and copy that makes the right person feel like the product was built for them.
That feeling doesn't come from AI. It comes from customer research. The AI just helps you write from it faster.
Ready to validate your idea?
Start using WarmLaunch today to grow your waitlist.