Business Finance

Operations

Operations & ExecutionDifficulty: ★★★★

an AI native, retail transformation, operations, and holding company

You inherit P&L ownership for three retail brands the Holding Company acquired last quarter. Combined Revenue: $180M. Combined EBITDA: negative $4M. Each brand runs its own warehouse, its own customer service team, its own buying process. The PE operators want positive EBITDA in 18 months. You have one shared technology team and a mandate to automate everything that doesn't require human judgment. The question isn't what to build - it's what to consolidate, what to automate, and what to leave alone.

TL;DR:

Operations is the sustained system that converts a Holding Company's Capital Allocation into repeatable P&L outcomes across every brand it owns. In a PE-Backed retail Portfolio, the Operator's job is to build shared infrastructure, deploy automation to replace Commodity Labor, and create Unit Economics that no standalone competitor can match.

What It Is

Operations is the machinery that sits between Capital Allocation decisions and P&L results - not for a single quarter, but permanently.

You already know Execution converts decisions into outcomes. Operations is what makes Execution repeatable. If Execution is scoring a goal, Operations is building the training program, the scouting Pipeline, and the stadium.

In a Holding Company running a Multi-Brand Portfolio, Operations has a specific meaning: the shared systems, processes, and teams that serve every brand in the Portfolio. This includes:

  • Shared technology - one engineering team building tools deployed across N brands
  • Shared back-office - consolidated finance, HR, and Compliance Risk functions
  • Shared fulfillment - warehouses and logistics serving multiple brands from the same infrastructure
  • Brand-specific Execution - merchandising, marketing, and customer experience stay with each brand

The automation thesis: this generation of Operations replaces Commodity Labor with software wherever the task is structured and repeatable. Not as a Cost Reduction exercise alone - as a structural Competitive Advantage that compounds over time through the Feedback Loop of every transaction making the system smarter.

Why Operators Care

Every line on the P&L is an operational output. Revenue depends on whether your Pipeline converts. Costs depend on whether your processes are efficient. Profit is the residual - and the Operator controls every lever between the top line and the bottom line.

Here's why Operations at the Holding Company level matters more than Operations at a single brand:

1. Cost sharing creates structural Unit Economics. If you build an automated customer service system for Brand A, deploying it to Brands B and C costs almost nothing. Your Cost Per Unit drops with every brand you add. A standalone competitor has to build and pay for the same capability alone.

2. Operating Value is what buyers pay for. When a PE-Backed Holding Company exits, the Valuation reflects whether the buyer believes the Operations machine will keep producing results. An Operator who built repeatable systems commands a higher Valuation than one who reached the same EBITDA through one-time cuts. Repeatable EBITDA backed by systems is Operating Value. One-time cuts are tactical - they don't survive the next disruption.

3. Throughput determines everything. The Operator's job is to maximize Throughput - the rate at which the organization converts inputs (Labor, inventory, Capital Investment) into outputs (Revenue, Cash Flow, CSAT). Every Bottleneck you identify and clear is a direct P&L improvement.

How It Works

Running Operations in a PE-Backed retail Holding Company has three layers:

Layer 1: Identify What Shares and What Doesn't

Not everything should be consolidated. The decision rule is simple:

  • Consolidate functions where the work is identical across brands (finance, legal, technology infrastructure, warehousing)
  • Keep separate functions where brand differentiation matters (creative, merchandising, brand identity, customer experience)

Consolidation is where the Unit Economics advantage lives. Every shared function spreads its costs across more brands, driving down the Cost Per Unit per brand. The cost of the shared technology team is part of your Cost Structure regardless of whether you serve 3 brands or 8 - but the cost per brand drops as the Portfolio grows.

Layer 2: Build Automated Processes

Automation in this context doesn't mean 'add a chatbot.' It means redesigning processes so the default path is handled by software and humans handle Exception Review.

Concrete pattern:

  1. 1)Map the process (e.g., customer service ticket resolution)
  2. 2)Measure the defect rate of current human handling
  3. 3)Build a system that handles the Commodity cases (password resets, order tracking, return labels)
  4. 4)Route exceptions to humans with full context
  5. 5)Measure the new defect rate and Cost Per Unit

This is Workforce Transformation. Be honest about what that means: roles are eliminated. If you automate 60% of ticket volume, you need fewer agents. The Operator's responsibility is to execute this with appropriate severance, retraining investment, and a reasonable timeline - not to pretend the reduction isn't happening. The remaining roles are harder, higher-value, and typically higher-paid. Throughput goes up and Cost Per Unit goes down, but only if you handle the human side with integrity.

