Strategy Consulting Framework: The Practitioner's Guide

Why Frameworks Exist (And Why Most Consultants Use Them Wrong)

Strategy consulting frameworks aren't magic. They're structured lenses - ways to stop spinning on a problem and start breaking it apart systematically. Top consulting firms like McKinsey, BCG, and Bain built their reputations partly on being rigorous and repeatable. Frameworks give junior consultants a starting point so they don't reinvent the wheel on every engagement.

But the dirty secret? The framework isn't the insight. Your judgment is. A framework tells you what to look at. It's your knowledge of the business, the market, and the client that tells you what it means. If you're running a framework and just filling in boxes, you're doing busywork dressed up as strategy.

The best use of a strategy consulting framework is to structure your thinking fast, communicate clearly to a client, and make sure you're not missing a critical angle. That's it. Use them as a starting point - not a finish line.

There's another mistake I see all the time: consultants memorizing frameworks for interviews and then treating them like gospel on actual engagements. Real consulting work doesn't come with a label that says "this is a Porter's Five Forces problem." You show up, hear a messy problem statement, and have to decide which lens gives you the fastest path to a useful answer. That judgment - which framework, when, and how deep to go - is the actual skill. The framework is just the vehicle.

This guide covers the frameworks I've seen work repeatedly on real engagements, how to combine them, when to reach for each one, and how to build the consulting practice that actually gets you in front of clients who need this work done. Let's get into it.

The Frameworks That Actually Show Up on Real Engagements

1. MECE (Mutually Exclusive, Collectively Exhaustive)

MECE is less a framework and more a thinking discipline - and it's the foundation everything else sits on. When you break a problem down into MECE buckets, you're making sure your categories don't overlap and together cover the entire problem space. No gaps, no double-counting.

In practice: if a client's revenue is declining, MECE forces you to split the analysis into revenue and costs - not revenue, costs, and "maybe leadership issues" as a third bucket (that's not MECE). Get the structure right first, then dig.

MECE also applies to how you communicate. A recommendation that's built on MECE logic is cleaner, easier to defend in a boardroom, and harder to poke holes in. Start every engagement by asking: are my buckets clean?

McKinsey consultants extend this into issue trees - breaking the problem statement into a branching structure of sub-questions, each MECE from the one above it. Issue trees let you assign workstreams to team members without overlap, which is why they're used almost universally on complex engagements. Even as a solo consultant, building an issue tree at the start of a project forces clarity before you spend a week going in the wrong direction.

2. The Profitability Framework

This is the workhorse. Any time a client says "we're making less money than we used to," you pull this out first. It breaks profitability into Revenue minus Costs - then each branch gets subdivided further. Revenue becomes Price x Volume. Costs split into fixed and variable. Variable costs break into cost-per-unit times units produced.

The reason this framework is so powerful is that it forces you to follow the math before you chase stories. Clients will tell you their problem is competition, or their team, or the economy. Run the profitability tree and you'll find out whether the issue is really volume, pricing, cost structure, or something else entirely.

Once you've identified which branch has the problem, you can move into sharper qualitative work. But start with the numbers. A company might think declining profit is a market share problem when really it's a fixed cost structure that hasn't adjusted to lower volume. The framework won't let you skip that step.

The profitability framework is also the most commonly tested framework in consulting case interviews - roughly 20% of all case questions at the major firms involve some version of a profitability problem. There's a reason for that: profit pressure is the most universal trigger for bringing in outside help. Master this one cold.

3. Porter's Five Forces

Developed by Michael Porter, this framework examines five forces that shape industry profitability: threat of new entrants, bargaining power of buyers, bargaining power of suppliers, threat of substitutes, and intensity of rivalry. It's the go-to tool for understanding competitive dynamics before making a market entry, pricing, or positioning decision.

What makes it valuable in practice is that it forces you to think beyond direct competitors. Most business owners are obsessed with who else is in their market. Porter's framework makes you consider the entire ecosystem - who could enter, what buyers could switch to, how much leverage your suppliers actually have.

