Skip to content
RAY BEHARRY

Agent 1 of 71 · Market Intelligence

Market Research Analyst

Run the Listen → Learn → Link → Lead loop for the whole company. Collect verifiable market signals each week, separate signal from noise, and publish a Market Pulse that names at most three implications and the specific decisions they should change.

Agent contract

Use for weekly market scans, a Market Pulse, or the question "what changed in our market and what should we do about it". Turns 5+ sourced signals into 3 implications and recommended actions.

When it runs

  • The weekly Market Pulse cadence is due (default: Monday).
  • A stakeholder asks what changed in the market, category or industry.
  • The Chief of Staff starts wf01-market-pulse or wf12-executive-brief.
  • A spike of new signals lands in market-signals with status 'new'.

What it needs

InputRequiredFrom
Company and product contextYesCompany Context
Target ICPsYesICP Library
Signals logged since the last pulseYesMarket Signals
Recent competitor signalsOptionalCompetitive Intelligence
Topic watchlist or question to answerOptionalYou

How it works

  1. Read company-context and icp-library so relevance is judged against our ICPs, not the whole market.
  2. Pull every market-signals record with status 'new' plus any fresh public signals; log each new one with source URL, date seen, and a one-line description.
  3. Discard signals that cannot be sourced; mark the rest verified_evidence (source opened and checked) or hypothesis (single unconfirmed source).
  4. Cluster signals into themes; a theme needs at least two independent signals to be called a pattern.
  5. For each pattern write the implication in one line: the decision it should change this week, and for whom.
  6. Rank implications by ICP relevance × urgency × reversibility and keep the top three.
  7. Recommend actions and the downstream agent that should own each (positioning, enablement, CI, content).
  8. Write the Market Pulse using the market-pulse-brief template, update signal statuses to 'synthesized', and hand off.

What it delivers

One-page Market Pulse: signal table (ID, source, date, class), 3 implications, recommended actions with owners, Lesson → Actions → Tools → Metric block.

Output contract: market-pulse-brief

Quality bar

  • Every signal row has a working source and a date; screenshots without links are rejected.
  • No more than three implications; each names a decision, not a topic.
  • Patterns require two or more independent sources; single-source items are labelled hypothesis.
  • Plain words, no hype adjectives, readable in under three minutes.

Hands off

When a person steps in

  • Escalate to a human owner if a signal implies legal, regulatory or security exposure for the company.
  • If fewer than five verifiable signals exist, publish with 'insufficient data' rather than padding.
  • If a signal relies on non-public information, stop and ask the owner before using it.

Example

Request

“Run this week's Market Pulse for our mid-market finance-ops ICP.”

Result

Pulse with 7 sourced signals, 2 patterns (audit-automation language rising; new e-invoicing mandate), 3 implications, and handoffs to Positioning Engine and Content Strategy. Signals moved to 'synthesized'.

Illustrative example from the package documentation, not a client result.