I'm not here to ship features.
I'm here to remove frustration.

Every Shopify store has people behind it. Someone in operations who manually exports orders every morning. Someone in finance cross-checking numbers between two systems that should talk to each other. Someone on the team who knows exactly what's broken but has nobody to hand the ticket to.

That's where I start. Not with the tech stack, with the frustration. If I can find the thing that costs someone an hour a day and make it disappear, everything downstream gets better: the person, the team, the business. In that order.

How I approach the work

I work with what you already have. Before introducing anything new, I look at the tools your clients are already paying for, the apps, the platforms, the subscriptions, and ask how far we can get with those. New monthly costs only come in when there's no other way.

Shopify is where most of this happens. Every store I work on has a different story, a different pain, a different team. That variety is exactly why I like it. You don't solve the same problem twice.

I've been doing this for real clients, on live stores and websites, for years. Wonderful Dental. Zoe Rowyn Bridal. E-Flight Academy. MKB Digiwerkplaats. Match-IT. Not experiments, production, with real people on the other end waiting for it to work.

The tools I use

Stack

  • Shopify FlowNative triggers, tag-based segmentation, order workflows, automation that stays inside Shopify without a third-party dependency
  • ZapierMulti-step flows, custom code steps, cross-app integrations, built around the tools your client already pays for
  • Make.comCountdown timers, custom HTTP integrations, routers and iterators, for branching logic Zapier can't handle cleanly
  • Custom code automationsWhen no-code options run out, custom integrations and app development to connect systems the existing stack can't bridge

What I solve

  • Klaviyo flows that broke after a tag or metafield change
  • ShipStation not receiving correct order data from Shopify
  • Shopify Flow triggers firing at the wrong time, or not at all
  • Two fulfilment apps that need to route orders without stepping on each other
  • Manual ops work that should have been automated months ago

What I'm not, is the dev who needs a senior to explain the ticket twice.

What I am, is the dev who comes back the next day with it fixed, and can tell you exactly what broke and why.

Send me the tickets that keep sitting there.

Send me three tickets that have been sitting for over a month. I'll tell you which one I can solve this week, which ones take two weeks, and which I'd leave for someone else - and why.

+ Book a backlog audit

YOU GOT NOTHING TO LOSE.