Run this analysis on a new client before their first strategy session and you'll walk in with context most of their internal team doesn't have. That's what justifies a consulting fee.

One thing worth flagging: don't present Porter's Five Forces as a finished framework in a boardroom. Use the concepts - competitive rivalry, supplier power, buyer power, threat of substitution, barriers to entry - and weave them into a tailored analysis. Executives who've been through strategy work before will see a raw Five Forces slide as junior output. The insight you derive from it is what matters, not the template.

Where Five Forces shines in practice is market entry decisions and competitive positioning work. If a client is asking "should we enter this new vertical?" or "why are our margins shrinking even though revenue is growing?", Five Forces gives you the diagnostic structure to answer it fast.

4. McKinsey 7S Framework

The 7S model examines seven interconnected organizational elements: Strategy, Structure, Systems, Shared Values, Style, Staff, and Skills. The critical insight embedded in the model is that changing one element ripples through the others. If you shift strategy from cost leadership to premium positioning, you probably need to restructure teams, upgrade skills, and reset shared values - you can't just update the strategy deck and call it done.

On real consulting engagements, the 7S framework shows up most in three situations: post-merger integration, organizational redesign, and strategy execution diagnosis. It gives consulting teams a structured way to assess whether a client's organization is set up to deliver on its strategy. For post-merger integration specifically, the biggest integration challenges almost always come from misalignment in shared values and style - not from structural or systems differences.

Use 7S when a client's strategy looks fine on paper but execution is broken. Nine times out of ten, the culprit is misalignment between one of the hard elements (strategy, structure, systems) and one of the soft elements (style, staff, skills). Map all seven, find the gap, and you've found the problem.

The 7S framework also pairs well with SWOT. Use 7S for the internal deep dive - how are these seven elements aligned or misaligned? - and then use SWOT to layer in the external context. That combination gives you a complete picture: what's happening inside the organization and how it stacks up against outside forces.

5. The 3Cs Framework

Developed by Kenichi Ohmae, the 3Cs - Company, Customers, Competitors - is a clean, fast way to stress-test a strategic position. It's especially useful for market entry, brand strategy, and go-to-market work. You're asking: where do our company's strengths intersect with what customers actually need, and where do competitors leave a gap we can exploit?

This framework is underrated for independent consultants because it's quick to run, easy to present, and cuts straight to the positioning question clients are usually actually asking - even when they've framed it as something else. When a client says "we need a marketing strategy," they usually mean "we don't know how to articulate our differentiation." The 3Cs gets you there in a single working session.

Run it in sequence: start with Customers (what do they actually need, not what does the client think they need), move to Competitors (where are the gaps, where are the overlaps), then land on Company (what capabilities genuinely match that opportunity). The intersection of those three circles is your strategic sweet spot.

6. The BCG Growth-Share Matrix

The BCG Matrix classifies a business's products or units into four quadrants - Stars (high growth, high share), Cash Cows (low growth, high share), Question Marks (high growth, low share), and Dogs (low growth, low share) - based on market growth rate and relative market share. The purpose is resource allocation: where should limited capital and management attention go?

Cash Cows generate more cash than they consume and should be managed to maintain market share while funding other units. Stars are leaders in high-growth markets that require investment to sustain their position. Question Marks need hard decisions - invest to build share, or cut? Dogs are typically candidates for divestiture or restructuring.

Use this with clients who have multiple product lines or business units and no clear sense of where to focus. It makes prioritization visual and defensible. One caveat: the matrix is a snapshot. Build in a regular review cadence so the analysis doesn't go stale. A product that's a Cash Cow today can become a Dog faster than a quarterly review cycle if market conditions shift.

The BCG Matrix is also a natural companion to the Ansoff Matrix. Once you've mapped where your products sit today (BCG), you can use Ansoff to plot where to grow from there. They're different lenses on the same question: what do we do with what we have, and where do we go from here?

7. The Ansoff Matrix

