3C Framework in Strategy: Company, Customer, Competitor

The 3C framework in strategy uses Company, Customer, and Competitor to test whether a strategic move makes sense: what the client can do well, what customers need or will pay for, and how rivals may respond. In a consulting case, it works best for market entry, growth, pricing, new product, and competitive-positioning prompts where the recommendation depends on fit across those lenses. It fails when you recite labels without a client objective, data requests, or branch priority. Interviewers need to hear how each branch changes the decision. A strong answer sounds like a focused issue tree, not a textbook list: here is what must be true about the company, here is what customers must believe, and here is where competitors can make the move unattractive. Use 3C to organize thinking, then customize it to the actual question in front of you.

For the broader distinction, read case structure vs case framework before memorizing another named model.

What the 3C framework means in strategy

Company means the client side of the decision: capabilities, economics, assets, channels, brand, constraints, and strategic fit. Customer means demand: segments, needs, willingness to adopt, buying behavior, and barriers to switching. Competitor means the alternatives customers already have and how rivals might defend their position through price, product, distribution, relationships, regulation, or speed.

That makes 3C useful, but incomplete. A strategy is not a checklist. Harvard Business Review's strategy reference is a good guardrail here: strategy is about choices, positioning, and tradeoffs, not simply listing business topics. In a case interview, 3C should help you decide what to investigate first. It should not replace a custom issue tree.

A weak candidate says they want to look at Company, Customer, and Competitor, then asks broad questions under each bucket. A stronger candidate names the decision and turns each branch into a test: can the company win, do customers care enough, and can competitors block the move?

When to use 3C in a case interview

Use 3C when the case decision depends on fit between the client, the market, and rivals. It is especially natural in market entry, growth strategy, pricing, new product launch, business-unit strategy, and competitive response cases. If the prompt is about entering a new geography, launching a subscription product, defending share after a rival's move, or choosing which customer segment to prioritize, the Company-Customer-Competitor logic gives you a clean starting shape. The market entry case interview guide is the closest companion when the prompt is a launch or entry decision.

It is usually weaker for pure profitability, operations, supply chain, or exhibit-heavy cases. A declining profit case often needs revenue and cost drivers before customer or competitor labels. A factory throughput case may need process bottlenecks and capacity. A chart-led case may need you to read the exhibit and form a sharper branch from the data.

This matches what firms test. BCG's case interview preparation page emphasizes structuring the approach, asking thoughtful questions, analyzing data, doing quick calculations, and identifying important factors. McKinsey's interviewing page frames cases as problem-solving conversations around business problems. A 3C answer works only if it shows that behavior.

How to build a Company-Customer-Competitor structure

Start with the decision, not the labels. Restate the objective in plain business terms: should the client enter, grow, price differently, launch, respond, or stop? Then make each C a testable question.

Candidate opening:

I would assess whether this move is attractive by testing the client's ability to win, the customer demand behind the opportunity, and the competitor pressure that could affect margins or adoption. I would start with customer demand if the biggest uncertainty is whether anyone wants the offer, but I would start with company economics if the client may lack the assets or margins to win.

That sounds simple because the logic is visible. You are not saying the framework name and hoping the interviewer approves. You are showing how the branches affect the answer.

Use this construction sequence:

• Objective: define the decision and success criteria.
• Company: what must be true internally for the client to win?
• Customer: what must be true about demand, adoption, and willingness to switch?
• Competitor: what must be true about alternatives, differentiation, and likely response?
• Priority: which branch is most likely to change the recommendation?
• Data: what evidence would prove or disprove the branch?

Check overlap with the MECE framework. Customer demand and competitor pressure often blur together. Customer belongs to needs, segments, adoption, and buying behavior. Competitor belongs to alternatives, rival advantages, and expected response. Market size should not be dumped under both.

If you want to test whether the structure is more than a memorized 3C label, Road to Offer helps by making you state the objective, pick a branch, and attach data requests before moving on.

Worked example: applying 3C to a market entry case

