06-reference

commoncog mckinsey consulting origins

2026-07-14·reference·source: Commoncog·by Cedric Chin

How to Build a $3.3 Billion Dollar Consulting Company ... From Scratch

Why this is in the vault

McKinsey is the canonical example of consulting expertise packaged into a replicable methodology at scale — Chin's two new cases trace exactly how that happened, and the moat question he poses maps directly to RDCO's harness-engineering thesis.

The core argument

The McKinsey arc runs in two phases. In the founding phase (1926), James Oscar McKinsey invented "budgeting" as a management discipline, transforming accounting from bookkeeping into a forward-looking control tool — a reframe that gave McKinsey its initial wedge: not accountants, but advisors with a methodology. The second phase belongs to Marvin Bower, McKinsey's successor, who deliberately positioned management consulting as a profession — with rigor, standards, and a replicable problem-solving system. Bower's strategy was deliberate; the WWII demand surge was opportunistic. Chin's central analytical question: has McKinsey's moat held across a century, and what is it actually made of? The companion members-only case ("Scaling McKinsey") covers Bower's professionalization strategy and whether the methodology moat persisted as competitors replicated the form without the underlying rigor.

Mapping against Ray Data Co

Ben's phData DSA role is a direct instantiation of Marvin Bower's core challenge — making consulting judgment legible and transferable at scale without it depending on individual genius. McKinsey's durable asset wasn't any one partner's insight; it was a structured problem-solving methodology, client development protocols, and a people-development system that made expertise reproducible across practitioners. The CLAUDE.md + skills + vault + SOPs stack is RDCO's equivalent: Ray's tacit operational judgment packaged into a methodology the Claude-as-COO agent can execute without reconstructing from scratch each session.

The sharpest tension Chin surfaces is moat durability. McKinsey's methodology advantage eroded as competitors replicated the form (slide decks, frameworks, partner model) without the underlying rigor. RDCO's analogous risk: the harness-engineering methodology layer gets commoditized as frontier models improve and everyone ships CLAUDE.md clones. The McKinsey story suggests the moat in consulting came from people development and selection standards — the process for inducting and calibrating practitioners — as much as from the methodology itself. The open question for RDCO: what is the analog to McKinsey's analyst/associate training pipeline in an AI-native operation?

Secondary connection: McKinsey's initial wedge was a reframe — budgeting as a management tool, not bookkeeping. Ben's phData positioning is the same move: framing AI deployment as a methodology discipline (targeting systems, outcome procurement) rather than a tooling discipline. The wedge creates the category; the methodology creates the moat.

Curation section

Cases announced this issue:

External links:

Member forum highlights: Moat identification on "invisible companies" (cornered-resource businesses hiding in plain sight); investing expertise + NDM knowledge management as a decision-tracking system; Swiss watch capital allocation comparing Hayek vs. Richemont's acquisition strategy; writing expertise improvement program in progress; Cultural Frames underpinning Business Theories (Chin's favorite thread this week).

Related