Establishing Catalog Visibility

Strategic intent: Give an internal unit, for the first time, an honest answer to "what do we do, for whom, and what does it cost us?" — without yet introducing prices. Everything downstream depends on this baseline.

#Overview

This is Layer 0 of the Adopting Distributed P&L pipeline. It combines two activities that belong together:

1. Cost tagging — attributing every cost element to the internal client it serves.
2. Service catalog definition — naming services, defining scope, identifying consumers, classifying by type.

The deliberate constraint of Layer 0 is the absence of prices. The unit knows its costs and its services but has assigned no price to anything. There is no P&L, no revenue concept, no simulation. The single goal is visibility.

This is the first product thinking for the unit: the shift from "we do things for people" to "we offer these specific services to these specific clients."

#When to use it

• As the mandatory first step of any P&L-adoption transformation (no layer can be skipped)
• When an internal service is treated as overhead and "cannot answer whether it is efficient or valuable"
• When the organization suspects consumption asymmetries hidden by annual budget allocation
• Before any pricing, showback, or chargeback conversation

#Composition

1. #1. Tag the cost base to internal clients

   For each cost element, attribute it to the internal client(s) it serves:

   • Personnel — time sheets; every hour tagged to the internal client it was dedicated to
   • Software licenses — allocated per user or per unit
   • External services (auditors, consultants) — attributed to the consuming unit

   Directional accuracy (±10%) is sufficient at this stage. Precision improves organically as the habit forms.

2. #2. Name and scope the services

   Move from "we support the business" to a concrete list: name each service, define its scope and boundaries, identify who consumes it and how often.

3. #3. Classify each service by type

   Assign one of four types — the classification drives later pricing and consultation logic:

   • Tax — mandatory, algorithmic, allocation-formula based (consumers cannot refuse)
   • Subscription — recurring access to a capability
   • Unit Consumption — priced per unit consumed
   • On-Demand — negotiated per engagement

4. #4. Publish the catalog and the cost map

   Produce a complete cost map distributed across internal clients, plus a published catalog with names, scopes, consumers, frequencies, and types. The unit can now state: "We offer these N services; we spent $X on Unit A, $Y on Unit B; here is what each involves."

#Inputs

• Required: access to the unit's full cost base (personnel, licenses, external spend)
• Required: the unit team's time to articulate what it actually does
• Recommended: a node classification (differentiating / supporting / generic) to frame later targets

#Outputs

• Cost map — every cost element tagged to a consuming internal client
• Published service catalog — names, scopes, consumers, frequencies, type classifications
• Asymmetry findings — consumption imbalances invisible under budget allocation
• Scope-ambiguity register — boundary violations and informally delivered services surfaced

#Process heuristics

• A spreadsheet is enough. Layer 0 does not require sophisticated tooling — the goal is visibility, not precision.
• Cost tagging is information quality, not accounting. Aggregate cost ÷ volume gives a rough price without tagging; tagging is what reveals who consumes disproportionately, which sub-activity is expensive, when costs concentrate.
• Expect surprises. One internal client consuming 60% of capacity while another consumes 5% is the typical first revelation.
• Name the informal services. Services delivered without acknowledgment are the ones that distort everything later.

#Validation criteria

• Every material cost element tagged to at least one internal client
• Service catalog published with scope, consumers, frequency
• Each service classified as Tax / Subscription / Unit Consumption / On-Demand
• No prices assigned (Layer 0 discipline preserved)
• Consumption asymmetries explicitly documented

#Common mistakes

• Jumping to prices — pricing belongs to Layer 1; doing it here skips the visibility discipline
• Over-engineering precision — ±10% is fine; perfectionism stalls the transformation
• Ignoring informal work — unacknowledged services break later pricing accuracy
• Skipping classification — service type drives downstream pricing and negotiation logic

#Used in pipelines

• Adopting Distributed P&L — as Layer 0

#Connections

• Feeds: Running the Shadow P&L — Layer 1 derives prices from this cost data
• Cascades to: every unit that provides inputs to the pilot must also begin Layer 0 (the cascading-dependency problem)

#Related reading

• Boundaryless field methodology "The P&L Adoption Mechanism: From Cost Center to Autonomous Unit"
• Legacy 3EO Toolkit — node classification and the platform-organization topology