# Market Industry Insights Briefing

> Turn broader market and industry signals — analyst reports, regulatory shifts, macro trends, adjacent-market moves, category-wide funding patterns — into a structured brief connecting external change to strategic implications, distinct from any single named competitor's actions. Use for a recurring cadence or ahead of planning cycles when leadership needs "what's happening in our market" synthesized rather than gathered raw.

- Skill: `saurabhships/market-industry-insights-briefing` (Agent Skill)
- Install (CLI): `npx skillmds@latest add saurabhships/market-industry-insights-briefing`
- Raw SKILL.md: https://api.skillmd.com/api/skills/saurabhships/market-industry-insights-briefing/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: saurabhships (https://skillmd.com/u/saurabhships)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/saurabhships/market-industry-insights-briefing

---


# Market & Industry Insights Briefing

## Why this exists

This is a different job from `competitive-intelligence-briefing`, not a broader version of it. That skill tracks named competitors; this one tracks the category and market as a whole — regulatory changes, macro-economic shifts affecting buyer budgets, analyst positioning of the space, industry-wide customer behavior shifts, and adjacent markets that could expand or threaten your category. Failure modes specific to this level of analysis:

1. **Conflating it with competitive intel** — "Competitor X raised a round" belongs in the other brief; it only belongs here if a *pattern* of funding across the category is itself the insight.
2. **News without implication** — same underlying problem as the competitive brief: a fact with no "so what for us" is not an insight.
3. **Recency bias** — treating one analyst's hot take or one data point as an established trend without checking for corroboration.

## Process

### 1. Define source categories deliberately

Analyst reports (Gartner, Forrester, category-specific analysts), regulatory/compliance news relevant to the industry, macro-economic indicators relevant to buyer budgets, industry conference and community discourse, adjacent-market moves (a category that could expand into or threaten yours), and broader customer/user behavior research beyond your own product's usage data.

### 2. Route competitor-specific findings elsewhere

If a finding is really about one named competitor's specific move, it belongs in the competitive brief. Keep this one at the category/market level — this boundary is what keeps the two briefs from duplicating each other.

### 3. Connect every finding to a strategic implication

Does this affect market sizing, buyer priorities, how the category gets defined, or long-term roadmap direction? State the answer explicitly. As with the competitive brief, "monitor only, no clear implication yet" is a legitimate answer — better than manufacturing a connection that isn't really there.

### 4. Check for trend vs. single data point

Before treating one analyst's claim or one data point as an established trend, look for at least one corroborating source. If you can't find one, label it "early signal, unconfirmed" rather than presenting it as settled.

### 5. Separate observation from interpretation

State plainly what was actually reported, distinct from your own read on what it implies — the same discipline as the confidence-tagging in `usage-trend-narration`. A reader should be able to tell which parts are fact and which are your judgment call.

### 6. Roll up at two altitudes

A light-touch weekly scan for anything time-sensitive, and a more thorough quarterly synthesis that ties multiple weeks together into an actual point of view for planning cycles. Weekly scanning without periodic synthesis just produces a pile of disconnected facts, never a real read on where the market is heading.

### 7. Output format

```
## Market & Industry Insights — Week of [date]
**This week's headline:** [...]

| Finding | Category | Source | Trend or single data point? | Strategic implication | Confidence |
|---|---|---|---|---|---|

**Watching (early/unconfirmed signals):** [...]
```

## Anti-patterns to avoid

- Don't duplicate the competitive brief — route named-competitor news there, even if it's tempting to include here too.
- Don't present one analyst's opinion as market consensus.
- Don't skip stating confidence — a claim about where the market is heading is a bigger commitment than a single week of evidence usually supports.
- Don't skip the quarterly rollup — it's the step that turns weekly scanning into an actual strategic point of view.

## Example (illustrative, placeholder industry)

```
## Market & Industry Insights — Week of 2026-08-24
**This week's headline:** Two independent analyst notes this month both flag "AI-assisted reporting" as a maturing must-have in this category, not a differentiator — a shift worth planning around.

| Finding | Category | Source | Trend or single data point? | Strategic implication | Confidence |
|---|---|---|---|---|---|
| Analyst report frames AI-assisted reporting as table stakes, not differentiator | Analyst positioning | Two independent analyst notes | Trend (corroborated) | Roadmap items pitched as "AI innovation" may land as "catching up" instead — reframe positioning | Medium |
| New data-residency regulation proposed in a key market | Regulatory | Government proposal, industry press | Single data point (proposal stage, not law) | Could require regional data hosting if passed; worth scoping cost now rather than after it passes | Low (early stage) |

**Watching (early/unconfirmed signals):** One industry newsletter claims a major adjacent-category player is exploring entry into this space; no corroborating source found yet.
```

Note the regulatory item is flagged with low confidence and framed as "worth scoping now" rather than an urgent alarm — proportionate to the fact that it's still a proposal, not a passed law.