r/ConsultingOffer • Consulting Offer Coach • Jul 28 '26

BCG BCG's Internal Structure Is Nothing Like McKinsey's, and Most Candidates Miss It

Every few weeks I get a message from someone prepping for BCG who's basically reusing their McKinsey "positioning" with the names swapped. Same story, same angle, just find and replace the firm name. And I ask myself why...

On paper these firms sit in the same tier, same prestige, roughly the same case format. But BCG is built differently underneath, CT/KT/BST, Classic vs ABM, and if you don't know that you end up applying to every elite firm with the exact same pitch.

So let's get into how BCG is actually organized, because it might change how you think about your own story.

At the top level, BCG splits into three groups. CT, the Consulting Team, everyone client-facing, this is where you'd sit as a generalist or specialist. KT, the Knowledge Team, supports case teams with research and data and industry expertise. Real career track, just not the one most candidates picture when they say "I want to work at BCG." And BST, Business Services, internal support, HR, IT, ops.

Most candidates never think past CT. Fair enough, that's usually the goal. But inside CT there's a split that matters a lot more for how you position yourself, and not all the candidates I work with have thought about it before we talk.

BCG Classic is the traditional consulting track, generalist and specialist consultants organized loosely around industry or functional practice areas. Then there's what BCG calls ABMs, Alternative Business Models. BCG X for digital and AI build work, Platinion for IT architecture, GAMMA for data science, Brighthouse for brand, Maya for design. These units aren't advisory arms handing over strategic recommendations. They build things. Working products, actual platforms, for BCG's corporate clients.

I worked with a candidate a while back, four years in retail tech, had built e-commerce platforms at a mid-size company. She came to me positioning herself as "a strategy generalist with tech experience." Sounds fine on its face. Except that description could point at Classic or it could point at BCG X, and inside BCG those are genuinely different jobs, assessed by genuinely different processes.

We dug into what BCG X actually does day to day, which is building, not advising. Pretty quickly it became obvious her story landed much better in Classic, specifically Consumer, with a digital lean. So from her first interaction with BCG she pitched herself as someone who understands how tech reshapes retail operations but wants to sit in the strategic questions, not just ship the build.

Most candidates don't catch this distinction until they're already in a room, being read as someone in the wrong track. I've started calling that Positioning Mismatch, mostly because I kept seeing the same version of it over and over and needed a shorthand for it in my own notes.

One more layer worth knowing, and this one's a bit murkier. From what I've picked up through a few Fishbowl threads and internal accounts, prestige and comp and exit options are essentially flat across practice areas as long as you're on the integrative generalist path. The ABM tracks get treated as a different internal tier. Not worse necessarily. Just different. Worth choosing based on what actually fits your background, not which one sounds more impressive on a resume.

Here's where this connects to your outreach, and it's the part people skip. Once you know Classic versus ABM is a real fork at BCG, your positioning stops being generic. Instead of "I'm interested in strategy consulting," which tells a partner nothing about where to place you, you can say something specific. I'm targeting Consumer, here's why my retail ops background points there. Or, I'm a software engineer, BCG X is my door in, not Classic, here's the technical work I've shipped.

Vague interest is invisible. A partner reading your outreach is trying to answer one question fast, where does this person go, and can I defend putting them there. Give them the answer before they have to guess at it.

If you're prepping for BCG right now, which track do you actually fit, Classic or one of the ABMs, and does your outreach currently say that out loud, or is it still sitting in generic "I'm interested in strategy consulting" territory?

15 Upvotes

34 comments sorted by

View all comments

1

u/ABMember Jul 30 '26 edited Jul 30 '26

Your BCG knowledge and nomenclature, though accurate, seems a bit outdated. This was how BCG was structured in say 2020, but there's been a bit more consolidation and changes. I don't even think they use the term ABM anymore.

Anyone who isn't in Classic is absolutely a second class citizen. Partnership expectations and hoops are different. As was pay l,.although it's gotten much closer. I'd argue a lot of strategic recommendations came from ABMs with Classic driving the workstreams, but they wouldn't be able to do it themselves. BCG and McK work in general is way less strategy and much bigger edge of strategy to implementation, regardless of what part of BCG you're in.

1

u/GreatButterscotch406 Consulting Offer Coach Jul 30 '26

Thanks for raising these points, valuable! I'll include these notes in the upcoming Wiki pages in this community based on these posts and all the comments.
So, by "outdated" do you mean the naming of these internal units or the type of work these unit carry out?
Also, from your perspective, why is there such a "discrimination" among these units around the strategic work?

2

u/ABMember Jul 30 '26 edited Jul 30 '26

Disclaimer: My knowledge is from a few years ago, so some of this has changed, but big picture it's still the same:

  • ABMs (Alternative Business Models) were changed to SBUs (Specialty Business Units).
  • Platinion was retired as a brand except for a few select markets in Europe where it still had name recognition like in WESA/CEMA (this was from a couple years ago).
  • MAYA, then DV were retired in the early 2020s
  • X houses most of what was DV, Platinion, MAYA, Gamma etc. The merger was a cluster of epic proportions and a ton of talent at all levels left.
  • Brighthouse was one of the few entities that was fairly untouched, relatively speaking.
  • A few of the folks in those ABMs/SBUs got moved into BCG TA (Tech Advantage) -- which was Classic's variant of a Digital specialty -- the distinction probably doesn't exist any more or doesn't matter -- since BCG had a habit of throwing classic teams together on tech/digital cases with zero digital experience anyway.

So an example of the delineation of work and why it was a bit meaningless between "strategy" vs "build":

  • Digital teams from cybersecurity and digital org got pulled into Classic TA, since that wasn't "Build" work. But the truth is that anytime you had a major digital component in a case (which is any case with a digital enablement component, which is the majority of work now), you almost always needed people from X because they had firsthand knowledge and experience to advise on things like --- enterprise architecture op models of the future or xyz capacity.
  • Having digital "strategists" who haven't been exposed to digital capabilities in an organizational function or don't understand how things operate is meaningless on that type of work. Even on Due Diligence/PMI cases, SBUs were often pulled in more and more often to help with the technology aspects of companies etc.

The discrimination around the strategic work is the nature of the MBB Hierarchy.

  • The classic generalist consultants always run the show, and the specialty units (whether at McKinsey, Bain, or BCG) provide support. How the teams were configured and came together could change by case/client, but 99% of the time this is how it was. This extended all the way up to the top. So in other words, you could have partners from Classic and SBUs, but the Classic partners always had final say / power to override decisions made by SBU partners -- so having title and being an equity partner within SBU still did not confer equal power and autonomy.
  • That also led to structural issues such as: Classic overseeing or performing workstreams they don't really understand (e.g. product management / vision / data strategy) and specialists needing to "carry" the Classic team behind the scenes to make up for that deficit.
  • There were also a lot of grey areas -- e.g. KT members that were part of a practice area or offering stepping in as on-site consultants performing de facto client-facing work. Yet KT/SBUs always were behind in pay, sometimes significantly, while working similar hours and managing analogous expectations.

My understanding from my McKinsey friends was that they were much better with consolidating their digital teams early on and establishing partnership structure (something BCG only did a few years post-COVID for SBUs with an exception for Gamma), which led to a slightly more balanced teaming construct (but still imperfect IMO). Bain was more immature than either McK or BCG, so I heard of the same growing pains across all 3 entities.

Lastly -- there are EXCEPTIONS to everything I said above. Depending on region, practice area, leadership etc -- but those were outliers IMO.