I automate the boring stuff so your team stops losing hours to spreadsheets

Most engineers start their story with a "Hello World" script. Mine starts with a $2 million liability.

In 2019, while working in Finance at Ford Motor Company, I noticed a costly flaw in our process. We had interest rate spreads that needed daily updates across dozens of regions and thousands of contracts. This was during the end of the zero interest rate era, and we held our breaths each time the Fed announced a meeting.

Our manual lead time? 30 days.

I did the math: if the Fed hiked rates after each meeting, that 30-day lag could cost us roughly $2 million annually.

I proposed an automated fix. The response? "We don't have the technical resources or skills to do that."

So I built what I could myself. Cut that 30-day lead time down to 7 days.

That's when it clicked for me.

Code isn't just for engineers. It's a business tool. I build systems that solve expensive problems and give people their time back.

I'm a tech optimist and a problem-spotter. The biggest wins don't come from "Big AI" magic wands. They come from fixing the friction points that compound over time. The "death by a thousand cuts" issues. Small manual tasks that add up to massive time sinks.

If your team spends 20% of their week on repetitive clicks or manually importing contacts, you're not just losing time. You're losing the chance to focus on what actually matters.

I've inherited too many systems where the only documentation was "Steve's memory." And Steve quit. Everything I build is documented in the code itself. If I leave, the logic stays behind.

I pick reliability over trendiness. The tools I use aren't flashy, but they scale without the headaches. You only pay for what you use. No expensive servers sitting idle at 3 AM.

I spent the first half of my career in Sales and Business Development, moving through 7 states and 13 territories for Ford. I've been the "Field Rep" and I've been the "Lead Engineer."

That's the difference.

Most developers look at a Jira ticket and miss the bigger picture. There's a joke I've seen play out more times than I'd like:

An engineer designs a beautiful deck that meets all structural and safety codes. Except it has no stairs and isn't attached to the house.

When asked why, the engineer replies: "Well, that wasn't in the requirements."

I look at business processes differently. I've lived the pain of operations and manual data entry. I can tie technical architecture directly to business value. I speak Finance, I speak Sales, and I speak Python.

I've lived in Dallas, Atlanta, Denver, Nashville, Boston, Tampa, and now Detroit. I'm a generalist by choice. I can drop into any legacy system, identify the bottleneck, and ship the fix. The soundtrack? Creed and Nickelback are fine by me.