If BCG is about managing your current portfolio, the Ansoff Matrix is about plotting your future growth. Developed by Igor Ansoff and first published in the Harvard Business Review, it maps growth options across two axes: products (existing or new) and markets (existing or new). That gives you four quadrants, each with a meaningfully different risk profile.

Market Penetration - existing products, existing markets. Sell more of what you already sell to the people who already buy from you. This is the lowest-risk path because you're operating in familiar territory on both dimensions. Most day-to-day growth activity lives here: better pricing, improved retention, expanded distribution, more aggressive outreach.

Market Development - existing products, new markets. You know the product works. The question is whether it works somewhere else - a new geography, a new customer segment, a new channel. Moderate risk because you're not reinventing what you sell, just how you reach new buyers.

Product Development - new products, existing markets. You know the customer. You're building something new for them. Higher risk than penetration or development because you're taking product risk, but the customer relationship gives you a foundation.

Diversification - new products, new markets. The highest-risk quadrant. You're taking both product risk and market risk simultaneously. Companies that manage this well usually do so because they have strong brand equity or operational infrastructure that transfers. Companies that do it badly usually underestimated how different "new" really was.

The Ansoff Matrix's real contribution is making risk visible. Every growth initiative carries risk, but teams rarely talk about the type of risk explicitly. When you plot a client's growth portfolio on the matrix and see that every exciting initiative sits in the diversification quadrant, that's a signal to pause. When everything is market penetration and revenue growth is slowing, that's a signal to move. The framework doesn't make the decision - it makes the trade-off clear, which is what every good consulting framework should do.

Before running an Ansoff analysis, make sure you've completed a SWOT and ideally a Five Forces analysis first. You need to understand your client's actual strengths and the competitive landscape before you start evaluating which quadrant is realistic vs. aspirational.

8. SWOT Analysis

SWOT - Strengths, Weaknesses, Opportunities, Threats - is the framework everyone knows and most people run badly. It's a synthesis tool, not a discovery tool. It's designed to organize evidence you already have, not to generate it from scratch. When teams treat SWOT as a starting point and just brainstorm in a room, they end up with a list of opinions dressed up as strategy.

The right way to run a SWOT: do the research first. Use client interviews, financial data, market analysis, and competitive intelligence to populate each quadrant with facts, not gut feelings. Then use the SWOT to synthesize those findings into a clean strategic picture.

The SWOT quadrants only have strategic value when they're compared against each other. A strength that doesn't address any threat or opportunity is strategically neutral. The most powerful insights come from the intersections: which strengths can you leverage against which opportunities? Which weaknesses make you most vulnerable to which threats? That cross-analysis is the step most teams skip - and it's where the real strategic clarity lives.

SWOT is also distinct from PESTLE in an important way. SWOT looks at a company's internal health and its immediate competitive environment. PESTLE - or PEST - scans the macro-environmental forces shaping the entire industry. Think of SWOT as a business health check and PESTLE as a long-range weather forecast. They're not interchangeable, but they're highly complementary.

9. PESTLE Analysis

PESTLE (Political, Economic, Social, Technological, Legal, Environmental) is the macro-environment scanner. It's what you run when you need to understand the forces that are largely outside a company's control but critically within its need to understand. Regulatory shifts, inflation trends, demographic changes, technology disruption - these all live in PESTLE territory.

In practice, PESTLE is most useful as a pre-cursor to other frameworks. Run it before an Ansoff analysis to understand whether market development into a new geography is actually viable. Run it before a Porter's Five Forces analysis to understand which external macro-forces are reshaping competitive dynamics in the industry. PESTLE surfaces the context; the other frameworks help you decide what to do about it.

The political dimension covers regulatory change, government policy, trade conditions, and political stability. Economic factors include inflation, interest rates, consumer confidence, employment levels, and exchange rates. Social factors capture demographic shifts, cultural trends, and lifestyle changes. Technological factors address disruption, automation, and digital transformation. Legal factors cover compliance requirements and liability shifts. Environmental factors include sustainability pressures, climate risk, and ecological regulations.

