Running the Shadow P&L

Strategic intent: Give the unit a financial language for its contribution — and give consuming units a mirror — without yet moving any money. This is the constrained-autonomy space where the mindset shift becomes tangible.

#Overview

This is Layer 1 of the Adopting Distributed P&L pipeline. Building on the catalog and cost map from Layer 0, the unit derives prices, runs a shadow P&L (virtual revenue alongside real costs), and issues showbacks to consuming units.

No money changes hands. But the economics become visible for the first time — and visibility alone changes behaviour on both sides. Layer 1 is constrained autonomy: the unit behaves as if it were a business (making portfolio and pricing decisions, responding to showback signals) while the organization retains actual financial control.

#When to use it

• After Layer 0 is complete and validated (prices need a cost map to derive from)
• When the unit needs a financial identity to think strategically about its own portfolio
• When consuming units behave as if internal services are free
• As the trust-building stage before any real chargeback (Layer 2)

#Composition

1. #1. Choose the unit of measure per service — the pivot

   Cost is a pool; price is a ratio — and the denominator does not exist until someone chooses it. For each catalog service, decide what one unit of it is (an employee-month, a processed claim, a report, a subscription-month, an engagement). This is a semantic choice with behavioral consequences, not a fact to discover. Services split into two piles:

   • Shared overhead (consumed by everyone regardless of volume) — the "unit" is an allocation base (per employee, per revenue, fixed) and the price is whatever makes year-end totals reconcile: the tax model.
   • Demand services (consumed unit by unit) — the unit is a real consumption unit, and pricing requires the volume-and-consumer census from Layer 0: how many units were delivered, to whom. No census, no price, no showback.

2. #2. Derive cost-recovery prices

   The initial price for each service is arithmetic: service cost ÷ units delivered. A capability that cost $100,000 and produced 10 reports yields a $10,000 report. This is cost-recovery, not market pricing — the goal is equivalence, not margin.

3. #3. Run the shadow P&L

   Maintain a parallel financial view: virtual revenue (prices × volumes) alongside real costs (Layer 0 tagging). The unit can now say: "If we were a business, our revenue would be $X and our costs $Y." Keep the cost-based and price-based views simultaneously — the gap between them reveals inefficiencies and cross-subsidies invisible in either view alone.

4. #4. Issue showbacks to consuming units

   Send virtual invoices: a business line that saw "$0 for finance" now sees "$30,000/yr financial reporting, $22,000/yr statutory compliance, $8,000/yr budget support." No money moves; the information creates symmetry — both sides now see the same economic reality. Put a reconciliation view next to the showbacks (every unit's bill, summing to the provider's total cost): the first question anyone asks is "do the books balance?"

5. #5. Run "what-if" scenarios

   Model the consequences of raising a price, adding a service, or dropping one. This is where the unit develops judgment about its own economics — judgment that was impossible without an economic language for the work.

6. #6. Declare a pricing intention per service — where accounting becomes strategy

   Only now, with a working flat price as the anchor, the unit declares how it intends to price each service going forward:

   Intention	The rule	What it signals
   Utility	the cost-based price IS the price; the promise is reliability (SLA), not features	"competes on dependability"
   Tiered	basic vs premium versions of the same service, priced differently	"demand is segmented; let users self-select"
   Shaped	the price structure corrects the behavior that creates the cost (banded/slab prices)	"pricing is a governance instrument"
   Product	the service aims at external customers and real margin	"a business in incubation"

   Two mechanics make this safe:

   • Redistribution within breakeven. For a breakeven-mandated unit, Tiered and Shaped don't break the no-internal-margin rule: they redistribute the same total (Σ price × volume = service cost stays sacred) — the choice is only who pays which share. Premium subsidizes basic; the structure now carries information and incentives.
   • The product gate. Only Product legitimately breaks the breakeven ceiling — and only on external sales, after a sustained internal SLA track record. Declaring it changes no price tomorrow; it opens a workstream toward the gate.

   The flagship rule: first pass, mark intentions only (minutes per service); deep design (tier prices, slab curves) for 2–3 flagship candidates at most — everything else stays Utility until there's a reason.

#Inputs

• Required: completed Layer 0 cost map and typed service catalog
• Required: tentative input prices from dependency units (rough estimates are acceptable)
• Recommended: node classification (sets the expected shadow result — breakeven for generic, small margin for supporting)

#Outputs

• Service prices — cost-recovery prices for every catalog item
• Shadow P&L — virtual revenue minus real costs
• Showback reports — virtual invoices for consuming units
• Scenario models — pricing / portfolio "what-if" analyses

#Process heuristics

• Cost-recovery first. Don't chase margin at Layer 1; equivalence is the point.
• Have the deficit reframe ready. The unit's first reaction to a computed price is fear of structural deficit — prepare the answer before the numbers appear: for a generic internal unit there is no market price to be "in deficit" against; breakeven is the target by construction, and the price IS what covers the cost.
• Order-of-magnitude surprises are the product, not a bug. Expect computed prices to differ wildly from the unit's own guesses (a factor of 50 is not unheard of); treat the gap as the agenda for the next iteration — allocation too coarse? the guess covered a sub-service?
• Parallel accounting is a feature. The cost↔price gap is the most valuable diagnostic the unit gets.
• Showbacks change behaviour without money. Consumers start weighing what they request; providers start seeing themselves as value-producing.
• Lead with "same total, fairer shares, better incentives" — never with "premium pricing". The redistribution-within-breakeven argument must land before the tiering conversation starts, or the room's ethical reflex ("aren't we monetizing colleagues?") shuts it down.
• Harvest the unit's own prior reasoning. Seed each service's intention with ideas the team already voiced (a slab proposal, a basic/premium split) — the exercise becomes recognition, not imposition.
• Intention first, design second, ratification third. The unit proposes intentions; resulting price structures enter the catalog and the VAM through governance ratification. The intention sheet is a strategy document, not a tariff decree.
• Sequence circular prices. When Unit A's price is an input to Unit B and vice versa, set provisional prices, respond, iterate to convergence.

#Validation criteria

• Every catalog service has a declared unit of measure (allocation base for overhead, consumption unit for demand services)
• Volume-and-consumer census available for every demand service
• Every catalog service has a cost-derived price
• Shadow P&L maintained (virtual revenue vs real cost)
• Showbacks delivered to all consuming units on a regular cadence
• At least one "what-if" scenario produced
• A pricing intention (Utility / Tiered / Shaped / Product) declared per service, with 2–3 flagships selected for deep design
• Incentives tied to operational maturity, not virtual financials

#Common mistakes

• Treating the shadow P&L as real — no money moves at Layer 1; promising otherwise destroys trust
• Pricing for margin too early — distorts the cost-recovery baseline
• Skipping showbacks — without the mirror, consuming behaviour never changes
• Tying bonuses to virtual revenue — invites gaming; reward process maturity instead
• Treating the first price as the end state — flat cost-recovery forever misses that pricing is a design surface (the four intentions)
• Letting intentions drift into price-setting — units want to set tier prices and slab curves immediately, before volumes and behavior data justify them; hold the flagship line

#Used in pipelines

• Adopting Distributed P&L — as Layer 1

#Connections

• Requires: Establishing Catalog Visibility — Layer 0 provides the cost data prices are derived from
• Feeds: Reaching Financial Autonomy — the shadow P&L becomes the real P&L at Layer 2

#Related reading

• Boundaryless field methodology "The P&L Adoption Mechanism: From Cost Center to Autonomous Unit" — the parallel-accounting insight and the bidirectional meeting point
• Legacy 3EO Toolkit — the Value Adjustment Mechanism and contract patterns