Prompt: a residential energy company is considering launching a home battery product. Should it enter the market?

A generic answer would say: analyze company, customers, competitors. That is not enough. A better issue tree would look like this:

• Company: Can the client source or build batteries at attractive economics? Does it have installation capacity, customer support, financing options, and an existing channel into homes? What constraints could block rollout?
• Customer: Which households would adopt first? What problem are they solving: backup power, lower bills, energy independence, or sustainability? What adoption barriers matter, such as upfront cost, installation hassle, trust, or payback uncertainty?
• Competitor: What alternatives already exist? Are solar installers, battery makers, utilities, or financing platforms better positioned? How might incumbents respond on price, bundles, warranties, or channel access?

The initial data request should match the biggest uncertainty. If demand is unknown, ask for customer segments, adoption drivers, switching barriers, and evidence of willingness to buy. If economics are unclear, ask for unit economics, installation cost, service cost, and channel conversion. If competitive pressure is the risk, ask for rival offerings, price points, distribution advantages, and response history.

The synthesis should connect the branches. If customers want backup power but the client lacks installer capacity and competitors already own the trusted channel, the answer may be no or enter through a partnership. If the client has a strong customer base, a low-cost channel, and competitors are fragmented, the answer may be yes with a focused segment launch.

Before timed practice, the case structure builder can help turn this example into a spoken tree with branch priority and evidence requests.

Questions and checklist for each 3C branch

Use this as a quick pre-practice checklist. The goal is not to ask every question. The goal is to pick the questions that would move the recommendation.

The table is also a self-check. If your Company branch is only strengths and weaknesses, it is too vague. If your Customer branch is only market size, it is too shallow. If your Competitor branch is only a list of names, it does not explain pressure.

Common mistakes that make 3C sound memorized

The main failure is starting with the labels before the objective. The interviewer hears a memorized framework because the candidate has not said what the framework is supposed to decide. Better version: I want to assess whether entry is attractive by testing internal ability to win, customer adoption, and competitor response.

Another mistake is asking broad, non-decision questions. What are customer preferences? is weaker than: which customer segment has the strongest unmet need and lowest adoption barrier? What is the competitive landscape? is weaker than: which alternative would customers choose today, and can we beat it on value, trust, or access?

Candidates also double-count market size. They put demand under Customer, then put market attractiveness under Competitor, then put revenue under Company. Better version: keep demand under Customer, rival pressure under Competitor, and the client's economics under Company.

The last mistake is failing to synthesize. They analyze each branch, then give a recommendation that does not use the branch findings. BCG's interview process page emphasizes problem-solving, analytical ability, and communication. Your structure must therefore help the interviewer follow your reasoning, not just admire your labels.

Practice drill: turn 3C into an interview-ready issue tree

Road to Offer works best here as a sequence. Take a market entry or growth prompt. Draft the Company, Customer, and Competitor branches. Say the opening out loud in the Case interview structure drill. Then test whether the branches connect into a final answer with the Synthesis drill. If a specific weakness appears, use the free drill picker to isolate that skill before returning to full cases.

Your answer is ready when it passes this mini rubric:

• Objective-led: the structure starts from the client decision.
• Branch-specific: each C has a clear test, not a generic bucket.
• Non-overlapping: customer demand, competitor pressure, and company economics do not repeat the same idea.
• Data-driven: each branch has evidence you would request.
• Prioritized: you know which branch you would investigate first and why.
• Synthesized: you can explain how branch findings change the recommendation.

When your issue tree no longer sounds like labels, move into a full case so the same logic survives data, math, and synthesis.

Sources and Further Reading (checked 2026-06-02)

• McKinsey & Company - Interviewing at McKinsey
• Boston Consulting Group - Case Interview Preparation
• Boston Consulting Group - Interview Process
• Harvard Business Review - What Is Strategy?
• Harvard Business School Institute for Strategy and Competitiveness - Business Strategy
• Yale Office of Career Strategy - Consulting