Layer 3: Graduated Autonomy

Brand general managers need freedom to run their brands, but the Holding Company needs consistency in financial controls and Quality Systems. Graduated Autonomy solves this:

  • Centralized controls: Chart of Accounts, Budget approval thresholds, Quality Gates on vendor selection
  • Decentralized decisions: Pricing within guardrails, marketing creative, customer segmentation, local inventory mix
  • Escalation triggers: any decision above a dollar threshold or outside policy goes to Exception Review

This structure lets the Operator scale oversight across 5, 10, or 20 brands without scaling headcount linearly.

When to Use It

You're building Operations infrastructure - not just executing - when:

1. Turnaround situations. A PE-Backed acquisition with negative EBITDA needs an Operations overhaul, not just Cost Reduction. Cutting costs without building systems means you'll need to cut again next year. Build the machine that produces lower costs permanently.

2. Post-acquisition integration. After an acquisition joins the Multi-Brand Portfolio, the Operator has to decide what to consolidate and what to leave independent. Get this wrong and you destroy the brand's value through lost differentiation. Get it right and Unit Economics improve immediately because the new brand's volume flows through existing shared infrastructure.

3. Scaling beyond what humans can manage. When Pipeline Volume or order volume outgrows your team's capacity, adding headcount linearly is the wrong answer. Build automated processes that scale with volume while headcount stays flat. This is where Competitive Advantage compounds.

4. Building Operating Value before an exit. If the Time Horizon to a sale is 18-36 months, the Operator needs to show that EBITDA improvements are structural (built into Operations) rather than tactical (one-time cuts that revert). Buyers pay a higher Valuation for Operating Value backed by repeatable systems because they're buying future Cash Flow, not past Cost Reduction.

Worked Examples (2)

Consolidating Customer Service Across Three Brands

The Holding Company owns three retail brands. Each runs independent customer service:

  • Brand A: 40 agents, $2.8M/yr cost, 200K tickets/yr
  • Brand B: 25 agents, $1.75M/yr cost, 120K tickets/yr
  • Brand C: 30 agents, $2.1M/yr cost, 150K tickets/yr

Total: 95 agents, $6.65M/yr, 470K tickets/yr. Average Cost Per Unit per ticket: $14.15. CSAT scores average 72%.

  1. Measure the Bottleneck. Audit ticket types across all three brands. Finding: 62% of tickets are Commodity work (order status, return labels, password resets). 38% require human judgment (complaints, damaged goods, policy exceptions).

  2. Build the shared system. Deploy one AI-powered Triage system that handles the 62% Commodity tickets automatically. Implementation Cost: $400K one-time build by the shared technology team. The same system serves all three brands.

  3. Right-size the human team. 62% of 470K tickets = 291K automated. Remaining 179K tickets need human agents. The AI pre-loads context for human agents, boosting productivity from ~5K to ~6.5K tickets/agent/yr. New headcount: 179K / 6.5K = 28 agents. That means 67 roles are eliminated. Plan for severance, retraining offers, and a phased timeline.

  4. Calculate the new Cost Structure. 28 agents at ~$70K Total Compensation = $1.96M/yr. AI system maintenance: $180K/yr. Amortized build cost: $400K over 2 years = $200K/yr. Total: $2.34M/yr. New Cost Per Unit: $2.34M / 470K = $4.98 per ticket (down from $14.15).

  5. Decompose the CSAT impact. Commodity tickets (62% of volume) get instant resolution - expect ~95% CSAT on those. Exception tickets (38% of volume) are now handled by a smaller team managing only the hardest cases with less institutional backup - expect CSAT to hold at ~72%, possibly lower during the transition. Blended CSAT estimate: (0.62 × 95%) + (0.38 × 72%) = ~86%, up from 72% overall. Monitor exception ticket CSAT separately - if it drops below 68%, you have a Service Recovery problem to address.

  6. Measure the P&L impact. Annual savings: $6.65M - $2.34M = $4.31M/yr EBITDA improvement, with the Amortized build cost already included in the $2.34M total.

