How to Use ChatGPT for Market Research in 30 Minutes (With Prompts)
You need to research a new market for a product pitch next week. Traditional approach: spend 3-5 days browsing industry reports, analyzing competitors, reading analyst blogs, compiling data into slides.
You don't have 5 days. You have an afternoon.
ChatGPT can't replace deep, primary research (customer interviews, surveys, A/B tests). But it can compress the secondary research phase from days to 30 minutes by synthesizing its training data into structured market intelligence.
I've used ChatGPT to research markets for product launches, pitch decks, and strategic planning. The output quality shocks people: "You researched this in 30 minutes?"
This guide shows you exactly how to use ChatGPT for five types of market research: competitive analysis, customer personas, market sizing, trend analysis, and go-to-market strategy. With copy-paste prompts you can use immediately.
What ChatGPT Can and Can't Do for Market Research
What ChatGPT Excels At
✅ Synthesizing existing knowledge
- Summarizing industry trends from its training data
- Explaining market dynamics and business models
- Identifying common competitive positioning strategies
✅ Framework application
- Applying Porter's Five Forces to your market
- Creating SWOT analyses
- Building customer persona templates
✅ Brainstorming and ideation
- Generating market segmentation ideas
- Suggesting positioning strategies
- Identifying potential risks and opportunities
✅ Structured formatting
- Creating comparison tables
- Organizing insights into frameworks
- Generating presentation-ready content
What ChatGPT Can't Do
❌ Access real-time data
- ChatGPT's training data has a cutoff (varies by model, currently ~mid-2024 for GPT-4)
- Can't browse live websites or APIs (unless using plugins)
- Can't verify if companies still exist or have pivoted
❌ Provide proprietary data
- No access to paid market research reports (Gartner, Forrester, etc.)
- Can't query private databases or financial systems
- No real-time stock prices, revenue figures, or funding data
❌ Replace primary research
- Can't interview your actual customers
- Can't run surveys or collect quantitative data
- Can't validate hypotheses with real-world tests
The strategy: Use ChatGPT for fast secondary research and hypothesis generation. Validate critical assumptions with real data before making decisions.
Research Type 1: Competitive Analysis
The Prompt
Prompt
I need a comprehensive competitive analysis for [YOUR PRODUCT/COMPANY] in the [MARKET/INDUSTRY] space. Product description: [Brief description of what you're building] Target customer: [Who you're serving] Please provide: 1. **Direct Competitors** (5-7 companies) - Company name - Product offering - Target customer - Key differentiators - Pricing model - Strengths and weaknesses 2. **Indirect Competitors** (3-5 alternatives) - What customers use instead of dedicated solutions - Why these alternatives exist 3. **Competitive Positioning Matrix** - Create a 2x2 matrix with relevant axes for this market - Place each competitor on the matrix - Identify white space opportunities 4. **Market Leaders Analysis** - Who are the top 3 market leaders? - What makes them successful? - What are their vulnerabilities? 5. **Competitive Moats** - What defensive moats do incumbents have? - Which are hardest to overcome? - Which are weakening? Format as structured markdown with tables where appropriate.
Example: SaaS Project Management Tool
Prompt:
Prompt
I need a comprehensive competitive analysis for a new project management tool in the SaaS space. Product description: AI-powered project management tool that automatically creates tasks, assigns them to team members based on skills and availability, and predicts project risks. Target customer: 10-50 person product teams at B2B SaaS companies Please provide [... rest of prompt above ...]
ChatGPT Output (excerpt):
markdown
1## Direct Competitors23| Company | Product | Target Customer | Key Differentiator | Pricing | Strengths | Weaknesses |4|---------|---------|-----------------|-------------------|---------|-----------|------------|5| Asana | Task/project management | 10-500+ teams | Workflow automation, multiple views | $10.99/user/mo | Strong adoption, integrations | Complex for small teams |6| Monday.com | Work OS platform | 10-200+ teams | Customizable workflows, visual | $8/user/mo | Flexible, beautiful UI | Expensive at scale |7| Linear | Issue tracking | Product/eng teams | Speed, keyboard shortcuts | $8/user/mo | Developer-loved UX | Limited PM features |8| ClickUp | All-in-one PM | 5-100+ teams | Feature breadth | $5/user/mo | Lots of features | Feature bloat, slow |9| Jira | Issue/project tracking | 10-1000+ eng teams | Deep customization, reporting | $7.75/user/mo | Enterprise features | Steep learning curve |1011## Indirect Competitors12131. **Spreadsheets (Google Sheets, Excel)**14 - Why: Free, familiar, flexible15 - When chosen: Very small teams (<5), simple projects, budget constraints16 - Weakness: Manual updates, no automation, breaks at scale17182. **Notion**19 - Why: All-in-one workspace, custom databases20 - When chosen: Teams wanting docs + tasks in one place21 - Weakness: Not built for PM workflows, missing Gantt charts, reporting22233. **Slack/Teams + plugins**24 - Why: Work where communication happens25 - When chosen: Very small teams, lightweight needs26 - Weakness: Poor task organization, no progress tracking2728## Competitive Positioning Matrix2930**Axes: Simplicity (X) vs. Power (Y)**
Power
↑
│ Jira ▲
│ ClickUp ▲
│ Monday ▲
│
│ YOUR PRODUCT ☆
│ (AI-powered, balanced)
│
│ Asana ▲ Linear ▲
│
│ Trello ▲ Notion ▲
│
└──────────────────────────────→ Simplicity
Prompt
**White Space Opportunity**: Mid-market teams (10-50 people) want power-user features (Jira-level capabilities) without Jira's complexity. Linear proved there's demand for simple-yet-powerful tools, but focuses only on eng teams. Your AI-powered approach targeting product teams fills this gap. ## Market Leaders Analysis ### 1. Asana **Success factors:** - Early mover advantage (2008 launch) - Strong product-led growth motion - Excellent integrations ecosystem (200+ apps) - Trusted by Fortune 500 companies **Vulnerabilities:** - Complexity creep - added so many features it's overwhelming for small teams - Pricing pressure - competitors offer more features for less - Slow to adopt AI - reactive vs. proactive project management - Enterprise focus - neglecting SMB segment ### 2. Monday.com **Success factors:** - Visual, beautiful, intuitive UI - Marketing excellence - aggressive paid acquisition - Flexible "work OS" positioning allows expansion beyond PM - Strong customer success org reducing churn **Vulnerabilities:** - Expensive at scale (pricing increases rapidly with seats) - Feature bloat - trying to be everything to everyone - Notification overload - users report alert fatigue - Limited depth in specific verticals [...] ## Competitive Moats **Network Effects** (Weak) - PM tools have weak network effects - teams can switch tools easily - Integrations create some stickiness but APIs are standardized - **Opportunity**: Incumbents don't have strong moats here **Data Lock-in** (Medium) - Years of project history creates switching friction - Custom workflows and automations hard to recreate - **Challenge**: Need excellent import tools to overcome **Brand & Market Share** (Strong) - Asana, Monday, Jira are household names in their segments - Sales cycles shorter for known brands - **Challenge**: Requires differentiated positioning to break through **Team Skill & Habits** (Medium) - Teams trained on existing tools resist change - Muscle memory with keyboard shortcuts, workflows - **Opportunity**: AI can reduce learning curve dramatically
How to Use This Analysis
- Identify positioning: You're targeting the "simple but powerful" quadrant
- Focus messaging: Emphasize AI-powered automation that Asana/Monday lack
- Pricing strategy: Position between ClickUp ($5) and Asana ($11), maybe $7-8
- Feature priorities: Nail core PM workflows first (don't fall into feature bloat trap)
- Go-to-market: Target teams frustrated with Asana's complexity or Monday's cost
Research Type 2: Customer Personas
The Prompt
Prompt
Create 3 detailed customer personas for [YOUR PRODUCT]. For each persona, provide: 1. **Basic Profile** - Name and job title - Age range and background - Company size and industry - Reporting structure 2. **Goals and Motivations** - Primary job goals (what they're measured on) - Personal motivations (career growth, efficiency, etc.) - Success metrics they care about 3. **Pain Points and Challenges** - Day-to-day frustrations - Tools that aren't working - Process bottlenecks - Political or organizational obstacles 4. **Current Solutions** - What they use today (tools and workarounds) - What they like about current solutions - What they're missing 5. **Buying Process** - Are they the decision maker or influencer? - Who else is involved in purchase? - Typical evaluation criteria - Budget authority 6. **Content Preferences** - Preferred content types (blog, video, webinar, etc.) - Where they hang out online - Trusted information sources - Buying triggers Use realistic, specific details. Avoid generic descriptions.
Example Output (excerpt)
markdown
1## Persona 1: "Overwhelmed Owen" - Product Manager23**Basic Profile**4- Owen Chen, 32, Senior Product Manager5- 5-7 years PM experience, previously in consulting6- Works at 80-person B2B SaaS company (Series B funded)7- Reports to VP Product, manages 2 PMs and works with 12 engineers89**Goals and Motivations**10- Ship product roadmap on time (measured on delivery velocity)11- Increase feature adoption rates (current: 40%, target: 60%)12- Build a career path to VP Product in 2-3 years13- Wants to be seen as organized, strategic, data-driven leader1415**Pain Points**16- Juggling 3-4 concurrent projects, constantly context-switching17- Spends 2 hours daily in status update meetings instead of strategy18- Uses 5 different tools (Jira for eng, Asana for PM team, Notion for docs, Sheets for roadmap, Slack for everything)19- Can't quickly answer "What's the status?" without manually checking multiple places20- Engineering team hates current process - too much overhead21- Misses early warning signs of at-risk projects until too late2223**Current Solutions**24- Jira for engineering tasks (required by eng team)25- Asana for PM team coordination (personal preference)26- Weekly status email updates (manual, tedious, often ignored)27- Spreadsheet to track overall roadmap28- **What works:** Jira's deep issue tracking, Asana's collaboration29- **What's missing:** Unified view, automation, predictive insights3031**Buying Process**32- Influencer, not final decision maker (VP Product approves)33- Needs buy-in from Engineering Manager (must not disrupt eng workflow)34- Evaluates: Does it save time? Does eng team like it? Easy to adopt?35- Budget authority: Can approve $500/month, needs approval for $1,000+36- Typical evaluation: 2-week trial with PM team, then broader pilot if successful3738**Content Preferences**39- Reads: Product Hunt, Hacker News, Lenny's Newsletter40- Watches: YouTube tutorials (wants 5-minute quick starts, not 1-hour courses)41- Attends: Local PM meetups, occasional webinars from trusted brands42- Buying trigger: Sees peer company using it successfully + testimonial43- Hates: Sales calls without context, generic outbound emails4445**How to Market to Owen:**46- Show time savings with specific examples: "Eliminate 10 hours of status updates per month"47- Emphasize engineering team satisfaction: "Developers rated usability 4.8/5"48- Offer 30-day trial with hands-on onboarding (Owen is busy, needs help getting started)49- Case studies from similar-sized SaaS companies50- Content format: 5-minute demo videos, not 30-slide decks
This level of detail helps you:
- Write marketing copy that resonates
- Design onboarding for Owen's specific needs
- Prioritize features that solve his pain points
- Choose marketing channels where Owen hangs out
Research Type 3: Market Sizing (TAM/SAM/SOM)
The Prompt
Prompt
Help me estimate the Total Addressable Market (TAM), Serviceable Addressable Market (SAM), and Serviceable Obtainable Market (SOM) for [YOUR PRODUCT]. Product: [Description] Target customer: [Customer description] Geography: [Markets you're targeting] Pricing: [Your pricing model] Please: 1. **TAM (Total Addressable Market)** - How many potential customers exist globally? - What's the total revenue opportunity if you captured 100% of the market? - Show your calculation methodology 2. **SAM (Serviceable Addressable Market)** - How many of those TAM customers fit your specific target profile? - What realistic revenue could you address? - Show how you narrowed from TAM 3. **SOM (Serviceable Obtainable Market)** - What market share is realistically achievable in 3 years? - What revenue does that represent? - What assumptions are you making? 4. **Market Growth** - Is this market growing or shrinking? - What's the estimated CAGR (Compound Annual Growth Rate)? - What trends are driving growth/decline? 5. **Key Assumptions** - List critical assumptions used in these estimates - Which assumptions have highest uncertainty? - How would estimates change if assumptions are off by 50%? Use bottom-up and top-down approaches where possible.
Example Output (excerpt)
markdown
1## TAM (Total Addressable Market)23### Approach 1: Bottom-Up Calculation45**Target customer:** Product teams (10-50 people) at B2B SaaS companies6**Pricing:** $10/user/month × 30 users avg = $300/month per company = $3,600/year78**Step 1: How many B2B SaaS companies exist globally?**9- US B2B SaaS companies: ~25,000 (estimate from industry reports)10- Europe B2B SaaS: ~15,00011- Asia-Pacific SaaS: ~10,00012- Rest of world: ~5,00013- **Total: ~55,000 B2B SaaS companies globally**1415**Step 2: What % have product teams of 10-50 people?**16- <10 people: 40% of companies (too small)17- 10-50 people: 30% (TARGET)18- 50-200 people: 20% (too large for initial focus)19- 200+ people: 10% (enterprise, different needs)20- **Target segment: 55,000 × 30% = 16,500 companies**2122**TAM Calculation:**2316,500 companies × $3,600/year = **$59.4M annual TAM**2425### Approach 2: Top-Down Calculation2627Global project management software market: $6.5B (2024)28- B2B SaaS-focused PM tools: ~15% of total market = $975M29- Teams of 10-50 people: ~25% of B2B segment = $244M30- **TAM: ~$244M**3132**Reconciliation:** Bottom-up ($59M) significantly lower than top-down ($244M). Likely because:33- Bottom-up assumes $10/user pricing (conservative)34- Top-down includes all competitors, some priced higher ($15-20/user)35- Using blended average: **TAM = ~$150M**3637## SAM (Serviceable Addressable Market)3839**Narrowing TAM to realistic addressable market:**4041**Geography Filter:**42- Initially targeting US + Canada only43- 25,000 / 55,000 = 45% of global market44- **$150M × 45% = $67.5M**4546**Product-Market Fit Filter:**47- Not all product teams need AI-powered PM tool48- Best fit: teams struggling with complexity, want automation49- Estimate 40% fit this profile50- **$67.5M × 40% = $27M**5152**Competition Filter:**53- Some companies locked into enterprise contracts (Jira, Monday)54- Some happy with free/cheap tools (Trello, Notion)55- Realistic addressable: 60% open to switching56- **$27M × 60% = $16.2M**5758**SAM: ~$16M** in North America for teams actively seeking better PM solutions5960## SOM (Serviceable Obtainable Market)6162**3-Year Market Share Assumptions:**6364**Year 1:** 0.5% market share (getting initial traction)65- $16M × 0.5% = **$80,000**66- ~22 customers at $3,600/year67- Assumes: Product-market fit achieved, early adopters6869**Year 2:** 2% market share (scaling up)70- $16M × 2% = **$320,000**71- ~89 customers72- Assumes: Word-of-mouth growth, first 100 customers happy7374**Year 3:** 5% market share (established player)75- $16M × 5% = **$800,000**76- ~222 customers77- Assumes: Strong brand in niche, high NPS (>40), Series A funding for sales/marketing7879**SOM Year 3: $800K** (realistic without massive funding)8081With Series A funding ($5M+) and aggressive growth:82- Could target 10-15% market share83- SOM: $1.6M - $2.4M8485## Market Growth8687**Project Management Software Market Growth:**88- Historical CAGR (2019-2024): 10.1%89- Projected CAGR (2024-2029): 11.3%9091**Growth Drivers:**921. Remote/hybrid work increasing need for async collaboration (+)932. AI integration creating new capabilities (+)943. SMB digital transformation accelerating (+)954. Market maturing, consolidation pressure (-)9697**Estimated market growth for your segment: 12-15% CAGR**98- Faster than overall market due to SMB SaaS boom99- AI differentiation capturing share from traditional PM tools100101## Key Assumptions & Sensitivity102103**Critical Assumptions:**1041051. **Number of target companies (16,500)**106 - Source: Industry estimates, not hard data107 - If off by 50%: TAM ranges $75M - $225M108 - **Confidence: Medium (60%)**1091102. **Pricing ($10/user/month)**111 - Competitive range: $5-15/user112 - If you price at $15: TAM increases 50%113 - If you price at $5: TAM decreases 50%114 - **Confidence: High (85%)** - validated by competitor pricing1151163. **Market share achievability (5% in Year 3)**117 - Based on similar SaaS startup benchmarks118 - Requires strong product-market fit + funding119 - Without funding: more like 2-3%120 - **Confidence: Medium (65%)**1211224. **% of market open to switching (60%)**123 - Assumption based on churn rates in PM software (20-30%)124 - If only 30% open to switching: SAM halves125 - **Confidence: Low (50%)** - needs validation with surveys126127**Sensitivity Analysis:**128129| Scenario | TAM | SAM | Year 3 SOM |130|----------|-----|-----|------------|131| Conservative (all assumptions -30%) | $105M | $11M | $560K |132| Base Case | $150M | $16M | $800K |133| Optimistic (all assumptions +30%) | $195M | $21M | $1.05M |134135**Recommendation:** Use base case ($150M TAM, $16M SAM, $800K Year 3 SOM) for pitch materials, but validate key assumptions through customer discovery interviews before finalizing strategy.
Research Type 4: Trend Analysis
The Prompt
Prompt
Analyze current trends in [YOUR INDUSTRY/MARKET] that could impact [YOUR PRODUCT]. Please provide: 1. **Major Trends (5-7)** - Description of the trend - Why it's happening (underlying drivers) - Current state vs. future state - Timeline (is this happening now, or 3-5 years out?) 2. **Impact Assessment** - How does each trend affect your product positively or negatively? - Which trends are opportunities to leverage? - Which are threats to mitigate? 3. **Strategic Implications** - What should you do in response to each trend? - Which trends to bet on heavily? - Which to monitor but not act on yet? 4. **Trend Maturity** - Which trends are overhyped (Gartner "peak of inflated expectations")? - Which are proven and safe to build on? - Which are emerging and high-risk but high-reward? Include sources or reasoning for each trend's validity.
Example Output (excerpt)
markdown
1## Major Trends in Project Management Software (2026)23### 1. AI-Native Workflows45**Description:** PM tools embedding AI throughout the user experience, not as an add-on feature.6- Auto-generating tasks from meeting transcripts7- Predicting project risks before they materialize8- Suggesting optimal resource allocation based on historical data910**Why it's happening:**11- LLMs (GPT-4, Claude) now reliable enough for production use12- Users expect AI capabilities in all software13- Competitive pressure - everyone adding AI features1415**Current vs. Future:**16- Current (2026): Basic AI features (smart suggestions, auto-categorization)17- Future (2028): AI as primary interface (voice commands, predictive project management)1819**Timeline:** Happening NOW, accelerating rapidly2021**Impact on Your Product:**22- ✅ **Opportunity:** Your AI-powered approach is perfectly timed23- ⚠️ **Risk:** Incumbents (Asana, Monday) are adding AI features - must move fast24- **Strategic Implication:** Make AI core to product identity, not a feature checkbox2526### 2. Consolidation of Work Tools2728**Description:** Backlash against "tool sprawl" - companies using 10+ disconnected SaaS tools.29- Trend toward all-in-one platforms (Notion, ClickUp's "replace all your tools" positioning)30- Buyers prefer integrated suites over best-of-breed point solutions3132**Why it's happening:**33- Tool fatigue - context switching kills productivity34- Budget pressure - CFOs pushing for consolidation35- Better platform APIs make integration easier3637**Current vs. Future:**38- Current: Teams use 8-12 tools on average39- Future: 3-5 core platforms + specialized tools4041**Timeline:** Happening now, will intensify over next 2 years4243**Impact on Your Product:**44- ⚠️ **Threat:** Standalone PM tool might lose to all-in-one platforms45- ✅ **Opportunity:** Position as "best-of-breed PM that integrates seamlessly"46- **Strategic Implication:** Build deep integrations with Slack, Notion, Google Workspace - don't try to replace them4748### 3. Async-First Work Culture4950**Description:** Shift from synchronous (meetings, real-time chat) to asynchronous (recorded videos, documents, threaded discussions) as default.51- 4-day work weeks and distributed teams normalizing different schedules52- "Maker time" protected from meeting interruptions53- Documentation-first culture5455**Why it's happening:**56- Zoom fatigue from pandemic57- Global teams across time zones58- Research showing deep work requires uninterrupted time5960**Current vs. Future:**61- Current: Async communication exists but meetings still dominant62- Future: Meetings are exception, async is default6364**Timeline:** Early adoption phase now, mainstream in 3-4 years6566**Impact on Your Product:**67- ✅ **Opportunity:** PM tools that support async workflows (video updates, detailed context in tasks) win68- ⚠️ **Risk:** Real-time features (live collaboration, synchronous chat) become less important69- **Strategic Implication:** Build for async-first: rich task descriptions, video embeds, threaded discussions, notification controls7071### 4. No-Code/Low-Code Customization Demands7273**Description:** Users expect to customize software themselves without involving developers.74- Workflow builders75- Custom fields and views76- Automation rules without code7778**Why it's happening:**79- Users are more tech-savvy (grown up with smartphones)80- One-size-fits-all products don't work for diverse team needs81- Companies can't afford custom dev for every tool8283**Current vs. Future:**84- Current: Advanced tools (Airtable, Notion) offer no-code; traditional PM tools don't85- Future: No-code customization is table stakes8687**Timeline:** Mainstream already, becoming mandatory8889**Impact on Your Product:**90- ✅ **Must-have:** Need workflow customization, not just rigid templates91- ⚠️ **Balance:** Too much flexibility creates complexity (see ClickUp's feature bloat)92- **Strategic Implication:** Start with opinionated workflows, add customization layer in Year 29394[... additional trends ...]9596## Trend Maturity Matrix9798| Trend | Maturity | Hype Level | Action |99|-------|----------|-----------|--------|100| AI-Native Workflows | Early | High | **Bet heavily** - Core differentiator |101| Consolidation | Mainstream | Medium | **Address** - Deep integrations required |102| Async-First | Emerging | Medium | **Build for** - Design with async in mind |103| No-Code | Mainstream | Low | **Plan for** - Add in Year 2 |104| Real-Time Collaboration | Mature | Low | **Table stakes** - Include basics only |105106**Strategic Priorities:**1071081. **Double down on AI** - It's the wave, and you're positioned to ride it1092. **Integrate deeply** - Can't fight consolidation, must integrate with popular platforms1103. **Design for async** - Emerging but certain trend, build this in from day 11114. **Delay no-code** - Important but not critical for MVP, add post-PMF
Research Type 5: Go-To-Market Strategy
The Prompt
Prompt
Help me develop a go-to-market (GTM) strategy for [YOUR PRODUCT]. Product: [Description] Target customer: [Customer description] Competitive positioning: [Your unique value prop] Please provide: 1. **Channel Strategy** - Which acquisition channels fit this product and customer? - Rank by priority (1-10) and explain reasoning - What budget allocation would you recommend? 2. **Messaging Framework** - Core value proposition (1 sentence) - Key messaging pillars (3-4 main themes) - Proof points for each pillar - Competitive differentiation 3. **Launch Sequence** - Month-by-month plan for first 6 months - What to focus on each month - Success metrics to track 4. **Pricing Strategy** - Recommended pricing tier structure - Positioning relative to competitors - Freemium vs. paid-only recommendation 5. **Early Traction Tactics** - How to get first 10 customers - How to get to 100 customers - What changes between 10 and 100 Be specific and tactical, not generic advice.
Example Output (excerpt)
Channel Strategy
| Channel | Priority (1-10) | Reasoning | Budget % |
|---|---|---|---|
| Product-Led Growth (Free Trial) | 10 | PM tools thrive on PLG - users can sign up and test immediately | 5% (infra only) |
| Content Marketing (SEO Blog) | 9 | PMs actively search for PM best practices, tool comparisons | 25% |
| Community Building (Slack, Forum) | 8 | PM community is active online, word-of-mouth drives adoption | 10% |
| Product Hunt Launch | 8 | PM/tech audience lives on PH, credibility signal | 5% |
| LinkedIn Organic (Founder personal brand) | 7 | B2B buyers research vendors on LinkedIn, trust thought leaders | 10% (time investment) |
| Paid Search (Google Ads) | 6 | High intent keywords ("best project management software") but competitive | 20% |
| Integration Marketplaces | 6 | Slack App Directory, Jira Marketplace - reach existing users | 5% |
| Cold Outbound (Email/LinkedIn) | 4 | Low conversion for PM tools, better for enterprise sales | 5% |
| Paid Social (LinkedIn Ads) | 3 | Expensive CPMs, lower intent than search | 10% |
| Conferences/Events | 2 | High cost, slow ROI, better for later-stage companies | 5% |
Recommended Focus (First 6 Months):
- Months 1-2: PLG infrastructure + Content Marketing foundation
- Months 3-4: Product Hunt launch + Community building
- Months 5-6: LinkedIn personal brand + Paid search experiments
Messaging Framework
Core Value Proposition:
"AI-powered project management that eliminates busywork, so product teams ship faster without the chaos."
Key Messaging Pillars:
Pillar 1: "No More Status Updates"
- Proof: AI automatically summarizes project status from task activity
- Saves: 10 hours per week in status meetings and update emails
- Differentiation: Competitors still require manual status reports
Pillar 2: "Predictive, Not Reactive"
- Proof: AI flags at-risk projects 2 weeks before deadline issues surface
- Result: Ship 23% more projects on time (customer data)
- Differentiation: Traditional PM tools show you what happened, not what will happen
Pillar 3: "Loved by Engineers"
- Proof: Integrates with Jira, doesn't replace dev tools engineers love
- Result: 4.8/5 developer satisfaction in beta (vs 3.1/5 for typical PM tools)
- Differentiation: Built for eng+PM collaboration, not PM-dictated processes
Pillar 4: "Simple Enough to Adopt in a Week"
- Proof: Average onboarding: 3 days (vs 4-6 weeks for Jira)
- Result: No consultants needed, no 6-month implementations
- Differentiation: Power of Jira/Monday without the complexity
[... continues with Launch Sequence, Pricing Strategy, etc. ...]
Prompt
## Combining Multiple Research Types The real power comes from using multiple research types together. **Example workflow for a new product:** 1. **Start with Competitive Analysis** → Understand the landscape 2. **Then Customer Personas** → Know who you're targeting 3. **Then Market Sizing** → Validate there's a real opportunity 4. **Then Trend Analysis** → Ensure you're building for the future 5. **Finally GTM Strategy** → Plan how to reach customers Each research type informs the next. Competitive analysis reveals positioning opportunities. Customer personas inform messaging. Market sizing validates effort. Trends shape product roadmap. GTM strategy pulls it together. ## Validating ChatGPT Research ChatGPT provides great hypotheses. Validate them before betting your company: **Validation methods:** **For Competitive Analysis:** - Visit competitor websites, check actual pricing - Sign up for free trials, test products yourself - Search Twitter/Reddit for real user complaints - Check G2/Capterra reviews for patterns **For Customer Personas:** - Conduct 10-15 customer interviews - Run surveys with target segment - Join online communities, observe conversations - Test messaging with A/B tests **For Market Sizing:** - Cross-reference with industry reports (if accessible) - Talk to industry analysts or consultants - Survey potential customers on willingness to pay - Start with bottom-up (small pilot) before assuming top-down TAM **For Trends:** - Check Google Trends for search volume data - Review Gartner Hype Cycle reports - Monitor VC investment in the space - Join industry conferences, observe discussion topics **For GTM:** - Test one channel at a time with small budget - Measure actual CAC (Customer Acquisition Cost) vs. assumptions - Iterate based on real conversion data - Don't commit to strategy until you've validated channel-market fit ## Conclusion ChatGPT compresses secondary market research from days to 30 minutes. It won't replace deep primary research, but it gives you a solid foundation fast. **The research workflow:** 1. Use ChatGPT to generate hypotheses and structured research 2. Validate critical assumptions with real data 3. Use insights to guide product and marketing decisions 4. Iterate based on market feedback **Key prompts to save:** - Competitive analysis - Customer personas - Market sizing (TAM/SAM/SOM) - Trend analysis - Go-to-market strategy Start with one research type today. Pick the most urgent question you need answered. Adapt the prompts in this guide. See what you learn in 30 minutes. You'll be shocked how much ground you can cover with the right prompts and a structured approach. ## Frequently Asked Questions **How current is ChatGPT's market data?** ChatGPT-4's training data cutoff is around mid-2024. For company-specific info (funding rounds, product launches, pricing), verify with live searches or company websites. ChatGPT is excellent for industry trends and competitive dynamics that change slowly, less reliable for news or recent events. Always note the knowledge cutoff date when presenting research. **Can I trust ChatGPT's market sizing numbers?** Use ChatGPT's sizing as a starting point, not final answer. The methodology is sound (bottom-up × top-down validation), but specific numbers may be estimates. Cross-reference critical figures with industry reports or analyst data. For investor pitches, always footnote sources and validate key assumptions independently. ChatGPT helps structure thinking, not replace real data. **What if ChatGPT gives outdated competitor information?** Always verify competitor details (pricing, features, positioning) on their current websites. ChatGPT may reference companies that pivoted or shut down. Use ChatGPT for competitive framework and analysis structure, then fill in actual current data yourself. The thought process is valuable even if specific details are stale. **Should I cite ChatGPT in research reports or presentations?** No. Treat ChatGPT as a research assistant, not a source. Verify claims and cite original sources: "According to industry reports..." not "According to ChatGPT...". Use ChatGPT to accelerate research and structure thinking, but always validate and attribute to proper sources. Think of it like using Google—you cite sources you find, not Google itself. **How do I get ChatGPT to give less generic, more specific answers?** Provide more context in your prompts: specific product details, target customer attributes, pricing models, and competitive positioning. Ask for examples: "Show 3 specific examples" rather than "Explain the concept". Request structured formats: tables, bullet points, numbered lists. Use follow-up prompts: "This is too generic, give me specific tactics for B2B SaaS with $10/user pricing targeting 50-person teams." --- *Related articles: [AI Data Analysis with ChatGPT and Spreadsheets](/posts/ai-data-analysis-chatgpt-spreadsheets), [Claude AI Workplace Automation Guide](/posts/claude-ai-workplace-automation-guide)*
Sponsored Content
Interested in advertising? Reach automation professionals through our platform.