Case Study
Financial Decisions Framework
A structured framework for capital allocation and financial decisions across a multi-domain portfolio — applied to operating 7 business domains simultaneously with a single operator and constrained resources.
The problem: capital allocation across unlike domains
Operating 7 business domains with a single operator and finite capital creates a distinct resource allocation challenge. The domains have radically different characteristics: some are revenue-generating today (Blockwise Intelligence, Sandbox Labs client work), some are pre-revenue investments in future positioning (VioletStudios Bloom, UMANO catalog), and some are strategic assets that generate non-financial returns (Master OS, Personal career assets).
Traditional capital allocation frameworks assume comparable domains — comparable risk profiles, comparable timelines, comparable metrics. Applying NPV analysis to UMANO vs. Blockwise Intelligence vs. Master OS produces nonsense because the comparison is structurally invalid. The assets aren't comparable, and the returns aren't denominated in the same unit.
The financial decisions framework addresses this by establishing a decision hierarchy and domain-specific evaluation criteria before doing any cross-domain comparison.
Framework structure
Layer 1: Domain classification
Before any financial decision, classify the domain by its current operating mode:
Layer 2: Decision type classification
Not all financial decisions are the same kind. Three types appear across the 7-domain portfolio:
Fixed-cost commitments with defined terms — subscriptions, contracts, retainers. Evaluated on: monthly cost relative to monthly revenue, cancellation flexibility, and strategic lock-in risk. Default: prefer variable to fixed.
Discretionary spend aimed at growth — ads, equipment, tooling, contractors. Evaluated on: expected return timeline, minimum viable test budget (test before scaling), and portfolio fit (does this investment benefit multiple domains?).
Recurring operational costs — hosting, services, infrastructure. Evaluated on: marginal cost per unit of output, switching costs, and automation potential (can this cost be eliminated by building instead of buying?).
Layer 3: Cross-domain portfolio allocation
After classifying domains and decision types, cross-domain allocation follows a priority order based on current phase:
- Cover operating costs of revenue-positive domains first. Revenue-generating domains should be self-sustaining. If they're not, they're not actually revenue-positive — they're subsidized.
- Fund investment-phase domains by expected value and horizon. Shorter horizon + higher probability = higher priority. Domains with no defined inflection point go on hold, not on a budget line.
- Allocate residual capital to strategic/non-financial domains. Master OS infrastructure and career assets consume time (the scarcest resource) not primarily capital. Capital allocation to these domains is usually about tooling and opportunity cost, not direct spend.
Applied: the 7-domain portfolio in 2026
Applying the framework to the current portfolio as of May 2026:
What this framework produces
The framework's primary output is not a capital allocation table — it's a decision boundary. For any financial decision, the framework answers: which layer does this decision belong to? What domain classification applies? What is the right evaluation criterion for this decision type?
The practical effect: it eliminates analysis paralysis on resource allocation. When a new opportunity or expense arises across any of the 7 domains, the framework provides a structured path to a decision in under 5 minutes — without requiring a full financial model for every decision.
The other output: it surfaces misalignment early. If a domain claims to be investment-phase but has no defined inflection point, the framework forces that conversation. Most "strategic" spend that doesn't produce returns is actually misclassified — it should be in the investment-phase bucket with explicit success criteria and horizon dates.