Italian lake architecture reflected in still water

Portfolio Architecture

The portfolio should reflect the institution—not the other way around.

MCO converts objectives, liabilities, liquidity, taxes, and existing holdings into a role-based architecture that can be implemented, monitored, and explained.

The Design Question

What must the capital do—and when must it do it?

Allocation begins with purpose. A family office may need liquidity for taxes, capital calls, and distributions while preserving strategic holdings. An RIA may need scalable models that remain tax-aware across households. A fiduciary institution may need spending support or liability alignment. The architecture is built from those obligations outward.

Core Workstreams

From balance sheet to investable structure.

01

Capital Segmentation

Separate operating liquidity, near-term distributions, strategic reserves, long-horizon growth, and opportunistic capital before selecting investments.

02

Allocation & Risk Budgets

Define target exposures, sleeve roles, acceptable drawdown, concentration limits, liquidity bands, and the return engine expected from each allocation.

03

Public / Private Integration

Treat private commitments, direct holdings, real assets, and public portfolios as one economic system rather than parallel reporting silos.

04

Tax-Aware Design

Coordinate gain budgets, tax lots, charitable strategies, completion portfolios, direct indexing, and asset location with qualified tax professionals.

05

Transition Sequencing

Move from the current portfolio to the target architecture in a sequence that respects taxes, liquidity, market impact, operational dependencies, and decision capacity.

Cypress-lined road in Tuscany

Architecture Standard

The optimal spreadsheet is not always the optimal portfolio.

Implementation Reality

A portfolio is only institutional if it can survive implementation.

Theoretical precision can destroy value when it ignores tax basis, redemption terms, capital calls, custody, market impact, or governance capacity. MCO treats those constraints as design inputs—not as problems discovered after the recommendation is approved.

  • Explicit liquidity reserves and capital-call coverage
  • Role-based benchmarks and monitoring standards
  • Staged transition paths with decision gates
  • Portfolio look-through across funds, entities, and managers
  • Documented rebalancing ranges and exception rules

Representative Deliverables

A portfolio map that can be governed.

Capital segmentation and liquidity ladder
Strategic allocation and sleeve-role map
Look-through exposure and concentration analysis
Tax-aware transition sequence
Public/private commitment and pacing view
Rebalancing ranges, benchmarks, and review triggers
Discuss a portfolio architecture mandate

Confidential Dialogue

A coherent portfolio begins with a coherent purpose for capital.

The first conversation is used to define the decision problem, the existing constraints, and whether MCO's perspective can add value.

Start a Conversation