Industry News & Market Tracking

What to track

Signal categories

Source hierarchy

1. Company press releases — Official announcements (most reliable, most biased)
2. Tech news outlets — TechCrunch, The Verge, Ars Technica, VentureBeat, The Information
3. Industry publications — Specific to your vertical (e.g., SaaStr, Built In, Protocol)
4. Analyst firms — Gartner, Forrester, IDC, CB Insights (high quality, often paywalled)
5. Financial news — Bloomberg, Reuters, Crunchbase for funding and M&A
6. Developer news — Hacker News, dev.to, GitHub trending for technical signals
7. Social signals — Twitter/X from company leaders and industry analysts

Search strategies

For competitor news

• "[competitor name]" + announcement

  or

  "[competitor name]" + launch

• "[competitor name]" + funding

  or

  "[competitor name]" + acquisition

• "[competitor name]" + "we're excited"

  (press release language)
• Set time filters: last week, last month, last quarter

For market trends

• "[product category]" + trend + [current year]

• "[product category]" + market size

  or

  "[product category]" + growth

• "state of [product category]"

  for annual survey data

• "[product category]" + predictions

  for analyst perspectives

For technology shifts

• "[technology]" + "for [your domain]"

  (e.g., "AI for project management")
• Check Hacker News for technical community sentiment
• Search GitHub trending for open-source signals
• Monitor platform announcements (AWS, Google Cloud, Azure, OpenAI, Anthropic)

Analysis framework

Impact assessment

Trend identification

1. Collect — Gather 5-10 related data points
2. Timeline — Plot them chronologically to see velocity
3. Triangulate — Confirm from multiple independent sources
4. Contextualize — What's driving this trend? Is it accelerating or plateauing?
5. Project — If this continues, what happens in 6/12/18 months?

Strategic implications

• What changed? — Factual description of the news
• Why does it matter? — Impact on our customers, market, or competitive position
• What should we do? — Specific recommended action (or explicit "no action needed")
• By when? — Urgency and timeline for response

Output structure

1. Headline Summary — 3-5 bullet overview of the most important developments
2. Key Developments — Each item with:
   • What happened (factual, with source link)
   • Impact assessment (relevance, urgency, impact, confidence)
   • Strategic implication for your product
3. Trend Analysis — Patterns across multiple developments
4. Market Signals — Weaker signals that are worth watching but not yet confirmed
5. Recommended Actions — Prioritized list of responses
6. Sources — All links cited

Quality standards

• Separate fact from opinion — "Company X raised $50M" (fact) vs "This signals they'll compete in enterprise" (analysis)
• Date everything — News has a shelf life. Always include publication dates.
• Cite primary sources — Link to the original announcement, not a blog post about the announcement
• Note paywalled sources — If referencing analyst reports, note that the full report requires a subscription
• Provide context — "$20M funding round" means different things for a seed startup vs an established company

Anti-patterns

• Don't treat every competitor announcement as a crisis — most launches don't change the market
• Don't confuse announcement with adoption — launching a feature ≠ customers using it
• Don't over-index on hype cycles — the "AI for everything" announcements rarely match reality
• Don't ignore non-obvious competitors — adjacent products expanding into your space are often bigger threats
• Don't present news without the "so what" — PMs need implications, not a news ticker