Software / Systems Engineer

I build the software
that connects your
systems together.

Shopify, ERPs, inventory tools, internal software, marketplaces — I build the pipes between them, and the automation that takes manual work off your team's plate. I'm not an ops person; I'm the developer ops teams call when the systems side is the bottleneck.

Three problems. Solved properly.

Most businesses I talk to have at least one of these. If any of them sound familiar, that's where we start.

01

Your systems aren't talking to each other

Shopify, Amazon, your ERP, your WMS, your BI tool — most of the manual work in an operation happens in the gaps between systems like these. I build the connections between them, so data moves on its own instead of someone moving it by hand.

  • Get inventory, orders, and reporting feeding into one place automatically
  • Replace manual data entry between systems with a real integration
  • Turn separate tools into one connected pipeline
  • Know what's happening in the business without pulling it together by hand
Automated 90% of a $2.5M/yr ecommerce business — solo, from scratch
02

Your internal tools are slowing people down

Internal tooling is chronically under-built. Teams end up waiting on a developer for things they should be able to do themselves, or working around a system that was never quite finished. I build the tool that closes that gap.

  • Let your team do things themselves instead of waiting on someone else
  • Replace the clunky workaround your team has been tolerating for years
  • Get rid of the approval bottlenecks that slow every decision down
  • Fix the broken internal system everyone complains about but nobody touches
Built an internal platform adopted by 100+ employees at Amazon
03

Your cloud bill is too high

Most businesses are overpaying for cloud infrastructure and don't have a clear picture of why. I look at what's actually running, find where the waste is, and make targeted changes that bring the monthly bill down without disrupting anything that works.

  • Find out exactly what you're paying for and why
  • Cut the tools and services you're running but don't need
  • Make changes that shrink the bill without breaking anything
  • Set up alerts so costs never creep up unnoticed again
Delivered >$100k+ in annual savings across Amazon and Paychex

Work that moved the needle

Real outcomes at Amazon, Paychex, and a business I built myself from scratch.

>$100k+
Cost Reduction
Hundreds of thousands saved in annual cloud spend

Identified waste across cloud infrastructure and third-party tooling at Amazon and Paychex. Eliminated redundant logging that was inflating Splunk costs by 30%, and cut cloud resource usage through architecture changes. The savings repeat every month with no ongoing effort.

$2.5M
Automation
Built a $2.5M/yr business that ran itself

Designed and built software that operated an eBay dropshipping business almost entirely without human involvement — automatically placing orders with retailers, syncing inventory, adjusting prices, calculating margins, and managing shipping. 90% of operations were handled by code over 5 years and $2.5M in revenue.

100+
Internal Ops
Self-service platform adopted across Amazon teams

Built an internal tool that let engineers and non-technical stakeholders run their own pre-release validation — without waiting on a developer. Over 100 people across teams adopted it. What used to take hours of back-and-forth now takes minutes.

300M+
Internal Ops
Massive data migration — completed with zero downtime

Planned and executed the migration of 300M+ records from a legacy system to a modern data store. Built automated validation at every step to catch any issue before it became a problem. Nothing broke. Nothing was lost. The product launched on schedule.

Internal Ops
Modernized a legacy API that partners kept complaining about

Inherited underperforming API endpoints at Paychex that were causing recurring support complaints from third-party partners. Tracked down the root causes, rebuilt the slow and fragile paths, and eliminated the failures. Partners stopped complaining. The team stopped firefighting.

How it works

It usually starts with a conversation, not a proposal. I ask questions about what's actually happening day to day, and if there's something worth fixing, I'll look at the systems or workflow involved and come back with a clear plan and a price before any work starts. From there, I either build it myself or hand your team a plan they can run with — whichever makes more sense.

Got something
manual or disconnected?

Tell me what it is. If it's something I can help with I'll say so, and if it's not I'll tell you that too — either way, you'll get a straight answer.