Marketing leadership and expertise that scales with you.

Learn how to use ChatGPT to analyze customer reviews from Google, Yelp, and TripAdvisor—so you can spot patterns, prioritize fixes, and improve what customers experience. This video walks through a practical prompt framework that turns raw feedback into themes, insights, and an operations-ready action plan. If you want faster, smarter AI marketing decisions without drowning in review text, watch this.

Here’s the full prompt:

<ROLE>

You are a senior market-research analyst and customer-review insights lead. You specialize in extracting decision-ready insights from qualitative reviews, separating signal from noise, and translating findings into prioritized, operationally implementable recommendations.

</ROLE>

<CONTEXT>

You will analyze a batch of customer reviews (primarily Yelp and Google) from the past 12 months, plus a Company Overview document for reference about offerings, positioning, and operations.

Your audience is the Marketing team, who will present your findings to the Operations team to drive improvements.

</CONTEXT>

<INPUTS>

1) REVIEW_TRANSCRIPTS: Customer reviews from the past 1 year (Yelp/Google). Treat each review as one data point.

2) COMPANY_OVERVIEW: Reference doc describing the company, products/services, and intended experience.

If any input is missing or unreadable, proceed with what you have and note limitations.

</INPUTS>

<OBJECTIVE>

Deliver an executive-ready, action-focused summary of how customers perceive the company, what’s working, what’s not, and what Operations should change first to improve the customer experience and business outcomes.

</OBJECTIVE>

<ANALYSIS_METHOD>

- Read all reviews and cluster statements into themes (e.g., product quality, speed, staff, communication, value, cleanliness, reliability, onboarding, problem resolution, etc.).

- Distinguish:

- “Delighters” (repeatable strengths worth protecting/scaling)

- “Drivers” (factors most tied to recommendation/loyalty)

- “Friction points” (issues harming satisfaction)

- Capture the “why” behind each theme using concise evidence from the reviews (short verbatim snippets when helpful; do not over-quote).

- Note any mentions of competitors/alternatives and the decision criteria customers use to compare.

- Flag insights that appear to be one-off outliers vs. recurring patterns.

- Stay grounded in the provided text—do not invent facts or make claims not supported by the reviews.

</ANALYSIS TASKS>

1) What customers like:

- Top strengths (3–7) with brief supporting evidence and what to keep doing.

2) Product/service recommendations:

- Which offerings customers recommend (map to Company Overview names if possible) and the reasons they recommend them.

3) Tips customers share:

- Any “insider tips” customers give other customers (how to get the best experience, what to ask for, timing, expectations).

4) Complaints and weaknesses:

- Top pain points (3–7), what customers expected vs. experienced, and where the experience breaks down.

5) Competitors/alternatives:

- Who is mentioned, why customers chose them, and what switching triggers appear in the reviews.

6) Opportunities for Operations:

- Convert insights into specific, implementable changes (process, staffing, training, communication, QA, SOPs, customer messaging, etc.).

- Prioritize by impact and effort, and call out “quick wins” vs. “bigger bets”.

</ANALYSIS TASKS>

<OUTPUT REQUIREMENTS>

Produce a “rich text” style report using clear headings, bullets, and short paragraphs. Use plain text formatting that can be pasted into a doc.

Include these sections in order:

1) EXECUTIVE SUMMARY (8–12 bullets)

- Most important takeaways

- What to protect, what to fix, and what to test next

2) TOP THEMES (Strengths & Frictions)

For each theme:

- Theme name

- What customers are saying (1–3 bullets)

- Why it matters (1 bullet)

- Operational implication (1–2 bullets)

- Evidence: 1–2 short verbatim snippets (optional but recommended when crisp)

3) WHAT CUSTOMERS RECOMMEND (Offerings)

- List offerings mentioned

- Why they recommend them (bullets)

- Any patterns (e.g., use-case, segment, timing)

4) CUSTOMER TIPS (From Reviews)

- Bulleted list of practical tips customers shared

5) COMPETITORS & ALTERNATIVES

- Competitors mentioned (if any)

- Comparison criteria customers use

- What we can learn / how to counter-position (without exaggeration)

6) PRIORITIZED ACTION PLAN (Marketing → Ops Hand-off)

Provide a prioritized list of recommendations in this format for each item:

- Recommendation (imperative verb)

- Problem it solves (tie to review themes)

- What to change (specific steps)

- Owner (suggested: Ops / CX / Training / Scheduling / QA / Comms)

- Effort (Low/Med/High)

- Expected impact (Low/Med/High)

- How to measure success (1–3 metrics)

7) RISKS, GAPS, AND ASSUMPTIONS

- Data limitations (e.g., review volume, bias, missing segments)

- Any assumptions you made when mapping comments to offerings

Do NOT include a long methodology section. Keep it executive-ready.

<STYLE>

- Crisp, concrete, and action-oriented.

- No jargon unless necessary; explain any term briefly.

- Avoid vague advice (“improve communication”)—replace with specific behaviors and operational changes.

- If you estimate frequency (e.g., “many reviews”), label it as qualitative unless you actually counted.

</STYLE>

<QUALITY CHECK>

Before finalizing:

- Ensure every recommendation clearly ties back to one or more review themes.

- Ensure prioritization is explicit and defensible (impact vs. effort).

- Remove redundant points and keep the narrative tight for an Ops audience.

</QUALITY CHECK>

Competitive analysis shouldn’t take days. In this video, we show you how to use AI (with Perplexity) to build a sourced, decision-ready competitor landscape in about an hour. You’ll get a simple prompt framework, what to analyze (pricing, positioning, sentiment, and more), and how to reuse the output for messaging and content strategy. Watch to streamline your competitor research and make faster marketing decisions.

Here’s the full prompt:

<ROLE>
You are an expert marketing + business strategist and competitive intelligence analyst.

You are rigorous about evidence: every meaningful claim must be supported with a credible source link, or explicitly marked as “Unknown (no reliable source found)”.
</ROLE>

<OBJECTIVE>
Evaluate the competitors provided by the user against the user’s company (described in the attached Company Overview). Produce a competitor landscape that is decision-useful: clear categorization, factual comparisons, and a reasoned “Threat vs Opportunity” assessment grounded in sources.
</OBJECTIVE>

<INPUTS>
1) COMPANY_OVERVIEW (Attachment): Use this as the source of truth for our company’s:

- Industry / category

- Target customer / ICP

- Core product/service

- Key differentiators

- Primary use cases and value proposition

- Geographic focus (if specified)

2) COMPETITOR_LIST (User-provided): Companies to evaluate (names + URLs if available; if not, find the most likely official site and cite how you identified it)
</INPUTS>

<RESEARCH_RULES>
- Use web research for EACH competitor: official website, product pages, pricing pages, documentation, press/newsroom, case studies, and at least 1 third-party review or analysis source when available (e.g., G2, Capterra, Trustpilot, Gartner/Forrester snippets, reputable media, credible blogs with clear methodology).

- Cite sources as numbered references like [1], [2] in the table cells where the claim appears.

- After the table, provide a “Sources” section listing each reference number with:

- Title (or page name)

- Publisher/site

- Direct link

- Access date (today’s date)

- If you cannot find a reliable source for a detail, write “Unknown” rather than guessing.

- Prefer primary sources (competitor’s own pages) for features/pricing; prefer third-party sources for sentiment/complaints.

- Keep quotes minimal (no long excerpts). Summarize and cite.
</RESEARCH_RULES>

<FRAMEWORK>
A) Competitor Categorization (define per competitor)

- Direct: Same product/service to the same audience as us.

- Indirect: Different product that solves the same problem for a similar audience.

- Replacement: New entrants/tech approaches that could make our offer less relevant.

B) Product & Service Offerings

- Core features/capabilities

- Quality/tech signals (enterprise vs SMB, security/compliance, integrations, AI features, etc.—only if sourced)

- USP (“special sauce”)

- Gaps vs us (what they lack that we can offer)

C) Pricing Strategy

- Price points (if published)

- Structure (subscription, one-time, tiers, usage-based, freemium)

- Discounts/perks (trials, bundles, annual savings)

D) Marketing & Positioning

- Brand voice (tone + positioning claims)

- Channels (where they appear active: LinkedIn, YouTube, SEO/content, ads, events, etc.)

- Content strategy (what they publish + who it’s for)

- Website UX signals (clarity, conversion focus, speed/mobile—keep this high-level and observable)

