Aeterna

You built the operation.
You don’t have the infrastructure
to see across it.

I build the operational infrastructure that goes missing when a company outgrows its systems — workforce utilization, service performance, margin by team and service line, across everything you run.

Operational Architecture

Who this is

Built at Meta. Applied privately.

I built the operational visibility infrastructure at Meta for a distributed workforce of 400 technical contract workers and 30 project managers across North America. Performance evaluation. Throughput and quality tracking. Leadership dashboards used to identify where the operation was losing money. Seven production systems. 500 users. M.S. in Statistics. Every finding is measured.

Aeterna applies that same discipline privately, to companies whose operations have outgrown their visibility — systems that each define the numbers differently, commitments that vary by team or acquired brand, and leadership that needs to see across all of it. Capacity is deliberately limited: two concurrent engagements, never more than three retainer clients.

You work with me directly on every engagement.

Currently accepting inquiries for Q4 2026

The deliverable

The Operational Architecture Plan

The Velocity Audit produces a precise, actionable document — not a strategy deck. Every finding is measured from your systems during the audit. Every recommendation is specific enough to build from. The plan quantifies five things:

Operational Architecture Plan — Structure

Measured per engagement

Operational Assessment

Operational Visibility Gaps

Quantified from your systems during the audit — not projected from a template

Utilization variance — how your team's time is actually deployed across the operation
Coordination overhead — hours consumed by manual reporting and cross-team handoffs
Reporting cycle time — how long leadership waits for a complete operational picture
Integration gap inventory — where systems do not talk, and what closing each gap requires
Margin visibility — profitability by team, service line, and contract type

The plan is the diagnosis. The prototype is the proof. Every Audit closes with a working system — built from your data, running on delivery day.

How it works

Diagnose. Build. Sustain.

I

The Velocity Audit

A working prototype, running on delivery day. Not a mockup. Not a promise for the Build phase.

A two-to-three week diagnostic of operational workflows across your teams and systems. I map where visibility breaks down, where data is siloed, where manual coordination is consuming your team's time — and deliver an Operational Architecture Plan specifying exactly what needs to be built.

$25kFlat fee
II

Build

Source code in your repository. Not dependent on me to keep running.

The systems the Audit specified — built, deployed, and documented. Integrations across your existing tools, performance dashboards, cross-team reporting, workflow automation. A visibility layer on top of your existing stack, not a rip-and-replace.

$40k – $100kFlat fee
III

Operational Intelligence Retainer

Monthly operational visibility across your distributed workforce. A Yield Report on what the infrastructure is doing for you — systems health, utilization data, one improvement shipped each month. Available following a Build engagement.

$8k – $12kPer month

Who this is for

This is right for you if —

The engagement roster is deliberately small. Fit matters more than volume.

  • →Your company has outgrown its systems. Through acquisition, headcount growth, or new service lines — the tools that ran the operation at half this size no longer show the whole picture.
  • →You have 50–500 people delivering the work. Distributed teams create the visibility gap this work addresses. Below 50, the problem is manageable. Above 500, the engagement requires a different scope.
  • →Leadership needs operational visibility it does not currently have. Utilization, performance, cost, quality — across the whole operation, not just within each team.
  • →You want systems, not advice. Everything I recommend, I build. The Architecture Plan leads to running infrastructure — not a presentation deck.
  • →Something makes this urgent. A transaction on the horizon, an integration underway, a growth target with a date. The improvements this work delivers are measurable — and they need to be.

Clarity

What Aeterna is not

Not this

  • ×A generic AI strategy presentation
  • ×A team of junior analysts you will never meet
  • ×Recommendations without implementation
  • ×A subscription to software you configure yourself
  • ×A finding you take on faith until the Build begins

This

  • →A diagnostic built from your actual workflows, tools, and data
  • →One practitioner, directly, on every engagement
  • →Running infrastructure delivered, not just proposed
  • →Your code, in your repo, under your control — not a platform you rent
  • →A running system on delivery day — not a promise to build later

The practice

The methodology is proven. The capacity is small.

Aeterna is a new private practice. The methodology is not. I built this exact category of infrastructure at Meta — operational visibility for a 400-person distributed workforce, in production, serving 500 users. You are evaluating the methodology, not the brand.

Two concurrent engagements. Three retainer clients, never more. The capacity is small because the work is deep — and because the person who diagnoses is the person who builds.

Begin here

The Velocity Audit starts
with one conversation.

We speak for 30 minutes. You describe the operational challenge. I tell you honestly whether this engagement is right for your operation.

Begin an inquiry