Operator · Lewisville, TX

I build personal operating systems for people who run multiple things.

A 30-year family restaurant. An AI consulting practice. A household. Investments. Each is a domain. The harness is what holds them together.

Book a discovery call
What I do

I run a restaurant and built the system that runs the restaurant.

Most operators outgrow their tools before they realize the tools are the bottleneck. After two decades watching my family's restaurant grow, I spent the last 18 months building a personal operating system that holds revenue data, vendor invoices, staff certifications, customer loyalty, AI agents, and daily decisions in one coherent layer.

The result: my morning briefing is generated locally by a small AI model at 6 a.m. and reads, more often than not, "Nothing pressing." That's not because nothing is happening. It's because the system is doing the work I used to do in my head.

Compounding — state on disk compounds, state in your head decays PRINCIPLE — COMPOUNDING Write it once. It pays forever. Every logged decision is reusable context. The pile becomes leverage. value time in your head on disk State in your head decays — state on disk compounds
The product

The Harness.

A personal operating system for high-agency people who run multiple things. Three layers.

The three layers of the harness — Vault, Brain, Harness AI The operator reads downward LAYER 03 Harness AI An agent that lives inside your system slash-commands · cron · signals local + cloud models LAYER 02 Brain Living documents that compress state BRAIN.md MEMORY.md CHANGELOG.md PLAYBOOK.md · VOICE.md LAYER 01 Vault Filesystem on hardware you own 12 numbered categories
01 — Vault

One filesystem. Every domain.

Numbered categories standardized across your businesses, your personal life, your investments. Same shape, different content. Lives on hardware you own, not in someone else's cloud.

02 — Brain

Living documents that compress state.

BRAIN. MEMORY. CHANGELOG. PLAYBOOK. A small set of files that hold what's true now, carry decisions forward, and surface decay before it becomes a fire.

03 — Harness AI

An agent that lives inside your system.

Not a chatbot you visit. Local + cloud AI integrated at the substrate level — reads your real state, operates on your real artifacts. Slash commands, cron jobs, morning briefs, autonomous monitors.

"Most mornings my brief reads 'Nothing pressing.' That's not because nothing is happening — it's because the system is doing the work I used to do in my head."
— From a recent Tuesday at 6:02 a.m.
Pricing

Four ways in.

Start with the Foundation kit if you want the methodology + scaffolding. Step up to a done-with-you tier when you need it built around you.

Foundation Start here

DIY starter kit. Vault template, core docs scaffolded, 5 starter slash commands, 45-minute setup video, 30-page operator guide, day-30 email check-in.

$500self-paced
Single domain

Done-with-you. One business plus your personal life, one cron-driven data source, hardware spec'd and configured.

$5,0004 weeks
Multi-domain

Up to three vaults coordinated through a shared bus. For owners running more than one thing.

$10,0006 weeks
Multi-domain + handoff

Above, plus a handoff package built for a partner, spouse, or successor. Bilingual delivery available.

$15,0008 weeks
What working together looks like

Five stages. Eight weeks at the longest.

Discovery call

Thirty minutes. We map your domains, your current tools, your real bottleneck. If it doesn't fit, I'll say so.

Scaffolding

I set up your vault on your hardware, in your environment, with your data. I spec the right machine for your workload, or work with what you have.

Cron-on day

We turn on the automation together and watch it run for a week. Real data, real failures, real fixes.

Operate

You run the system for 2-4 weeks. I'm on call for course corrections, additions, and the inevitable "why is this thing breaking?"

Graduation

The system is yours. The discipline is now habit. We document what comes next — together or on your own.

The 30-day curve — discipline drops sharply at day 14, then recovers The shape of the first thirty days Discipline · Engagement Day 1 Day 3 Day 7 Day 14 Day 21 Day 30 Day 60 Day 90+ Excited Feels like work The hardest day — "consider abandoning" Inflection — system pays back Invisible — just how you operate Risk window · Day 7-21 "If you can survive day 14 with the five-minute discipline intact, you'll make it to day 30."
Writing

Notes on building.

I write about operator-grade AI, family business, the discipline of vault-based work, and the surprises that surface when you put data and intuition next to each other.

June 5, 2026 · 5 min The 17-Day Silence A green light over an empty room: how a job that reported success every night, while doing nothing, taught me to stop trusting status codes. June 5, 2026 · 5 min Nothing Pressing The best thing my system tells me most mornings is that there is nothing to tell me. That sentence took thirty years to earn. June 5, 2026 · 5 min The Bellini Paradox A drink that looked like a money-loser, and the assumption that was lying about it. June 5, 2026 · 5 min The Name That Was a Server A perfect zero is rarely bad luck. Usually it is the data telling you it is not what it says it is.

Book a 30-minute discovery call.

We'll map your situation in real time and decide together whether the Foundation kit, a done-with-you tier, or something else fits. If it doesn't, I'll tell you.

Book a call