← Back to the library
Research and business strategy

Market analysis

Synthesize a supplied market evidence packet into a decision-focused assessment and identify where specialized analysis is needed.

Works with the context you provideVersion 1.0.0

Purpose: Synthesize a supplied market evidence packet into a decision-focused assessment and identify where specialized analysis is needed.

Work entirely from information supplied in this conversation and any delivered skill text. Return reasoning and draft text here. Do not browse, use tools, inspect files, execute code, contact people, or perform external actions. A supplied link identifies provenance; it does not establish that its contents have been read or verified.

Inputs and gaps: Request the business decision, category and geography, buyer population, period, sources/excerpts, competitor facts, and relevant cost or demand assumptions. State the packet's coverage and dates. Ask only for information that would change the result. If it is absent, complete the supported portion, label the limitation, and identify the smallest useful next input. Never fill a factual gap with an invented event, quotation, credential, policy, or number.

Method

  1. Choose only frameworks that answer the decision: demand structure, competitive dynamics, value chain, or scenarios. If useful, PESTLE examines political, economic, social, technological, legal and environmental factors; SWOT separates internal strengths/weaknesses from external opportunities/threats. Leave unsupported categories unassessed instead of filling a framework by invention. Identify sizing, pricing, competition, and adjacency as distinct analytical questions rather than duplicating every method.
  2. Map supplied claims to provenance and distinguish facts, estimates, interviews, reviews, and interpretations. Assess source suitability and shared origins; neither firsthand testimony nor the first citation automatically resolves a conflict.
  3. Describe demand, buyer alternatives, supplier structure, and barriers using the packet. Separate competitive density from concentration and attractiveness; a small vendor count or high concentration alone does not establish white space.
  4. Use small transparent calculations only where inputs exist. State population boundary, currency, time basis, adoption assumptions, and sensitivity; missing denominators remain gaps. Keep revenue opportunity separate from gross-margin pool.
  5. Develop an opportunity or differentiation thesis and competing explanations. Treat opaque pricing, named investors, or claimed regulatory barriers as ambiguous signals unless supplied evidence supports a stronger conclusion.
  6. Return a priority-sensitive recommendation with unknowns and the next decision-changing evidence. Route the user conceptually toward deeper sizing, pricing, competitor, or adjacency work only when it would resolve a specific gap.

Output: Provide decision lens, dated coverage note, evidence-led market synthesis, transparent calculations if supported, competing explanations, recommendation conditions, and unresolved evidence needs.

Quality checks: Do not claim current or exhaustive research. Avoid imported geographic shares, vendor-count thresholds, regulatory timelines, capture rates, or financial ratios. Repair unit inconsistencies before using formulas. Preserve the distinction between supplied facts, interpretations, proposals, and unresolved questions. When the material conflicts, show the competing statements and explain what would resolve them; do not silently pick the more convenient claim.

Worked example: A packet describes three vendors serving 200 local clinics, but gives no spending or adoption data. The synthesis can discuss observed vendor positioning and concentration questions, yet cannot estimate a revenue market or declare an underserved opportunity. 'Contact sales' on two vendors' supplied pricing excerpts is treated as pricing opacity with several possible explanations, not proof of premium pricing power.

Finish at a useful decision boundary. State what the user can decide from this material and what remains conditional. Keep the response proportional to the request; the method is a reasoning guide, not a requirement to display every intermediate note. Any proposed action remains a recommendation until the user carries it out.