Xavi Ablaza

P&L engineer, technical founder, and operating-systems builder for engineering organizations.

P&L engineering × technical leverage

Every operating decision is a P&L decision.

P&L engineering is the discipline of turning technical work into margin, velocity, resilience, and option value — with enough financial language that the bet can be compared against every other bet.

P&Ltechnical decisions expressed as margin, cash, risk, and option value

5 loopsmap, price, allocate, ship, compound — measured together

1 graphcustomers, product, systems, teams, spend, and ownership connected

The System

Map→ Price→ Allocate→ Ship→ Compound

Five steps, applied to every platform, team, process, and reliability decision. The loop does not stop after the migration ships.

The Operator

Allocator· Operator· Builder· Scientist

Four lenses, each common alone — the combination is what compounds.

Build the P&L engineering substrate

I work on organizations where engineering is no longer just delivery capacity: it is the control plane for margin, reliability, cost, trust, velocity, and organizational learning.

Email GitHub LinkedIn

01 Map

Your engineering organization is a dependency graph →

Services, teams, cloud accounts, incidents, deploy paths, vendors, and approval queues form a directed graph. Walk the edges and the real bottlenecks become visible.

02 Price

Price reliability, toil, and velocity in dollars →

Every platform project has expected return, variance, delay cost, blast-radius reduction, and maintenance drag. If you cannot price the queue, you cannot defend the roadmap.

03 Allocate

Construct the engineering portfolio →

Rank infrastructure bets by risk-adjusted return, sequence by dependency, and account for correlation: same team, same stack, same vendor, same reviewer queue.

04 Ship

Systems that converge by construction →

Design rollout gates, incident budgets, migrations, and autonomy levels so improvement is ratcheted into the workflow instead of requested in retro notes.

05 Compound

Build the appreciating asset →

Cloud credits burn. Dashboards rot. But runbooks, verifiers, golden paths, labeled incidents, and deployment muscle can appreciate through use.

Frameworks

The Factory Typology →Knowledge work is manufacturing — but which factory? Name the input, process, and output signature, then borrow the mature operating playbook. Your Chart of Accounts Is a Directed Graph →Every cost and revenue line is a node. Every causal relationship is an edge. Walk the graph and find the mispriced edges where value leaks. The Performance Frontier →Locate where excellence lives when nobody agrees what good looks like: map the distribution, find the 99th percentile, compute the gradient. The Demand Field →Demand is a force field on the optimization landscape. It is fixed, hidden, and acts on the product whether you measure it or not. Capital Allocation →Every operating decision is a capital allocation decision. Rank instruments by risk-adjusted return, map tolerances, and construct the portfolio. Kill Protocol →The allocator skill is saying no: marginal Sharpe, left-tail survivability, and base-rate verification before a bet consumes the slot. The Operating Efficient Frontier →The set of portfolios that maximize expected return at each risk level. Points below the frontier are dominated; the question is which point you choose. The Risk Tolerance Map →Map cash, runway, covenants, and narrative constraints into the preferred point on the efficient frontier. Different firms can correctly choose different points. Correlated Execution Risk →Operating portfolios are not sums of individual NPVs. Shared teams, stacks, vendors, and review queues create shared failure modes. Designed Convergence →Design the game so convergence to the desired outcome is structural, not aspirational. Mechanism design meets Bayesian ratchet search. The Deity Problem →Your AI is trying to serve you but cannot read your mind. Use structured elicitation, revealed preference, and direct query to learn what the operator wants. Quality Hillclimb →Apply ratcheted quality gates to stochastic agent output. The agent does not need a plan — the gates create ascent. The Promotion Protocol →A three-state progression for safely giving AI more independence. Promote on demonstrated performance; roll back on drift. Knowledge Work as Capital →Every piece of knowledge work either compounds or depreciates. Models decay; data, verifiers, and rubrics can appreciate through use. The Capital Value of Verifiers →The verifier is one of the rare capital assets that appreciates through operating use: every failure it catches gets encoded into the next run.

Concept Graphs

Curated

Frameworks →Nine-plus strategic models for finding, pricing, and allocating operating value. Tools →Interactive calculators for pricing operating instruments — diagnose, calibrate, invest, value, and screen. Lexicon →Defined terms invented to name operating realities that existed but had no shared word. Positions →Four overlapping circles — Allocator, Operator, Builder, Scientist — and the intersections where the value lives. Thesis →The full lattice: every framework, tool, and term organized by allocation stage. Knowledge graph →Interactive map of how frameworks, tools, terms, positions, and posts connect.

Dense

Math + ML →Concepts from arithmetic to transformers, ordered by dependency with interactive visualizations. Money →Personal-finance decisions structured as a dependency tree — the why behind the standard flowchart. Visualizations →Animated and interactive concept surfaces in the local getablaza content graph.