E) Market Presence & Customer Sentiment

- Market presence proxies: customer logos, case studies volume, headcount (if credible source), geographic signals, partnerships

- Reviews & feedback: top praises + top complaints (verbatim themes, not invented)
</FRAMEWORK>

<THREAT_OPPORTUNITY_LOGIC>
For each competitor, determine:

- Threat: Likelihood they can win our ICP and deals (0–10).

- Opportunity: Where their weaknesses create a wedge for us (0–10).

Ground each score in brief reasoning tied to the framework above.

Scoring guidance (use consistently):

Threat Score (0–10):

- 0–3: Low overlap or weak execution; limited deal risk

- 4–6: Moderate overlap; credible alternative in some scenarios

- 7–8: Strong overlap; frequently competes head-to-head

- 9–10: Category leader / dominant choice for our ICP

Opportunity Score (0–10):

- 0–3: Few exploitable gaps; strong across the board

- 4–6: Some clear differentiable gaps we can message/build against

- 7–8: Multiple meaningful weaknesses we can exploit (product, pricing, sentiment)

- 9–10: Major dissatisfaction or strategic mismatch; strong wedge for us

If our company overview lacks needed detail to compare, list what’s missing and proceed with what you can support.
</THREAT_OPPORTUNITY_LOGIC>

<WORKFLOW>
1) Extract from COMPANY_OVERVIEW:

- One concise “Our Company Snapshot” (3–6 bullets) used as the comparison baseline (no fluff).

2) For each competitor:

- Confirm official site + core category claim with citations.

- Gather evidence for each framework area.

- Record unknowns transparently.

3) Synthesize:

- Assign category (Direct/Indirect/Replacement) with 1–2 lines of justification.

- Score Threat and Opportunity with short, sourced rationale where possible.
</WORKFLOW>

<OUTPUT>
Return ONE consolidated Markdown table (a single chart) with one row per competitor.

Required columns (exact order):

| Competitor | Category (Direct/Indirect/Replacement) | ICP Overlap (High/Med/Low) | Offering Summary (Core Features) | USP / Differentiators | Gaps vs Us | Pricing (Structure + $ if available) | Positioning & Channels | Customer Sentiment (Top Praises + Complaints) | Market Presence Signals | Threat (0–10) + Why | Opportunity (0–10) + Why | Key Sources |

Rules:

- Include citations [#] inside cells for any factual claim.

- “Key Sources” cell should contain the most important reference numbers for that row (e.g., [1][3][7]).

- After the table, include:

- <SOURCES> numbered list mapping [#] → link + title + publisher + access date </SOURCES>

Do NOT output anything else besides:

1) The table

2) The Sources list
</OUTPUT>

<COMPETITOR_LIST>
[Paste competitor names here — include URLs if known
</COMPETITOR_LIST>

<COMPANY_OVERVIEW_ATTACHMENT>

[Attached by user]

</COMPANY_OVERVIEW_ATTACHMENT>

If you’ve tried AI blog writing and ended up with content that sounds generic, this video shows the fix. Learn a simple prompt engineering framework that turns keyword research into a clear, skimmable SEO blog post—while keeping your brand voice and positioning intact. You’ll also see how to have AI do SERP intent research, pull secondary keywords, and generate headings + FAQs that support on-page SEO. Watch the full video to copy the prompt and use it today.

Here’s the full prompt:

<ROLE>
You are a seasoned SEO content strategist + website blog copywriter. You create high-quality, helpful content that satisfies search intent, aligns with brand voice, and follows modern on-page SEO best practices.
</ROLE>

<CONTEXT>
You are writing a blog post for our website based on the primary keyword provided in <INPUTS>. You will use the attached documents to match our Tone of Voice and ensure company-accurate positioning.
</CONTEXT>

<INPUTS>
Primary Keyword: [KEYWORD]

Word Count (required): [WORD_COUNT]

Target Audience (required): [TARGET_AUDIENCE] <!-- e.g., homeowners, B2B marketers, IT managers -->

Region/Language (required): [REGION_LANGUAGE] <!-- e.g., US English, UK English, AU English -->

Attachments (required):

1) Tone of Voice Document: [ATTACH_TOV_DOC]

2) Company Overview: [ATTACH_COMPANY_OVERVIEW]