Insight: To see why the Holding Company structure matters, run the math for Brand A going it alone. Brand A has 200K tickets. 62% automated = 124K. 38% need humans = 76K tickets. At 6.5K tickets per agent: 76K / 6.5K = 12 agents at $70K = $840K. But standalone, Brand A bears the full $400K build (Amortized at $200K/yr) and the full $180K maintenance. Standalone total: $840K + $200K + $180K = $1.22M/yr. Brand A's current cost is $2.8M, so standalone savings = $1.58M/yr. That's meaningful on its own. But the shared approach saves $4.31M across all three brands from the same $400K Capital Investment. Same build cost, 2.7x more P&L impact. That ratio widens with every brand added to the Portfolio.

Shared Technology Team ROI Across a Growing Portfolio

The Holding Company employs a 20-person technology team costing $4M/yr. The Portfolio currently has 4 brands. A fifth brand is being acquired. The PE operators ask: does the shared technology team need to grow?

  1. Current cost per brand. $4M / 4 brands = $1M/brand/yr in technology overhead. Each brand's standalone competitor spends $800K-$1.2M on an equivalent internal team. At $1M/brand, the Unit Economics advantage is modest.

  2. Add Brand 5 without adding headcount. The shared team's existing tools (Inventory Control system, customer service automation, reporting dashboards) deploy to Brand 5 with configuration work, not new builds. Estimate: 2 engineers for 6 weeks = ~$60K in Labor, plus $20K in infrastructure. Total one-time Implementation Cost: $80K.

  3. New cost per brand. $4M / 5 brands = $800K/brand/yr. Each brand now gets $1M+ worth of technology capability for $800K. The Competitive Advantage widens with every brand added.

  4. Project forward to 8 brands. Add 2 more engineers ($400K/yr) to handle increased support load. New total: $4.4M / 8 brands = $550K/brand/yr. Standalone competitors still pay $800K-$1.2M. The Unit Economics gap is now $250K-$650K per brand per year - a structural competitive moat.

Insight: The technology team's cost doesn't scale linearly with the number of brands it serves. Each new brand acquisition improves the Unit Economics of every existing brand. This is why Holding Company Operations creates a Competitive Advantage that standalone Operators cannot replicate - the cost per brand decreases as Portfolio size grows, while the capability delivered stays constant or improves.

Key Takeaways

  • Operations is the system that makes Execution repeatable. Building it is a Capital Investment; running it produces ongoing EBITDA improvement.

  • In a Holding Company, the Operator's structural edge is building capabilities once and deploying across N brands. This drives Unit Economics that standalone competitors cannot match.

  • Workforce Transformation means roles are eliminated. The Operator's job is to execute honestly - with severance, retraining, and timelines - while building automated systems that scale Throughput without scaling Labor costs linearly.

Common Mistakes

  • Consolidating brand-specific functions. Merging three brands' marketing teams into one 'shared' team destroys differentiation and brand identity. The decision rule: consolidate Commodity work (finance, technology, logistics), keep judgment work and creative at the brand level. If you erase what makes the brand distinct, you've destroyed the Asset you acquired.

  • Treating automation as a one-time Cost Reduction project. An Operator who deploys automation to cut costs and then moves on misses the compounding effect. Automated Operations is a Feedback Loop - every ticket the system handles generates data that improves future Triage accuracy, which handles more cases correctly, which generates more data. One-time savings are tactical; a compounding Feedback Loop builds a Data Moat that is structural Operating Value.

Practice

medium

A Holding Company owns 6 retail brands. Each brand independently runs its own returns processing: receiving returned goods, inspecting quality, restocking or disposing, and issuing refunds. Combined volume is 800K returns/yr. The current average Cost Per Unit is $11.50 per return ($9.2M/yr total). You estimate that 70% of returns can be auto-processed (photo inspection, auto-refund, auto-routing). The shared system costs $600K to build and $150K/yr to maintain. Human agents cost $65K/yr in Total Compensation and currently handle ~4K returns each. With AI pre-screening, human productivity rises to ~5.5K returns/yr. Calculate the annual EBITDA impact and the new Cost Per Unit for the shared model. Then calculate what a single standalone brand (handling ~133K returns/yr at $11.50 each) would save building the same system alone - bearing the full $600K build and full $150K/yr maintenance.

Hint: For the shared calculation: figure out humans needed for the 30% requiring judgment (240K / 5,500 per agent), then total Cost Structure = agents + maintenance + Amortized build. For the standalone calculation: the single brand bears the FULL build cost and FULL maintenance - don't divide those by 6.

Show solution

Shared model (6 brands, 800K returns):

