Selected systems

Work that makes the operation easier to run.

I build where the business problem is consequential and the handoff between operators, analysts, and technologists is usually weakest.

01Operating platform

ArborPlus

An internal operating platform connecting sales, scheduling, production, reporting, customer communication, and field-service workflows at A Plus Tree.

  • Product leadership
  • Business systems
  • Data platform
  • Workflow design

Context

A multi-entity service business creates complexity quickly: crews, territories, equipment, proposals, production, client communication, and financial accountability all have to move together.

What I built

I own the product and operating layer behind ArborPlus—translating leadership questions and field constraints into reporting, workflows, integrations, permissions, and product improvements.

Why it matters

The strongest internal software does more than digitize forms. It makes the company easier to see, easier to coordinate, and easier to improve.

Turned fragmented operating work into one practical system that leaders and field teams can use every day.
02AI work system

Loomfield

A self-hosted mission-control system that lets different AI agents work from the same durable context, project structure, and human-controlled rules.

  • AI systems
  • Product architecture
  • Knowledge systems
  • Human-in-the-loop design

Context

AI tools are powerful in the moment, but the useful context, decisions, and procedures they produce usually disappear into separate conversations.

What I built

Loomfield gives agents a shared brain, a project model, controlled read/write gateways, and a session workbench for launching, steering, and reviewing work across tools.

Why it matters

The value is not another chatbot. It is an operating layer where the work can become more reusable, more trustworthy, and less dependent on any one model vendor.

Moves AI work from isolated chats toward connected, inspectable systems that can learn without escaping human control.
03Decision systems

Operations intelligence

Forecasting, capacity, backlog, pricing, margin, and production systems built around the questions leaders actually need answered.

  • Executive reporting
  • Forecasting
  • SQL & Python
  • Operational judgment

Context

Most reporting stacks answer what happened. Operators need to know what is changing, what is stuck, what will happen next, and where intervention matters.

What I built

I design the metric, data, workflow, and review cadence together—then build the reporting and automation needed to keep the answer current.

Why it matters

A dashboard is only valuable when it changes a decision. The operating system includes the numbers, the definitions, the accountability, and the next action.

Replaced recurring manual analysis with durable decision tools and a clearer operating cadence.
Working range

From leadership question to live system.

The work moves comfortably across operating design, product management, data modeling, prototyping, implementation, adoption, and executive communication.

Operate

Business operations, field-service workflows, accountability, change management

Model

KPIs, forecasting, capacity, backlog, margin, pricing, process definitions

Build

Internal tools, SQL, Python, APIs, integrations, AI automation

Lead

Product direction, executive reporting, prioritization, cross-functional delivery