30 Claude Prompts That Generate Market Research
Describe your market and Claude returns a finished research artifact you can drop into a deck or memo: TAM/SAM/SOM sizing models, competitor landscapes, buyer personas, trend radars, pricing benchmarks, and go-to-market plans. Structured docs and tables, not "tell me about my industry."
In short: This page contains 30 copy-paste ready prompts, organized into 6 categories with a description and pro tip for each. The first 15 prompts are free instantly โ no signup needed. Hand-curated and tested by the AI Academy team.
Market Sizing (TAM / SAM / SOM)
5 promptsTop-Down TAM / SAM / SOM Model
1/30You are a market analyst who builds defensible market-sizing models for investor decks. <context> I need a complete top-down TAM/SAM/SOM sizing for my market, delivered as one self-contained research document I can paste straight into a pitch deck. State every assumption and show the math. </context> <inputs> - Product / category: [WHAT I SELL] - Target market and geography: [WHO AND WHERE] - Price point or ACV: [TYPICAL ANNUAL REVENUE PER CUSTOMER] - Total addressable universe I know of: [POPULATION / NUMBER OF COMPANIES, IF KNOWN] - Time horizon: [E.G. 5 YEARS] </inputs> <task> Build a sizing report with: a one-paragraph market definition, a TAM/SAM/SOM table (each with the number, the formula used, and the source or assumption), a funnel diagram in text from TAM down to SOM, a 5-year SOM growth projection table, and a short list of the three assumptions the whole model hinges on. </task> <constraints> - Show the arithmetic for every number; never state a figure without the calculation behind it. - Clearly label figures as estimate vs. sourced, and flag confidence (high/medium/low). - No hype adjectives; a skeptical investor should be able to challenge each line. </constraints> <format> Return the sizing report as a formatted document with tables (as an artifact), then a short note on which assumptions to pressure-test first. </format>
Produces a defensible top-down TAM/SAM/SOM model with visible math and labeled assumptions, ready to use in a pitch deck.
Pro tip: Give Claude one real number you trust (industry revenue or company count) and tell it to anchor the whole model to that instead of guessing the top line.
Bottom-Up Market Sizing
2/30You are a growth analyst who prefers bottom-up sizing because it is harder to dismiss than top-down. <context> Build a bottom-up market-size estimate for my business, delivered as a structured research doc that walks from unit economics up to total revenue potential. This is a finished artifact for a board memo. </context> <inputs> - Product and who buys it: [OFFER AND CUSTOMER] - Number of potential customers per segment: [ROUGH COUNTS BY SEGMENT] - Average price / units per customer per year: [PRICING AND USAGE] - Realistic penetration by year 3: [PERCENT, OR ASK ME TO ESTIMATE] - Geography: [MARKETS] </inputs> <task> Produce a report with: a build-up table (segment x customers x price x frequency = revenue), a rolled-up total addressable revenue figure, a realistic capturable share with the reasoning, a 3-year ramp table, and a comparison note explaining how this bottom-up number differs from a naive top-down guess and why. </task> <constraints> - Every row must trace to an input; make hidden assumptions explicit as their own labeled rows. - Give a low / base / high range for the final number, not a single false-precision figure. - Flag which inputs move the answer the most. </constraints> <format> Return the bottom-up model as a document with tables (as an artifact), then note the two inputs I should validate with real data before quoting the number. </format>
Builds a bottom-up market-size estimate from unit economics up to a low/base/high revenue range as a ready-to-use memo artifact.
Pro tip: Ask Claude to make every assumption a separate table row so you can swap one number and instantly see the total recalculate.
New-Category / Value-Theory Sizing
3/30You are a strategy consultant who sizes markets that do not exist yet using value-theory (willingness-to-pay for the problem solved). <context> My product creates a new category, so there is no existing market to measure. Build a value-theory sizing document that estimates the market from the economic value of the problem it removes. Deliver it as one self-contained research artifact. </context> <inputs> - The new thing I do: [PRODUCT] - The expensive problem it replaces: [CURRENT WORKAROUND AND ITS COST] - Who suffers this problem: [BUYER AND HOW MANY] - Share of that value I can reasonably charge: [PERCENT OR ASK ME] </inputs> <task> Write a sizing report with: a framing of the status-quo cost (time, money, or risk) per customer, a value-created-per-customer calculation, a defensible capture rate with reasoning, the resulting TAM, a sensitivity table showing the TAM at different capture rates, and a short narrative for why top-down category data does not apply here. </task> <constraints> - Ground the value claim in concrete cost drivers, not vague benefit language. - Show the capture-rate logic; do not just assert a percentage. - Give a range and mark confidence explicitly. </constraints> <format> Return the value-theory sizing as a formatted document with tables (as an artifact), then note how to defend it against a "that market is zero today" objection. </format>
Generates a value-theory market-size estimate for a new category based on the cost of the problem solved, as a ready-to-use artifact.
Pro tip: Feed Claude a real dollar cost of the current workaround (hours x wage, or a tool's price) so the value math rests on something concrete.
Serviceable Market by Segment & Geography
4/30You are a market-research analyst who segments an addressable market into prioritized, serviceable slices. <context> I have a rough total market but need it broken into serviceable segments and geographies with a priority ranking. Deliver a structured segmentation report I can use to focus sales and marketing. </context> <inputs> - Total market context: [WHAT I KNOW ABOUT MARKET SIZE] - Product: [OFFER] - Candidate segments: [BY INDUSTRY, COMPANY SIZE, ROLE, OR USE CASE] - Candidate geographies: [REGIONS OR COUNTRIES] - What makes a segment easy for me to serve: [FIT CRITERIA] </inputs> <task> Produce a segmentation report with: a table of segments x geography showing estimated size, fit score (1-5), reachability, and competitive intensity for each cell; a ranked shortlist of the top three serviceable slices with a one-line rationale each; and a note on which slice to attack first and why. </task> <constraints> - Score every cell on the same criteria so the ranking is comparable. - Distinguish 'big' from 'winnable'; call out large-but-hard segments explicitly. - Keep size figures labeled as estimates with confidence. </constraints> <format> Return the segmentation report as a document with a scoring matrix table (as an artifact), then note which segment to test first and the signal that would confirm it. </format>
Breaks a market into scored, prioritized serviceable segments by geography and use case as a ready-to-use segmentation report.
Pro tip: Tell Claude your actual sales motion (self-serve vs. enterprise) so the reachability scores reflect how you really win deals.
Market-Size Scenario & Sensitivity Table
5/30You are a financial analyst who stress-tests market-size assumptions with scenario modeling. <context> I already have a base-case market size but investors will attack the assumptions. Build a scenario and sensitivity analysis as one structured research document so I can show I have thought through the downside and upside. </context> <inputs> - Base-case market size and how it was derived: [NUMBER AND METHOD] - Key drivers behind it: [E.G. PENETRATION, PRICE, GROWTH RATE, CHURN] - Plausible low and high values for each driver: [RANGES, OR ASK ME] - Time horizon: [YEARS] </inputs> <task> Produce a report with: a driver table listing each assumption with its low/base/high value; a scenario table showing pessimistic, base, and optimistic market sizes with the resulting figure for each; a one-factor sensitivity table showing how the market size moves when each driver alone changes; and a short paragraph naming the single assumption the outcome is most sensitive to. </task> <constraints> - Keep the base case identical to my input; only vary the stated drivers. - Show the calculation logic for at least the pessimistic and optimistic cases. - Rank drivers by impact, not by order given. </constraints> <format> Return the scenario analysis as a document with tables (as an artifact), then note the one driver I should gather hard data on to tighten the model. </format>
Delivers a scenario and sensitivity analysis of a market-size model, ranking the assumptions that move the answer most, as a ready-to-use artifact.
Pro tip: Ask Claude to bold the driver with the widest swing so you know exactly where to spend research time before the next investor meeting.
XML tags are just the start. Learn the full Claude workflow.
A growing library of 300+ hands-on AI tutorials covering Claude, ChatGPT, and 50+ tools. New tutorials added every week.
Competitor Landscape
5 promptsCompetitive Landscape Matrix
6/30You are a competitive-intelligence analyst who maps markets for strategy teams. <context> I need a structured competitive landscape for my market, delivered as one self-contained research document with a comparison matrix I can present to leadership. Base it on what is publicly known and clearly flag anything you are inferring. </context> <inputs> - My product and category: [WHAT I DO] - Competitors I know of: [LIST, OR ASK ME TO SUGGEST] - Dimensions that matter to buyers: [E.G. PRICE, TARGET SEGMENT, KEY FEATURES, INTEGRATIONS] - My positioning goal: [WHERE I WANT TO STAND OUT] </inputs> <task> Produce a landscape report with: a one-paragraph market overview, a competitor comparison matrix (rows = competitors including me, columns = the buyer dimensions), a short profile of each competitor (positioning, target buyer, apparent pricing, notable strength and weakness), a section naming the whitespace or underserved need, and a recommended angle for where I should position. </task> <constraints> - Mark any figure or claim you are inferring as an inference, not a fact. - Keep each competitor scored on the same dimensions for a fair matrix. - Name a concrete whitespace, not a generic 'be better' suggestion. </constraints> <format> Return the landscape report as a document with a comparison matrix table (as an artifact), then note which two competitors to monitor most closely and why. </format>
Generates a competitive landscape report with a scored comparison matrix and a whitespace recommendation, ready to present to leadership.
Pro tip: Paste each competitor's homepage tagline so Claude classifies their real positioning instead of guessing from the name alone.
Single-Competitor Deep-Dive Profile
7/30You are a competitive analyst who writes detailed teardown profiles of individual rivals. <context> I need a deep-dive intelligence profile of one specific competitor, delivered as one structured research document my sales and product teams can act on. Distinguish verified facts from reasonable inference. </context> <inputs> - The competitor: [NAME AND WEBSITE] - What I most want to understand: [E.G. PRICING, TARGET SEGMENT, ROADMAP SIGNALS] - My product for comparison: [MY OFFER] - Any facts I already know about them: [NOTES] </inputs> <task> Write a competitor profile with these sections: overview and positioning; target customer and ICP; product and standout features; apparent pricing and packaging; go-to-market motion; strengths; weaknesses and gaps; and a table of how they compare to me on 5-6 buyer criteria. End with three ways I can win deals against them. </task> <constraints> - Label each claim as [known] or [inferred] so the team trusts the doc. - Be specific about weaknesses; avoid generic 'poor support' filler unless you can justify it. - The 'how to win' points must be actionable, not slogans. </constraints> <format> Return the competitor profile as a formatted document with a comparison table (as an artifact), then note what public sources would confirm the inferred claims. </format>
Produces a detailed single-competitor teardown with positioning, pricing, gaps, and how-to-win tactics as a ready-to-use intelligence doc.
Pro tip: Give Claude a screenshot or copy of the competitor's pricing page so the packaging analysis is grounded in their real tiers.
Feature Comparison Grid
8/30You are a product marketer who builds honest, buyer-facing feature comparison grids. <context> I need a feature-by-feature comparison of my product against competitors, delivered as one structured document with a grid I can adapt into a comparison page or sales enablement asset. </context> <inputs> - My product: [OFFER] - Competitors to compare: [2-5 NAMES] - Feature categories that matter: [E.G. CORE FEATURES, INTEGRATIONS, SECURITY, SUPPORT, PRICING MODEL] - Where I am genuinely stronger: [MY REAL ADVANTAGES] </inputs> <task> Build a comparison document with: a grouped feature grid (rows = features grouped by category, columns = products) using clear yes / partial / no or short values; a highlighted-differentiators section listing where I win with a one-line 'why it matters' for each; an honest section on where competitors currently lead; and a short buyer-guidance paragraph on who each product is best for. </task> <constraints> - Be honest where competitors win; a grid that says I win everything is not credible. - Group features so buyers can scan by what they care about. - Translate each differentiator into a buyer outcome, not just a checkmark. </constraints> <format> Return the comparison as a document with a grouped grid table (as an artifact), then note which rows are most likely to change as competitors ship updates. </format>
Builds an honest grouped feature comparison grid with differentiators and buyer guidance as a ready-to-use sales enablement artifact.
Pro tip: Tell Claude which features you will actually ship next quarter so it does not credit you for capabilities you cannot yet demo.
Positioning / Perceptual Map
9/30You are a brand strategist who visualizes competitive positioning with perceptual maps. <context> I need a positioning map of my market on two axes that matter to buyers, delivered as one structured research document with the map described in a way I can rebuild in a slide. </context> <inputs> - My product and category: [OFFER] - Competitors to place: [LIST] - Two axes buyers actually trade off: [E.G. PRICE vs. POWER, SIMPLE vs. CUSTOMIZABLE, SMB vs. ENTERPRISE] - Where I want to be perceived: [DESIRED POSITION] </inputs> <task> Produce a positioning report with: a definition of each axis and why buyers care about it; a coordinate table placing every competitor and me on both axes (values from -5 to +5) with a one-line justification each; a text description of the resulting quadrants and who occupies them; identification of the least-crowded quadrant; and a positioning-statement draft for the space I should own. </task> <constraints> - Justify every coordinate; do not scatter points arbitrarily. - Pick axes that represent real buyer trade-offs, not vanity metrics. - Name a defensible open position, not just 'the top-right corner'. </constraints> <format> Return the positioning analysis as a document with the coordinate table and quadrant description (as an artifact), then note how to test whether buyers actually perceive the axes the way you assumed. </format>
Delivers a perceptual positioning map with justified coordinates and an open-space positioning statement as a ready-to-use strategy artifact.
Pro tip: Ask Claude to propose three candidate axis pairs first, then pick the pair that best separates you from the pack before it plots anyone.
Competitive Battlecard
10/30You are a sales-enablement lead who writes battlecards reps use live on calls. <context> My sales team keeps losing to one competitor. Build a one-page competitive battlecard as a self-contained document reps can pull up mid-call. It must be scannable and blunt. </context> <inputs> - My product: [OFFER] - The competitor we lose to: [NAME] - Where we usually win and lose: [WHAT WE KNOW] - Common objections buyers raise: [OBJECTIONS] - Our proof points: [METRICS, CASE STUDIES, GUARANTEES] </inputs> <task> Build a battlecard with these blocks: a one-line 'why we win' summary; a why-we-win bullet list and a why-we-lose bullet list (be honest); a table of their claim -> our counter for the top objections; three landmine questions our rep should plant that expose their weaknesses; trap-setting talk tracks in the rep's voice; and a 'do not say' list to avoid triggering their strengths. </task> <constraints> - Keep it to a single scannable page; reps read it live, not as an essay. - Counters must be truthful and specific, backed by a proof point where possible. - Include an honest 'when to walk away' note if we are a poor fit. </constraints> <format> Return the battlecard as a formatted one-page document with a claim-vs-counter table (as an artifact), then note which section to update after each lost deal. </format>
Produces a rep-ready competitive battlecard with why-we-win/lose points, objection counters, and talk tracks as a ready-to-use sales artifact.
Pro tip: Feed Claude two real quotes from recent lost deals so the objection counters answer what buyers actually say, not what you assume.
Customer & Persona Research
5 promptsBuyer Persona Profile
11/30You are a customer-research strategist who builds evidence-based buyer personas. <context> I need a complete buyer persona for my primary customer, delivered as one structured research document the whole team can align around. Base it on my inputs and clearly flag any detail that is an assumption to validate. </context> <inputs> - Product: [OFFER] - Who I think buys it: [ROLE, INDUSTRY, COMPANY SIZE OR DEMOGRAPHICS] - The main problem they hire me to solve: [PROBLEM] - What I know about their goals and frustrations: [NOTES] - Where they hang out / learn: [CHANNELS] </inputs> <task> Write a persona document with: a name and one-line snapshot; role, context, and a typical day; top goals and success metrics; pains and frustrations; buying triggers and objections; how they research and decide; preferred channels and content; a 'what they need to hear from us' messaging note; and a short list of assumptions to validate with real interviews. </task> <constraints> - Make it specific and behavioral; avoid demographic cliches that do not affect the sale. - Separate verified traits from assumptions in a clearly labeled section. - Tie every pain to how my product addresses it. </constraints> <format> Return the persona as a formatted profile document (as an artifact), then note the three questions to ask real customers to confirm the risky assumptions. </format>
Generates a behavioral buyer persona with goals, pains, triggers, and messaging notes as a ready-to-use team-alignment artifact.
Pro tip: Paste two or three real quotes from customer calls and tell Claude to build the pains and triggers around those actual words.
Ideal Customer Profile (ICP) Doc
12/30You are a go-to-market strategist who defines tight ICPs so sales stops chasing bad-fit deals. <context> My team wastes time on deals that never close. Build a precise Ideal Customer Profile as one structured document with firmographic and behavioral criteria and a scoring rubric we can apply to any account. </context> <inputs> - Product: [OFFER] - My best current customers have in common: [TRAITS I HAVE NOTICED] - Deals that go badly usually look like: [ANTI-PATTERNS] - What triggers a real need for us: [BUYING SIGNALS] - Deal size or contract type: [PRICING CONTEXT] </inputs> <task> Produce an ICP document with: a one-paragraph ICP statement; a firmographic criteria table (industry, size, geography, tech, budget) with must-have vs. nice-to-have; behavioral and trigger signals that indicate readiness; explicit disqualifiers (who to say no to); and a 100-point account-scoring rubric mapping the criteria to points with a threshold for 'pursue vs. pass'. </task> <constraints> - Be exclusionary on purpose; a good ICP rules people out. - Make the scoring rubric add to exactly 100 and be usable in under two minutes per account. - Ground criteria in what my best customers share, not aspiration. </constraints> <format> Return the ICP as a document with the criteria and scoring tables (as an artifact), then note which single criterion best predicts a good-fit deal. </format>
Delivers a precise Ideal Customer Profile with firmographic criteria, disqualifiers, and a 100-point scoring rubric as a ready-to-use GTM artifact.
Pro tip: List your five happiest customers and five worst churned ones; Claude reverse-engineers sharper criteria from the contrast than from a wish list.
Jobs-to-be-Done Map
13/30You are a product researcher who applies the Jobs-to-be-Done framework to uncover why customers really buy. <context> I need a Jobs-to-be-Done analysis for my product, delivered as one structured research document that reframes what customers are truly hiring my product to accomplish. Deliver it as a reusable artifact. </context> <inputs> - Product: [OFFER] - Who uses it: [CUSTOMER] - The moment they reach for a solution: [TRIGGERING SITUATION] - What they currently use instead: [ALTERNATIVES INCLUDING DOING NOTHING] </inputs> <task> Produce a JTBD document with: the core functional job written as 'When [situation], I want to [motivation], so I can [outcome]'; a table of the main job broken into related functional, emotional, and social jobs; the desired outcomes and how customers measure success for each; the obstacles and anxieties blocking progress; the push/pull/habit/anxiety forces around switching; and where my product over- or under-serves the job today. </task> <constraints> - Frame jobs as customer goals, not product features. - Include emotional and social jobs, not only functional ones. - Be honest about where I over-serve (adds cost, not value) as well as under-serve. </constraints> <format> Return the JTBD analysis as a document with job and forces tables (as an artifact), then note which unmet outcome is the strongest opportunity to build or message around. </format>
Produces a Jobs-to-be-Done map with functional, emotional, and social jobs plus switching forces as a ready-to-use product research artifact.
Pro tip: Tell Claude about the last thing a customer 'fired' before choosing you; the switching forces get far sharper when anchored to a real story.
Customer Interview Guide & Synthesis Template
14/30You are a UX researcher who runs discovery interviews and turns them into decisions. <context> I am about to interview customers and need both a non-leading interview guide and a synthesis template, delivered together as one structured research document I can use before and after the calls. </context> <inputs> - What I am trying to learn: [RESEARCH GOAL / KEY QUESTIONS] - Who I am interviewing: [SEGMENT] - The product or idea in question: [OFFER] - Decisions this research will inform: [DECISIONS] - Interview length: [E.G. 30 MINUTES] </inputs> <task> Produce a document with two parts. Part one: an interview guide with a warm-up, open behavioral questions grouped by theme, follow-up probes, and a wrap-up, all timed to fit the length and written to avoid leading the witness. Part two: a synthesis template with a per-interview capture table (quote, observation, pain, surprise), an affinity-grouping structure to cluster findings, and a summary section that maps findings to the decisions. </task> <constraints> - Questions must ask about past behavior and real examples, never pitch the product or ask 'would you buy this'. - Keep the guide timed and realistic for the stated length. - The synthesis template must force evidence (quotes) before conclusions. </constraints> <format> Return the guide and synthesis template as one formatted document with tables (as an artifact), then note the one question most likely to surface a surprising insight. </format>
Delivers a non-leading customer interview guide plus a synthesis template that ties findings to decisions, as a ready-to-use research artifact.
Pro tip: Tell Claude the decision you must make after the interviews so it designs questions whose answers actually change what you do.
Voice-of-Customer / Review Mining Report
15/30You are an insights analyst who mines customer feedback into a structured voice-of-customer report. <context> I have a pile of raw customer feedback and need it turned into a structured voice-of-customer report, delivered as one self-contained document with themes, representative quotes, and priorities. </context> <inputs> - Where the feedback comes from: [REVIEWS, SUPPORT TICKETS, SURVEY OPEN-ENDS, CALLS] - The raw feedback: [PASTE FEEDBACK OR DESCRIBE THE TYPICAL COMMENTS] - Product context: [OFFER] - What I want to decide from this: [E.G. ROADMAP, MESSAGING, CHURN FIXES] </inputs> <task> Produce a voice-of-customer report with: a theme table (theme, frequency estimate, sentiment, a representative verbatim quote); the top praised strengths and top complaints ranked; the exact language customers use to describe the value (for reuse in copy); a churn-risk or friction section; and a prioritized action list mapping the loudest, highest-impact themes to next steps. </task> <constraints> - Anchor every theme to at least one real or realistic verbatim quote. - Separate what customers say they want from the underlying need. - Prioritize by frequency and impact, not by what is easiest to fix. </constraints> <format> Return the VoC report as a document with a themes table and prioritized actions (as an artifact), then note which customer phrase would make the strongest headline or tagline. </format>
Turns raw customer feedback into a themed voice-of-customer report with verbatim quotes and prioritized actions as a ready-to-use artifact.
Pro tip: Paste the feedback verbatim rather than summarizing it; Claude extracts the exact customer phrasing you can lift straight into marketing copy.
Industry & Trends Analysis
5 promptsPESTEL Macro-Trends Report
16/30You are a strategy analyst who assesses the macro forces shaping an industry. <context> I need a PESTEL analysis of the external forces affecting my market, delivered as one structured research document I can use in a strategy review. Focus on what is decision-relevant, not an encyclopedia. </context> <inputs> - Industry / market: [SECTOR] - Geography: [WHERE I OPERATE] - My business and what I am deciding: [CONTEXT AND DECISION] - Time horizon: [E.G. NEXT 3 YEARS] </inputs> <task> Produce a PESTEL report with a section for each factor (Political, Economic, Social, Technological, Environmental, Legal): 2-4 specific, current forces per factor, each tagged with likely direction (rising/falling), impact on my business (high/medium/low), and time horizon. End with a table ranking the top five forces by impact and a short 'so what' paragraph on the strategic implications. </task> <constraints> - Every force must state a concrete implication for my business, not a generic observation. - Mark speculation as speculation and note where a data source would confirm it. - Rank by impact so I know what actually matters. </constraints> <format> Return the PESTEL report as a document with the factor sections and a ranked-impact table (as an artifact), then note which two forces I should build a contingency plan for. </format>
Produces a decision-focused PESTEL macro-trends report with impact-ranked forces and strategic implications as a ready-to-use strategy artifact.
Pro tip: State the specific decision you face (enter a market, raise prices, hire) so Claude filters out trends that are interesting but irrelevant to it.
Industry Trend Radar
17/30You are an industry analyst who builds trend radars that separate signal from hype. <context> I need a trend radar for my industry, delivered as one structured research document that classifies trends by maturity and time-to-impact so I know what to act on now versus watch. </context> <inputs> - Industry: [SECTOR] - My business and role in it: [CONTEXT] - Trends I am already tracking: [LIST, OR ASK ME TO IDENTIFY] - Planning horizon: [E.G. 0-3 YEARS] </inputs> <task> Produce a trend-radar report with: a table of 8-12 trends, each with a one-line description, maturity stage (emerging / growing / mainstream / declining), time-to-impact (now / 1-2 yrs / 3+ yrs), and relevance to me (high/medium/low); a 'radar' grouping of trends into act-now, prepare, and watch buckets; and a short section on the two trends most likely to be over-hyped versus genuinely disruptive. </task> <constraints> - Distinguish durable shifts from fads; call out hype explicitly. - Rate relevance to my specific business, not the industry in the abstract. - Keep descriptions concrete enough that I could brief someone in one line. </constraints> <format> Return the trend radar as a document with the trend table and act/prepare/watch buckets (as an artifact), then note the single trend I cannot afford to ignore this year. </format>
Delivers an industry trend radar classifying trends by maturity, time-to-impact, and relevance into act/prepare/watch buckets as a ready-to-use artifact.
Pro tip: Ask Claude to flag which listed trends are likely vendor hype versus real demand shifts so you don't reorganize the roadmap around a fad.
Emerging-Tech Disruption Scan
18/30You are a foresight analyst who assesses how emerging technologies could disrupt a business. <context> I need a disruption scan of emerging technologies relevant to my market, delivered as one structured research document that assesses threat and opportunity for each, with a recommended posture. </context> <inputs> - My business and current model: [WHAT I DO AND HOW I MAKE MONEY] - Technologies to assess: [E.G. AI AGENTS, SPECIFIC TECH, OR ASK ME TO SUGGEST] - What I most fear being disrupted: [CONCERN] - Time horizon: [YEARS] </inputs> <task> Produce a disruption-scan report with: a table of technologies, each with maturity, a plausible disruption scenario for my business, threat level, opportunity level, and time-to-relevance; a section describing the single most credible disruption narrative in a short paragraph; a 'defend' list and an 'attack' list of moves; and a recommended posture (ignore / monitor / experiment / invest) for each technology. </task> <constraints> - Give balanced threat AND opportunity framing for each tech, not just doom. - Make disruption scenarios concrete and mechanism-based, not buzzword bingo. - Recommend a clear posture per technology. </constraints> <format> Return the disruption scan as a document with the technology assessment table (as an artifact), then note which technology to run a small experiment on within 90 days. </format>
Produces an emerging-tech disruption scan with threat/opportunity scoring and a recommended posture per technology as a ready-to-use foresight artifact.
Pro tip: Tell Claude exactly how you make money today; the sharpest disruption scenarios are the ones that break your specific revenue mechanism.
SWOT With Market-Trend Overlay
19/30You are a strategy consultant who builds SWOT analyses grounded in market reality rather than internal opinion. <context> I need a SWOT analysis for my business that connects internal strengths and weaknesses to external market trends, delivered as one structured document with a follow-on strategy matrix. </context> <inputs> - My business: [WHAT I DO] - Honest self-assessment of strengths and weaknesses: [NOTES] - Key market trends affecting me: [TRENDS, OR ASK ME TO IDENTIFY] - My competitive context: [KEY RIVALS OR PRESSURES] </inputs> <task> Produce a SWOT document with: four populated quadrants (strengths, weaknesses, opportunities, threats) with 3-5 specific, evidenced points each; then a TOWS strategy matrix pairing them into concrete moves (SO = use strengths to seize opportunities, ST = use strengths to counter threats, WO = fix weaknesses to unlock opportunities, WT = defend against weakness-threat combinations); and a shortlist of the top three strategic priorities that emerge. </task> <constraints> - Every SWOT point must be specific and defensible, not a platitude like 'great team'. - Opportunities and threats must tie to real external trends, not internal wishes. - The TOWS moves must be concrete actions, not restated quadrants. </constraints> <format> Return the SWOT and TOWS as a document with quadrant and strategy-matrix tables (as an artifact), then note which single priority to start this quarter. </format>
Delivers a SWOT analysis linked to market trends plus a TOWS strategy matrix of concrete moves as a ready-to-use strategy artifact.
Pro tip: Push Claude to challenge each 'strength' by asking whether a competitor could claim the same; it weeds out generic points fast.
Trend Impact & Opportunity Matrix
20/30You are a market strategist who turns raw trends into prioritized business opportunities. <context> I have a list of trends but need them converted into concrete, prioritized opportunities for my business, delivered as one structured research document with an impact-versus-effort matrix. </context> <inputs> - My business: [WHAT I DO] - Trends to evaluate: [LIST, OR ASK ME TO IDENTIFY] - My capabilities and constraints: [WHAT I CAN AND CANNOT DO] - Goal these opportunities should serve: [E.G. NEW REVENUE, RETENTION] </inputs> <task> Produce a report with: for each trend, one or two concrete opportunities it opens for my business; a table scoring each opportunity on potential impact (1-5), effort/feasibility (1-5), time-to-value, and strategic fit; an impact-versus-effort placement describing which opportunities are quick wins, big bets, or traps; and a prioritized shortlist of the top three with a first step for each. </task> <constraints> - Translate abstract trends into opportunities I could actually pursue, given my constraints. - Score consistently so the prioritization is comparable. - Flag seductive-but-low-fit opportunities as traps. </constraints> <format> Return the opportunity matrix as a document with the scoring table and quick-win/big-bet grouping (as an artifact), then note the one quick win to start this month. </format>
Converts trends into scored, prioritized business opportunities on an impact-versus-effort matrix as a ready-to-use planning artifact.
Pro tip: List your real constraints (budget, headcount, tech) so Claude's feasibility scores reflect what you can ship, not an idealized roadmap.
Pricing Research
5 promptsCompetitive Pricing Benchmark Table
21/30You are a pricing analyst who benchmarks how a market prices and packages. <context> I need a competitive pricing benchmark for my category, delivered as one structured research document with a comparison table so I can see where I sit and where the gaps are. Mark inferred prices clearly. </context> <inputs> - My product and current pricing: [OFFER AND MY PRICES] - Competitors to benchmark: [LIST] - What buyers are actually paying for (the value metric): [E.G. SEATS, USAGE, FEATURES] - Segment: [WHO BUYS] </inputs> <task> Produce a pricing benchmark with: a table of competitors x their tiers showing entry price, mid price, top price, the value metric they charge on, and what unlocks each tier; a section on the common pricing models in the category (flat, per-seat, usage, tiered) and which dominates; an analysis of where my pricing sits (underpriced, aligned, premium) with reasoning; and identified pricing whitespace (an underserved price point or model). </task> <constraints> - Label any price you infer versus one that is publicly listed. - Normalize tiers so the comparison is apples-to-apples where possible. - Name a concrete pricing gap, not a vague 'consider adjusting'. </constraints> <format> Return the pricing benchmark as a document with the comparison table (as an artifact), then note which competitor's pricing move would hurt me most and how I would respond. </format>
Generates a competitive pricing benchmark table with value metrics, positioning analysis, and pricing whitespace as a ready-to-use research artifact.
Pro tip: Paste each competitor's pricing page URL contents so the tiers are exact rather than inferred, then have Claude flag anything it had to estimate.
Van Westendorp Price-Sensitivity Plan & Analysis
22/30You are a pricing researcher who runs Van Westendorp Price Sensitivity Meter studies. <context> I want to run a Van Westendorp price-sensitivity study and analyze the results. Deliver one structured research document containing both the survey design and an analysis template that turns responses into a recommended price range. </context> <inputs> - Product being priced: [OFFER] - Target respondents: [WHO I WILL SURVEY] - Current or candidate price: [PRICE, IF ANY] - Sample data or 'template only': [PASTE RESPONSE DATA OR SAY TEMPLATE ONLY] </inputs> <task> Produce a document with two parts. Part one: the four Van Westendorp questions worded correctly (too cheap, cheap/bargain, expensive, too expensive), screening questions, and a note on minimum sample size. Part two: an analysis template explaining how to plot the cumulative curves, how to read the point of marginal cheapness, point of marginal expensiveness, optimal price point, and indifference price point, and a results table to fill in. If I pasted data, compute the ranges; otherwise show the worked method with example numbers. </task> <constraints> - Word the four questions exactly per the method; a subtle rewording invalidates results. - Explain each derived price point in plain language, not just jargon. - If computing from data, show the logic; if template, use clearly-labeled example numbers. </constraints> <format> Return the study plan and analysis as one document with the question set and a results table (as an artifact), then note the sample size and respondent quality needed for the result to be trustworthy. </format>
Delivers a Van Westendorp price-sensitivity study design plus an analysis template that derives an acceptable price range as a ready-to-use artifact.
Pro tip: Paste real survey responses if you have them and Claude computes the four price points directly instead of leaving you a blank template.
Value-Based / Willingness-to-Pay Analysis
23/30You are a pricing strategist who sets prices from customer value rather than cost. <context> I want to price based on the value I create for customers, not my costs. Deliver one structured research document that estimates willingness-to-pay and recommends a value-based price with the reasoning. </context> <inputs> - Product and the outcome it delivers: [OFFER AND RESULT] - The measurable value to the customer: [TIME SAVED, REVENUE GAINED, COST AVOIDED] - Customer segment and their budget context: [WHO AND THEIR SPEND] - Next-best alternative and its price: [COMPETITOR OR STATUS QUO COST] </inputs> <task> Produce a WTP analysis with: a value quantification (the dollar value created per customer per year, shown as a calculation); a reference-price framing against the next-best alternative; an estimated willingness-to-pay range with the reasoning; a value-based price recommendation and the share of value it captures; a fairness check (does the customer clearly keep more value than they pay); and three ways to justify the price to a skeptical buyer. </task> <constraints> - Show the value math; do not assert willingness-to-pay without deriving it. - Ensure the recommended price leaves the customer a clear surplus. - Ground the reference price in a real alternative. </constraints> <format> Return the WTP analysis as a document with the value calculation and price recommendation (as an artifact), then note the one value driver to quantify precisely to defend the price. </format>
Produces a value-based willingness-to-pay analysis that derives a defensible price from customer value created as a ready-to-use pricing artifact.
Pro tip: Give Claude one hard number for the value you create (hours saved x wage, or extra revenue) and the whole price recommendation becomes defensible.
Packaging & Tier Design Report
24/30You are a monetization strategist who designs pricing tiers and packaging. <context> I need a packaging and tier design for my product, delivered as one structured research document with a recommended tier structure, what goes in each, and the logic. This is a finished artifact for a pricing review. </context> <inputs> - Product and its features: [OFFER AND FEATURE LIST] - Customer segments and their needs: [SEGMENTS] - The value metric I want to charge on: [E.G. SEATS, USAGE, OUTCOMES] - Business goal: [E.G. LAND SMB, PUSH UPGRADES, MOVE UPMARKET] </inputs> <task> Produce a packaging report with: a recommended set of 3-4 tiers with names, target segment, price anchor, and the value metric per tier; a feature-to-tier allocation table showing what is in each tier and which features are the deliberate 'fence' that drives upgrades; the free/trial strategy if relevant; add-ons versus core decisions; and the upgrade path logic explaining why a customer moves from one tier to the next. </task> <constraints> - Each tier must serve a distinct segment and give a clear reason to upgrade. - Choose value-metric fences deliberately; explain why each gated feature drives expansion. - Avoid too many tiers; justify the number chosen. </constraints> <format> Return the packaging design as a document with the tier and feature-allocation tables (as an artifact), then note which single feature placement most affects upgrade revenue. </format>
Delivers a tier and packaging design with feature allocation, upgrade fences, and pricing logic as a ready-to-use monetization artifact.
Pro tip: Tell Claude which feature is your biggest 'wow'; where it places that feature across tiers largely determines your upgrade rate.
Price-Change Impact & Elasticity Model
25/30You are a revenue analyst who models the impact of a price change before it ships. <context> I am considering a price change and need to model the revenue impact under different demand assumptions. Deliver one structured research document with a scenario model so I can decide with eyes open. </context> <inputs> - Current price and volume: [PRICE AND CUSTOMERS OR UNITS] - Proposed new price: [NEW PRICE OR RANGE] - Assumed price elasticity or churn reaction: [ESTIMATE, OR ASK ME] - Cost per unit / gross margin: [MARGIN CONTEXT] - Segment or plan affected: [SCOPE] </inputs> <task> Produce a price-change model with: a baseline revenue and margin snapshot; a scenario table showing revenue, volume, and gross profit under low/base/high demand-response assumptions for the new price; the break-even volume loss (how much churn the price rise can absorb before revenue falls); a note on segment-specific risks (who churns first); and a clear go / adjust / hold recommendation with the reasoning. </task> <constraints> - Show the elasticity math and the break-even calculation explicitly. - Present low/base/high scenarios, not a single optimistic number. - Call out which customer segment carries the most churn risk. </constraints> <format> Return the price-change model as a document with the scenario and break-even tables (as an artifact), then note the leading indicator to watch in the first 30 days after the change. </format>
Produces a price-change impact model with elasticity scenarios and a break-even churn threshold as a ready-to-use decision artifact.
Pro tip: Ask Claude for the break-even churn number first; knowing how many customers you can lose before revenue drops reframes the whole decision.
Most people use 10% of Claude. Tutorials unlock the rest.
AI Academy: 300+ hands-on tutorials on Claude, ChatGPT, Midjourney, and 50+ AI tools. New tutorials added every week.
Go-to-Market Research
5 promptsGo-to-Market Strategy One-Pager
26/30You are a go-to-market strategist who compresses a launch plan into a single decisive page. <context> I need a go-to-market strategy one-pager for my product or feature, delivered as one structured document that a leadership team can align on in one read. It should be a finished artifact, not an outline. </context> <inputs> - Product / feature: [WHAT IS LAUNCHING] - Target market and ICP: [WHO] - The core problem and our differentiated promise: [POSITIONING] - Primary GTM motion: [SELF-SERVE / SALES-LED / PLG / PARTNER] - Goal and timeframe: [E.G. 500 CUSTOMERS IN 6 MONTHS] </inputs> <task> Produce a GTM one-pager with: a one-sentence positioning statement; the target segment and ICP; the value proposition and top three differentiators; the primary GTM motion and why it fits; the priority channels; a pricing and packaging summary; the key metrics and targets; the biggest risks with mitigations; and a 90-day action list. Keep it tight and decision-ready. </task> <constraints> - Everything must fit a genuine one-pager; cut anything that is not decision-relevant. - Be specific: real channels, real numbers, real first actions. - The motion must match the price point and buyer, and you should say why. </constraints> <format> Return the GTM one-pager as a formatted document (as an artifact), then note the single assumption the whole plan depends on most. </format>
Generates a decision-ready go-to-market one-pager covering ICP, positioning, motion, channels, metrics, and a 90-day plan as a ready-to-use artifact.
Pro tip: Tell Claude your price point and buyer up front; it will flag if your chosen GTM motion (e.g. sales-led at a $20/mo price) simply cannot pay for itself.
Channel Strategy & Prioritization Matrix
27/30You are a demand-generation strategist who picks the right acquisition channels instead of spreading thin. <context> I need a channel strategy for reaching my target customer, delivered as one structured research document that scores and prioritizes channels so I know where to focus first. Deliver it as a reusable artifact. </context> <inputs> - Product and price point: [OFFER AND PRICING] - Target customer and where they spend attention: [ICP AND HABITS] - Budget and team capacity: [WHAT I CAN RESOURCE] - Sales cycle and deal size: [CONTEXT] - Channels already tried: [WHAT WORKED / DID NOT] </inputs> <task> Produce a channel report with: a table scoring 8-10 candidate channels (SEO, paid, content, outbound, partnerships, community, events, etc.) on audience fit, cost, time-to-results, scalability, and effort; a recommended primary channel and two supporting channels with reasoning; a rough CAC expectation and leading metric per prioritized channel; a 'do not bother yet' list with why; and a 90-day channel test plan. </task> <constraints> - Match channels to my price point and sales cycle; a long sales cycle rarely fits impulse channels. - Recommend focus, not a scattershot 'do everything'. - Be honest about channels that are wrong for this stage. </constraints> <format> Return the channel strategy as a document with the scoring matrix and 90-day test plan (as an artifact), then note the one channel to prove out before scaling spend. </format>
Delivers a scored channel prioritization matrix with a focused recommendation and a 90-day test plan as a ready-to-use GTM artifact.
Pro tip: Tell Claude your deal size and sales-cycle length; it uses them to rule out channels whose economics can't support your price point.
Beachhead Market Selection Doc
28/30You are a go-to-market strategist who helps founders pick a beachhead market to dominate before expanding. <context> I have several possible markets and need to choose one beachhead to win first. Deliver one structured research document that scores the candidates and recommends where to start, with the reasoning. </context> <inputs> - Product: [OFFER] - Candidate markets / segments: [2-5 OPTIONS] - What I want out of the first market: [E.G. FAST REVENUE, REFERENCES, LEARNING] - My unfair advantages: [WHERE I HAVE AN EDGE] </inputs> <task> Produce a beachhead-selection report with: a scoring table rating each candidate on urgency of need, ease of reach, competition, my right-to-win, willingness to pay, and expansion potential into adjacent markets; a recommended beachhead with a clear rationale; a definition of what 'dominating' this beachhead looks like (a concrete milestone); the adjacent markets it unlocks next; and the top risk of choosing it. </task> <constraints> - Score all candidates on the same criteria for a fair comparison. - Favor a small market I can dominate over a big one I would be invisible in; explain the trade-off. - Define a concrete 'we own this beachhead' milestone, not a vague goal. </constraints> <format> Return the beachhead selection as a document with the scoring table (as an artifact), then note the first proof point that would confirm the chosen market is right. </format>
Produces a scored beachhead market selection with a recommended starting segment and expansion path as a ready-to-use GTM strategy artifact.
Pro tip: Push Claude to favor a niche you can fully dominate; a small market you own beats a big one where you're a rounding error.
Messaging & Positioning Canvas
29/30You are a positioning strategist who turns market insight into a crisp messaging framework. <context> I need a messaging and positioning canvas for my product, delivered as one structured document that gives my team a single source of truth for how we talk about the product. Deliver it as a finished artifact. </context> <inputs> - Product: [OFFER] - Target customer and their alternative today: [ICP AND STATUS QUO] - The core value and proof: [OUTCOME AND EVIDENCE] - Competitors and how they position: [RIVALS] - Brand tone: [HOW WE SOUND] </inputs> <task> Produce a positioning canvas with: a positioning statement (for [ICP] who [need], [product] is the [category] that [key benefit], unlike [alternative]); the market category we choose to compete in and why; three differentiators each with a supporting proof point; the primary value proposition plus messaging pillars; a message-per-persona table if there are multiple buyers; the objections and our responses; and a set of approved headline and boilerplate copy the team can reuse. </task> <constraints> - Choose a category deliberately; positioning fails when the reference frame is unclear. - Every differentiator needs a proof point, not just a claim. - Keep messaging consistent across the canvas; no contradictory promises. </constraints> <format> Return the positioning canvas as a document with the statement, pillars, and per-persona table (as an artifact), then note which differentiator to lead with in the first thing a prospect sees. </format>
Delivers a messaging and positioning canvas with a positioning statement, differentiators, and reusable copy as a ready-to-use team artifact.
Pro tip: Feed Claude the exact category buyers already shop in; forcing a brand-new category name usually confuses more prospects than it wins.
Launch Plan & GTM Timeline
30/30You are a launch manager who turns a go-to-market strategy into a sequenced, owner-assigned plan. <context> I have a product to launch and need a structured launch plan with a phased timeline, delivered as one self-contained document my team can execute against. Deliver it as a finished artifact. </context> <inputs> - What is launching and target date: [PRODUCT AND DATE] - Audience and primary channels: [WHO AND WHERE] - Team and rough resources: [WHO IS INVOLVED] - Success metric for the launch: [E.G. SIGNUPS, REVENUE, PRESS] - Assets I already have: [WHAT EXISTS] </inputs> <task> Produce a launch plan with: three phases (pre-launch, launch, post-launch) with dates working back from the target; a task table per phase (task, owner placeholder, channel, due offset, dependency); the messaging and asset checklist per phase; the launch-day run-of-show; the success metrics with targets; and a risk-and-contingency section for the two most likely things to go wrong. </task> <constraints> - Sequence tasks with realistic lead times and dependencies; do not stack everything on launch day. - Assign an owner placeholder to every task so nothing is unowned. - Tie the plan to the stated success metric. </constraints> <format> Return the launch plan as a document with the phased task tables and run-of-show (as an artifact), then note the one pre-launch task that, if slipped, would force moving the date. </format>
Produces a phased launch plan with a sequenced task timeline, run-of-show, and contingencies as a ready-to-use go-to-market artifact.
Pro tip: Give Claude a hard launch date and it will work backward to flag which task must start first so the timeline is actually achievable.
Frequently Asked Questions
Prompts are the starting line. Tutorials are the finish.
A growing library of 300+ hands-on tutorials on ChatGPT, Claude, Midjourney, and 50+ AI tools. New tutorials added every week.
7-day free trial. Cancel anytime.