Why I’m Building OmniMint
By Matthew Andrews ·
I began trading in 2020. At first, what drew me in was the market itself: watching prices move, making decisions, and seeing those decisions produce results. Over time, I became increasingly interested in the process behind those decisions.
What was I doing repeatedly? Which parts depended on my judgment, and which parts could I express in code? Could I build a system that fit around the other responsibilities in my life?
Those questions eventually led me to OmniMint. Getting there brought together experiences that, for a long time, had felt like separate chapters.
Building Around the Life I Had
While serving in the Army, I was also working toward my degree and building a rental business. My schedule was demanding, and trading added another activity that needed my attention.
I started developing algorithms and automating parts of my trading workflow. I wanted to follow the approaches I was developing without having to step away from work to check the market throughout the day.
That gave programming a very personal purpose. I could take something that was difficult to manage manually, break it into smaller decisions, and build a process around it.
As I explored additional strategies, I kept finding more work around the trading itself. Different assets meant different platforms. Each platform introduced another workflow to manage.
I began wondering how much of that fragmentation was necessary—and what a more connected experience could look like.
A Question That Changed the Scope
Then people began asking whether they could use my algorithms in their own accounts.
It sounded like a straightforward request. Researching what it would involve showed me how much more there was to build.
An algorithm running for my own use was only one piece. Supporting someone else would require an organization around the work, secure connections, appropriate permissions, and a reliable way to manage those relationships.
The question grew from “How do I automate my own workflow?” into “What would it take to build something other people could use responsibly?”
That became the starting point for OmniMint.
What Leading Teams Taught Me
My professional experience was pushing me toward similar questions.
After leaving the military, I moved into technical leadership. I worked with teams delivering complex applications, and I became increasingly interested in the processes surrounding their work.
Repeated tasks, unnecessary handoffs, and recurring mistakes could consume a surprising amount of time. In one role, I identified opportunities for automation within my first sixty days. Those improvements produced estimated annual labor savings of more than $250,000.
That experience reinforced something I had already begun learning through programming: improving the process could matter as much as improving any individual task within it.
I wanted to bring that way of thinking into my own work. If a system required people to keep correcting the same problem, I wanted to understand why—and what would need to change.
Bringing the Research Into the Work
My education gave me another way to explore those questions.
After completing my Executive MBA at UTSA, I continued studying software engineering at St. Mary’s University. My coursework and specialization have focused on agentic systems and workflow optimization.
My capstone and planned research explore multi-agent architectures that can diagnose mistakes, learn from them, and improve how they work. The question I keep returning to is whether a workflow can use its own diagnosis to avoid repeating a mistake.
That remains a research goal. Building it requires more than an appealing idea; it requires evidence that the system can recognize a problem, make a useful correction, and perform better afterward.
This work has helped shape the foundations of OmniMint and the questions I want to pursue as I build it.
Why This Matters to Me
My path here has included sales, military service, real estate, technical leadership, and returning to school more than once.
Across those experiences, I kept finding myself drawn to understanding how things worked and looking for ways to improve them. Trading gave me a problem I cared about personally. Programming gave me a way to begin solving it. Leadership and education helped me see the broader work required.
OmniMint grew out of that combination.
I’m building it because I want to explore what a more connected trading experience can become, and because I want to put years of learning into something of my own.
This blog will be a place to share that process: the decisions, the lessons, and the questions I’m still working through.