One caveat: PESTLE is not a one-time exercise. Political, economic, social, and technological conditions shift fast. A PESTLE from 18 months ago may already be significantly outdated, especially in sectors experiencing rapid regulatory change or technology disruption. Build in a refresh cadence - at minimum annually, quarterly in high-velocity markets.

For independent consultants, running a PESTLE for a client before their first session is a fast way to demonstrate strategic breadth. It shows you're thinking beyond their internal operations and positioning yourself as a partner who understands the broader forces shaping their business - not just a problem-solver for whatever's on fire this quarter.

10. Value Chain Analysis

Introduced by Michael Porter (the same Porter behind Five Forces), Value Chain Analysis dissects how a company creates value at every operational stage - from inbound logistics to service delivery. You use it to identify where profits are made or lost, and where efficiency improvements yield the most benefit.

The framework splits activities into two types: primary activities (inbound logistics, operations, outbound logistics, marketing and sales, service) and support activities (firm infrastructure, human resource management, technology development, procurement). Every activity either adds to the customer's willingness to pay or adds to cost. The strategic question is: which activities create competitive advantage, and which are just table stakes?

Value Chain Analysis is most useful for operations and margin improvement engagements. If a client is asking "why is our gross margin lower than competitors with the same revenue?" the value chain gives you the structure to trace where costs are leaking and where value is being destroyed rather than created. Consulting teams frequently apply this to assess supply chain inefficiencies or to find cost-reduction opportunities in manufacturing, distribution, or service delivery.

It also pairs well with the profitability framework. When the profitability tree tells you the problem is in cost structure, the value chain tells you where in the cost structure to look.

How to Stack Frameworks: Combinations That Work on Real Projects

The mistake most consultants make is picking one framework and running it in isolation. Experienced consultants stack them. Here's how the combinations play out in practice:

Market Entry Decision: Start with PESTLE (is the macro environment favorable?), run Porter's Five Forces (is the industry structurally attractive?), then 3Cs (is there a positioning gap we can fill?), then Ansoff (which entry quadrant are we in and what does that mean for risk?). That sequence gives you a complete picture before the client commits capital.

Declining Profitability: Start with the Profitability Framework (where in the P&L is the problem?), then Value Chain Analysis (which activities are driving cost or eroding value?), then Porter's Five Forces (is this an industry-level problem or company-specific?). Layer in SWOT to frame the strategic response.

Strategy Execution Failure: Use 7S first (which elements are misaligned?), then SWOT (are the internal weaknesses structural or fixable?). If the issue is organizational culture, the soft elements of 7S - style, shared values, staff - are where the real work happens.

Growth Planning: BCG Matrix (where do we stand today?), then Ansoff (where can we go?), then 3Cs (what positioning makes sense in the target market?), then PESTLE (what external forces do we need to account for?).

The key is sequencing. Frameworks used in the right order create compounding insight. Used in the wrong order, or in isolation, they produce a list of observations that doesn't add up to a recommendation.

How to Build Your Own Consulting Framework for a Client

Here's what separates solid consultants from those who just template-match: they build custom frameworks for specific client problems. That doesn't mean ignoring the classics - it means adapting them.

Start with the problem statement. Write it out in one clear sentence. Then ask: is this fundamentally a profitability problem, a competitive positioning problem, an organizational alignment problem, or a growth decision? That answer points you to the right foundational framework.

From there, layer in the specific context. A B2B SaaS company facing churn isn't the same as a manufacturing company facing margin compression - even if both ultimately show up as "declining profitability." The framework gives you the structure. Your industry knowledge fills in the content.

Custom frameworks don't need to be invented from scratch. Most of the time, the best client-specific framework is a modified version of a classic with renamed buckets that use the client's own language. When a client sees their own terminology in your structure, they trust it more. That's not manipulation - it's good communication. The framework should feel like it was built for them, because in a real sense it was.

