Operational systems for the next industrial age.

Problem

Jobs, due dates, and status lived in spreadsheets, on whiteboards, and in people’s heads, so every handoff needed a conversation.

System

One board to plan the week against real capacity, see where every job stands, send problems to the right person, and refresh the numbers each morning without anyone pulling them.

Result

Coordination moved from conversations to a shared board. The office plans from the same view the floor works from, and the manager is no longer the bottleneck.

My roleProblem framing · Workflow and product design · Architecture · Implementation · Testing and rollout

Problem

Answering that meant pulling sales, stock, and margin out of several systems by hand, and the answer changed depending on who did the pulling.

System

A review tool that scores every product on sales velocity, sell-through, and stock on hand, runs the heavy analysis overnight, and puts each decision in front of the right person to approve.

Result

Reviews happen on a schedule with the same evidence every time, instead of whenever someone has a free afternoon.

My roleDecision model · Workflow and UX · Data architecture · Cloud implementation · Production hardening

Problem

Every new product meant reading mockups and spec sheets, then typing the same details into the store, variant by variant.

System

Vision models read the mockups and spec sheets, fixed rules fill in whatever should never be guessed, and the result is a complete, validated draft record. A person checks each one before anything reaches the store.

Result

Setup turned from a chore into a review. People spend their time on the judgment calls, and nothing publishes without approval.

My roleWorkflow model · Product and UX · AI and rules design · API architecture · Acceptance and verification

Problem

A stock report lists everything at zero without saying which gaps are costing sales.

System

Each day a model estimates the sales lost to every empty item from its own history, then ranks the gaps biggest first, with every estimate traceable.

Result

The restock conversation starts with the biggest losses instead of the longest list.

My roleBusiness logic · Forecasting model · Data architecture · Decision UX · Reliability and boundaries