A prompt by Will Mulholland of Intelligent Growth for product marketers. You paste a product description and several interview transcripts, and the assistant acts as a skeptical analyst: it quotes the three strongest themes, names one product claim the interviews do not back up, and suggests three questions for the next round. It is told to say when evidence is thin rather than invent themes. Remove customer names and personal details from the transcripts before you paste them.
Act as a sharp, skeptical research analyst. I'm pasting a product description
and [NUMBER] real customer interview transcripts.
Do three things:
1. The three strongest themes across the interviews, in customers' own words
where possible. Quote them.
2. The one thing my product description claims that the interviews do NOT
support. Tell me where I'm probably wrong.
3. Three questions I should ask in the next round to pressure-test my
assumptions.
Be blunt. If the evidence for a theme is thin, say so. Do not invent themes
to fill the list.
Audit a YouTube channelThis prompt reviews a YouTube channel from its link, details, screenshots, analytics, or videos. It checks search visibility, the videos themselves, thumbnails, titles and tags, subscriber growth, rival channels, and Shorts. You get 7-, 30-, and 90-day plans, ideas for new videos and their titles, and scores from 1 to 100.Marketing
Audit an ecommerce welcome email seriesA prompt from email marketer Chase Dimond that checks an online store's welcome emails against ten rules, from sending the first email right away to stopping the series after a purchase. You paste your signup popup, each email in sequence with its subject, the preview line, timing and buttons, and whether the series stops on purchase. It returns fixes ranked by likely effect on sales, paste-ready rewrites for the top three in your brand voice, and any rule it could not check.Marketing
Audit and fix a site's technical SEO with CodexA prompt for Codex, or another coding agent with access to your website's code, that reviews the whole site for technical SEO and then makes the changes itself rather than only listing them. It covers titles, topical relevance, internal and outbound links, speed, crawlability, structured data, canonical tags and Core Web Vitals, and borrows attribute names from the leaked Google API documents as hints. It asks for white-hat changes only, keeps existing features and design, and ends with a changelog plus the off-site work left to do.Marketing