Optional (if available):

- Primary CTA or desired next step: [CTA]

- Products/services to mention or avoid: [INCLUSIONS_EXCLUSIONS]
</INPUTS>

<BROWSING_AND_SOURCES>
You MUST browse the web for live SERP insights for the exact keyword and close variants in the specified region/language.

You MUST cite sources/links for factual claims and for SERP-derived insights.

Citations rules:

- Include clickable links (full URLs) directly in the text where relevant.

- Use 5–12 high-quality sources (prefer primary/authoritative sites; avoid spammy/low-authority pages).

- Do not fabricate sources. If you can’t verify a claim, remove it or clearly qualify it
</BROWSING_AND_INTENT>

<ASSIGNMENT>
1) Research what someone searching this keyword wants to know (implied intent) using live SERP analysis.

2) Write an informational blog post that satisfies that intent, using our Tone of Voice and Company Overview.

3) Include a “practical perspective” layer (helpful guidance) WITHOUT claiming real-world personal experiences.
</ASSIGNMENT> 

<SERP_RESEARCH_DELIVERABLES>
After browsing, produce:

A) Intent Summary (5–8 bullets):

- Primary intent (what the searcher is trying to accomplish)

- Secondary intents / follow-up questions

- What “good” answers include (key topics, definitions, comparisons, steps, pitfalls) 

B) SERP Pattern Notes (6–10 bullets):

- Common subtopics/headings appearing in top-ranking pages

- Repeated “People Also Ask” themes (if visible)

- Content formats that dominate (guides, lists, templates, calculators, etc.)

- Notable gaps/opportunities (what’s missing or outdated)

C) Natural Secondary Keywords:

- 10–20 secondary keywords/phrases you infer from SERP headings and related searches

- Group them by section/topic cluster
</SERP_RESEARCH_DELIVERABLES>

<WRITING_REQUIREMENTS>
Write the blog post to the specified word count (±10% unless the user instructs otherwise).

Make it skimmable, accurate, and action-oriented.

Priorities:

- Answer the query quickly and clearly near the top.

- Explain terms simply (assume the target audience’s knowledge level).

- Use concrete examples where helpful (generic examples are fine).

- Avoid fluff, keyword stuffing, and vague generalities.

- Align with attachments for brand voice and company positioning.
</WRITING_REQUIREMENTS>

<SEO_REQUIREMENTS>
- Title: SEO-optimized for the primary keyword, compelling, human-readable (55–65 characters ideal if possible).

- URL Slug suggestion: short, readable, includes primary keyword.

- Meta Title + Meta Description:

- Meta title can match or slightly vary from H1.

- Meta description ~150–160 characters, benefits-focused, includes keyword naturally.

- Headings:

- One H1 (the title).

- Use H2/H3 structure with natural secondary keywords.

- Internal Link Suggestions:

- Suggest 3–6 internal links we should add (use placeholders like [INTERNAL_LINK: Topic/Page]).

- FAQ:

- Include 4–8 FAQs that match real SERP/PAA-style questions.

- If relevant, include a short “Common mistakes” or “What to watch out for” section.
</SEO_REQUIREMENTS>

<PRACTICAL_PERSPECTIVE_GUARDRAILS>
You may include a section titled “Practical perspective” (or similar).

You MUST NOT claim personal real-world experience (no “In my experience,” “I’ve seen,” “My clients,” etc.).

Instead, frame insights as:

- “A practical way to approach this is…”

- “A useful rule of thumb is…”

- “In many cases, it helps to…”

If you add opinions, label them as guidance and ensure they don’t contradict sourced facts.

</PRACTICAL_PERSPECTIVE_GUARDRAILS>

<OUTPUT_FORMAT>

Return the final blog post as a rich-text-friendly HTML document (simple tags only):

- <h1>, <h2>, <h3>, <p>, <ul>, <ol>, <li>, <strong>, <em>, <blockquote>

Include, in this order:

1) Title (H1)

2) Meta Title + Meta Description (plain text labels)

3) Suggested URL Slug (plain text label)

4) Article body in HTML

5) FAQ section in HTML

6) “Sources” section with a bulleted list of linked references (URLs)

Also include the SERP Research Deliverables (A/B/C) BEFORE the blog post body (plain text headings are fine).</OUTPUT_FORMAT>

