How to Analyze Market Strategy

Market strategy analysis is the process of applying a chosen framework to a specific business question, then showing the data, assumptions, and reasoning behind the answer. It might size a market with TAM/SAM/SOM, assess industry attractiveness with Porter's Five Forces, or scan macro risk with PESTLE.

The useful output is not a polished strategy slide. It is a decision aid that says what market is being analyzed, which constraints matter, where the numbers came from, how confident the assumptions are, and what the result means for a real decision.

Why market analysis quietly misleads teams

Market analysis often fails by looking more certain than it is. A TAM number appears without a source, SOM is treated like a percentage of ambition instead of go-to-market capacity, or a PESTLE scan lists obvious macro factors without ranking what actually matters.

The bundle's method treats unsupported numbers as defects. Market sizing uses top-down and bottom-up estimates, then reconciles them. Porter ratings name the drivers and strategic implication for each force. PESTLE factors are prioritized by impact and probability, then turned into responses or leading indicators.

What the manual process looks like

Done by hand, a credible market strategy analysis follows a strict path:

1. Write the business context, market boundaries, customer segment, geography, competitors, and decision the analysis must inform.
2. Choose one framework for the job: TAM/SAM/SOM, Porter's Five Forces, or PESTLE.
3. Gather source material from industry reports, public data, competitor pages, customer research, and supplied internal context.
4. Apply the framework rigorously, showing math, ratings, assumptions, confidence, and caveats.
5. Verify the high-stakes numbers or ratings against their sources and reject unsupported claims.
6. Summarize the strategic implications and route the analysis to the decision owner for approval.

The trap is mixing frameworks until the output becomes a survey of everything. One well-applied framework beats a broad report that never answers the decision.

What an agent can automate

An agent can handle the research, framework discipline, and verification loop:

• Read the brief first. The agent starts from the business context and the decision, not from a generic market template.
• Apply the chosen framework. For TAM/SAM/SOM it defines the market, builds top-down and bottom-up estimates, scopes SAM, grounds SOM in GTM capacity, and projects assumptions. For Porter it rates the five forces with drivers and implications. For PESTLE it scans six macro categories and prioritizes by impact and probability.
• Cite market data. Every market number carries a source URL or is explicitly labelled as an estimate.
• Show the working. The output includes population counts, formulas, confidence ratings, and assumptions rather than final numbers alone.
• Verify before approval. A verifier spot-checks headline numbers, math, source fit, SOM realism, and hidden assumptions before the analysis reaches the human.

The agent drafts the pack. The human still approves how the strategy changes.

The guardrails that make it safe

Strategy artifacts can influence fundraising, hiring, market entry, and product bets, so unsupported confidence is the failure mode to design against. The first guardrail is source discipline: no market number is allowed to look like data unless it has a traceable source.

The second guardrail is adversarial verification. The verifier checks whether the source actually says what the analysis claims, whether the math reconciles, whether SOM is grounded in capacity, and whether Porter or PESTLE ratings are justified by named drivers. Approval comes only after that check.

Set it up in Task Machine

The Market & Strategy Analysis Pack playbook installs the Strategy Analyst, Analysis Verifier, Strategy Analysis Desk, Read, analyze, verify, approve workflow, Business context and analysis brief, and the skills for market sizing, TAM/SAM/SOM, Porter, and PESTLE analysis. Setup takes a few minutes. You need a Task Machine workspace and permission to install playbooks (workspace owners have it). Web search and fetch access help ground market data, but the agent can label estimates and gaps when live research is unavailable.

1. Find the playbook

Open Playbooks in your workspace and search for "market strategy", or browse the Research category. The card shows the analyst, verifier, strategy workflow, brief document, and analysis skills it creates.

2. Preview what it installs

Select Preview & install to inspect the records before anything is created. The preview shows the Strategy Analyst, Analysis Verifier, Strategy Analysis Desk, Read, analyze, verify, approve workflow, Business context and analysis brief, and the framework skills.

3. Define the analysis scope

Click Start setup and fill in the market or category, customer segment, competitors, and strategic decision context. Also choose the analysis framework in the setup flow. Use one framework per assignment so the output answers the decision instead of becoming a general report.

4. Generate and review

Use Generate customized playbook. Task Machine writes your scope into the analyst instructions, verifier checks, workflow, and business-context brief. In the review step, confirm that the workflow reads the brief, runs the chosen framework, verifies numbers and assumptions, and waits for approval.

5. Install

Click Install customized playbook to create the records. Two follow-ups arrive in your inbox: fill the strategy analysis brief, and start Read, analyze, verify, approve. The first run reads the brief, applies the framework, verifies sources and assumptions, and waits for approval before the analysis is used.

What good looks like

A strategy analysis is ready when the decision owner can challenge it:

• The framework fits the question. TAM/SAM/SOM for market size, Porter for industry structure, PESTLE for macro context.
• Numbers are sourced or labelled. No headline figure appears without a source URL, shown math, or an estimate label.
• SOM is realistic. It reflects GTM capacity and competition, not a wishful share of the market.
• Assumptions are explicit. The analysis names confidence, caveats, and validation paths.

Common questions

Should one analysis include TAM/SAM/SOM, Porter, and PESTLE? Usually no. Pick the framework that answers the decision. Run a separate pack when another decision needs another framework.

Can this replace customer discovery? No. Market size and industry structure do not prove product-market fit. Pair the analysis with customer interviews when the decision depends on demand.

What happens when sources disagree? The agent should show both, explain the reconciliation, and label confidence rather than forcing a false single answer.

Can it use gated analyst reports? It can read public portions through browser access when available. It should not invent gated data it cannot access.