70% automated = 560K returns handled by software. 30% need humans = 240K returns. At 5.5K returns per agent: 240K / 5.5K = 44 agents. Agent cost: 44 × $65K = $2.86M. Maintenance: $150K/yr. Amortized build: $600K / 2 years = $300K/yr. New total: $3.31M/yr. Cost Per Unit: $3.31M / 800K = $4.14 per return (down from $11.50). EBITDA impact: $9.2M - $3.31M = $5.89M/yr savings.

Standalone brand (133K returns, $1.53M current cost):

70% automated = 93K. 30% need humans = 40K. At 5.5K per agent: 40K / 5.5K = 7.3, round up to 8 agents. Agent cost: 8 × $65K = $520K. Maintenance: $150K/yr (full cost, no one to share with). Amortized build: $600K / 2 = $300K/yr (full cost). Standalone total: $970K/yr. Savings: $1.53M - $970K = $560K/yr.

The contrast: the shared approach yields $5.89M in annual savings from one $600K build. The standalone brand yields $560K from the same $600K build - a Payback Period over a year just for the build cost. Per brand, the shared model saves ~$982K/yr ($5.89M / 6) vs $560K standalone. The Holding Company gets 75% more savings per brand because the Capital Investment is Amortized across 6x the volume.

hard

You're evaluating whether to add a 7th brand to the Holding Company's Portfolio. The shared Operations infrastructure (technology, finance, customer service) currently costs $12M/yr serving 6 brands. Adding Brand 7 would require $200K in one-time integration costs and an estimated $400K/yr in incremental support costs. Brand 7's standalone Operations cost is $3.2M/yr. What is the benefit to Brand 7, and how does the addition change Unit Economics for the existing 6 brands? (Note: equal Allocation is used here for clarity. In practice, you would allocate by usage volume or Revenue weight - brands with more transactions or higher Revenue bear a proportionally larger share of shared costs.)

Hint: Think about Allocation of the shared cost. Before Brand 7: $12M / 6 = $2M per brand. After Brand 7: ($12M + $400K) / 7 brands. Compare Brand 7's new allocated cost to its standalone $3.2M. Then check what happened to the per-brand cost for existing brands.

Show solution

Before Brand 7: Shared cost = $12M / 6 brands = $2M per brand.

After Brand 7: Shared cost = ($12M + $400K) / 7 brands = $12.4M / 7 = $1.77M per brand. (In practice, this Allocation would be weighted by each brand's usage or Revenue rather than divided equally - equal division is shown here to isolate the structural effect.)

Brand 7's benefit: Standalone cost was $3.2M. Allocated shared cost is $1.77M. Savings: $1.43M/yr (a 45% Cost Reduction). The $200K one-time integration cost has a Payback Period under 2 months.

Existing brands' benefit: Per-brand cost drops from $2M to $1.77M. Each existing brand saves $230K/yr. Total benefit to existing Portfolio: 6 × $230K = $1.38M/yr.

Total value created: $1.43M (Brand 7 savings) + $1.38M (existing brand savings) = $2.81M/yr in aggregate EBITDA improvement from adding one brand to existing shared Operations. This is why PE operators acquire aggressively into an existing Operations platform - every new brand improves the Unit Economics for the entire Portfolio, and the surplus created far exceeds the incremental cost.

Connections

Operations builds directly on all three prerequisites. The P&L gives you the scorecard - every operational improvement shows up as a Financial Statement Line Item change in cost or Revenue. Execution taught you that output only counts if it moves Revenue or Profit; Operations is the system that sustains Execution quarter after quarter without heroics. The Holding Company structure is what makes Operations powerful - shared infrastructure across a Multi-Brand Portfolio creates the compounding Unit Economics advantage that defines the Operator's job. From here, the concepts branch into specifics: EBITDA Optimization is the tactical discipline of improving Operations line by line, PE Portfolio Operations and Turnaround are the contexts where you deploy these skills under time pressure, Knowledge Capital is the long-term Asset your Operations machine builds as institutional knowledge accumulates, and Data Moat is the Competitive Advantage that compounds as every transaction your automated systems process makes the Feedback Loop smarter and harder for competitors to replicate.

Disclaimer: This content is for educational and informational purposes only and does not constitute financial, investment, tax, or legal advice. It is not a recommendation to buy, sell, or hold any security or financial product. You should consult a qualified financial advisor, tax professional, or attorney before making financial decisions. Past performance is not indicative of future results. The author is not a registered investment advisor, broker-dealer, or financial planner.