O
Observe
See the work where it happens, not where the process map says it happens.
40+
Tools shipped to production
Operations · systems · technology
Fewer moving parts. Better operations.
We find where a business is losing time, money, or confidence in its numbers. Then we remove the unnecessary work and build a system that keeps the fix in place.
How the work moves
Observe
Verify
Reduce
Build
Measure
Understand the operation.
Build only what earns its place.
100s
Manual hours automated away
4
Ways to engage
1
Owner from diagnosis to delivery
Working sequence
Understand the work before changing it.
We start with the operating reality: sit with the people doing the work, trace the process and the numbers, remove what adds no value, then build the smallest durable fix. First-principles reasoning guides the work; the goal is not to force every problem through the same template.
V
Verify
Trace the process and the numbers back to their source.
R
Reduce
Remove the step, field, report, or handoff that adds no value.
B
Build
Make the smallest durable system that solves the remaining problem.
M
Measure
Confirm the change held and the team can own what remains.
What we do
Diagnosis first.
Then the build.
A useful system starts with the right diagnosis. We map the work, test the assumptions, and build only what the business needs.
Diagnose
Operations & process audits
We map how work actually flows — not the org chart version — and find the bottleneck, the double-entry, the report nobody reads. Often the metric everyone trusts is the thing that’s lying.
Find the breakBuild
Automation & internal tools
Python automation, data pipelines, and internal web apps that replace manual work and remain maintainable after launch.
Build the fixLead
Fractional tech & ops leadership
Technology planning, vendor decisions, data infrastructure, and delivery discipline for teams that need experienced ownership without a full-time hire.
Own the systemSelected work
The problem.
The decision.
The result.
Client and employer details stay private. The shape of the problem — and what changed — doesn’t have to.
A closing pipeline the whole team runs on
Problem
Deal-closing status lived in spreadsheets and inboxes; no one had a single trustworthy view of what was closing and when.
Build
A full-stack web app (Flask + React) with role-based sign-in that tracks every deal through closing, generates the builder and lender documents, and syncs nightly from the system of record.
Status
In daily use across the team — one source of truth for the pipeline, with the document busywork gone.
Cutting time-to-start in half — before automating anything
Problem
Starting a house ran through a slow, error-prone process that every downstream team inherited.
Approach
Audited the process end to end and fixed the strategy first — sequencing, ownership, and what could be removed — before writing a line of automation.
Result
Cut the time to start a house roughly in half while improving accuracy — which paid off again in every process downstream.
Writing
Drafting.
Notes on technology, operations, and the occasional detour through beer, sports, and a winding career — published on Substack, collected here.
A Spin-Off of a Spin-OffSubstack
Drafting, a work-in-progressHazy AIPASubstack
Technology Lessons from the BrewhouseThe SEO that still works when half of search is a robot
Five things that move rankings in 2026 — and the one metric that’s lying to youPut it on the table
Got a process
that fights you
every day?
Advisory engagements, audits, and build work — plus the occasional talk or workshop. If something fights you every day, that’s usually where the leverage is.
Start a conversation ↗