Market Attractiveness Framework for Industry Analysis

The market attractiveness framework helps you decide whether a market deserves deeper analysis, investment, or entry planning before the case turns into launch tactics. In a consulting interview, treat it as a decision screen: define the client's objective, test demand, economics, industry structure, access and right to win, then isolate the risk that could change the answer fastest. A strong answer does not say the market is attractive because it is large. It explains who would buy, why the economics work, how competitive intensity affects profit, whether the client has a credible path in, and what would make the opportunity unattractive. Use the framework when a prompt asks whether to pursue a geography, segment, category, or product line. Then move from labels to data requests and recommendation logic fast, because interviewers reward structured judgment, not reciting a strategy-class vocabulary list.

If the prompt has already moved from whether to enter to how to enter, use the market entry case interview guide alongside this framework.

What the market attractiveness framework actually decides

Market attractiveness sits upstream of market entry. Market entry asks whether the client can win and how they should enter. Market attractiveness asks whether the market is worth the client's attention in the first place.

That distinction matters because a case interviewer is not grading your ability to name categories. Bain's interviewing page frames cases around client problems and structured problem solving, which is closer to real consulting work than classroom taxonomy. Yale's consulting overview also frames the work around profitability, effectiveness, growth, and strategy. The framework is useful because it forces you to connect the client's objective to a practical business decision.

Start with the decision sentence: our client is deciding whether to pursue this market because they want growth, margin expansion, strategic control, or a stronger position in a related category. Once that is clear, the issue tree should be custom enough to fit the client and clean enough to avoid overlap. The MECE framework is useful here because market attractiveness branches should be separate, but still complete enough to support a recommendation.

Industry structure belongs in the framework, but it is not the entire answer. Harvard's Institute for Strategy and Competitiveness describes industry structure as driven by five competitive forces, which makes competitive intensity a real branch of attractiveness. Still, demand, economics, access, right to win, and risk need their own space.

Market attractiveness table: branches, questions, and data requests

Use the framework as a live issue tree, not as a static scorecard. The goal is to ask for the data that would move the recommendation, then interpret it.

A good driver tree can help you turn these branches into testable drivers instead of repeating market size, growth, and competition. For real projects, official sources such as the U.S. Census Bureau's Economic Census can support market size and business activity research, but in an interview you should ask for the type of data before asserting a value.

Worked example: should a client pursue a new market?

Prompt: A regional cafe chain is considering entering a nearby city. The CEO wants to know whether the city is attractive enough to justify expansion.

Weak answer: market size, growth, competition, profitability. That sounds organized for a few seconds, but it does not tell the interviewer what you are trying to prove. It also treats every cafe chain as if it had the same brand, cost base, locations, and operating strengths.

A stronger spoken structure would start from the decision. I would assess whether this city is attractive for our client's expansion by testing demand for the cafe concept, the economics of serving that demand, the competitive landscape, our right to win through locations and brand fit, and key risks such as rent, labor, or local regulation. I would start with demand and location access because if the target customers are not concentrated near viable sites, the economics will not matter much.

That answer gives the interviewer a decision screen and a priority. The first data request could be customer foot traffic by neighborhood, cafe spending patterns, competitor density, and available storefront economics. You do not need to invent numbers. You need to say what data would prove the market is attractive.

The recommendation logic is simple: if target customers are concentrated near viable sites, competitors leave room for differentiation, and unit economics can work at expected rents, the city is worth deeper entry planning. If demand exists but all viable sites are locked up or pricing cannot cover costs, the market may be interesting but unattractive for this client.

If your issue tree still sounds like labels instead of a spoken interview answer, the structure drill is the right next rep because it forces you to prioritize the branch before asking for data.

Questions that choose the right branch first

The main difference between a framework user and a strong candidate is branch selection. A framework user walks through every category in order. A strong candidate asks which branch could break the recommendation.

Before you commit to the issue tree, ask yourself: what would make this market a clear no-go? If the answer is weak customer need, lead with demand. If it is thin margin, lead with economics. If incumbents control distribution, lead with access and competitive intensity. If the client has no credible reason to win, lead with client fit.

Then ask what the client needs to believe for entry to make sense. Maybe they need to believe that premium customers are underserved. Maybe they need to believe their existing brand travels to a new geography. Maybe they need to believe the profit pool is not already captured by suppliers, platforms, or landlords.

Finally, ask what data would change the answer fastest. This question keeps the structure tied to action. It also prevents the common trap of making the tree sound balanced when the case is clearly about one uncertainty.

Common mistakes that make market attractiveness answers weak

The large-market fallacy is the most common mistake. A market can be large and still be unattractive because customers are expensive to reach, margins are thin, competition is intense, or the client has no right to win. Large is not the same as accessible, profitable, or defensible.

The second mistake is building a scorecard before defining the decision. A scorecard can be useful after you know the client's objective, but arbitrary weights make the answer feel fake. In a case, explain what matters most and why. If the client needs profitable growth quickly, economics and access may matter more than broad market excitement.

The third mistake is ignoring client capabilities. Market attractiveness is not universal. A city, segment, or product category may look attractive for an incumbent with strong channels and unattractive for a new entrant with no distribution. This is where right to win matters.

The fourth mistake is double-counting competition. Candidates often put competitors under market size, pricing, barriers, and risk until every branch says the same thing. Keep competitive intensity in one clear place, then explain how it affects economics and recommendation logic.

The final mistake is using case structure vs case framework backward: memorizing a framework label and forcing the case into it. Porter's Five Forces can sharpen the industry structure branch, but it should not replace the full attractiveness answer.

Practice drill: build the first issue tree under pressure

Use a short prompt and make yourself speak the first layer out loud. Try this: a home battery company is considering entering a new regional market and wants to know whether the opportunity is attractive.

Your task is to define the decision, build the first issue tree, pick the branch you would test first, and ask for the data that would prove or disprove attractiveness. Do not move into launch mode yet. Stay on the question of whether the market deserves pursuit.

A clean issue tree might test customer demand, unit economics, competitive intensity, access and right to win, and risks around regulation or technology shifts. The first branch depends on the prompt. If the case hints that adoption is uncertain, start with demand. If the prompt mentions strong incumbents, start with competition and access. If the client already has customers nearby, start with economics and channel leverage.

For repetitions, use the case interview structure drill and force yourself to say the data request after the structure. Then use the Road to Offer drill engine when you want targeted practice across structure, synthesis, chart reading, and math. Duke Career Hub's case resources also point candidates toward practice and advice from consultants, which is the right direction: you improve this framework by using it under pressure, not by rereading it.

Once you can verbalize the first layer clearly and choose the highest-impact branch, a full case is the better test because it checks whether your market logic survives math, exhibits, and recommendation pressure.

Sources and Further Reading (checked 2026-05-30)

• Institute for Strategy and Competitiveness at Harvard Business School - Industry structure is driven by five competitive forces, which is relevant to the competitive intensity branch of market attractiveness.
• Institute for Strategy and Competitiveness at Harvard Business School - The Five Forces
• Bain & Company - Interviewing
• Yale Office of Career Strategy - Consulting
• Duke Career Hub - Case Interview Resources
• U.S. Census Bureau - Economic Census
• U.S. Census Bureau - Data Tools and Applications