Founder · Systems Builder · Technologist
I do not build apps. I build technology stacks.
From embedded hardware and cloud infrastructure to machine learning and real-time financial systems, I work across the entire stack when the problem requires it.
I solve problems with systems — simple where simple works, sophisticated where it has to be. My companies are structured the same way I build: the intelligence that decides what data means is kept separate from the platform that turns it into something a person can use.
Technology & Intelligence
Three entities, each with a distinct job. The intelligence layer is kept separate from the products it powers, so the models are an asset in their own right rather than a feature of one application.
The technology foundation. Owns the core technology and intellectual property, develops the foundational software, holds the reusable models and systems, and sets strategic direction for the companies beneath it.
The intelligence company. It determines what the data means — predictive models, signal detection, market intelligence, and decision-support systems. Its technology can power multiple products; the intelligence itself stays a separate asset.
The commercial operating company. It takes intelligence and turns it into a usable product and workflow — the platform, the accounts, the automation, the broker connectivity, and everything a customer actually touches.
The end-user product: an intelligent trading platform powered by Clickvision Intelligence. Market data, options analytics, predictive models, alerts, automation, and broker connectivity in one workflow.
Research & Projects
Technology work that sits outside the operating companies — some of it heading somewhere, some of it built because the problem was interesting.
An ESP32-based physical aviation information system: custom electronics, PCB design, addressable LEDs, displays, and live aviation weather on a map you can read from across the room.
Cockpit technology concepts: ATIS and ATC transcription, voice interaction, aviation data visualization, and Bluetooth connectivity — all aimed at reducing pilot workload rather than adding another screen to scan.
SQL Server and database architecture, distributed and remote infrastructure, APIs, cloud deployment, production troubleshooting, and the automation that removes the work nobody should be doing by hand.
Embedded and connected devices — the firmware, the boards, and the data pipelines that make physical things useful.
Capabilities
The chain, end to end: data acquisition → APIs → databases → processing → intelligence → machine learning → decision logic → automation → interface → notifications → cloud infrastructure → production operations.
Designing systems from the data layer through intelligence, application logic, automation, and execution. Breaking complicated problems into modular components that can evolve independently.
Pipelines that capture, normalize, enrich, store, and deliver data reliably. Real-time feeds, structured databases, APIs, event-driven workflows, and the operational problems that appear between them.
Predictive systems from raw data through feature engineering, model training, evaluation, deployment, and feedback loops. Intelligence built as a reusable layer rather than embedded inside a single application.
Options-market analytics, market structure, gamma exposure, volume and open-interest analysis, contract selection, predictive opportunity modeling, real-time alerts, and broker integrations.
Python, SQL, REST APIs, authentication and token management, asynchronous workflows, automation, integrations, backend services, and production systems.
Cloud Run, containers and Docker, distributed systems, database infrastructure, remote systems administration, deployment pipelines, production troubleshooting, and service reliability.
Replacing repetitive human workflows with systems that capture information, make decisions, trigger actions, communicate results, and recover from predictable failures.
ESP32 development, firmware, addressable LEDs, displays, custom PCB design, power systems, hardware prototyping, PCBA, and manufacturing workflows.
Applying aviation operational experience to software: data visualization, human-machine interfaces, situational awareness, and cockpit automation.
The part that happens after the demo works — authentication failures, expired tokens, dead feeds, database inconsistencies, deployment problems, network issues, monitoring, recovery, and making a system dependable enough for someone else to rely on.
From problem to production
Understand the real workflow before designing the solution.
Separate the problem into data, intelligence, platform, automation, and execution.
Prototype quickly, validate assumptions, and get something working.
Instrument the system. If it cannot be measured, it cannot be improved.
Remove manual dependencies and build the feedback loops.
Find the failures that only appear in production.
Put it in front of real users and let reality improve the design.
How I work
I build systems that run without me. A platform that needs a human watching it is not a platform, it is a job — so the work goes into the parts nobody sees: the capture that never misses a day, the labeling that stays honest, the retraining loop that closes by itself.
I care most about the boring layer. Most systems fail at the boundaries — a stale price, a silent timeout, a feed that dies while still looking alive. Aviation makes you fluent in that category of failure, because there it is the one that kills you.
And I ship. Running programs for other people taught me that a working thing in front of a real user teaches you more in a week than a year of planning does.
Why I build this way
Thirteen years of Army aviation taught me systems thinking before I ever called it engineering. Aircraft, crews, communications, mission planning, logistics, weather, intelligence, and command decisions all had to work together. Failure rarely came from one component; it came from the boundary between them.
That experience shaped how I build software today. I look for dependencies, failure modes, bottlenecks, missing feedback loops, and the places where a system can appear healthy while quietly failing underneath.
I flew UH-60s, ran the Air Mission Planning System for the 42nd Infantry Division, and built the automated system that managed the movement of its aviation assets. New York Medal of Valor, Army Commendation Medal.
Full work history and education on LinkedIn. View profile →