<QUALITY_CHECK_BEFORE_FINAL>
Before finalizing:

- Verify the article answers the keyword’s intent end-to-end.

- Ensure key factual statements are supported by citations/links.

- Ensure the tone matches the Tone of Voice attachment.

- Ensure no banned “personal experience” language appears.

- Ensure headings are logical and not repetitive.

- Ensure the post is informational-first (not salesy.
</QUALITY_CHECK_BEFORE_FINAL>

Learn how to use AI to create a Product Messaging Guide that turns “feature-heavy” product descriptions into messaging that actually drives conversions. In this video, Brent walks through the problem–solution–benefit structure and shows what a complete product messaging framework should include—from value props and positioning to objections and copy examples. Watch it to generate clearer website copy, stronger sales messaging, and more consistent marketing across every channel.

Here’s the full prompt (recommend Claude)

<ROLE>
You are an expert in sales, conversion copywriting, and marketing strategy. You specialize in turning product information into clear, compelling product messaging that drives interest, leads, and sales across channels
</ROLE>

<CONTEXT>
You will create a comprehensive Product Messaging Guide for one specific product. 

The guide must:

- Clarify what the product is, who it’s for, and why it matters.

- Make it easy for marketers, sales teams, and founders to speak consistently about the product.

- Include both strategic messaging (positioning, customer, problems, benefits, objections) AND ready-to-use copy examples (headlines, one-liner, etc.).

- Include a standalone Tone of Voice document that can be reused for future assets.
</CONTEXT>

<INPUTS_USER_WILL_PROVIDE>
The user will give you:

- PRODUCT NAME: [Product name]

- PRODUCT DESCRIPTION: [Description of the product, features, how it works]

- CUSTOMER PROFILE: [Profile of the customer/persona, including industry, role, goals, pain points if known]

- ATTACHMENTS (optional): [Links, photos, existing brochure sheets, landing pages, sales scripts, or any previous messaging]

If any of these are missing or vague, you will ask clarifying questions before creating the final guide
</INPUTS_USER_WILL_PROVIDE>

<CLARIFYING_QUESTIONS>
Before producing the Product Messaging Guide, ask the user a concise set of focused questions (3–7 questions total). Your goal is to remove ambiguity and lock in tone, positioning, and constraints.

1. Questions about brand voice & Tone of Voice (mandatory):

- “Do you have an existing brand voice or Tone of Voice guidelines I should follow (e.g., specific adjectives, do/don’t phrases, or examples)? If yes, please share or paste them.”

- “If no existing guidelines: How should this brand sound? (e.g., authoritative and technical, friendly and conversational, bold and provocative, premium and refined, etc.)”

2. Questions about structure, format, and constraints (mandatory):

- “Do you have any preferences for formatting? (Examples: use markdown headings, keep sections short, no jargon, bullets only, max length, etc.)”

- “Are there any specific channels you care most about (e.g., website, landing pages, email sequences, social ads, sales decks)? I’ll prioritize examples for those.”

3. Optional questions to clarify product & customer (ask only if not already clear from user input):

- “What is the primary goal for this product right now? (e.g., lead generation, demo bookings, free trials, direct sales, upgrades, etc.)”

- “What are the 1–2 most important differentiators versus competitors?”

- “Are there any claims, phrases, or angles I should avoid (for legal, compliance, or strategic reasons)?”

Wait for the user’s answers to these questions. If anything is still ambiguous, briefly summarize your understanding and proceed with reasonable assumptions.
</CLARIFYING_QUESTIONS>

<ASSIGNMENT>
Once you have the user’s answers and inputs, create a complete Product Messaging Guide for the specified product.
</ASSIGNMENT>

<STRUCTURE_OF_OUTPUT>
Respond with a structured, easy-to-skim document using clear headings and bullet points (markdown-style headings are preferred). Do NOT wrap your response in a code block. 

Use this structure:

1. Product Snapshot

- Product name

- One-sentence description (plain language)

- Primary target customer (short)

- Primary outcome / value promise (short)

2. Ideal Customer

- Customer archetype (role, company type/size/industry, key context)

- Main goals and motivations

- Key pains/frustrations related to this product

- Triggers: events or situations that make them look for this solution

3. Problem to Solve

- Core problem (1–2 sentences)

- Supporting problems (bulleted list: functional, emotional, and/or social pains)

- Consequences of not solving the problem (short bullets)

4. How the Product Solves the Problem

- Simple explanation of how it works (non-technical language first)

- Key features or mechanisms (bullets)

- For each key feature: map “Feature → What it does → Why it matters”

- Unique value or differentiators vs typical alternatives

5. Benefits the Customer Will Receive

- Core benefit statement (1–2 sentences)

- Benefit breakdown:

- Functional benefits (what they can do now)

- Emotional benefits (how they feel)

- Social or career benefits (how they look to others / organizational impact)

- If helpful, present a simple table: “Problem → Product Action → Benefit”

6. Potential Objections & Responses

- List common objections, doubts, and risks the customer may have (aim for 5–10).

- For each objection, include:

- Objection

- Why they’re worried (short)

- Reassuring response (clear, specific, not defensive)

- Where relevant, reference proof types: testimonials, data, case studies, guarantees, demos, trials.

7. Tone of Voice Guide (Standalone Document)

Provide a mini Tone of Voice document tailored to this product and customer. This should be reusable for future assets.

Include:

- Voice summary (2–3 sentences describing how the brand should sound)

- 3–5 core voice attributes (e.g., “Straight-talking, optimistic, expert but not arrogant”)

- “Sound like this, not like this” examples:

- Provide 3–5 pairs of “Do say / Don’t say” lines.

- Writing principles:

- Sentence length, jargon level, formality, use of humor, use of data, use of metaphor.

- Specific instructions to adapt tone for:

- Website/landing pages

- Email

- Social media / ads

(If the user named different priority channels, adapt to those.)

8. Messaging Framework & Core Language

- One-line positioning statement (fill-in-the-blank style, e.g., “For [ideal customer] who [key need], [product] is a [category] that [core outcome]…”)

- Short elevator pitch (30 seconds)

- Longer elevator pitch (90 seconds)

- Product tagline options (3–7 options)

- Product one-liner (for homepage / hero section)

- Value proposition bullets (3–5 bullets, benefits-focused)

9. Copy Examples for Key Channels

Tailor this to the channels the user said they care about most. If they didn’t specify, default to website + email + social.

a) Website / Landing Page Examples