One thing that's always worth doing before you walk into the first client meeting: a solid discovery call where you ask the right diagnostic questions before you commit to any framework at all. I've built a Discovery Call Framework specifically for this - getting the information you need upfront so you're not guessing at the problem halfway through the engagement.

Presenting Framework-Based Recommendations

A consulting framework is only as good as how you communicate it. The Pyramid Principle - another McKinsey staple - says lead with the conclusion, then back it up with supporting arguments, then evidence. Most people do it backwards: they walk through all the analysis, then reveal the answer at the end. That's backwards for executive communication.

When you present findings, your first slide should answer the question the client hired you to answer. Everything after that is the "why." This is what separates a sharp consulting deliverable from an academic report nobody acts on.

Structure your recommendation deck so every slide has a clear headline that could stand alone as a statement. If you can read only the headlines and understand the story, the deck is working. If reading only the headlines leaves you confused, the deck isn't structured yet - it's just organized. There's a difference.

A few practical presentation rules I always apply:

• Lead with the answer. Not "we analyzed three scenarios" - lead with "we recommend option B, here's why." The analysis supports the answer; it doesn't replace it.
• One idea per slide. If a slide needs two headlines to make sense, it's two slides.
• Anticipate the top three objections. Build them into the narrative with pre-emptive responses. Nothing kills credibility faster than being surprised by a pushback you should have seen coming.
• Make the "so what" explicit. Every analytical finding needs a "so what" - what does this mean for the decision the client has to make? Findings without implications are just interesting facts.

The Pyramid Principle is also useful for written deliverables - memos, interim updates, email summaries. Lead with the conclusion, support with three to five structured arguments, then evidence. Every time. It trains clients to read your work in the right order, which means your recommendations actually land instead of getting buried in the appendix.

A Framework for Running the Consulting Engagement Itself

Beyond the analytical frameworks, good consultants also need a delivery framework - a repeatable process for how engagements run from kickoff to final presentation. Here's a clean version that works for most strategy projects:

• Phase 1 - Define: Nail the problem statement. Run a structured discovery session. Agree on what success looks like and how you'll measure it. Don't skip this - a poorly defined problem is the number one cause of consulting projects that go sideways. Use the MECE discipline here: make sure the problem you've defined actually covers the full issue, not just the symptom the client first described.
• Phase 2 - Diagnose: Gather data, run your framework analysis, interview stakeholders. Stay MECE. Resist the urge to jump to recommendations before you've actually looked at the evidence. This is where your framework stacking happens - running the right analytical tools in the right sequence.
• Phase 3 - Design: Develop options, not just one recommendation. Clients who feel they have choices are more bought-in to the final decision. Present two to three scenarios with clear trade-offs. Use the Ansoff Matrix logic here: what's the risk profile of each option? What does execution require?
• Phase 4 - Deliver: Present findings using the Pyramid Principle. Lead with the answer. Back it with logic and data. Anticipate the objections and address them proactively. Make the "so what" explicit on every slide.
• Phase 5 - Drive Implementation: The best consulting engagements don't end at the presentation. Build in a follow-on phase or at minimum a 30-day check-in. Clients who see results become long-term relationships. And long-term client relationships are far more profitable than one-off projects.

This five-phase process isn't original - every consulting firm has a version of it. What matters is that you have one, you communicate it to the client upfront, and you run it consistently. Process predictability is a trust signal. Clients who know what's coming next don't micromanage. Clients who feel like the project is improvised will.

Common Framework Mistakes (And How to Avoid Them)

I've watched a lot of consultants present framework-based analysis over the years - some of it sharp, a lot of it not. Here are the mistakes that come up most consistently:

Template-matching without thinking. Seeing a revenue problem and reflexively pulling out the profitability framework before understanding the context. Sometimes the profitability math is obvious and the real problem is a 7S alignment issue. Always spend five minutes on the problem statement before you decide which framework to reach for.

Running frameworks in isolation. Porter's Five Forces without PESTLE context, or Ansoff without BCG foundation. Frameworks compound. Use them in combination and in the right sequence.

