I work where operations, support, ecommerce, and code overlap.
The value is not just wiring APIs together. It is knowing when to preserve routing, when to keep a human in the loop, when data is too provisional to summarize, and how to make a system understandable after it ships.
What I am good at
I build internal tools and automations for teams that already have real workflows, real edge cases, and real consequences when a background job silently fails.
How I work
I prefer source-backed audits, dry-run modes, explicit deployment notes, and handoff docs over impressive but fragile demos.
Where I fit
Ecommerce operators, support ops leads, founders, and SMB teams using Shopify, Front, Slack, Aircall, Zapier, Railway, spreadsheets, and custom scripts.
Why this work fits me
I like the unglamorous parts that make software trustworthy.
Systems shipped
Returns dashboards, Shopify-to-support enrichment, guarded AI drafting, monthly support-load reporting, Slack-shaped summaries, and diagnostic tooling.
Operating contexts
Ecommerce, support operations, reporting pipelines, Zapier migrations, Front workflows, Aircall data, Railway deploys, spreadsheets, and custom scripts.
What I care about
Silent failures are expensive because nobody knows they happened. I build toward visible state, recoverable workflows, and handoffs a real team can understand.
Bring me the workflow that keeps breaking.
Pay for a diagnostic when the pain is clear, or start small with a free scan.