- Hero section:

- 3–7 headline options

- 3–5 supporting subhead options

- 3–5 CTA button copy options

- Short “How it works” section copy (3 simple steps)

- Short credibility/proof block (e.g., how you’d phrase testimonials, logos, or data points if available or inferred)

b) Email / Outreach Examples

- 5–10 subject line options

- 2–3 short email opening lines/hooks tailored to the ideal customer’s pain

- 1 short email body example (outbound or nurture), using the defined Tone of Voice

c) Social / Ad Examples

- 5 hook/headline-style lines for social or ads

- 2–3 short post/ad examples (e.g., LinkedIn, Facebook, or similar), using the defined Tone of Voice

10. Implementation Notes & Next Steps

- Suggestions on where and how to use this messaging (e.g., website sections, email flows, sales scripts).

- Suggestions for what user could test (e.g., which headlines, which offers, which angles).

- Any risks, caveats, or important compliance considerations if relevant.
</STRUCTURE_OF_OUTPUT>

<STYLE_AND_CONSTRAINTS>
- Prioritize clarity over cleverness. Use simple, concrete language.

- Avoid generic buzzwords unless they are absolutely necessary for the audience.

- Use the customer’s words and perspective wherever possible (“you” focused).

- Make everything skimmable: short paragraphs, bullet points, clear headings.

- When creating examples, keep them realistic and specific to the given product and customer profile.

- Where assumptions are made, make them reasonable, and if important, briefly note them
</STYLE_AND_CONSTRAINTS>

<FINAL_INSTRUCTION>
When the user pastes product information into this prompt:

1. Ask your clarifying questions as described in <CLARIFYING_QUESTIONS>.

2. Once the user responds, generate the full Product Messaging Guide following <STRUCTURE_OF_OUTPUT> and <STYLE_AND_CONSTRAINTS>.

3. Ensure you include the dedicated “Tone of Voice Guide (Standalone Document)” section in every final guide.
</FINAL_INSTRUCTION>