Presenting the framework instead of the insight. Showing a client a neatly filled-in 3Cs template isn't an insight - it's a table. The insight is the conclusion you drew from it: "your positioning gap is here, your competitors haven't addressed this customer need, and your strongest capability maps directly to it." That's what a client is paying for.

Skipping stakeholder interviews. Frameworks need to be populated with real data, not assumptions. If you're running a 7S analysis based purely on public information and your own observations without interviewing the client's leadership team, you're going to miss things. The soft elements especially - style, shared values, skills - require firsthand input.

Not updating the analysis. A PESTLE or competitive landscape analysis that was accurate at kickoff can be materially wrong by the time you present recommendations, especially in fast-moving markets. Build in checkpoints to validate that your framework findings still hold.

Over-engineering the framework. A three-level issue tree covering 47 sub-questions for a $15K engagement is overkill. Right-size the analytical work to the problem. Independent consultants especially need to match the depth of analysis to the complexity of the problem and the budget of the engagement.

The Operational Side: Getting Consulting Clients in the First Place

Frameworks don't matter if you don't have clients. And getting consulting clients is its own discipline - one most strategy consultants underinvest in relative to the craft of consulting itself.

The fastest path I've seen to consistent consulting pipeline is cold outreach combined with a clear, specific positioning statement. Not "I help companies grow" - something like "I help Series A SaaS companies reduce churn in the first 90 days of customer onboarding." Specific wins every time. The more you try to appeal to everyone, the more you appeal to no one.

Your ICP (ideal client profile) for a consulting practice should be tight: a specific industry, a specific company size, a specific role (who actually signs the check), and a specific problem you solve better than anyone else. Once you have that defined, outreach gets dramatically easier because you're not selling strategy consulting in the abstract - you're offering a specific solution to a specific known pain.

When you're building your prospect list for outbound, clean contact data on the right decision-makers is non-negotiable. For finding business emails of the executives and business owners at your target companies, this email finding tool is worth having in your toolkit. Pair it with a B2B lead database to build targeted prospect lists filtered by company size, industry, and title - so you're reaching the exact type of buyer who hires strategy consultants, not cold-calling random people.

Once you're in conversations, your proposal is where deals die or get signed. A weak proposal leaves fees on the table and creates confusion about scope. A strong one makes the client feel like you already understand their problem and have a credible plan to solve it. I have a set of Proposal AI Templates built specifically for consultants - worth using as a baseline before you customize.

Once you close, protect yourself. Have a proper contract in place before any work starts. Scope creep kills consulting profitability faster than almost anything else. Use a solid Agency Contract Template as your starting point - it's much easier to customize a proven document than to draft one from scratch.

Pricing and Positioning a Strategy Consulting Practice

Most independent consultants undercharge. Not by a little - by a lot. The root cause is almost always that they're pricing based on their cost (how many hours will this take?) instead of value (what is this decision worth to the client?).

A strategy engagement that helps a client avoid a bad market entry decision - one that might have cost them $2M in wasted capital - is worth a lot more than the hourly rate of whoever ran the analysis. Price to the value of the outcome, not the time you spent.

Retainer models are almost always better than project-based work for strategy consultants, for the same reason a gym membership beats a one-time personal training session for the gym. Predictable monthly revenue lets you do better work because you're not constantly in business development mode. It also deepens the client relationship - you become a trusted advisor rather than a vendor hired for a one-time project.

Positioning matters more than credentials. You don't need a McKinsey badge to charge McKinsey-adjacent fees. You need a specific claim, a track record of relevant results, and a clear articulation of who you serve and what problem you solve. Niche positioning in consulting - especially for independent practitioners - creates premium pricing power. The more specialized you are, the less you compete on price.

How Independent Consultants Can Apply These Frameworks Without a Big-Firm Budget

Here's the thing most consulting framework guides don't address: the resources available to a solo or boutique consultant are completely different from a 15-person McKinsey team with six weeks of client budget.

