My career has progressed from field project management to enterprise program delivery and ultimately to directing a configuration services division. Throughout that progression, I kept encountering the same types of problems: information spread across disconnected spreadsheets, reporting that required hours of manual work, inconsistent handoffs, and important relationships hidden inside processes that only a few people fully understood.
Rather than continuing to manage around those limitations, I began building solutions for them. Today, I combine operational leadership with hands-on systems development. I map workflows, identify the data relationships behind them, and build dashboards, automations, and internal tools that help teams understand what is happening and what needs attention.
The common thread throughout my work is curiosity. I enjoy taking complicated systems apart, understanding why they function the way they do, and finding better ways to connect the pieces.
Outside of work I am usually thinking about systems in a different sense: golf, history, and what makes complex things hold together over time.
Technology has interested me for as long as I can remember. When I was eight years old, I taught myself to enter programs on a TI 99/4A — line by line from the manual, with no way to save anything and no one to ask for help. Every bug was mine to find and fix alone. Around the same time I was taking apart electronics to understand how they worked. Those experiences taught me something that stayed: complicated systems become less intimidating once you understand the relationships between their parts.
That early curiosity shapes how I approach operations today. I want to understand how a system works, why it behaves the way it does, and how its parts can be reorganized into something better.
I use AI-assisted development as an execution accelerator within a structured systems design process. I define the operational problem, map the workflow and data relationships, establish requirements, direct the architecture, validate the outputs, and remain accountable for the finished system.
AI-assisted development allows me to create at a pace that more closely matches the speed at which I understand and process complex systems. The operational knowledge, design, and accountability remain mine.
I approach technology from an operational leadership perspective — understanding the business problem, mapping the process and data behind it, and then directing the build. Tools accelerate execution. They don't replace the understanding that makes the work meaningful.
In 2026, I founded CommitState, an independent technology and operations consulting practice focused on practical systems, workflow automation, reporting, integration, and custom software solutions. The practice complements my full-time leadership experience by providing an additional environment for developing operational systems and solving real business problems.
CommitState follows the Resolve · Commit · Deploy method: understand the current state completely before designing a solution, and design completely before building.
Work spanning a production system running in a live operational environment, interactive technical demos, and a client-facing application. Each shows a different dimension of how I approach operational systems design.
Leadership had no unified view of operations — project status, production, inventory, billing, and revenue existed in disconnected spreadsheets requiring hours of manual assembly.
Designer & Builder · eBryIT, Inc. · 75% reduction in reporting effort
View Case Study →Relational data model connecting projects, devices, revenue, billing, and inventory into a single operational view. Demonstrates the data architecture behind enterprise deployment reporting.
Portfolio Demo · Interactive relational data model
View Case Study →State-machine lifecycle tracking with immutable audit records, dwell time analysis, and technician-level production performance reporting — the same reporting layer automated at eBryIT.
Portfolio Demo · 300K+ devices annually
View Case Study →Full business management platform built for a small business client. Covers the complete estimate-to-payment workflow: estimate creation with status tracking, invoice generation, client CRM, a 100+ item pricing catalog organized by category, room-based estimating, payment logging, outstanding balance tracking, and business reporting — all running in the browser with no backend infrastructure required.
Key advantages: Zero hosting cost, works offline, all data stays local to the client, no subscription fees, purpose-built around how the business actually estimates and invoices work.
Client Project · IndexedDB · HTML/CSS/JS · Proprietary — not publicly available
I use AI-assisted development as an accelerator for turning operational knowledge, workflow requirements, and system designs into practical tools. The business logic, requirements, architecture, validation, and accountability remain grounded in my operational experience.
Turn production, backlog, billing, and project data into daily or weekly summaries for leadership. Replace manual reporting with structured, AI-generated briefings that highlight performance, risks, and recommended actions.
Classify inbound emails, customer requests, project updates, and attachments into structured workflows. Reduce manual triage, ensure consistent routing, and build a traceable intake layer across high-volume operations.
Identify stalled work, aging backlog, quality issues, missing data, delayed shipments, and billing gaps before they become escalations. Surface anomalies automatically so teams can act rather than audit.
Convert operational documentation into a searchable assistant for technicians, leads, managers, and onboarding. Reduce reliance on tribal knowledge and improve consistency across teams and shifts.
Use structured data to track vendor performance, project status, SLA risk, and delivery constraints. Build visibility into dependencies and risks that are typically buried in spreadsheets or email threads.
Bring structure and traceability to IT asset disposition workflows. Track devices from decommission through data wipe, grading, remarketing, or destruction, with audit records, chain-of-custody visibility, and reporting that supports compliance and vendor accountability across the full ITAD lifecycle.
Best aligned with Director-level roles in operations, service delivery, deployment services, and business systems — and Head of Operations roles where operational leadership and systems-building are the same job.
I believe strong operations depend on clear ownership, useful information, practical systems, and teams that understand how their work connects to the larger outcome. My role as a leader is to create that clarity, remove barriers, build accountability, and give people the tools they need to succeed.
Undergraduate Coursework in Computer Science
Formal academics gave way to a decade of applied practice — designing and building operational systems, directing enterprise technology delivery, and developing the tools described throughout this site.