Selected systems · automation · product work
I turn ambiguous problems into working systems.
I work across the gap between business process, product design and implementation: mapping what needs to happen, structuring the information, connecting the tools and iterating until people can actually use it.
What this portfolio proves
Four projects, four different forms of systems thinking.
Turning a live manual business process into a connected operating workflow at meaningful scale.
Combining messy external data, custom scoring and real user state to support decisions.
Coordinating many devices, shared state, private state, identity and game progression.
Encoding ownership, permissions, valid transitions, notifications and history into internal software.
Selected work
The projects that best explain how I think.
Each case study focuses on the difficult part of the problem—not an exhaustive list of screens.
B2B Operations Transformation
Rebuilt a fragmented order-to-fulfilment process into a connected workflow spanning web intake, CRM, documents, shipping, inventory and analytics.
Decision engine · Data productDraft9 Fantasy Basketball
A custom 9-category decision engine that normalizes multiple data sources, models roster fit and simulates draft, trade and waiver moves against real ESPN league state.
Realtime multiplayer · Consumer productListcheta
A phone-first multiplayer state machine with room synchronization, private master-device state, profiles, persistent statistics and bilingual gameplay.
Internal product · Sales operationsLeadFlow
A role-aware operating system that moves prospects through qualification, production, calls, invoicing, payment and handover with explicit workflow guardrails.
Working pattern
I am most useful when the brief is incomplete.
Understand the real process
Find the actual decisions, handoffs and failure points—not just the stated feature request.
Make the logic explicit
Define data, states, ownership and rules so the system has a coherent shape before it grows.
Connect the moving parts
Implement interfaces, APIs, automations, integrations, persistence and supporting logic.
Use it against reality
Test real behavior, expose edge cases and improve the workflow rather than defending the first version.