You have to right-size both the scope of analysis and the tools you use. A full Five Forces analysis that would take an MBB team two weeks can be compressed into a focused half-day if you're sharp about what data you actually need versus what's nice to have. The discipline is knowing where to go deep and where a directional read is enough to move forward.

Secondary research is your primary data source as an independent consultant. Industry reports, company filings, trade publications, LinkedIn patterns, and customer reviews are all publicly accessible and often enough to populate a PESTLE or Five Forces analysis to a level of accuracy that's useful for decision-making. You're not publishing a journal article - you're helping a client make a better decision than they would have made without you.

Stakeholder interviews are your qualitative anchor. Where secondary data tells you what's happening in the market, interviews tell you how it's playing out inside this specific organization with these specific people. Twenty well-structured stakeholder interviews will surface more actionable insight than a hundred-page data analysis.

When you need direct contact information to reach decision-makers at prospective client companies, ScraperCity's people finder cuts the research time significantly - you spend time on outreach and conversations, not on hunting for email addresses manually.

One more thing on tools: don't over-engineer your deliverable format. A crisp 12-slide PowerPoint built on a clear MECE structure will beat a 60-slide deck every time in terms of executive impact. The instinct to add more slides when you're nervous about your analysis is almost always wrong. Strip it back to the clearest, most defensible story you can tell.

The Framework You Need Most Is Actually a Business Development System

I've worked with thousands of consultants and agency owners. The ones who struggle aren't usually weak on strategy frameworks - they're weak on generating consistent business. They're brilliant at solving problems for clients they have, but terrible at finding new ones.

The fix is treating business development like a system with the same rigor you'd apply to any client engagement. Define your ICP. Build your list. Craft your outreach. Follow up systematically. Track conversion rates at every stage and optimize what's not working.

That means having a clear outbound sequence - not just sending one cold email and hoping. It means a follow-up cadence. It means knowing your numbers: how many prospects do you need to contact to generate one conversation? How many conversations to generate one proposal? How many proposals to close one engagement? When you know those numbers, you know exactly what you need to do this week to hit your revenue target next quarter.

The strategic frameworks in this article give you the analytical foundation to deliver great work once you're in the room. But getting in the room is a separate skill that requires its own systematic approach. Most consultants conflate being good at consulting with having a consulting business. They're not the same thing. The craft and the business are both required.

If you want to go deeper on building that system - the full outbound process, how to position a consulting practice, how to price and close - I go into all of it inside Galadon Gold.

The frameworks in this article give you the analytical foundation. But the real leverage is in building a consulting practice that generates consistent revenue while you deliver great work. Both sides matter.

Quick-Reference: Which Framework for Which Problem

When you're standing in front of a new client problem and need to decide fast, here's the short version:

• Declining profits - Start with the Profitability Framework, then Value Chain Analysis.
• Market entry or expansion decision - PESTLE, then Porter's Five Forces, then 3Cs, then Ansoff.
• Competitive positioning or differentiation - 3Cs first, then Porter's Five Forces.
• Portfolio prioritization - BCG Growth-Share Matrix, then Ansoff for growth planning.
• Strategy execution failure - McKinsey 7S first, then SWOT for the broader context.
• Strategic planning for a new business or product - SWOT for internal, PESTLE for external, Ansoff for growth direction.
• Organizational restructuring or post-merger integration - McKinsey 7S is your primary tool.
• Pricing or margin strategy - Profitability Framework plus Porter's Five Forces (buyer power, competitive rivalry).

No framework is universally right. The skill is knowing which one gets you to the useful answer fastest given the problem in front of you. Build that judgment through reps - the more engagements you run, the faster the pattern recognition becomes. Early in your practice, use the frameworks deliberately. Eventually, you'll reach for the right one intuitively. That's when consulting becomes genuinely fast and genuinely valuable.

Keep this list nearby. Add to it as you find combinations that work for your specific niche. And remember: the framework is just the starting point. The judgment you apply to what you find is what actually earns the fee.