Workflow tools, shown clearly
I build software that fixes real-world workflow problems.
From cabinet production to internal tooling, I design and build applications that reduce manual work, cut down errors, and improve throughput.
My background is in production environments where inefficiency has a real cost: wasted material, lost time, and bottlenecks between departments. The tools here were built to deal with those problems directly.
Site direction
Portfolio first
This site is here to show the work clearly: what the tools do, who they help, and why they were built the way they were.
What this site is for
A portfolio of practical software, not a startup pitch.
The point of this site is simple: instead of trying to explain these tools from memory in an interview, I can show the problem, the solution, the demo, and the reasoning behind it.
Tool Pages
Each tool gets a straight explanation of the problem it solves, how it works, and where it fits.
Demo Media
Short videos and screenshots can sit next to the write-up without needing backend infrastructure.
Case Studies
Longer write-ups can dig into constraints, adoption, UI tradeoffs, and implementation decisions.
Featured tool
Rover
A Windows desktop utility for moving CAM and CNC jobs between machines when tool names do not line up cleanly.
Rover scans supported files, pulls out unique tool identifiers, and lets the user map old names to new ones in a simple table. Those mappings can be saved as JSON and reused across similar jobs.
Instead of editing files one by one, the operator can review the mapping once and apply it across the whole file set. It is a small tool, but it removes a lot of repetitive cleanup.
Who it is for
Shops that need to move jobs between machines without manually fixing every mismatched tool reference.
Safe workflow
Dry run mode previews changes, optional .bak backups protect the originals, and mappings can be saved and reused.
Supported formats
.cid, .bpp, and common G-code style formats including .tap, .nc, .cnc, and .gcode.
Select a folder
Point Rover at a job folder and optionally include subfolders.
Review detected tools
The app gathers unique identifiers and shows them in an old name to new name mapping table.
Preview safely
Use dry run and backups before writing any changes across the file set.
Apply in bulk
Reuse saved JSON mappings whenever similar conversions come back again.
Deeper case study
Sanitized workflow suite
Beyond individual tools, I am building a broader workflow suite meant to connect multiple parts of the production pipeline. That is the project on this site that deserves the deeper breakdown.
It includes things like cut optimization tools, cabinet dimension calculators, file conversion utilities, and internal dashboards or tracking systems. The long-term goal is a cleaner flow of data between departments, with less friction and less wasted effort.
One of the more important design choices was visual familiarity. Parts of the interface were intentionally kept close to the ERP users already knew, which reduced cognitive switching and made adoption easier.
Suite overview
Internal application demo
This video shows a sanitized copy of the internal application. Customer data and company branding were removed before it was added to the portfolio.
Workflow continuity across tools
The suite connects department tools into one operational flow, so handoffs stay clear and data remains consistent.
Measured process improvement
The implementation targets slower, repetitive, and error-prone steps by standardizing outputs and reducing manual rework.
ERP-aligned interface strategy
The ERP-style visual language was intentional to reduce training time, lower transition cost, and improve adoption on the floor.
Module spotlight
Cut department full walkthrough
This narrated cut module video goes deeper than the suite overview. It shows how the department landing page is used, what gets generated from Quick Generate, and how the paperwork supports the day-to-day cut workflow.
The walkthrough covers the MDB export path for machine-driven components, the workbook views used on the floor, grouped hand-cut reporting, end-of-day material reporting, label printing, restock handling, PO filtering, and department-specific diagnostics.
Operational flow coverage
The walkthrough covers the flow from landing page inputs to generated files and department paperwork.
Production impact
The module ties together CNC-bound outputs, hand-cut paperwork, reporting, and inventory-aware decisions in one operator workflow.
Full walkthrough
Cut module narrated demo
This is the longer version for anyone who wants the details. It is better as a second click after the suite overview, not the first thing a viewer has to commit to.
Short module demos
Additional modules and utilities in short, focused demos.
Each clip highlights scope, operator interaction, and output so the workflow can be evaluated quickly without a long walkthrough.
Short module demo
Custom module
The custom module is built to take a large amount of data and make it easier to work with. It gives the floor operator quick filters for frames, doors, drawers, headers, and other components, along with grouping and firm-date tracking.
It also includes style and color management, department-specific label printing, and a report manager that helps calculate panel sizes, styles, and rail cuts before outputting the paperwork used by the department.
Suite utility demo
Wood usage calculator
This utility is part of the same suite, but it is not tied to a single department screen. It accepts direct user input or CSV order-list uploads and uses a quick-reference catalog of known products.
The generated report includes dimensions, material usage, optional material pricing and operator cost estimates, expected machine runtime, and daily capacity estimates driven by administrator-defined variables.
Reports can be exported to PDF or CSV. If an order includes an unknown product, that miss is logged and forwarded to the administrator application for follow-up.
Suite prototype demo
Warehouse mapper and inventory verification
This prototype models warehouse structure first: areas, aisles, racks, and storage locations. From that structure, the system generates a visual layout and assigns standardized location IDs so inventory can be mapped consistently.
It is intentionally shown as a prototype: functional in its current state, with a basic UI that is still unrefined.
Setup supports manual entry and CSV import, and each bay can store either a single product or mixed products with independent quantities. The bay-level view and aggregated overview make it easier to see where products are stored and how inventory is distributed.
Search returns all matching locations and quantities. During picking, users can confirm expected counts or run blind counts where expected values are hidden, which improves unbiased verification and catches discrepancies in normal workflow.
Suite control center
Administrator application
This application is the central control layer for the department tools. It lets management define rules for both the Cut and Custom workflows, including logic used by the wood usage calculator.
Instead of hardcoding behavior in each tool, SQL queries and processing rules can be updated centrally, so workflow changes can be deployed without modifying every core program.
Administrators can launch department tools, review databases, and manage backups, updates, and rollbacks with password encryption built in. Bug reports and feature requests flow into a work queue that highlights missing items and construction issues for production follow-up.
Secondary projects
Some tools are better shown through structure than visuals.
Not everything here is a video-first project. Some of the more useful work is developer tooling: utilities that make handoff, planning, and repeatable AI-assisted workflows easier to manage.
Developer tooling
AI Prime
AI Prime is a repo-local CLI for structured AI collaboration in software projects. It scaffolds a repeatable working surface for durable project truth, session handoff state, append-only logs, and contract-style planning.
It also includes a local contract wizard and validation flow, but it does not depend on external AI APIs. The value is in making multi-session AI work more consistent, inspectable, and easier to hand off between agents.
View AI Prime repositoryPublic secondary project showing developer-tooling range, not a primary showcase piece.
Experimental R&D
AI Gamer
AI Gamer is an early experimental system focused on multi-domain meta-learning and transferable reasoning patterns. It was built as a research-style project to test how learned inference behavior might transfer across domains.
This is intentionally presented as an early app: functionally interesting, but not positioned as a polished production product. It belongs in the portfolio as exploratory engineering work and technical range.
View AI Gamer repositoryAbout the work
Most of my work sits at the intersection of manufacturing and software.
I tend to work on problems where inefficiency shows up in very practical ways: slower output, repetitive manual work, unnecessary mistakes, or handoff issues between departments.
That usually means building tools that are clear, useful, and easy to adopt inside environments that already have established systems and habits.
What to expect here
Real tools, real constraints, and case studies that explain why the implementation looks the way it does.
Portfolio structure
Tools are organized as concise demos with deeper case-study coverage where the workflow and implementation details matter most.